Job Title: QA Automation Engineer Location: Fort Washington, PA - Onsite Job Description: Develop, execute, and maintain test plans, test cases, and test scripts for real-time control systems Collaborate with cross-funct…
QA Engineer jobs in Washington, DC
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 2,582 · sorted by freshness
Hybrid Position in Washington DC*Position is subject to contract award*3 professional references requiredPosition DescriptionThe QA/ Test Engineer ensures the quality and reliability of system releases through structured…
Role: Senior QA Engineer with Playwright Remote (USA / Canada) - Candidates can be either in USA or Canada Job Type: W2 Contract Responsibilities: Verify completed work against acceptance criteria, design intent, and exp…
Job Title: QA Engineer Duration: 4-month contract Location: Hybrid, 2-3 days in (Bellevue, WA) Key Responsibilities Perform manual functional and regression testing within Microsoft Dynamics 365. Execute and validate end…
Job Description Job Description Security Clearance: SECRET position. Personnel must possess a final DoD granted SECRET security clearance Experience and Degree: Mid: PhD; Master’s degree with 5 years of experience; Bache…
Job Description Job Description Role Summary We are looking for a QA Engineer to validate a predictive cybersecurity platform across backend APIs, frontend dashboards, simulation logic, deterministic bundle generation, i…
HCLTech is looking for a highly talented and self- motivated QA Engineer to join it in advancing the technological world through innovation and creativity. Job Title: QA Engineer- (Audio testing) Position Type: Full Tim…
QA Automation Engineer Job Summary We are seeking a collaborative and forward-thinking experienced QA Automation Engineer to join our established QA team as our resident Automation Specialist. You will be joining a close…
What qa engineers earn in Washington
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 Washington 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 Washington?
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.