What should a QA tester put on a resume?

The products and features you tested, the kinds of testing you did, the tools you used, and numbers: bugs found, critical issues caught before release, test cases owned, and any time you saved.

How do I move from manual QA to automation on my resume?

Show any automation you've done, even small: scripts, a few Selenium or Playwright tests, API checks in Postman. Add a project that automates a real app, and list the language you wrote it in.

What are the top skills for a QA engineer resume?

A test automation framework (Playwright, Selenium or Cypress), a programming language, API testing, CI integration, and test planning. Add performance or mobile testing if the role needs it.

How to write a QA engineer or software tester resume

By Mubeen Jawed, founder of ResumeForDev · Updated November 7, 2026

Short answer

A QA engineer resume should show how your testing changed release quality and speed, not just which test cases you wrote. Use numbers like automated coverage, regression time, escaped defects and release frequency, for example “Automated 420 regression tests in Playwright, cutting the release check from 2 days to 40 minutes.” Name your tools (Selenium, Playwright, Cypress, Postman, JMeter), the kind of testing you did, and the CI system your tests run in.

Key points

Write testing as outcomes: escaped bugs, regression time, release speed.
Manual testers: show the scale and the bugs that mattered.
Automation and SDET roles: name the framework, language and CI.
API, performance and mobile testing are separate keywords. List the ones you've done.

Manual QA vs. automation vs. SDET

QA job titles cover very different work. A manual QA tester resume should show the products and test plans you owned and the critical bugs you caught. A QA automation engineer resume should lead with frameworks and coverage. An SDET (software development engineer in test) resume reads close to a developer resume: test infrastructure, code, and CI. Match your headline and first bullets to the title on the posting.

Before and after

Before:Responsible for testing the web application and reporting bugs.

After:Owned test plans for the checkout and payments flows across web and iOS, logging 180+ defects in a quarter, including 3 payment-blocking issues caught before release.

QA metrics you can put on a resume

Quality numbers for QA bullets
Metric	Example phrasing
Automated tests	automated 420 regression cases
Regression time	cut the full regression run from 2 days to 40 minutes
Escaped defects	reduced production bugs per release from ~12 to 3
Flaky tests	brought flaky-test rate from 9% to under 1%
Release cadence	enabled a move from monthly to weekly releases
Coverage	raised API test coverage to 85% of endpoints

Example QA engineer bullets

Built a Playwright and TypeScript end-to-end suite (300 tests) running in parallel in GitHub Actions, blocking merges on failure.
Wrote 150 Postman and REST Assured API tests covering auth, orders and refunds, catching a pagination bug that affected 8% of order lookups.
Ran JMeter load tests before Black Friday that exposed a database connection limit at 1,200 concurrent users, fixed before launch.
Replaced a brittle Selenium suite with Cypress, cutting average run time 60% and flaky failures from 15 a week to 2.
Introduced a risk-based regression checklist for mobile releases, reducing escaped defects per release by about half.

QA skills section

Automation: Playwright, Selenium WebDriver, Cypress, Appium
Languages: Java, Python, TypeScript or JavaScript
API and performance: Postman, REST Assured, JMeter, k6
Process: test planning, regression testing, exploratory testing, BDD (Cucumber)
Tools: Jira, TestRail, Git, Jenkins or GitHub Actions

If the job description lists specific test types (accessibility, security, mobile), mirror the ones you've actually done. Pull its exact wording into your bullets with the approach in tailoring a resume to a job description.

On ResumeForDev, set your target role to “QA Automation Engineer”. Without a job post, the keyword check falls back to a general software vocabulary, so for this role it's worth pasting the job description. Paste a job description and the keyword check uses that post's terms instead; on Pro, the writer also tailors the bullets to it. Before writing, it asks follow-up questions about the numbers above, and it removes any number or skill you never gave it. Your first resume is free.

Frequently asked questions

What should a QA tester put on a resume?: The products and features you tested, the kinds of testing you did, the tools you used, and numbers: bugs found, critical issues caught before release, test cases owned, and any time you saved.
How do I move from manual QA to automation on my resume?: Show any automation you've done, even small: scripts, a few Selenium or Playwright tests, API checks in Postman. Add a project that automates a real app, and list the language you wrote it in.
What are the top skills for a QA engineer resume?: A test automation framework (Playwright, Selenium or Cypress), a programming language, API testing, CI integration, and test planning. Add performance or mobile testing if the role needs it.