QA Engineer resume example

This example resume shows how a QA Engineer can present automation, API testing and release-quality work with specific, believable outcomes. Alex Morgan is a fictional candidate based in Manchester.

Start with this template

Alex Morgan

QA Engineer

Manchester

Professional summary

QA Engineer with six years' experience in web and API test automation across agile delivery teams. Builds maintainable Cypress and REST Assured suites, embeds checks into CI pipelines and reports quality risks clearly to developers and product owners.

Experience

QA Engineer · Brightfield Software
2021 – Present
- Built a Cypress regression suite of 220 tests that ran on every pull request, cutting manual regression effort from three days to under one day per release
- Developed REST Assured and Postman API checks integrated into GitHub Actions, catching contract-breaking changes before merge and reducing staging defects by 30%
- Created a dashboard tracking defect escape rate and flaky tests, helping the team reduce flaky failures from 12% to 4% over two quarters
Junior QA Analyst · Northgate Digital Services
2018 – 2021
- Executed and documented exploratory and regression testing for a customer portal, logging 150+ reproducible defects with clear steps and environment details
- Maintained test data sets and environment documentation, making regression runs repeatable and shortening test setup time by about 40%
- Partnered with developers and product owners in backlog refinement to write testable acceptance criteria, reducing story rework during sprint reviews

Skills

Test automation · Cypress · Playwright · API testing · REST Assured · Postman · Jira · CI/CD (GitHub Actions) · SQL · Exploratory testing

Education

BSc, Computer Science — University of Salford (2018)

This example is fictional and written for illustration. Replace every name, company, date and number with your own facts.

Name the tools you actually used for each test layer (UI, API, performance) inside bullets, not only in the skills list, so recruiters see where they applied.
Quantify automation impact with something measurable: regression time saved, flaky test rate, or defects caught before release.
Show collaboration with developers and product owners, such as refining acceptance criteria, since QA work happens early in delivery as well as at the end.
Mention how tests run in CI, including the trigger and pipeline tool, to separate automated suites from scripts run by hand.
Include evidence of judgment, like risk-based test selection or release-readiness input, rather than only listing test execution tasks.

Should a QA Engineer resume focus on manual or automated testing?

Reflect what the job advert asks for. If you do both, show how they complement each other: exploratory testing to find new risks, automation to protect stable behaviour. Give each a concrete outcome.

How do I show impact if I do not own release decisions?

Use metrics you influenced: defects found before release, regression time saved, flaky test reduction or escape rate. Describe your contribution plainly, such as supplying risk information that informed the release decision.

Is it worth listing certifications like ISTQB?

Yes, if you hold one, list it briefly in education or a certifications line. Employers often treat it as a supplement, so your practical results in the experience section usually carry more weight.