About the Role Dennis 7 Dees has been growing people, plants, and places in the Pacific Northwest since 1956 — and we are ready to make our business systems as strong as the work we deliver. We are looking for a Business…
QA Engineer jobs in Portland, OR
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
8 shown of 186 · sorted by freshness
automation applications and related services. This position involves working closely with end users, system integrators, OEM's, engineering consulting firms and electrical contractors, specifying and applying our product…
Manual QA Tester (Part-Time, On-Site Portland) Rapta, Inc. · Portland, OR · Part-time, W-2 · On-site About Rapta Rapta... ...a production line slows down — so we treat QA as a first-class engineering discipline. The Role…
with Tier 2 material suppliers, T1 apparel factories, material supplier management, material and product development, manufacturing engineering and product integrity. You will serve as the regional connection point betwe…
The City of Beaverton is seeking an Assistant City Traffic Engineer (ACTE) who will play a key role in shaping the future of traffic and transportation in the city. This position is in the Public Works Transportation Eng…
the Americas is a close-knit team focused on selling and supporting the world’s leading semiconductor fabricators. The Solutions Engineering team is our key technical resource allowing Keysight to deliver high-performanc…
We are SLR Consulting (US), a 500+ coast-to-coast team of advisory, environmental/ engineering, and regulatory professionals. We deliver environmental and sustainability services to our clients through the integration of…
Job Description Job Description Qualifications: Here's what you'll need: Bachelor's degree in chemical engineering or similar engineering degree At least 8 years of experience in a chemical process engineering role on fa…
What qa engineers earn in Portland
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $29–$42 | $61k–$88k |
| Mid level | $42–$58 | $88k–$121k |
| Senior | $56–$77 | $116k–$160k |
Adjusted for the Portland 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 Portland?
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.