← CV Examples
QA EngineerQA Engineer CV example (2026)
A QA engineer CV leads with a summary declaring your manual/automation balance and stack — hiring managers sort candidates into those buckets in seconds — then experience where bullets carry testing numbers: suite sizes, automation coverage, escaped-defect rates, regression cycle time. Name frameworks and languages exactly (Playwright + TypeScript scores; 'automated testing tools' doesn't). Quality metrics that moved because of your work are the strongest bullets in the category.
What recruiters scan for in a QA Engineer CV
- 1Automation stack: framework + language, stated plainly
- 2Coverage and scale: test counts, automation percentage, pipelines
- 3Quality outcomes: escaped defects, regression time, release cadence
- 4API/backend testing depth beyond UI clicking
Example QA Engineer CV
A condensed but realistic example — note how every bullet pairs an action with a number, and how tools and methods are named exactly. Details are fictional.
Ivan Petrov
QA Engineer · Automation (Playwright/TypeScript)
Belgrade, RS · ivan.petrov@email.com · github.com/ipetrov-qa
Summary
QA engineer with 6 years across manual and automation testing, now automation-focused on a fintech web platform. Built a Playwright/TypeScript suite (900+ tests) that cut regression from 4 days to 6 hours; escaped-defect rate down 70% over two years. ISTQB certified.
Experience
Senior QA Engineer
2022 – present
Ledgerpay (fintech SaaS)
- Designed and built the UI automation suite from scratch (Playwright, TypeScript, Page Object Model): 900+ tests running in CI on every merge, full regression down from 4 days manual to 6 hours.
- Own API testing for the payments service (Postman + automated REST checks in CI); caught a rounding defect pre-release that would have misposted ~€40k/month.
- Cut escaped defects 70% over two years (tracked per release in Jira); release cadence moved from monthly to weekly on the same headcount.
- Stabilised a flaky legacy suite from 82% to 99.5% pass consistency by fixing waits, isolating test data, and quarantining with exit criteria.
Adriatic Software (agency)
- Wrote and executed test plans for 12 client web/mobile projects; maintained a 400-case regression library and ran UAT with client stakeholders.
- Introduced exploratory-testing charters that found 30% of all pre-release defects despite taking 10% of testing time.
Skills
- Playwright & Cypress (TypeScript)
- Selenium (Java) — maintenance level
- API testing (Postman, REST Assured)
- CI/CD (GitHub Actions, Jenkins)
- Test planning & exploratory testing
- SQL for test data & validation
- ISTQB Foundation (2020)
Education
BSc Computer Science, University of Belgrade, 2019
ATS keywords for QA Engineer roles
These terms appear most often in QA Engineer job descriptions and carry the most ATS score weight. Make sure the ones you can honestly claim appear in your CV — in the exact phrasing.
- 1Test automation (Selenium, Playwright, Cypress)
- 2API testing (Postman, REST Assured)
- 3Test planning, regression suites, and exploratory testing
- 4CI/CD integration (Jenkins, GitHub Actions)
- 5Defect management in Jira / ISTQB certification
See how your QA Engineer CV scores
An example shows the target — the free ATS checker shows your distance from it: score, keyword gaps, and the fixes ranked by impact. And when you're applying to a specific job, the AI Adapt flow rewrites your CV against that exact posting — honestly, without inventing experience. $4 to download.
QA Engineer CV FAQ
Manual QA moving to automation — how do I write the CV?
Show the transition in progress, not aspiration: tests you've already automated (even 20), the framework you're learning with proof (a GitHub repo of Playwright tests), and your manual expertise reframed as test design — which is the half of automation that tools can't do. Apply to hybrid roles, where that mix wins.
What metrics belong on a QA CV?
Regression cycle time before/after automation, escaped-defect trend, automation coverage, suite stability (flake rate), and release cadence enabled. One money bullet — a defect caught with quantified business impact — is worth the whole skills section.
Is ISTQB worth listing?
In Europe and enterprise environments, yes — it's a common ATS filter and costs one line. In startup-heavy markets it matters less than a GitHub link with real test code. List it; just don't lead with it over hands-on evidence.