that learn from one another. If you’re driven to solve meaningful challenges, we’d love to meet you. The Team: Marketplace Quality Engineering: Every second, our bidder evaluates millions of ad opportunities across thous…
QA Engineer jobs in Seattle, WA
QA engineers make sure software works before users find out it does not. The role blends manual exploratory testing with automated test suites and close collaboration with developers.
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 qa engineer roles
12 shown of 1,161 · sorted by freshness
Labelmaster is an established and growing company that takes the complexity out of shipping Dangerous Goods (Hazmat) making the world a safer place. Were seeking people who: Dont want to work for typical corporate or box…
address clients most complex digital transformation needs. Leveraging our holistic portfolio of capabilities in consulting design engineering and operations we help clients realize their boldest ambitions and build futur…
**Company Background** We are a remote software engineering team specializing in Web Development, AI/ML, QA, and Data Engineering. We collaborate with international clients and provide technical development services. **J…
Responsibilities Build and enhance automation frameworks and customer-centric automated testing processes. Develop and maintain automated tests using Python and Selenium. Build internal tools that support quality at scal…
and fundamentally transformative to the way goods — and eventually people — move around the planet. We are a team of mission-driven engineers with experience across aerospace, robotics and self-driving cars working to ma…
to support post-maintenance return to service and first-time activation of system upgrades. Establish training curriculum for engineers and technicians and proctor training for the team as needed. Support robust methods…
hardware that can directly impact the safety of service members and civilians? Shield AI is looking for a hands-on Vibration Test Engineer to help validate the next generation of intelligent autonomous systems through ri…
Job Summary: System One is seeking a Software QA/ SDET for a long-term opportunity in the nuclear technology and energy sector. Responsibilities Develop and execute test plans, test cases, and quality assurance procedure…
or exploring a new city for the first time. About the Role Throne is looking for a full-time Software Quality Assurance ( QA) Engineer to be a crucial member of the Software and R&D Engineering Teams. Thrones are proprie…
years of experience for software testing Experience in network QA testing is a plus Knowledge of mobile technologies, operating... ...#Quality Assurance #Field Testing #Network Tester #Mobile Engineer #Test Assurance #QA…
building and celebrating better ways of working in this world, all so that folks can find and pursue a love of the outdoors. As a Test Engineer, you will be responsible for ensuring products perform as intended to delive…
What qa engineers earn in Seattle
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $33–$48 | $69k–$100k |
| Mid level | $48–$66 | $100k–$138k |
| Senior | $63–$87 | $131k–$181k |
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
How would you test a login form?
Go beyond happy path: invalid inputs, security cases, lockouts, accessibility, and different devices. Structure your answer into categories so it sounds systematic.
What do you automate, and what do you test manually?
Automate the repeatable and regression-prone; explore manually where human judgment finds new bugs. Showing you know automation has a maintenance cost is the senior move.
Walk me through a great bug report you have written.
Reproduction steps, expected versus actual, environment, evidence, and severity. Emphasize that a good report saves a developer an hour.
A developer says your bug is not a bug. What do you do?
Show that you argue from the user's perspective and the spec, escalate with data if needed, and keep the relationship collaborative.
How do you decide what to test when time is short before a release?
Risk-based prioritization: critical paths, recent changes, and areas with bug history. Naming the tradeoff explicitly is what they want to hear.
How do you keep an automated test suite from becoming flaky?
Talk about stable selectors, proper waits, isolated test data, and quarantining flaky tests instead of ignoring red builds.
Resume tips that move the needle
For qa engineers specifically — generic advice costs you here
Quantify your impact in defects: escape rate reduced, critical bugs caught pre-release, regression time cut.
Name your automation stack and the size of suites you built or maintained, such as number of tests or coverage of critical flows.
Show progression from manual to automation if that is your path — it is the expected trajectory and worth making explicit.
Mention the domains you tested (payments, healthcare, mobile) since domain risk knowledge transfers.
Include CI/CD integration work; a suite that runs on every pull request is worth more than one run by hand.
Where this role goes
Typical progression
Applying for qa 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.