Updated October 2026
A startup QA engineer interview needs four stages: a screen, a test strategy session on your own product, a pairing session on a flaky test, and a final round with a founder. Between them they test whether the candidate will make developers ship faster or add a queue at the end of each sprint.
Spend more time on what a candidate would choose not to test than on what they would test. Anyone can list test cases. The QA engineers who speed a team up can explain which risks they would accept, and why, before you ask.
Our illustrative example runs through the questions: a Seed-stage consumer app with six developers, a fortnightly release, and two founders who test by hand the night before each one.
| Stage | Who | Length | What it tests |
|---|---|---|---|
| 1. Screen | Hiring manager | 30 min | Which kind of QA they are, release cadences they know |
| 2. Test strategy | Senior developer | 60 min | What they would test, automate and skip in your app |
| 3. Flaky test pairing | A developer | 90 min | Debugging, test code quality, working with developers |
| 4. Final round | Founder and product lead | 45 min | Release judgement, how they say "not ready" |
Strong answer: Concrete examples on both sides of the release decision, and a clear sense of whether they prefer building automation or exploratory testing.
Red flags: Every story ends with them blocking a release, or they cannot recall a bug they found outside a script.
Strong answer: Starts from risk and how often each area changes, pushes tests down to the cheapest level, and asks to join planning.
Red flags: Wants end-to-end tests for everything, or treats coverage as the goal.
Question 4 is the one to grade hardest, because it is the job you are hiring for.
"I'd write end-to-end tests for sign-up and checkout first and run them on every merge. Then I'd pair with each developer on unit tests for their own features, so the founders only test what changed."
Why 3, not 4: a sound plan with no date for the last manual night, and no word on what happens when a check fails at midnight before release.
Strong answer: Named causes such as timing, shared test data or test order, and a quarantine rule with an owner and a deadline.
Red flags: Adding retries or longer waits as the fix, or never deleting a test.
Strong answer: Coaching rather than policing, and a clear statement of risk that leaves the founder to decide.
Red flags: "QA signs off" language, or treating developers as the people who make the bugs.
Give the candidate a small web app with five end-to-end tests, two of them flaky: one from a timing problem, one from shared test data. Pair for 90 minutes with a developer, with a short written note afterwards. Keep the whole exercise under 3 hours.
Listen to how they talk to the developer. Your QA hire will spend most days persuading people, and the pairing shows that better than any question.
| Outcome | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Release confidence | Relies on gut feel | Uses a checklist | Clear criteria for "ready" | Releases without a manual freeze |
| Regression automation | Manual only | Automates when told | Automates by risk | Removes manual passes for good |
| Flaky tests | Reruns until green | Quarantines, never fixes | Finds root causes | Builds a suite people trust |
| Developer testing habits | Tests after developers | Reviews their tests | Pairs on tests | Developers test unprompted |
| Escaped bugs | Not tracked | Counted | Tracked by cause | Causes shrink release on release |
We run engineering searches on a fixed fee agreed upfront from $4,900 to $21,900 per hire (see pricing). One dedicated recruiter screens candidates against your scorecard, with first screened candidates within 7 days. More on how we hire.
Technical enough to write and review test code in your main language. Set the level in your QA engineer job description before you interview.
A paired session beats a take-home for QA, because it shows how they work with developers. Keep any exercise under 3 hours.
Aim to finish the four stages within two weeks. If QA is part of a wider engineering push, see how to hire 5 engineers in 60 days.
Worth a brief chat about your next hire? Book a free call.