Role: Senior Backend Software Engineer Location: San Diego, CA (in-office) Salary Range: $165,000 - $220,000 / yr + stock options, 401k matching, and other benefits Role Overview: Seasats' vehicles operate for months at…
Backend Developer jobs in San Diego, 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 89 · sorted by freshness
Software Test Engineer will be responsible for the quality of the developed product and participating in manual and automated testing... ...in both the manual and automated testing of user interface and backend software…
Staff / Sr Staff Engineer - System SoftwareCategorySoftwareLocationSan Diego, CA ExperienceMore than 8 Years Work Expe.Job Description• Bring up new platform boards and verify the major functions independently• Regular s…
test, and operate Hivemind capabilities. It connects autonomy developers with the applications, services, compute, data, and workflows... ...integrations, and agent tools. Working across frontend architecture, backend se…
from Architecture, Product Management, and Operations to design, develop, test, and release featuresCommunityContributes to standards,... ...AI technologies and tools, applying them to user experiences or backend solutio…
Follow Shield AI on LinkedIn, X, Instagram, and YouTube. Job Description:Shield AI is seeking a Senior Engineer to help design, develop, and integrate a safety critical Run-Time Assurance (RTA) product. The Hivemind Foun…
development and implementation of highly effective applications meet the evolving needs of ICE. Responsibilities: The Full Stack Developer will be responsible for the design, development, integration, testing, deployment…
and subject matter experts from the areas of systems engineering, hardware, firmware, RF front-end design, and signal processing. Developing software for a variety of microarchitectures, including DSP, ARM, or RISC-VDeve…
It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing peo…
after year. About the role We are looking for a full-stack Web Developer to join Miva's Professional Services team. This is a client-... ..., and error handling Troubleshoot and resolve frontend, backend, and configurati…
end standards and best practices. Responsibilities Design, develop, and maintain responsive, accessible, and performant web... ...performance, accessibility, and security. Collaborate with backend and platform engineerin…
advanced knowledge of software engineering practices and techniques, technology trends, and working knowledge of domain expertise. - Develop detailed software architecture and design documents. -Ability to implement the…
What backend developers earn in San Diego
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $41–$57 | $85k–$118k |
| Mid level | $57–$82 | $118k–$171k |
| Senior | $79–$108 | $165k–$224k |
Adjusted for the San Diego 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 Diego?
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.