About Deploy Deploy is an intelligence infrastructure platform that gives developers and enterprises access to open source and proprietary AI models. For leading open source LLMs, Deploy operates an optimized model infer…
Backend Developer jobs in Seattle, WA
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 818 · sorted by freshness
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…
senior engineer to build reliable systems that improve outcomes for restaurant customers. The role We are hiring a Senior Backend Software Engineer to build scalable services for automated restaurant revenue recovery. Yo…
creators, agencies and referrers, and payouts go out on a schedule.The roleYou will be one of the first engineers to own Bantyr's backend end to end: the API, the data model, the money paths and the infrastructure undern…
Lightning. Founded in 2019, we build an end-to-end platform for developing, training, and deploying AI systems—designed to take ideas... ...our impact. What We're Looking For We’re looking for a Backend Engineer to help…
Work with a talented group of engineers to change the way private information is shared. What we're looking for: ~2+ years backend development ~ BS in computer science or equivalent experience ~ Languages: Python, C#, Ja…
read up more about our values, and vision at revefi.com . The Role: Senior Software Engineer We're looking for a strong backend engineers who thrives in early-stage environments and wants to make a big impact. You'll hel…
lives of millions. We’re solving huge problems and believe that every team member has a big role to play. The role We’re adding Backend Engineers to help build the foundations that power everything at Grid. You’ll work a…
-response technology, including flight-critical firmware and advanced pilot-assistance capabilities. About this Role: As a Backend Engineer working on LiveOps at BRINC, you will build and manage the real-time backend inf…
Aerostrat is a fast-growing B2B SaaS company building a complete maintenance planning solution for the aviation industry. Our core product, Aerros, enables our customers to plan all the maintenance on hundreds of aircraf…
businesses understand and stop fraud and abuse. Your work will span backend services, enterprise APIs, and user experiences that put... ...configure defenses, and understand how Radar protects them Develop the shared pla…
WHY SOCURE? Socure is building the identity trust infrastructure for the digital economy — verifying 100% of good identities in real time and stopping fraud before it starts. The mission is big, the problems are complex,…
What backend developers earn in Seattle
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $43–$60 | $90k–$125k |
| Mid level | $60–$87 | $125k–$181k |
| Senior | $84–$114 | $175k–$238k |
Adjusted for the Seattle 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 Seattle?
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.