Job Title: Backend Engineer Department/Team: Engineering Reports To: Backend Engineering Manager Job Summary The Backend Engineer at FlowPlay is responsible for developing, maintaining, and optimizing server-side applica…
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 196 · sorted by freshness
systems that manage a large volume of information and use them to fulfill business goals for the company and its partners.Improve backend scalability and performance by integrating lightweight backend framework, overhaul…
implementing UI components and scaling our open source design system for web frameworks. We want to abstract away implementation details so developers can focus on building great experiences for their customers.A day in…
mentoring senior engineers, improving how teams plan and execute, and developing the next generation of technical leaders.Collaborate with... ...experience designing, building, and operating large-scale backend or full-s…
resilient, high-performance platform services and distributed backend systems. Benchmark platform performance, collect metrics, publish... ...capacity while optimizing performance and cost efficiency. Develop and operate…
creating the technical headroom for entirely new capabilities, including AI-native, agentic experiences. The work spans the full stack: backend services and APIs through the mobile (React Native) and web experience layer…
PermanentCompany: WalmartAbout Role: We are looking for a Software Engineer ( Backend) to join our team and contribute to the development of world-... ...mobile apps for performance and scalability. What you'll do: Devel…
facing solutions, owning everything from frontend experiences to backend services and cloud infrastructure.Build the engineering... ...standard for engineering excellence.Own the Full Stack: Design and develop solutions…
technical solutions using analysis, experience, and decision making Developing solutions to client problems through application of methods... ...in full stack software development across frontend and backend technologies…
occasional use. Experience with other AI coding assistants/agents (GitHub Copilot, Cursor, OpenAI Codex, etc.) • Proficiency in Java and backend frameworks such as Spring / Spring Boot (or equivalent enterprise Java stac…
We are seeking an IAM Full Stack Developer with strong experience in Identity and Access Management, PingOne integrations, Java/Spring Boot, front-end development, and cloud-native technologies. The ideal candidate will…
Ruby on Rails Tech Lead to lead development teams in designing, developing, and delivering scalable software solutions. The ideal... ...Design and optimize application architecture, APIs, databases, and backend services.…
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.