Last Minute Resume
Try for free

QA Engineer resume example

QA and software testing resumes should show both sides of the job: the bugs you caught before customers did, and the automation that made testing faster. Name your frameworks and put numbers on coverage and release quality.

Free to start. No card needed.

Why this resume works

  • Every bullet starts with a verb and ends with a result, most with a number.
  • The skills a QA engineer job post asks for appear in the Skills section and again inside the bullets.
  • A single, standard layout (Classic) that applicant tracking systems read top to bottom.
  • Standard headings (Summary, Work Experience, Education, Skills) so the ATS files each part correctly.

Hannah Lee

QA Automation Engineer

hannah.lee@email.com • (604) 555-0147 • Vancouver, BC • linkedin.com/in/hannahlee

Professional Summary

QA engineer with 4 years of experience in manual and automated testing for web and mobile apps. Builds test frameworks in Selenium, Playwright and Rest Assured, and works inside Agile teams to stop bugs before release. ISTQB certified.

Work Experience

QA Automation Engineer

2022 – Present

Medisync Health

  • Built a Playwright and TypeScript test suite of 650 tests that runs on every pull request in 12 minutes.
  • Automated 80% of the regression suite, cutting release testing from 5 days to 1.
  • Added API tests with Rest Assured for 120 endpoints; production bugs fell 45% in a year.
  • Ran performance tests in JMeter before a launch and found a bottleneck that would have failed at 2,000 users.

Software Test Engineer

2020 – 2022

Quickcart

  • Wrote and ran 1,200 manual test cases for the Android and iOS shopping apps.
  • Logged and tracked 900+ defects in Jira with clear steps, screenshots and severity.
  • Built the team's first Selenium framework in Java with TestNG and page objects.

Education

BASc, Electrical Engineering

2016 – 2020

University of British Columbia, Vancouver, BC

Skills

Automation: Selenium WebDriver, Playwright, Cypress, Appium, Rest Assured, Postman

Languages and frameworks: Java, TypeScript, Python, TestNG, JUnit, Cucumber (BDD)

Process and tools: Manual testing, regression testing, API testing, JMeter, Jira, TestRail, Jenkins, Git, Agile/Scrum

Certificates

ISTQB Certified Tester Foundation Level (CTFL), ISTQB

2021

Example QA engineer resume · Classic template · made-up person

QA Engineer resume summary examples

Two or three lines at the top: your years of experience, your strongest skills, and the result you are known for.

This example

QA engineer with 4 years of experience in manual and automated testing for web and mobile apps. Builds test frameworks in Selenium, Playwright and Rest Assured, and works inside Agile teams to stop bugs before release. ISTQB certified.

Entry level

Software tester with ISTQB Foundation certification and hands-on practice writing test cases, logging bugs in Jira and automating web tests in Selenium with Java. Detail-oriented and ready to join an Agile team.

Experienced

QA lead with 9 years of experience building test strategy and automation for fintech platforms. Leads a team of 7 testers, owns release quality for 3 products, and brought escaped defects down by 70%.

Write your own with the free summary generator →

QA Engineer resume bullet points

Use them as a pattern, not a copy: swap in your own numbers. If you don't have a number, describe the before and after.

  • Automated 80% of the regression suite, cutting release testing from 5 days to 1.

  • Built a Playwright suite of 650 tests that runs on every pull request in 12 minutes.

  • Added API tests for 120 endpoints, lowering production bugs by 45% in a year.

  • Found a performance bottleneck in JMeter load tests that would have failed at 2,000 users.

  • Wrote and ran 1,200 manual test cases across Android and iOS apps.

  • Logged 900+ defects in Jira with clear steps, making fixes faster for developers.

  • Built a Selenium framework with page objects and TestNG that the team still uses.

  • Joined sprint planning to add acceptance criteria, catching unclear requirements before coding.

Turn your own duties into bullets with the free bullet point generator →

Skills and ATS keywords for a QA engineer resume

Skills that often appear in QA engineer job posts. Add only the ones you really have, in the same words the post uses, and check every job post for its own.

  • Manual testing
  • Automation testing
  • Selenium
  • Playwright
  • Cypress
  • Appium
  • API testing
  • Postman
  • Rest Assured
  • Java
  • Python
  • TestNG
  • Cucumber
  • Regression testing
  • Performance testing
  • JMeter
  • Jira
  • Test cases
  • Agile
  • CI/CD
Cover letter examples →See which keywords your resume is missing for a real job →

How to write a QA engineer resume

  1. 01

    Show manual and automation

    Most QA posts ask for both. Name the automation tools and languages you use, and keep one bullet about exploratory or manual testing.

  2. 02

    Count what you prevented

    Bugs caught before release, fewer escaped defects, shorter regression cycles: these are the numbers that show a tester's value.

  3. 03

    Name the kinds of testing

    Regression, API, performance, mobile and accessibility testing are separate keywords in job posts. List the ones you have done.

  4. 04

    Mention the ISTQB

    In Canada, Europe and India the ISTQB Foundation certificate is a common requirement for testing roles. US employers ask for it less often but still count it in your favor.

QA Engineer resume, section by section

Header and title

Hannah's title is "QA Automation Engineer", which tells the reader she's beyond manual testing before they read a bullet. Use the title closest to the posting: QA Engineer, SDET, Test Automation Engineer or Software Tester.

Summary

Her summary covers both manual and automated testing, the platforms (web and mobile), her frameworks (Selenium, Playwright, Rest Assured), how she works (inside Agile teams) and her ISTQB certification. It answers the three questions QA managers ask: what you test, with what, and how.

Work experience

Her bullets measure two things: speed and prevention. A 650-test Playwright suite running in 12 minutes, regression cut from 5 days to 1, production bugs down 45% after API tests on 120 endpoints, and a performance bottleneck found before launch. Each says what would have gone wrong without her.

Showing progression

Her earlier role is mostly manual: 1,200 test cases and 900+ defects logged, then the team's first Selenium framework. That's the common path from manual to automation, and laying it out this way answers the question before an interviewer asks it.

Skills

Grouped into automation tools, languages and frameworks, and process and tools. Name the kinds of testing too (regression, API, performance), since many job posts screen for them.

Certification and education

ISTQB Foundation is widely recognized for QA roles, so list it in its own section. Any degree works; Hannah's is in electrical engineering.

Entry-level to senior QA engineer resume bullet points

Manual tester (0–2 years)

  • Wrote 600 test cases from user stories and ran them each sprint for a banking web app.
  • Logged 350 defects in Jira with steps, logs and screenshots; 95% were accepted as valid.
  • Tested the Android app on 12 devices and OS versions before each release.
  • Ran smoke tests on every staging build and stopped 4 releases with critical bugs.

Automation engineer (3–5 years)

  • Built a Cypress suite of 400 tests that runs in parallel in CI in 9 minutes.
  • Automated the top 50 user journeys on Android and iOS with Appium.
  • Added contract tests between 6 microservices, catching breaking API changes before merge.
  • Cut flaky tests from 12% to under 1% by fixing waits and isolating test data.

QA lead (6+ years)

  • Lead 6 QA engineers across 3 product squads and own release sign-off.
  • Set quality gates in Jenkins (coverage, failed tests, open critical bugs) that every release must pass.
  • Cut escaped defects from 30 a quarter to 8 by bringing testers into story refinement.
  • Introduced risk-based testing that shortened regression for minor releases from 3 days to 1.

Mistakes to avoid on a QA engineer resume

  • Counting test cases only

    "Executed 2,000 test cases" shows effort, not value. Add what the testing caught, how fast it ran, or how release quality changed.

  • Automation with no result

    "Automated regression tests in Selenium" leaves out why it mattered. Say how much time it saved or how many bugs it caught before release.

  • A list of every tool

    Selenium, Cypress, Playwright, Appium, TestComplete, UFT and Katalon together suggest shallow use of each. List the ones you've built real suites with.

  • Not naming the product

    Testing a banking app, a health platform or a game are different jobs. Say what you tested, on which platforms, and for how many users.

Key takeaways

  • Show both manual and automation work, and how you moved between them.
  • Count what you prevented and how much faster testing became.
  • Name the kinds of testing and the frameworks you built.
  • Put ISTQB or other certifications in their own section.

Questions about QA engineer resumes

Should I write QA engineer or software tester?
Use the title the job post uses. If you automate tests, "QA Automation Engineer" or "SDET" often brings better roles and pay.
How do I move from manual to automation testing?
Automate part of your current test suite, even a small one, and put it on GitHub. Then add a bullet about it and the language you used.
Is Selenium still worth listing?
Yes. It's still among the most requested testing tools. Add Playwright or Cypress too if you know them, since newer teams often use them.
How do I write a QA resume with no experience?
Pick a public website or app and test it properly: write a short test plan and test cases, log real bugs with clear steps, and build a small Selenium or Playwright suite on GitHub. Add the ISTQB Foundation certificate if you have it.
Should I mention performance or security testing?
Yes, even if it's one bullet. They're specialist skills that many testers don't have. Name the tool, such as JMeter, k6 or OWASP ZAP, and what you found.

Sources

Duties, pay, education and job outlook for software developers, quality assurance analysts, and testers in the US: U.S. Bureau of Labor Statistics, Occupational Outlook Handbook.

Your QA engineer resume, written with you.

Tell the AI about your work. It asks for the numbers, writes the bullets, and checks the ATS score as you go.

Start free