Hire a QA engineer who owns quality, not just the test runner
To hire a QA engineer, search past the title: strong testers also sit under SDET, quality engineer and test automation engineer. Source people who have kept a real suite stable in CI, screen on flakiness and test strategy rather than tool names, and run one practical exercise before the offer.
The short version
- Decide the manual and automation split before you write the job description. It changes who you search for.
- Search four titles, not one: QA engineer, SDET, quality engineer and test automation engineer.
- Screen on how a candidate killed a flaky test. Tool names are the easiest thing on a CV to inflate.
- Keep one hands-on exercise for the final stage, because no conversation proves someone can write a stable test.
Where QA engineers actually are
The QA title is unusually unreliable. The same work ships as QA engineer at one company, SDET at a second and quality engineer at a third, while "QA analyst" often means mostly manual testing. A search on one title misses most of the market, and a search on all of them returns people who have never written a line of test code.
So filter on evidence instead. Good automation engineers leave traces: a Playwright or Cypress framework described in detail, contributions to test tooling on GitHub, posts and talks in testing communities such as Ministry of Testing, and phrases like "reduced suite run time" or "owned the regression pipeline" on a profile. Those people are mostly employed and not reading job boards, which makes this a passive sourcing job.
Two adjacent pools are worth opening on purpose. Manual testers in regulated industries such as banking and medical devices bring test design discipline and often want to move into automation. Developers who gravitated toward test infrastructure bring the code and usually lack the exploratory instinct, so probe that in the interview.
Search strings for QA engineers
Two ways to write the same search. The Boolean version is for any profile database; the plain English brief is what an AI sourcing tool reads.
BOOLEAN
("QA engineer" OR "quality engineer" OR SDET OR "software development engineer in test" OR "test automation engineer")
AND (Playwright OR Cypress OR Selenium OR WebdriverIO)
AND (API OR "REST Assured" OR Postman OR Karate)
AND (CI OR "GitHub Actions" OR Jenkins OR GitLab)
NOT (intern OR trainee)
PLAIN ENGLISH BRIEF
QA automation engineer with 4+ years who has owned a Playwright or Cypress suite running in CI,
tests REST APIs as well as the UI, and has worked on a team shipping at least weekly.
Remote, US time zones.
VARIANT FOR A MANUAL HEAVY ROLE
QA analyst with exploratory and regression testing experience in a regulated product
(fintech, healthcare or medical devices), writes clear test cases and bug reports, some API testing.
What the QA engineer market looks like in 2026
Federal data from the BLS Occupational Outlook Handbook, read 5 October 2026. BLS files QA engineers under software quality assurance analysts and testers.
| Measure | Figure | What it means for your search |
|---|---|---|
| Median annual wage, QA analysts and testers | $104,300 (May 2025) | Half earn more. Senior SDETs in large tech markets sit well above the median. |
| Jobs held | About 187,600 (2025) | A small occupation next to software developers, so the pool is shallow per city. |
| Projected growth, QA analysts and testers | 6 percent, 2025 to 2035 | Steady demand, not a boom. Competition is mostly with developer roles for the same people. |
| Openings per year | About 106,100 | This figure covers developers, QA analysts and testers together, not testers alone. |
BLS does not publish a time to fill for this role. Treat any single number you see quoted as a guess.
From a QA brief to a ranked list
A plain English brief read into editable filters, then candidates ranked against the must-haves.
Paste the brief above and the filters come back editable. Everyone is judged against the must-haves: someone who lists Selenium but has never touched CI drops below the people who have, and nobody is removed from the list.
What to assess, and the questions that show it
Five competencies separate a QA engineer from a script recorder. Each card is a question, what a strong answer contains, and the follow-up for a thin one.
For your last release, how did you split coverage between unit, API and end to end tests?
A deliberate split with reasons, and one risky area they chose to test by hand through exploratory sessions rather than automate.
What did you decide not to test, and what happened?
Tell me about an automation suite you owned. What made it trustworthy, or not?
Concrete fixes for flakiness: proper waits instead of sleeps, isolated test data, and a run time they cut down and can name.
When a test failed intermittently, how did you decide whether the test or the product was at fault?
Describe a bug report you wrote that got fixed quickly.
Exact steps, environment, expected against actual, and the severity they argued for and why.
Was there a bug you rated higher than the developer did? How did that end?
How do you test a REST or GraphQL endpoint beyond the happy path?
Negative cases such as an expired token or a malformed body, contract checks, and the tool they used, like Postman or REST Assured.
Tell me about a time you held a release.
They made the case with evidence to the product manager and kept the relationship, rather than becoming the team's blocker.
A hiring process for QA engineers, step by step
Six stages. The practical exercise sits late on purpose: it is the most expensive stage for both sides, so only a short list should reach it.
- Write the role around the split State the ratio of manual to automation work, the stack and who owns the pipeline. Start from the QA engineer job description and cut what does not apply. "About 70 percent automation in Playwright and TypeScript, 30 percent exploratory testing on new features."
- Source on evidence, not title Run the search strings above, then read profiles for suites owned and problems fixed. Shortlist 15 to 25 people before any outreach goes out.
- Reach out with the problem Testers respond to a specific quality problem, such as a slow regression run, far more than to a generic opening. Say which framework and which pipeline they would own.
- Run a structured first round Twenty minutes on test strategy, automation and triage, scored against a fixed rubric. Use the QA engineer interview questions as the bank.
- Set one practical exercise Give a small app with planted bugs and ask for a short test plan plus a few automated tests. Keep it under 2 hours and review it together.
- Final round with the people they will work beside A developer and the product manager. Decide on written, independent scores before anyone discusses the candidate.
What goes wrong when hiring testers
Do
- Ask how they decided what not to automate
- Have an engineer who has maintained a suite write the rubric
- Check that API testing experience is real, not a Postman collection someone else wrote
- Tell candidates the release cadence; it decides how the job feels
Do not
- Filtering on one framework when the skill transfers in weeks
- A take-home that runs into a whole weekend
- Treating QA analyst and SDET as the same job
- Letting the interview turn into a tool quiz
How The Cognitive fits a QA search
The Cognitive covers the first half of the process. AI sourcing searches ~900M public profiles from a brief like the one above, reveals verified emails and phone numbers for the people you keep, and shows an "Open to work" badge and tenure per role. A reveal costs 4 credits for an email and 12 for a phone, charged only when a value comes back.
The first round is a live, two-way AI video interview of 10 or 20 minutes. The rubric stays fixed for the role while the follow-ups adapt to each answer, so a vague claim about "building the framework" gets a second question. It does not run code, so the practical exercise stays. Pricing: AI Sourcing and AI Interview each start at $99/month.
What the hiring team reads after the first round
An example report: each criterion scored 1 to 5, overall written feedback, and resume claims marked against what was said.
For a QA role, the useful part is the claim check. If a resume says "built the automation framework from scratch", the AI can probe it as one of up to 5 resume claims and mark it verified, refuted or unclear. Nothing is rejected automatically; your team decides who moves on.
More for QA hiring
QA engineer job description · QA engineer interview questions · AI interviewer for QA engineers · AI sourcing tool · Best technical recruiting tools · Boolean search generator
Try it
Paste your QA brief and see who comes back. Start free at app.thecognitive.io/signup. The free trial includes 100 sourcing credits.
Frequently asked questions
How much does it cost to hire a QA engineer?
Start with salary. BLS puts the median annual wage for software QA analysts and testers at $104,300 in May 2025, and automation specialists in large tech markets usually earn more. On top of that come recruiting costs: an agency fee if you use one, or your own sourcing and interview time. AI Sourcing and AI Interview each start at $99/month on The Cognitive.
Where can I find QA engineers?
Mostly not on job boards. Search profile databases across QA engineer, SDET, quality engineer and test automation engineer, look at testing communities such as Ministry of Testing, and read GitHub for people who maintain test tooling. Manual testers in regulated industries moving into automation are an underused pool.
How long does it take to hire a QA engineer?
No public source publishes a reliable time to fill for this role, so be wary of a single quoted number. What you control is the gap between stages: a shortlist reviewed within 2 days, a first round candidates book themselves, and a practical exercise reviewed the same week. Most lost QA candidates are lost in those gaps.
What is the difference between a QA engineer and an SDET?
In practice the overlap is large and companies use the titles differently. SDET usually signals a developer level of coding: building and maintaining the test framework itself. QA engineer can mean that, or a role that mixes automation with exploratory and manual testing. Write down the split before you search, then search both titles.
Should a QA engineer interview include a coding test?
For an automation role, yes, but late and short. A conversation shows how someone reasons about flakiness, coverage and triage; only a hands-on exercise shows they can write a stable test. Keep it under 2 hours and review it with the candidate rather than grading it silently.
Can an AI interview tell whether a QA candidate really built their framework?
It can test whether the story holds. The AI asks how the suite was structured, what made tests flaky and what they changed, and follows up until the answer is specific. A resume claim such as "built the framework" can be one of up to 5 claims marked verified, refuted or unclear. It does not execute code.
Does The Cognitive reject QA candidates automatically?
No. Nothing is rejected automatically. Each report gives a 1 to 5 score per criterion, overall written feedback, a transcript and a recording. If the candidate came from your ATS, one of 60+ integrations writes a note back, and your team moves the stage.
Explore: Hire a software engineer · Best technical interview software · Boolean search string examples · Pricing