QA Engineer CV Example & Writing Guide

The full CV example

Two things to notice: the automation numbers are always tied to what the team could then do, and the manual work is not apologised for.

Fictional example. Replace the name, city, email, phone and every number with your own.

Why this CV works

Five things this example does that most QA CVs do not:

• Automation is measured by what the team could then do

  "Three days of manual regression to 40 minutes in CI" is good. "Which let the team move from fortnightly to weekly releases" is what makes it matter to a hiring manager who is paying for release speed rather than for tests.

• It counts escaped defects, the number QA is actually judged on

  9 per release down to 2. Test counts, coverage percentages and automation ratios are all proxies; escaped defects are the outcome. A candidate who volunteers that number is telling you they were measured and survived it.

• Flakiness is treated as a real defect

  12% of runs down to 1.5%, with the three causes named. Every engineer who has ignored a red pipeline knows what an unreliable suite costs, and fixing it is a specific skill that rarely appears on a CV.

• One found defect is described in detail

  A mispriced connecting itinerary, 1 in 40, found at a boundary nobody owned. A single well-chosen catch shows how the candidate thinks about risk, which a list of testing types cannot. It also gives the interview somewhere obvious to go.

• The support job is claimed, not hidden

  Two years in a support queue explains where the reproduction discipline came from, and the bullet says so in one line. Career-change entries are stronger when they carry their own justification instead of sitting there as a gap to explain.

Professional summary examples

Entry level

At entry level, one release you protected and one artefact you wrote beat a list of test types. Say plainly which parts were manual.

Mid level

Mid-level needs one speed number and one quality number, because automation without a defect outcome invites the question of whether the tests test anything.

Senior

Senior QA is a strategy and trust role. Name the scope you set standards for, and describe the mess you are good at walking into.

Experience bullet examples

Twelve bullets in weak and strong form. The figures are the fictional character's - yours have to come from your own defect tracker, your own pipeline timings and your own release notes, because the first interview question here is usually how you counted.

Weak

Performed manual and automated testing.

Stronger

Replaced a three-day manual regression pass with a 40-minute suite covering the 18 journeys that carry most bookings, which moved the team to weekly releases.

Why

Time saved plus the coverage decision plus what the team gained. The middle part is the judgement.

Weak

Improved software quality.

Stronger

Cut escaped defects from an average of 9 per release to 2 over three quarters using risk-based test design and an exploratory charter per changed area.

Why

Escaped defects is the number this job exists to move. Use it if you have it.

Weak

Wrote automated tests.

Stronger

Brought suite flakiness from 12% of runs to 1.5% by removing fixed waits, isolating test data per run and quarantining the four worst offenders.

Why

A flake number tells a reader you have maintained a suite, not just written one.

Weak

Found and reported bugs.

Stronger

Found the itinerary defect that mispriced 1 in 40 connecting journeys three days before release, by testing the boundary between two systems nobody owned.

Why

Pick one catch and describe the reasoning that led to it. That is your test design, demonstrated.

Weak

Used Jira to track defects.

Stronger

Rewrote the bug report template the squads use; reports returned as not reproducible fell from about a third to under 5%.

Why

The tool is incidental. The drop in rework is the achievement.

Weak

Tested APIs.

Stronger

Added contract tests below the interface layer, which caught breaking changes in minutes instead of during the end-of-sprint manual run.

Why

Name the level you moved testing to, and what got faster as a result.

Weak

Did cross-browser testing.

Stronger

Rebuilt the device and browser matrix from real session data, dropping 6 low-traffic combinations and adding 2 that were generating complaints.

Why

Evidence-based scope reduction is a QA skill. Testing everything is not a strategy.

Weak

Worked with developers on quality.

Stronger

Joined refinement for two squads and turned ambiguous acceptance criteria into explicit examples, which cut mid-sprint clarification tickets from about 12 a sprint to 3.

Why

Prevention beats detection. Count what stopped being asked.

Weak

Tested for accessibility.

Stronger

Ran the accessibility pass on the claims submission flow and stopped a release two days before go-live because the form was unusable with a screen reader.

Why

Stopping a release is the most consequential thing a tester does. If you have done it for a defensible reason, say so.

Weak

Ran user acceptance testing.

Stronger

Ran acceptance sessions with two claims handlers and converted their objections into 11 specific, reproducible defects instead of a general usability complaint.

Why

The conversion from complaint to defect is the work. Name the count.

Weak

Integrated tests into CI.

Stronger

Split the suite into a 6-minute pull-request tier and a full nightly run, so developers stopped skipping tests to get a merge through.

Why

Describe the behaviour you changed in other people, not the pipeline configuration.

Weak

Mentored junior testers.

Stronger

Taught two junior testers to write reproduction steps from log evidence; both now triage the incoming defect queue without review.

Why

Mentoring needs an outcome someone else performs, or it is an opinion about yourself.

Skills that belong on this CV

Education and certifications

QA takes people from support, from business analysis and from development, and a specific degree is rarely required. Keep education to degree, institution and years below experience. If you came from support or operations, keep that role on the CV in one line: reproduction discipline and user empathy are learned there, and the line explains the rest of the career.

Certifications

• ISTQB Foundation Level - Frequently named in adverts, particularly in agencies and regulated sectors. Cheap to hold and occasionally a screening filter.
• ISTQB Advanced Test Analyst or Test Manager - Worth it when you are moving towards test strategy or leading a QA function, and less so for hands-on automation roles.
• A certification in the automation tool you use - Less persuasive than a public repository showing a suite you designed, including how you handled test data.

In QA a foundation certificate is common enough that omitting it can be noticed, which is not true in most engineering roles. It still does not carry a CV: the escaped-defect number does.

How an ATS reads this CV

Appliora's ATS Checker runs 14 checks against an uploaded file and shows the text its parser extracted. Four of them catch the mistakes QA CVs make most, and the first is one testers cause by being tidy.

• Reading order

  Testers love a matrix, and a CV with a grid of tools against proficiency, or test types against projects, is common in this role. A parser reading across the page turns that grid into a run of unattached words. Read the extracted text and check that your job titles are still whole blocks rather than interleaved with table cells.

• Consistent dates

  QA careers accumulate contract and agency stints, sometimes two overlapping in the same period. Give each engagement its own dated entry and mark contract work as contract. The check reads date ranges and reports what it could not resolve, which is exactly where an unexplained overlap becomes a question.

• Bullet quality

  This is the heaviest content check: how many bullets carry a figure and how many open with an action verb. QA bullets drift into passive process description - "testing was carried out in line with the test plan" - more than any other engineering role, because the work is procedural. Start with a verb and carry a number.

• Concrete skills

  Listing every test type as a separate skill fills the block without adding information. The check looks for recognisable skills rather than fragments, so a glossary of testing nouns scores no better than a short list of tools and techniques you can be examined on.

Templates that suit this role

• ATS Structured

  Single column and conventional headings, which is the safest way to carry a tool list and a contract-heavy history through a portal without a matrix getting scrambled.

• Tech Stack

  Gives the automation stack a full-width block, useful when you are applying for an engineer-in-test role where the framework and language matter as much as the testing approach.

• Swiss One Page

  A one-page layout for testers with under four years, where the second page would otherwise fill with a list of test types.

Related roles

• Software Engineer
• Frontend Developer
• Backend Developer
• DevOps Engineer