$173.37k - $234.56k
complex scientific manufacturing processes at scale. Our workflow engine is the foundational layer — a system that lets scientists and... ...everything or an entire team is coordinating across steps.As a Software Enginee…
Engineering & IT · San Francisco, CA
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.
1,008
Open roles today
$50–$135/hr
Typical pay range
$178k
Median, full-time
12
Fresh in this list
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.
01
Open software engineer roles
12 shown of 1,008 · sorted by freshness
$150k - $180k
backend services powering the Zeta Identity Graph. How do you engineer distributed architectures to manage a profile store running in... ...latencies for billions of monthly events? We seek an innovative Senior Software…
$155k - $400k
deciding which events point to a problem, which belong together, and what a developer needs to know to investigate.As a Senior Software Engineer on the Issue Detection team, you'll design, build, and operate the systems…
hardest technical problems in music licensing, vendor royalties, and partner data delivery.Key job responsibilitiesAs a Software Development Engineer on the Partner Payments and Reporting teams, you will design and build…
We are looking for a Sr Java Engineer to help design and enhance the services behind a customer-facing Consumer Insights platform in San... ...insights product.• Deliver new backend capabilities and software enhancements…
$183.6k - $297k
Infrastructure ecosystem, including Identity & Access Management, API Gateway, and automated onboarding services.Senior Principal Software Engineers are:Technical experts that help accelerate adoption of the very best en…
is Atlassian’s managed relational database platform. It gives engineering teams a supported way to build applications on relational databases... ...by a common goal: to unleash the potential of every team. Our software p…
$141.2k - $278.3k
Position Summary Lead Cloud Infrastructure Engineer II - Workplace Engineering/M365 AI & Engineering helps organizations build, deploy, and operate integrated solutions across software, data, AI, networks, and hybrid clo…
existing environment with design porting to demonstrating a first pass functional environment. Job Description Application or Product Engineering background with minimum 5 to 20 years of experience is required in HW Assi…
$110.7k - $218.3k
Position Summary Salesforce Life Sciences Cloud Senior ConsultantDeloitte's Sales & Service practice partners with the world's leading life sciences companies to reimagine how their commercial, medical, and field organiz…
Job-ID27435142Reference26-04111Salary$175,000-$200,000 / year Role: Calypso Senior Software Engineer II Job Description: Purpose : Acts as a senior technical team member of a software development team and provides busine…
$197.3k - $313.7k
drive the technical direction for designing and implementing software that manages Kubernetes clusters at massive scale. You will lead... ...gaps, propose and drive solutions, and mentor other engineers as they build aga…
02
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.
03
What employers ask for
The skills these listings keep naming
Data structures and algorithmsSystem designGit and code reviewTesting and debuggingSQL and databasesAPIs and integrationCloud fundamentals (AWS/GCP/Azure)Clear written communicationCross-team collaboration
04
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.
05
Resume tips that move the needle
For software engineers specifically — generic advice costs you here
01
Name the languages and frameworks per role or project, not just in a skills block, so screeners can match you to the stack.
02
Quantify outcomes in engineering terms: latency reduced, error rate cut, deploy time shortened, users served.
03
Link to a GitHub profile or portfolio only if the pinned work is recent and readable.
04
Describe your role on team projects precisely — 'built the payments service' reads very differently from 'worked on payments'.
05
Keep the tech list honest; anything on the resume is fair game in the interview.
06
For senior roles, show scope: systems owned, engineers mentored, decisions driven.
06
Where this role goes
Typical progression
01
Junior Software Engineer
02
Software Engineer
03
Senior Software Engineer
04
Staff Engineer
05
Principal Engineer
Ten quiet minutes a day
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.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.