with other architects, designers, product managers and software developers to influence product direction and functional requirements,... ...delivering great softwareAdopter of modern LLM tools for Java backend developme…
Backend Developer jobs in San Jose, 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 407 · sorted by freshness
Lead) Software Engineer who will play a key role in designing, developing, and maintaining product features of our IAM platform for our... ...high performance, scalability, and reliability.Lead a team of backend software…
successful deliveryModel ServiceNow's core values and contribute feedback to improve team cultureQualifications10+ years of professional backend software development experience, with a focus on scalable distributed syste…
enterprise SaaS applications, with 5+ years in lead technical architecture or Staff/Principal engineering roles for cloud-native platforms. Backend Expertise: Deep hands-on experience building high-concurrency microservi…
OfferSalary:$161,000.00 - $221,000.00Location:Santa Clara,CAYou’ll benefit from a supportive work culture that encourages you to learn, develop, and grow your career as you take on challenges and drive innovative solutio…
The OpportunityWe’re building the next generation of AI-native product experiences, where conversations turn directly into outcomes. As a Senior Software Engineer on our Product teams, you’ll own significant areas of the…
The OpportunityWe’re building the next generation of AI-native product experiences, where conversations turn directly into outcomes. As a Staff Software Engineer on our Product teams, you’ll define how these capabilities…
The OpportunityAre you an experienced Software Engineer, Backend (Infrastructure) looking to make a significant impact at the intersection... ....We're looking for someone whoHas 2+ years of experience in developing and…
Agentic development, and Deep Learning. Among other things, our team develops the Action and Event Generation extensions for Isaac Sim. What... ...applications.Collaborate with multi-functional teams to build backend ser…
driving a major transformation across Capital One. What You’ll Do: Lead a portfolio of diverse technology projects and a team of developers with deep experience in distributed microservices, and full stack systems to cre…
driving a major transformation across Capital One. What You’ll Do: Lead a portfolio of diverse technology projects and a team of developers with deep experience in distributed microservices, and full stack systems to cre…
including the United States, Norway, Bhutan, and Ethiopia. To learn more, visit Position Overview We are seeking a Staff Backend Engineer to take our Model-as-a-Service (MaaS) working system and re-architect it into a co…
What backend developers earn in San Jose
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $48–$66 | $99k–$138k |
| Mid level | $66–$96 | $138k–$200k |
| Senior | $93–$126 | $193k–$262k |
Adjusted for the San Jose 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 Jose?
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.