QA Engineer Resume Keywords: Manual, Automation and SDET

Work out the job family before you pick keywords

Three jobs hide behind one title. A QA Analyst posting is written around process — test plans, traceability, UAT support, sign-off. A QA Automation Engineer posting is written around a stack — a language, a runner, a CI server. An SDET posting is written around engineering — code review, unit and integration coverage, test infrastructure other engineers depend on. The keyword overlap between the first and the third is small, and the ATS is matching against whichever one the recruiter pasted in.

The quick test: count how many requirements name a piece of software. If most of them do, the screen is a tool match and your skills block has to carry those exact product names. If most requirements describe activities — “define test strategy”, “coordinate UAT” — the screen is a process match and your bullets need the process nouns instead.

Testers lose most often in the middle case, where a posting names Selenium and also asks for exploratory testing. Cover both explicitly. Neither one implies the other to a keyword search.

Framework names date a resume faster than anything else

Selenium is still the highest-volume automation keyword and still worth listing if you have used it — it remains the default in Java-based enterprise suites. But Playwright and Cypress now appear across a large share of front-end automation postings, and a search for either will never match “Selenium”. Keyword matching has no notion of an equivalent tool. If you have shipped tests in Playwright, write Playwright.

The same applies one layer down. Postman, REST Assured and Newman are three separate strings at the API layer. “CI/CD” matches the concept but not a search for Jenkins, GitHub Actions or Azure DevOps, and postings almost always name the server rather than the concept.

Language matters more than testers expect, because a Java shop cannot adopt your Python suite. Put the language your automation is written in on a plain-text skills line, not only inside a bullet where a skills-block search will miss it.

Which QA keywords carry the most weight

Not every term on the lists above does equal work. These are the ones that most often act as knockout criteria in QA screening, and why.

Test automation

The most common hard requirement in current QA postings. Absent, and most automation roles filter you before a human reads anything.

Selenium, Playwright, Cypress

Name every one you have actually used. They are matched as separate strings; no recruiter search expands one into the others.

API testing

Increasingly the majority of a modern suite. Pair the discipline with the tool, because both get searched separately.

CI/CD plus the named server

“Continuous integration” matches the concept, “Jenkins” or “GitHub Actions” matches the posting. Write both forms.

SQL

Badly underrated. A large share of QA postings expect direct data validation, and it is a cheap term to be missing.

ISTQB Foundation

A genuine filter in the UK, Europe and India; largely ignored by US employers. Keep it, but do not lead with it for US roles.

Agile testing

Often used as a process-fit knockout. Name the ceremonies you actually took part in rather than the word “Agile” on its own.

Performance testing / JMeter

A specialty, not a default. Only claim it with a real load test behind it — but if you have one, it separates you from the field.

ATS keywords for a QA Engineer Resume

Use these as a checklist — include the ones that genuinely apply to you, matched to the wording of the job you are targeting.

Titles a QA resume should also match

Recruiters search titles as well as skills. If your last job title was internal jargon, put the market-standard equivalent in brackets beside it so both strings exist on the page.

QA Engineer

The broadest term, and the right headline title if your work spans manual and automated testing.

SDET / Software Development Engineer in Test

Write both forms once. US tech employers search the acronym far more often than the expansion.

Test Automation Engineer

The usual phrasing for the same job in UK and European postings.

QA Analyst

Signals a process-and-documentation role. Include it only if that is the work you want; it can filter you out of engineering-heavy screens.

Quality Assurance Engineer

Some ATS configurations do not treat “QA” and “Quality Assurance” as the same token, so put the unabbreviated form in your summary once.

How to get a QA Engineer Resume past the ATS

• Include both acronyms and full terms (e.g., 'API Testing' and 'Application Programming Interface Testing') as different ATS may search for either variant
• List specific testing types you've performed (regression, smoke, sanity, UAT) rather than generic 'testing experience' to match precise job requirement filters
• Mention programming languages used for test automation (Java, Python, JavaScript) in a dedicated skills section and within context of achievements
• Specify test management and defect tracking tools by exact name and version where relevant (e.g., 'JIRA', 'Bugzilla', 'Azure DevOps') as these are common ATS filters
• Use standard QA terminology such as 'test coverage', 'defect density', and 'test execution' rather than paraphrased alternatives to align with industry-standard searches
• Include methodologies explicitly (Agile, Scrum, Waterfall, DevOps) as these are frequently used as knockout criteria in ATS screening

Four things that sink a QA resume before a human sees it

Before & after: QA Engineer Resume bullets

QA Engineer Resume keywords — FAQ