How to write it
Decide which QA engineer you are, on the page
"QA Engineer" now covers manual testers, automation engineers and SDETs who write production code. A resume that hedges across all three reads as junior in each. Name it in the title line and in the summary — automation-first, exploratory specialist, or genuinely both with an order of strength.
If you do both, say which is primary and let the other appear as a strength rather than a claim of equal depth. "Automation-first, with exploratory testing on high-risk releases" is a clear, honest position.
Escaped defects is the metric that matters
Test counts are an activity measure; escaped defects are an outcome measure. How many bugs reached production, and what happened to that number while you were responsible for quality? That is the closest thing QA has to a revenue figure.
Pair it with cadence, because the impressive version is both together. Fewer defects while shipping more often means the testing got better rather than the team getting slower — which is precisely the objection a hiring manager has about investing in QA.
- Escaped or production defects, and the trend
- Regression cycle time, before and after automation
- Suite size in scenarios, and what it replaced
- Flake rate, which every engineering manager cares about
- Release frequency the testing enabled
Flakiness is the credibility test
Any tester can add automated tests. The engineer who takes a suite from 18% flaky to under 1% has done the hard, unglamorous work of fixing test data, timing and isolation — and has produced a suite people trust enough to block a release on.
This single bullet distinguishes someone who has maintained automation at scale from someone who has only written it. Very few QA resumes include it, which makes it exceptionally cheap signal.
Tests that don't run in CI don't count
A suite on a laptop is a hobby. Say where the tests run, when they run, and what they block — pull request checks, nightly runs, pre-release gates. Naming the pipeline shows you understand testing as part of the delivery system rather than as a phase after it.
This is also where the SDET boundary sits. If you have written CI configuration, built test infrastructure, or made someone else's tests faster, that is engineering work and should be described as such.
Show judgement about what not to automate
Mature quality engineering is largely about allocation: what gets automated, what gets explored by hand, what gets caught by monitoring instead. A resume that shows this thinking reads as senior, because it's the part juniors get wrong by trying to automate everything.
One line on risk-based test strategy, or on the exploratory pass you keep for high-risk releases, communicates it without an essay. Then let the exploratory find speak for the value: "found the 3 highest-severity defects of the year".