Maxana is seeking an experienced Backend Engineer for a confidential client — a well-funded AI platform company used by ML teams globally. In this role you will own features end to end across APIs, CLI tooling, billing s…
Backend Developer jobs in San Francisco, CA
Backend developers build the server-side logic, APIs, and data layers that applications run on. The job is designing services that stay correct, fast, and secure as usage 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 backend developer roles
12 shown of 3,799 · sorted by freshness
timeouts, cancellation, and recovery from model or tool failures. Develop scheduling systems for reliable deferred actions with correct... ...messages, downstream model calls, and tool calls. Set backend engineering stan…
About the Role As a founding backend engineer at an early-stage AI assistant company, you will own the reliable systems that power... ...timeouts, cancellation, and recovery from model or tool failures. Develop schedulin…
a workplace where people can be their best selves, make a real impact, and enjoy their work. We are looking for a Back-End Web Developer responsible for managing the interchange of data between the server and the users.…
We are looking for a Back-End Web Developer responsible for managing the interchange of data between the server and the users. Your primary focus will be development of all server-side logic, definition and maintenance o…
us, and we are working towards building a generation defining developer infrastructure company. We also wrote the spec for webhooks ( Standard... ....io. About the Role We are looking for a top performing backend enginee…
your colleagues are using Town too. These are the systems you'll build. You'll be a foundational hire, working across the full backend -- from LLM orchestration and workflow execution to the identity and knowledge layer…
We’re building the future of enterprise B2B SaaS with AI agents. We operate at the scale of our customers with 1% of the resources. That requires precision, good judgement, and a sense of daring. We care as much about mo…
About Layer Over the last decade, a vibrant ecosystem of SMB software tools has emerged to help SMBs manage and run their businesses. These tools help SMBs with everything from payments to payroll, but accounting has lag…
About Raindrop Raindrop is the monitoring platform for AI agents. Engineering teams at Fortune 100s and the fastest-growing AI companies (Vercel, Speak, Clay) use it to catch silent failures in production. When an agent…
the intersection of financial infrastructure, complex engineering, and product experience. About the Role We’re looking for a BackEnd Engineer to join our growing team at Fun and help architect the backend services that…
Preferred Qualifications Strong knowledge of Rust, backend service design, APIs, data systems, concurrency, and production software architecture. Experience formulating and completing technical analyses involving backend…
What backend developers earn in San Francisco
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $49–$67 | $101k–$140k |
| Mid level | $67–$98 | $140k–$203k |
| Senior | $94–$128 | $196k–$266k |
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
Design an API for a feature like comments or notifications.
Clarify requirements, then cover endpoints, data model, pagination, and error handling. Mentioning versioning and rate limits shows production experience.
How would you find and fix a slow database query?
Walk through reading the query plan, checking indexes, and considering caching or denormalization. Ground it in a query you actually fixed.
How do you keep two services consistent when both need to update data?
Discuss transactions, idempotency, and eventual consistency with outbox or saga patterns. Acknowledge tradeoffs rather than promising perfect consistency.
What do you monitor on a service you own?
Name the basics — latency, error rate, saturation — plus business-level signals. Bonus points for talking about alerts you tuned to reduce noise.
Tell me about a production incident you handled.
Structure it: detection, mitigation, root cause, prevention. Emphasize what changed afterward, not just the firefight.
How do you approach securing an API?
Cover authentication, authorization, input validation, and secrets handling. Naming OWASP-style risks concretely is enough; you are not expected to be a security engineer.
When would you choose a message queue over a direct call?
Talk about decoupling, retries, and absorbing spikes, and be honest about the added complexity of async debugging.
Resume tips that move the needle
For backend developers specifically — generic advice costs you here
State scale where you can: requests per second, data volume, or number of services — it is the fastest way to signal seniority.
Name the databases and infrastructure you ran in production, not just languages.
Describe reliability work — migrations without downtime, incident reduction, test coverage on critical paths.
If you designed an API others consume, say so and note how many teams or clients depend on it.
Avoid listing every framework you have touched; two stacks with depth read better than eight without.
Where this role goes
Typical progression
Applying for backend developer 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.