transformation by building the tools and experiences that thousands of developers use to create their own products. Plaid powers the tools... ...their finances. You will work across the stack, from reliable backend servi…
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 347 · sorted by freshness
Backend Application Engineer - Remote Bright Vision Technologies is a technology consulting and software development company... ...expertise with strong platform-engineering instincts, values internal developer experienc…
Opportunity Are you an experienced Senior Software Engineer, Backend (Infrastructure) looking to make a significant impact at the... ...for AI data workloads. Has 5+ years of experience in developing and architecting lar…
Today Govies Award for 2025. ABOUT THIS ROLE As a Staff Backend Software Engineer at LVT, you will serve as a primary technical... ...CI/CD workflows, and introduce tooling that enhances team-wide developer productivity…
critical role in designing, building, and scaling software across our entire user interface surface area and the mission-critical backend services supporting it. You will own features end-to-end—from building responsive…
growing! The Role We're hiring a Staff Software Engineer ( Backend) to lead the technical direction of the systems powering our... ...reviews, technical guidance, and architectural leadership Improve developer productivi…
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…
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…
blockchain-powered gaming experiences. We are looking for a **Senior Web3 Full Stack Developer* * to build seamless user experiences connecting blockchain networks, smart contracts, backend systems, and game platforms. Y…
Our client, an award-winning Legal Tech company, is hiring a Backend Engineer to join their team remotely. The successful candidate will join an early-stage team and play a pivotal role in developing AI-driven technology…
Job Description Job Description Senior Backend Engineer (Golang & AI Automation) Location: Seattle, WA (Hybrid) or Remote (US-based) Job Type: Full-time Salary Range: $140,000 – $180,000 / year The Opportunity EQL Edtech…
transparency, and control at every step. We’re looking for a Senior Backend / Core Engineer to help expand and deliver Vendia’s distributed... ...for our massively multi-tenant platform. You’ll design, develop, and deliv…
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.