Most QA engineers send the same CV to 50 jobs and wonder why the replies don't come. Applicant tracking systems (ATS) rank you against that one job description — its exact automation framework, test types and tooling. A CV that lists "manual testing, attention to detail, bug reporting" loses to one that mirrors the offer's "Playwright end-to-end suites in TypeScript, API testing with Postman, regression in CI/CD". This page shows how to tailor your existing QA CV to a specific offer — without inventing anything you can't defend in the interview.
How an ATS reads a QA engineer CV
Before a human sees it, your CV is parsed and scored. The ATS extracts skills, titles and years, then matches them against the job description. The closer your wording is to the offer, the higher you rank. Two rules follow: (1) use the offer's exact terms ("test automation with Playwright", not "automated checks"; "regression testing", not "re-testing"), and (2) keep the layout machine-readable — single column, real text, standard section headings. MaxCV keeps both intact while it tailors the content.
How to tailor your QA CV to the job offer
Tailoring is not rewriting your whole CV per job. It is re-ordering and re-phrasing what is already true so the offer's priorities surface first:
- Match manual vs automation weight. An SDET-style offer rewards code — frameworks, CI integration, flaky-test fixes; a manual-heavy offer rewards exploratory testing, test-case design and domain knowledge. Lead with the side the posting weights.
- Mirror the test types they name. If the offer says API, performance or mobile testing, those words — with your real tooling (Postman, JMeter, Appium) — belong in your top bullets.
- Match the process vocabulary. Scrum ceremonies, shift-left, test plans, TestRail/Jira — use the posting's exact process terms where they are true for you.
Paste the job link, upload your CV, and MaxCV does exactly this in ~30 seconds — and shows your match score climb (e.g. 28% → 84%).
Which keywords to copy from the job description
Pull keywords from three places in the posting: the title, the requirements list, and the "nice to have" section. Prioritise hard, checkable terms — frameworks, test types and tooling (e.g. Selenium, Playwright, Cypress, Appium, API testing, Postman, REST Assured, JMeter, regression, exploratory testing, CI/CD, Jenkins or GitHub Actions, Jira, TestRail, SQL, ISTQB). Only include a keyword if it is genuinely true for you; ATS keyword-stuffing that you can't back up gets exposed in the interview.
How to quantify your QA achievements
Recruiters skim for impact, not test-case counts alone. Turn "performed regression testing" into "automated the regression suite in Playwright (420 scenarios), cutting the release check from 3 days of manual work to a 40-minute CI run and catching two critical defects before production". Reach for: escaped defects, regression time, automation coverage, release cadence enabled, flaky-test rate reduced, environments covered. MaxCV suggests where a metric belongs and keeps the number tied to your real work.
Hard and soft skills that match the offer
Hard skills should be a near-mirror of the posting: automation frameworks and language, API and performance tooling, CI/CD, test management tools, SQL for data checks. Soft skills matter most when the offer names them — "advocating for quality", "working closely with developers", "clear bug reports" — so include only those the offer actually asks for, and show them in a bullet rather than as a bare list.
Tailoring a QA CV with little or no experience
Junior QA CVs win by mirroring the offer with demonstrable testing work, not job history. Their "test automation" becomes your "wrote a Cypress suite for a demo shop covering checkout and auth, running in GitHub Actions"; their "bug reporting" becomes real, well-written issues you filed against open-source projects. Lead with the framework the offer names, put an ISTQB certificate where it reinforces the requirements, and let MaxCV align the wording so a thin history still scores against the ATS.