Boolean search strings for QA engineers: manual vs. automation, frameworks, ISTQB and the manufacturing collision
On this page
- Specialties, tools and certifications that change what a QA search finds
- Ten Boolean strings by type of QA work
- What LinkedIn, Indeed and Google actually support
- Narrowing by product, stack and test ownership
- False positives worth excluding with NOT
- A worked example: three passes on a Playwright automation search
- What a search cannot verify
- Questions people ask
QA engineer searches go wrong in two directions. "Quality assurance" pulls in manufacturing quality engineers, pharmaceutical QA specialists, food safety auditors and call center QA analysts who score phone calls. Narrow to software, and the list still mixes manual testers who write test cases in a spreadsheet, automation engineers who build frameworks, SDETs who write as much code as developers, performance testers and QA managers. The client usually wants one of these, and the title rarely says which.
The tools and the kind of testing sort them. Below are ten strings by type of QA work, and what LinkedIn, Indeed and Google support as of October 2026. For screening once you have a list, see the QA engineer phone screen questions.
Specialties, tools and certifications that change what a QA search finds
| Specialty | Terms candidates write | Common titles |
|---|---|---|
| Manual and functional testing | test cases, test plans, regression, exploratory testing, TestRail, Jira | QA analyst, software tester, QA engineer |
| UI automation | Selenium, Playwright, Cypress, WebdriverIO, page object model | QA automation engineer, test automation engineer |
| API and back-end testing | Postman, REST Assured, contract testing, pytest | QA engineer, SDET |
| Mobile | Appium, XCUITest, Espresso, device farms | Mobile QA engineer |
| Performance | JMeter, k6, Gatling, LoadRunner, load testing | Performance test engineer |
- ISTQB. The International Software Testing Qualifications Board's Certified Tester Foundation Level (CTFL) v4.0 is its entry point, and its Certified Tester Advanced Level Test Automation Engineering (CTAL-TAE) v2.0 requires the Foundation Level certificate and practical experience, as of October 2026. Candidates write "ISTQB," "CTFL" or "ISTQB certified tester."
- Language matters with automation. Automation engineers usually work in Java, Python, JavaScript, TypeScript or C#. Put the client's language in a required block for automation roles.
Ten Boolean strings by type of QA work
Swap in the framework, language and product type from your own intake; these are examples.
Automation and SDET
1. UI automation engineer, TypeScript — LinkedIn general search
("qa automation engineer" OR "test automation engineer" OR "qa engineer" OR sdet) AND (playwright OR cypress OR webdriverio) AND (typescript OR javascript) NOT ("iso 9001" OR gmp OR "supplier quality" OR manufacturing)
2. Selenium and Java automation engineer — LinkedIn general search
("qa automation engineer" OR "automation test engineer" OR sdet) AND (selenium OR "selenium webdriver") AND java AND (testng OR junit OR cucumber)
3. SDET who builds frameworks — LinkedIn Recruiter, Job titles + Keywords filters
(sdet OR "software development engineer in test" OR "software engineer in test") AND ("test framework" OR "automation framework" OR "built the framework") AND ("ci/cd" OR jenkins OR "github actions" OR "gitlab ci")
4. API test engineer — LinkedIn Recruiter, Keywords filter
("qa engineer" OR sdet OR "api test engineer") AND ("api testing" OR "rest assured" OR postman OR "contract testing" OR pact) AND (python OR java OR typescript)Manual, mobile and performance
5. Manual QA analyst — Indeed Smart Sourcing
("qa analyst" OR "software tester" OR "qa tester" OR "manual tester") AND skill: ("test cases" OR "regression testing" OR "exploratory testing") AND (jira OR testrail OR zephyr) NOT ("quality control" OR "call center" OR haccp)
6. Mobile QA engineer — LinkedIn general search
("mobile qa engineer" OR "qa engineer" OR "mobile test engineer") AND (appium OR xcuitest OR espresso) AND (ios OR android)
7. Performance test engineer — LinkedIn general search
("performance test engineer" OR "performance engineer" OR "performance tester") AND (jmeter OR k6 OR gatling OR loadrunner) AND ("load testing" OR "stress testing" OR "performance testing")Credentials, entry level and X-ray
8. ISTQB-certified tester — Indeed Smart Sourcing
("qa engineer" OR "qa analyst" OR "software tester") AND (istqb OR ctfl OR "certified tester") AND skill: ("test planning" OR "test design" OR "defect tracking")
9. Entry-level QA with a computing degree — Indeed Smart Sourcing
("qa analyst" OR "junior qa" OR "qa intern" OR "software tester") AND fieldofstudy: ("computer science" OR "information technology" OR "software engineering") AND (selenium OR python OR "test cases")
10. Public profiles by stack and metro — Google X-ray
site:linkedin.com/in ("qa automation engineer" OR sdet) "playwright" "typescript" "raleigh" -jobs -recruiterWhat LinkedIn, Indeed and Google actually support
LinkedIn's Boolean help page requires capital AND, OR and NOT, supports quotes and parentheses, and does not support wildcards, as of October 2026. Testers write "QA," "Q.A." and "quality assurance," "end-to-end," "e2e" and "end to end," and "CI/CD" with and without the slash, so write variants out rather than hoping for a stem match. LinkedIn Recruiter's Boolean page lists Job titles among the Boolean filters and warns that too many facets in one query can cause problems; keep the framework block in Keywords and the title block in Job titles.
Indeed's Boolean
guide documents AND, OR, NOT, quotes and parentheses, a skill: field for the skills
section, and fieldofstudy: and school: for education. Manual testers and
career changers are often better represented on job boards, which is why strings 5, 8 and 9 are written
for Indeed.
Google's search operators page
documents quotes, site:, the minus sign and filetype:, but not OR. Public code
is another source for automation engineers: a repository with a well-structured test suite says more
than a profile. If you look there, contact candidates through channels they have chosen to publish.
Narrowing by product, stack and test ownership
Product type narrows quickly. Testing a consumer mobile app, a payments platform, a medical device's software and a data pipeline are different jobs. Ask the client what it ships and where bugs hurt most, then add domain words such as "payments," "healthcare," "embedded" or "data validation" as an optional block.
Stack comes next for automation roles. Language first, framework second, CI system third: an engineer who writes TypeScript tests in GitHub Actions pipelines can learn a new framework faster than a new language. For manual roles, the domain and the defect-tracking habits matter more than any tool.
Ownership words help with seniority. "Designed the framework," "introduced," "reduced flaky tests" and "defined the test strategy" tend to come from senior engineers; "executed test cases" and "maintained scripts" tend to come from earlier-career testers. Use them to rank, since thin profiles leave them out.
False positives worth excluding with NOT
- Manufacturing and supplier quality. "Quality engineer," "supplier quality," "ISO 9001," "Six Sigma" and "PPAP" profiles belong to physical products. Exclude them for software roles; for inspection roles, see the quality inspector screening questions.
- Pharmaceutical and food QA. "GMP," "GxP," "HACCP" and "batch record" profiles are regulated manufacturing QA. Keep "GxP" only if the client tests validated software for life sciences.
- Call center QA. "Quality analyst" profiles in contact centers score calls. Exclude "call center" and "call quality."
- Developers who mention testing. Many software engineers list unit testing and Jest. Require QA titles or test strategy terms; for developer searches, see Boolean search strings for software engineers.
- The Q&A collision. "QA" can be read as Q&A in some contexts. Always pair it with a testing word.
A worked example: three passes on a Playwright automation search
An invented search, shown as it actually gets narrowed.
Intake: A software company with a React web app needs a QA automation engineer to build out Playwright end-to-end tests in TypeScript, run them in GitHub Actions, and cut down flaky tests.
Pass 1: "qa engineer" AND automation: a long list including
manufacturing quality engineers, Selenium-Java testers, manual testers who mention automation once, and
developers.
Pass 2: ("qa automation engineer" OR "test automation engineer" OR sdet) AND
(playwright OR cypress) AND (typescript OR javascript) NOT ("iso 9001" OR manufacturing OR gmp):
much closer, though some profiles list Playwright from a short trial.
Pass 3: add AND ("github actions" OR "ci/cd" OR pipeline) AND (flaky OR
"test strategy" OR framework). Those terms tend to come from engineers who own a suite in CI
rather than run someone else's. The list is short enough to call, and each candidate is asked how they
tracked down their last flaky test.
The language and CI blocks did the narrowing. For QA automation, how tests run and who maintains them tells you more than the framework name.
What a search cannot verify
A string can find someone whose profile names the right framework and language. It cannot show whether they find the bugs that matter, how they push back when a release is not ready, or whether their tests are maintainable. The QA engineer phone screen questions test that thinking, the interview guide for QA engineers covers later rounds, and the QA engineer job description template helps pin down manual versus automation scope before you search.
Questions people ask
Why does a QA engineer search return manufacturing and food safety profiles?
Because quality assurance and quality engineer are also titles in manufacturing, pharmaceuticals, food production and call centers. Require software terms such as test automation, Selenium, Playwright, API testing or test cases, and exclude "ISO 9001," GMP, HACCP and "supplier quality" when the role is software.
What is the difference between a QA engineer and an SDET?
It varies by company, but SDET, or software development engineer in test, usually means someone who writes test code and frameworks with the same rigor as product code, while QA engineer can mean anything from manual testing to automation. Search for the work, such as framework design or CI pipelines, rather than relying on either title.
Is ISTQB certification worth searching for?
As an optional term. The International Software Testing Qualifications Board's Certified Tester Foundation Level (CTFL) is widely held, and its advanced Test Automation Engineering certification (CTAL-TAE) requires the Foundation Level first. Many strong automation engineers hold neither, so do not require it unless the client asks.
Should I search for a specific automation framework?
Include the client's framework and language, but keep alternatives in an OR block. An engineer fluent in Selenium with Java can learn Playwright, but switching languages takes longer than switching tools. If the client's stack is TypeScript, the language matters more than the framework name.