highest priority — our systems are designed to meet strict uptime targets, including no downtime during market hours. As a Senior Software Engineer, you will build and improve core infrastructure used by many engineering…
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 1,023 · sorted by freshness
accelerating frontier research with high-quality data, advanced training pipelines, plus top AI researchers who specialize in software engineering, logical reasoning, STEM, multilinguality, multimodality, and agents; and…
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 Expedia…
here to make things slightly better. We're here to change the game. The Role This is not a typical engineering role. We are looking for a Full-Stack Software Engineer who will focus entirely on moonshot innovation on the…
Accretive Technology Group — Full-Stack Software Engineer Location — This role is fully remote in the following states: Arizona, California, Colorado, Florida, Michigan, Missouri, Nevada, South Carolina, Texas, or Washin…
Startpage, MapQuest, and CouponFollow — and build the apps, search engines, and online publications that power them. Startpage (part... ...targeted. Startpage is looking for a full-stack Senior Software Developer to work…
Senior Software Engineer, AI/ML Platforms and Infrastructure – Brain Health Accelerator The Allen Institut e accelerates science for a healthier world through large-scale research designed to answer some of the most comp…
infrastructure. This role offers a unique opportunity to join a data engineering team to advance our capabilities with data processing... ...be hired* What You'll Own and Deliver (Responsibilities) As a software engineer…
the end user in mind Craft and quality: You hold yourself to a high bar for code quality and system design, and you make the engineers around you better About you ~5+ years of professional development experience, shippin…
into the Silicon Slopes CTO Hall of Fame in 2024. Product & Software Excellence: We were named one of The Software Report's Top 1... .../operations who run the managed log and broker, and the engineers building the agent…
measurable ROAS improvements. We're seeking a Senior Fullstack Engineer who thinks in experiences, not features. You'll architect our... ...to shape the product roadmap Requirements ~7+ years of software engineering expe…
Job Description Job Description Software Engineer | Engineering Intelligence Location: Seattle WA (Flexible Hybrid Schedule) Salary: $140-180k DOE Headquartered in Seattle with teams nationwide, we are a growing software…
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.