The QA engineering market in 2026 has a clear divide: manual-only testing experience is increasingly insufficient for mid-level and above roles, while test automation engineers — particularly those who have built frameworks rather than just written tests in someone else's — are in sustained demand. A QA engineer CV that lists "manual testing, regression testing, exploratory testing" without any automation evidence will not shortlist for the majority of roles at tech companies and product teams, even when the candidate has significant experience and strong domain knowledge. The second gap that costs QA engineers interviews is the absence of metrics: test coverage percentages, defect detection rates, regression suite sizes, and the critical number that almost no QA CV includes — the defect escape rate, which is the percentage of bugs that made it to production despite QA. The ones who track and reduce that number are operating at a different level from those who only count bugs found. This guide covers how to structure a QA engineer CV for the automation era, which ATS keywords matter, and how to write bullets that show engineering depth rather than test execution.

What QA Engineer Job Descriptions Require in 2026

QA engineer JDs split into three tracks, and the track determines what skills to lead with:

Test Automation Engineer / SDET: The dominant track in tech company and product team hiring. Primary expectation: the ability to design, build, and maintain automated test frameworks (not just write tests in an existing one). Requires programming ability in at least one language (Python, Java, JavaScript/TypeScript) and hands-on experience with at least one major automation framework. CI/CD integration is standard — tests must run in the pipeline, not just locally. JDs at senior level expect framework architecture ownership.

Manual QA Engineer: Still the dominant track in regulated industries (healthcare, finance, government) and at product companies in an early stage with limited engineering resources. Requires structured test case design, exploratory testing methodology, defect management discipline, and strong communication with developers. ISTQB Foundation or Advanced is a common filter credential.

Performance / Load Testing: A specialisation track. JMeter, k6, or Gatling for load testing; performance profiling, bottleneck analysis, and capacity planning. Appears as a standalone role at scale-up and enterprise companies; often a secondary skill expected at senior QA levels elsewhere.

Requirements across the majority of QA engineer JDs in 2026:

  • Automation framework experience — Selenium (mature, widespread), Cypress (JavaScript-native, popular at frontend-heavy teams), Playwright (rapidly growing, multi-browser, strong TypeScript support), or Appium (mobile). The framework matters — name it explicitly.
  • Programming in a test language — Python (pytest), Java (JUnit/TestNG), or JavaScript/TypeScript (Jest, Mocha). The language paired with the framework matters for ATS matching.
  • API testing — Postman for manual API exploration; REST Assured (Java), requests (Python), or Supertest (Node) for automated API tests. API testing is now a standard QA expectation, not a specialist skill.
  • CI/CD integration — tests running in GitHub Actions, Jenkins, GitLab CI, or CircleCI as part of the build pipeline. "Tests that run locally" is not CI integration; "tests that block deployment when they fail" is.
  • Test management — TestRail, Zephyr (Jira), or Xray for test case management, execution tracking, and coverage reporting. Defect management in Jira is assumed.

QA engineer salaries in 2026: £35K–£65K UK; $70K–$110K US. Senior automation engineers and SDETs reach £70K/$130K.

ATS Keywords for a QA Engineer Resume

QA ATS filtering is framework-specific and language-specific. "Selenium" and "Playwright" as exact strings matter more than "test automation experience."

Essential ATS terms for a QA engineer resume:

  • Title variants: QA Engineer, Quality Assurance Engineer, Test Automation Engineer, SDET, Software Development Engineer in Test, QA Analyst, Manual QA, Automation QA, Senior QA Engineer
  • Automation frameworks: Selenium, Playwright, Cypress, WebDriver, Appium, TestCafe, Puppeteer
  • Test frameworks: pytest, JUnit, TestNG, NUnit, xUnit, Mocha, Jest, RSpec
  • Languages: Python, Java, JavaScript, TypeScript, C#, Ruby
  • API testing: Postman, REST Assured, SoapUI, requests, Supertest, API automation
  • BDD: Cucumber, Gherkin, SpecFlow, BDD, behaviour-driven development, feature files
  • CI/CD: GitHub Actions, Jenkins, GitLab CI, CircleCI, CI/CD integration, pipeline testing
  • Performance: JMeter, k6, Gatling, Locust, load testing, performance testing, stress testing
  • Test management: TestRail, Zephyr, Xray, Jira, defect tracking, test case management, test coverage
  • Long-tail phrases: QA engineer resume examples, how to write a QA engineer resume, test automation engineer cv, SDET resume, Playwright automation resume, Selenium QA cv

Placement: Primary automation framework (Playwright / Selenium / Cypress) and test language (Python / Java / TypeScript) in your CV headline. CI/CD tool visible in Skills — it signals that your tests run in pipelines, not just locally. Test coverage percentage or regression suite size in the first experience bullet where available.

QA Engineer CV Structure and Bullets That Show Automation Depth

Section order:

  1. Headline — "QA Engineer | Playwright · TypeScript · API Testing · GitHub Actions · Cypress"
  2. Certifications — ISTQB Foundation or Advanced for manual/regulated contexts; AWS/Azure for cloud testing roles
  3. Skills — Test Automation / Languages / API Testing / CI/CD / Performance / Test Management
  4. Experience — 4–6 bullets per role; framework built vs. used, coverage %, defect metrics, CI integration
  5. Education — CS, software engineering, or related degree; bottom

One to two pages. For SDET roles, include GitHub link if you have public test framework repositories — framework architecture is the primary differentiator and a code sample proves it directly.

Three elements make a QA engineer bullet convincing: what was built or tested (framework, product, scope), the coverage or defect metric, and the outcome (release confidence, regression time, production quality). Three examples:

  • Built a Playwright automation framework from scratch for a React e-commerce platform — 340 end-to-end tests covering 94% of critical user journeys; integrated into GitHub Actions CI pipeline, reducing regression testing from 3 days of manual effort to 28 minutes per build
  • Identified 1,240 defects over 12 months with 91% catch rate pre-production — maintained average 18-minute turnaround from discovery to Jira ticket with full reproduction steps; zero P1 production incidents attributable to QA coverage gaps during the same period
  • Led API performance testing for a financial services platform using k6 — identified a throughput bottleneck at 800 concurrent users causing 12-second response times; collaborated with the backend team on query optimisation and caching, achieving sub-500ms response at 2,000 concurrent users under sustained load

QA engineering interviews test both test design thinking ("how would you test a login feature?") and automation code quality (write a Playwright test for this user journey, or review this test and identify its weaknesses). For SDET roles, expect a take-home or live-coding exercise. Your CV's framework architecture evidence determines whether you interview as a test writer or as a framework designer.

Three QA Engineer CV Mistakes That Lose Automation Roles

Manual-only evidence for automation roles. The majority of QA engineering roles at tech companies, scale-ups, and product teams require test automation as a primary skill. A CV with exclusively manual testing evidence — test cases written, exploratory sessions conducted, defect reports filed — will not shortlist for these roles regardless of the candidate's experience level or testing depth. If you have built any automation at all, lead with it. If you are transitioning from manual to automation, list the frameworks you are learning, any side projects where you have written automated tests, and any Udemy/Coursera automation courses completed. Show the direction of travel clearly.

Framework size and coverage never mentioned. "Wrote automated tests using Selenium" tells the recruiter nothing they can evaluate. A test suite of 12 tests covering one feature is meaningless; 400 tests covering 90% of critical user journeys is infrastructure. Add the numbers: tests written, coverage percentage, languages and frameworks used, and whether the suite is integrated into CI. These figures are available — they are in your test management tool and your CI dashboard. Pulling them takes 10 minutes and transforms a generic bullet into a specific, verifiable claim.

No CI/CD integration evidence. Test automation that only runs locally provides limited value — it does not block broken code from reaching production, does not give developers immediate feedback, and does not compound over time into a reliable regression suite. Hiring managers for QA engineering roles at engineering-led companies expect tests to be integrated into the deployment pipeline. If your automation runs in CI, say so explicitly: "integrated into GitHub Actions, running on every pull request." If it doesn't yet run in CI, that is a gap worth addressing before your next application — and a one-line addition to an existing pipeline is a reasonable first step.

If you are applying to QA engineer or test automation roles and want your CV rebuilt around the specific Playwright, Selenium, and CI/CD requirements in a target job description, Resumegpt generates your QA engineer CV from your work history in under 60 seconds — automation depth evidenced, coverage metrics surfaced, ATS-optimised, and exported as a PDF ready to submit.