A QA engineer posting can describe someone who designs and runs tests by hand, someone who writes automation code most of the day, or a developer who specializes in testing. These QA engineer resume keywords are grouped so you can pick the set that matches the posting, then back each term with work a QA lead can check.
Getting ghosted on QA Engineer applications?
It usually comes down to missing keywords. Scan your resume against your target job description to find exactly what the ATS expects you to have.
Find my missing keywords
Read the list below as a menu. A tester with three years of exploratory and regression work does not need Docker on the page, and an SDET resume without a programming language will raise questions. Keep the terms that match both the posting and your actual work. If you already have a posting open, the Resume Keyword Scanner shows which of these terms it uses and which ones your resume is missing.
QA engineer resume keywords, grouped by type of work
Testing types
- Functional testing
- Regression testing
- Smoke and sanity testing
- Integration testing
- End-to-end (E2E) testing
- API testing
- Exploratory testing
- User acceptance testing (UAT)
- Cross-browser and cross-device testing
- Accessibility testing (WCAG)
- Performance and load testing
Test design and process
- Test plans and test strategy
- Test cases and test scenarios
- Acceptance criteria
- Boundary value analysis
- Equivalence partitioning
- Risk-based testing
- Requirements traceability
- Defect lifecycle and bug triage
- Root cause analysis
- Shift-left testing
- BDD and Gherkin (Given/When/Then)
Automation frameworks and languages
- Playwright
- Cypress
- Selenium WebDriver
- Appium
- JUnit, TestNG or pytest
- Jest
- Cucumber or SpecFlow
- REST Assured, or Postman with Newman
- Page object model (POM)
- Java, Python, JavaScript, TypeScript or C#
- SQL
Pipelines and test environments
- CI/CD
- Jenkins, GitHub Actions, GitLab CI or Azure DevOps
- Git and pull requests
- Docker
- Test environments and test data management
- BrowserStack or Sauce Labs
- Parallel test execution
- Flaky test management
Test management and reporting
- Jira
- TestRail
- Xray or Zephyr
- Confluence
- Allure or other test reports
Performance testing tools
- JMeter
- k6
- Gatling
- LoadRunner
Ways of working and certificates
- Agile and Scrum
- SDLC and STLC
- Release testing and sign-off
- ISTQB Certified Tester Foundation Level (CTFL)
- ISTQB Advanced Level Test Automation Engineering (CTAL-TAE)
Count the code words in the posting
QA job titles are not consistent. "QA Engineer" at one company means mostly manual testing, and at another it means writing Playwright tests in TypeScript every day. QA Analyst, QA Tester, Test Engineer, Software Engineer in Test and SDET overlap in the same way, so the requirements list tells you more than the title does.
A quick way to read it: mark every requirement that names a language, a framework or a pipeline tool. Then mark every requirement about test design, documentation or working with product owners. If most of your marks are code words, lead your summary and skills section with automation keywords. If most are process words, lead with test design and manual testing terms, and list automation tools only where you have really used them. Our guide on finding job description keywords walks through this step in more detail.
| What the posting says | What the job usually involves | Keywords to lead with |
|---|---|---|
| "Write and execute test cases," "attention to detail," "support UAT" | Mostly manual and exploratory testing, often titled QA Analyst or QA Tester | Test cases, regression testing, exploratory testing, UAT, Jira, TestRail |
| "Build and maintain automated test suites," one framework named | Automation engineer who writes test code most days | The framework, the language, page object model, CI pipeline, API testing |
| "Contribute to the test framework," "code reviews," "design for testability" | SDET, close to a developer role | Language, framework design, unit and integration tests, CI/CD, Docker, code review |
| "Own quality for releases," "define test strategy," "mentor testers" | Senior QA or QA lead | Test strategy, test plans, risk-based testing, release sign-off, quality metrics |
Mixed postings are common at smaller companies with one or two testers. For those, put the posting's automation tool and its main manual testing terms close together near the top of the page, so a reader sees both without searching. Running the posting through the Resume Keyword Scanner is a quick way to see which side of the job it leans toward.
Name the framework, the language and where it runs
"Selenium" on its own tells a reader that you have used Selenium. A QA lead usually wants four more details: which language you wrote the tests in, how the framework was structured, where the tests ran, and roughly how many there were. Compare these two versions:
Skills line only:
Selenium, Java, Jenkins, TestNG
Experience bullet:
Built and maintained a Selenium WebDriver suite in Java with TestNG (page object model, about 400 tests) that ran nightly in Jenkins against staging.
The bullet contains the same keywords. It also answers the questions a reviewer would otherwise save for the interview.
Some teams have moved from Selenium or Cypress to Playwright in recent years, and postings tend to name the framework the team uses now. If you worked on a migration, say so: "Migrated 220 Cypress tests to Playwright with TypeScript and ran them in parallel, cutting the CI run from 38 to 14 minutes." That line covers two frameworks, a language, CI and parallel execution, and it shows the work behind them.
The opposite problem is a long tool list. A skills line with nine frameworks on a resume with two years of experience makes a reader wonder how deep any of them goes. Listing tools you opened once in a tutorial is one of the common resume keyword mistakes, and in QA hiring it can surface fast, since a technical round may ask you to read or write a short test in one of them.
Bug counts, and better numbers to use
A QA manager at a payments company I recruited for had one standard reply when a resume said "Reported 400+ bugs": how many of them got fixed? A high bug count can mean careful testing. It can also mean duplicates, cosmetic issues, or tickets closed as "works as designed." On its own, the number is hard to judge.
Numbers that describe what changed are easier to read:
- Escaped defects: bugs found in production after a release, before and after your work
- Regression run time: how long the suite took before and after you changed it
- Automation coverage: the share of the regression suite that runs automatically
- Flaky test rate: how many tests failed without a real bug, and how you brought that down
- Release cadence: for example, moving from monthly to weekly releases with the same team
- Scope: test cases written or reviewed for a specific feature or release
Be careful with coverage. "Achieved 90% test coverage" makes a reader ask: coverage of what? Code coverage from unit tests, requirements coverage, and the share of manual regression cases that are automated are three different measurements. Name the one you mean.
A bullet that uses these well might read: "Cut customer-reported bugs from about 12 per release to 4 over two quarters by adding API contract tests and a risk-based regression checklist." The numbers are modest and specific, which makes them easy to believe.
Test design terms need an example next to them
Boundary value analysis, equivalence partitioning and risk-based testing appear in QA analyst and QA engineer postings, often at banks, insurers and other companies with formal test processes. In a skills list they look the same on every resume. Attached to a real feature, they show how you think about testing.
Before:
Performed boundary value analysis and equivalence partitioning.
After:
Designed test cases for a loan application form using boundary value analysis on the income and age fields, which found a rounding error at the minimum loan amount before release.
Exploratory testing works the same way. Say what you explored and what came out of it: "Ran time-boxed exploratory sessions on the new checkout flow and logged 14 issues, including 3 payment failures on older Android devices."
If the posting mentions BDD, Gherkin or acceptance criteria, say whether you wrote the scenarios with the product owner or automated scenarios someone else wrote. Both are useful, and they are different tasks.
"Jira" can describe two different jobs
One QA lead I hired for ran Xray inside Jira. When a resume listed "Jira," her first question was whether the candidate had written and organized test cases there, or only filed bugs. Very few resumes answered it, so she asked every time.
Bug tracking and test management are separate skills, and some postings ask for both. Put the tool next to the task:
- "Wrote and maintained 600+ test cases in TestRail for the iOS and Android apps, organized by release and priority"
- "Linked Xray test executions to Jira stories so product owners could see test status for each sprint"
- "Logged and triaged defects in Jira with steps to reproduce, logs and screen recordings"
The last example matters for manual testers in particular. Clear bug reports save developers time, and phrases like "steps to reproduce" and "triage" show that you know how the process works.
API, mobile and performance testing: show the depth
Postings often mention these areas in one short line, such as "API testing experience is a plus." A short line in the posting still deserves a specific line on your resume.
API testing
"Postman" on its own often reads as sending requests by hand. If you built collections that run in CI with Newman, or wrote API tests with REST Assured or pytest, say so. Then name what you checked: status codes, response schemas, authentication, or contract tests between services.
Mobile testing
Name the platforms, how you tested, and the tools: iOS and Android, real devices or emulators, Appium, BrowserStack, TestFlight builds. Mobile postings often care about testing across many devices and OS versions, and about release timing for the app stores.
Performance testing
Name the tool and the load: "Wrote k6 load tests simulating 2,000 concurrent users on the search API and found a database connection limit before the holiday sales peak." Say whether you designed the tests or ran existing scripts and read the results, since postings for performance specialists expect the first.
ISTQB and other certificates
On the European QA openings I worked on, ISTQB Foundation Level appeared in the requirements much more often than on US ones, where it was usually missing or listed as a nice extra. If you hold it, write the full name and the abbreviation once, so it matches however the posting writes it:
- ISTQB Certified Tester Foundation Level (CTFL)
- ISTQB Certified Tester Advanced Level Test Automation Engineering (CTAL-TAE)
ISTQB certificates do not expire, so the year is optional. Foundation Level is required before the advanced automation exam. A certificate does not replace experience, though: an automation posting will still look for the framework and the language in your bullets.
Moving from manual testing to automation
Automation often appears in the first lines of QA engineer postings, which leaves experienced manual testers with a wording problem: how to show the automation work they have done at its real size.
One manual tester I coached had written "exposure to automation" at the bottom of her skills list. When we went through her last job, it turned out she had kept about 35 existing Cypress tests working for a year, updating selectors after each UI release and fixing tests that broke in the pull request pipeline. That is maintenance work on a real suite, and it reads very differently from "exposure." Her new bullet:
Maintained a 35-test Cypress suite (JavaScript) that ran on every pull request in GitHub Actions; updated selectors after UI releases and replaced fixed waits with assertions to cut false failures.
The verb matters here. "Maintained," "extended," "built" and "designed" describe four levels of automation work, and a QA lead will usually ask which one you mean. If your job did not include automation, a public repository helps more than a course certificate: a small Playwright or pytest suite against a demo site, a short README, and a pipeline that runs it.
Keep your manual testing keywords too, along with the domain words from the products you tested, such as payments, insurance claims or electronic health records. QA postings in regulated industries often ask for that domain experience by name, and our overview of resume keywords by industry shows how much that vocabulary changes between fields. The AI Resume Optimizer can draft versions of a bullet that use a posting's terms; check each draft against what you actually did before you keep it.
If you are aiming at SDET roles, expect postings that read like developer jobs, with data structures, code reviews and framework design. Our software engineering resume keywords guide covers that side of the vocabulary.
Where each group of keywords belongs
- Summary: the job title as the posting writes it (QA Engineer, Quality Assurance Engineer, Software Engineer in Test), your years of experience, your testing focus and your main framework. For example: "QA Engineer with 5 years in web and API testing for B2B SaaS, building Playwright suites in TypeScript that run in GitHub Actions."
- Skills section: grouped like the lists above (testing types, automation, pipelines, tools), with the posting's most important terms first. The Resume Keyword Scanner lists the ones your draft still misses. Keep only terms you can explain.
- Experience bullets: the context behind each keyword: what you tested, with which tool, at what size, and what changed.
- Certifications: ISTQB lines and any cloud or tool certificates the posting mentions.
- Projects: automation work outside your job, with a link to the repository.
If your skills sit in two columns or a table, the text can come through out of order when an applicant tracking system reads the file, so check the layout with the ATS Resume Checker. For tailoring each section to a specific opening, see how to match your resume to a job description.


