the Opportunity JeffreyM Consulting is partnering with a fast-growing, Y Combinator-backed AI startup to hire a Full Stack Software Engineer for its New York City engineering team. The company is building an AI-native pl…
Software Engineer jobs in New York, NY
Software engineers design, build, and maintain the applications and systems behind modern products. The work spans writing code, reviewing designs, and keeping software reliable as it grows.
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
Open software engineer roles
12 shown of 5,819 · sorted by freshness
About the Team Come help us build and develop tools serving hundreds of engineers internally! We’re looking for a Fullstack Software Engineer to join our Developer Insights team. About the Role Our mission is to improve…
About the Team and Role: Pinecone is looking for a full-stack engineer to bring a new level of visibility, control, and trust to our... ...technical guidance. You should have: At least 2 years of software engineering exp…
rigorous problem-solving, and obsessive attention to detail. Our engineering team is elite, our lawyers ship code every day, and we are... ...our products. We are predominantly looking for full-stack software engineers,…
on foot or in a vehicle, our technology is an ironman suit for engineers, linemen, and vegetation crews: same worker, same boots on the... ...cutting edge hardware, sensors (LiDAR, camera, etc…), AI and software designed…
Full-Stack Software Engineer Company Overview The built world generates more data than almost any other industry. Almost none of it is being used. Rentana is changing that, building the AI copilot for real estate that di…
of compassion, collaboration, and momentum, and we are just getting started. The Role We're looking for a Full-Stack Software Engineer to join our engineering team and help build the technical foundation of Coral Care's…
As a member of our team, you will collaborate with world-class engineers, architects, and visionaries, and work across organizational... ...infrastructure, to the core of the network itself. As a Full Stack Software Engi…
based on impact Position Overview As an early full-stack engineer, you’ll help build Conductor’s core application: a user-facing... ...control regulations (ITAR/EAR) ~3+ years as a professional software engineer ~ Strong…
commercial teams making high-stakes decisions. You’ll tackle rich engineering challenges across: Performance — We’re processing large... ...or enterprise settings Why Join Atrix as a Fullstack Software Engineer? Mission-…
Substack is building a new economic engine for culture, giving the brightest, most interesting, and most creative people on the internet... ...help you learn. Requirements ~3–6 years of professional software engineering…
ourselves, combining that technology with a human being at the point of sale. We are looking for a versatile Full Stack Software Engineer with a strong technical foundation and the ability to work across the entire stack…
What software engineers earn in New York
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $48–$67 | $99k–$139k |
| Mid level | $67–$95 | $139k–$198k |
| Senior | $92–$127 | $191k–$264k |
Adjusted for the New York market from national ranges.
What employers ask for
The skills these listings keep naming
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Walk me through a project you built and the technical decisions behind it.
Pick one project and go deep. Explain the tradeoffs you weighed, not just the stack you used, and name one thing you would do differently now.
How would you design a URL shortener (or similar small system)?
Start with requirements and rough scale before drawing boxes. Interviewers care more about how you reason through storage, uniqueness, and reads versus writes than a perfect answer.
Tell me about the hardest bug you have debugged.
Describe your process: how you reproduced it, narrowed the cause, and confirmed the fix. A methodical story beats a dramatic one.
How do you decide when code is good enough to ship?
Talk about tests, review, and risk relative to the change. Showing judgment about tradeoffs matters more than claiming perfection.
Describe a time you disagreed with a teammate about a technical approach.
Show that you argued from evidence, listened, and committed to the outcome. Avoid stories where the point is simply that you were right.
How do you approach learning an unfamiliar codebase?
Mention concrete tactics: reading tests, tracing a request end to end, making a small safe change first. This signals you can become productive quickly.
What would you do if a production incident happened right before a deadline?
Prioritize stabilizing production and communicating early. Interviewers want calm triage, not heroics.
Resume tips that move the needle
For software engineers specifically — generic advice costs you here
Name the languages and frameworks per role or project, not just in a skills block, so screeners can match you to the stack.
Quantify outcomes in engineering terms: latency reduced, error rate cut, deploy time shortened, users served.
Link to a GitHub profile or portfolio only if the pinned work is recent and readable.
Describe your role on team projects precisely — 'built the payments service' reads very differently from 'worked on payments'.
Keep the tech list honest; anything on the resume is fair game in the interview.
For senior roles, show scope: systems owned, engineers mentored, decisions driven.
Where this role goes
Typical progression
Applying for software engineer jobs in New York?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.