in a way that can scale? Our teams of hundreds of scientists, engineers, aerospace professionals, and futurists have been working hard... ...Basic qualifications- 5+ years of non-internship professional software developm…
Software Engineer jobs in Seattle, WA
Software engineers design, build, and maintain the applications and systems behind modern products. The work spans writing code, reviewing designs, and keeping software reliable as it 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 software engineer roles
12 shown of 489 · sorted by freshness
of AI, and you are the future of Salesforce.Our Public Cloud engineering teams are responsible for innovating and maintaining a large scale... ...Skills:A related technical degree required4+ years backend software develo…
learning provides secure, differentiated, and personalized experiences that drive loyalty and traveler satisfaction.The Senior Software Development Engineer - ML Platform role is a part of the ML Platform team. We build…
research experiment — it is a production rebuild that will redefine how Amazon understands every product on the planet. As a Software Development Engineer on this team, you will help architect, build, and ship the AI-nat…
The Pipelines team, part of the Amazon Software Builder Experience (ASBX) organization, builds and operates the CI/CD platform used by... ...customer and the proving ground.We are seeking a Software Development Engineer…
or assume sponsorship for employment visas for this position, now or in the future.The OpportunityLendingTree is looking for a Software Engineer to join our Insurance technology team and help build, enhance, and support…
Job Description: Software Engineer IBellevue, WA- Technology - Full time - R31016Job Description:What you’ll do:Design, develop and implement solutions using varied technologies focusing on scalability, latency, and resi…
Amazon Fulfillment Technologies (AFT) powers the physical engine at the heart of Amazon. AFT forms the invisible back half of Amazon... ...a button into packages at your door. We build and operate the software, hardware,…
of Amazon's e-commerce business is the Item & Offer Platform engineering team. The platform is used by millions of merchants to expose... ...central piece of Amazon's shopping experience. We are looking for a Software De…
Software Development Engineer, DynamoDB Search and IndexingAmazon DynamoDB is a serverless, distributed NoSQL database that delivers single-digit millisecond performance at virtually any scale. The DynamoDB Search and In…
Amazon is seeking a Software Development Engineer for our AWS Networking organization to join a team designing and developing software and services required to configure and automate networking devices. The successful ca…
Terra) team owns geospatial cloud infrastructure, geospatial edge software, as well as geospatial data. The team’s north star is to... ...warfighter missions.ABOUT THE JOBWe are looking for Software Engineers to join our…
What software engineers earn in Seattle
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $45–$63 | $94k–$131k |
| Mid level | $63–$90 | $131k–$188k |
| Senior | $87–$120 | $181k–$250k |
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
Walk me through a project you built and the technical decisions behind it.
Pick one project and go deep. Explain the tradeoffs you weighed, not just the stack you used, and name one thing you would do differently now.
How would you design a URL shortener (or similar small system)?
Start with requirements and rough scale before drawing boxes. Interviewers care more about how you reason through storage, uniqueness, and reads versus writes than a perfect answer.
Tell me about the hardest bug you have debugged.
Describe your process: how you reproduced it, narrowed the cause, and confirmed the fix. A methodical story beats a dramatic one.
How do you decide when code is good enough to ship?
Talk about tests, review, and risk relative to the change. Showing judgment about tradeoffs matters more than claiming perfection.
Describe a time you disagreed with a teammate about a technical approach.
Show that you argued from evidence, listened, and committed to the outcome. Avoid stories where the point is simply that you were right.
How do you approach learning an unfamiliar codebase?
Mention concrete tactics: reading tests, tracing a request end to end, making a small safe change first. This signals you can become productive quickly.
What would you do if a production incident happened right before a deadline?
Prioritize stabilizing production and communicating early. Interviewers want calm triage, not heroics.
Resume tips that move the needle
For software engineers specifically — generic advice costs you here
Name the languages and frameworks per role or project, not just in a skills block, so screeners can match you to the stack.
Quantify outcomes in engineering terms: latency reduced, error rate cut, deploy time shortened, users served.
Link to a GitHub profile or portfolio only if the pinned work is recent and readable.
Describe your role on team projects precisely — 'built the payments service' reads very differently from 'worked on payments'.
Keep the tech list honest; anything on the resume is fair game in the interview.
For senior roles, show scope: systems owned, engineers mentored, decisions driven.
Where this role goes
Typical progression
Applying for software engineer 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.