web experiences for business audiences. Partner with product engineers to integrate capabilities, APIs, data, and directory-style... ...partners. Requirements ~7+ years of frontend and/or full-stack software development…
Software Engineer jobs in San Francisco, CA
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 7,695 · 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…
a venture-backed startup and we’re looking to grow our team significantly in 2025 - join us! We are seeking a Full Stack Software Engineer who embodies both technical excellence and a relentless drive to elevate our prod…
About Mariana Minerals Mariana Minerals is a software- first, vertically integrated minerals company on a mission to supply the critical... ...Minerals is looking for a highly motivated Full Stack Software Engineer to wo…
About the Team The ChatGPT team works across research, engineering, product, and design to bring OpenAI’s technology to the world. We seek to learn from deployment and broadly distribute the benefits of AI, while ensurin…
past year, and are growing nearly 20% month over month. The team you'll build with We’re former YC founders and founding engineers. We like hard problems, strong opinions, and getting something into customers’ hands whil…
We recently raised our pre-seed from a16z Speedrun , Reach Capital , and JFF Ventures , and are now hiring a Full Stack Engineer to help build the product that institutions use to interact with their data every day. The…
About the Team The Coding team is reimagining how software is built in the AI era. We build tools and workflows that help software engineers work faster, tackle more ambitious projects, and spend less time on repetitive…
Substack is building a new economic engine for culture, giving the brightest, most interesting, and most creative people on the internet... ...to help you learn. Requirements At least 3+ years of software engineering exp…
and Culture doc here . Position Summary As a full stack engineering on the product eng team you will be working on the most... ..., or a related field. ~3+ years of experience in Full Stack Software Development. ~ Experi…
experiences, with a high bar for quality, reliability, and user trust. About the Role We’re looking for product-minded software engineers to build the next generation of consumer experiences in ChatGPT across these verti…
Our team sits at the intersection of research, product, design, and infrastructure. We work closely with model researchers, mobile engineers, frontend engineers, and platform teams to build intuitive experiences and scal…
What software engineers earn in San Francisco
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $50–$71 | $105k–$147k |
| Mid level | $71–$101 | $147k–$210k |
| Senior | $98–$135 | $203k–$280k |
Adjusted for the San Francisco 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 San Francisco?
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.