QA engineer interview questions: risk, releases and escaped bugs

QA interviews test risk-based testing, a release you blocked, and a bug that escaped — the three stories that show whether quality is judgement or checklists.

QA engineer6 questionsUpdated 2026-11-15

QA rounds look for whether you decide what to test under time pressure, and whether you own the bugs that got out. Test-case trivia scores lower than a clear risk argument.

Recruiter screenTechnical screenTest strategy caseHiring managerOffer
Question 1

Tell me about a release you blocked.

What it is testing
Whether you can hold a line with evidence.
How to answer
The risk, the evidence, who was told, and the decision. Include the case where you were overruled and it shipped fine.
Question 2

How do you decide what to test with limited time?

What it is testing
Risk-based prioritisation.
How to answer
Change surface, customer impact, historical defect density, and what you deliberately left to monitoring.
Question 3

Tell me about a bug that escaped to production.

What it is testing
Whether you fix the escape or the tester.
How to answer
The bug, why the tests missed it, the test or check added, and the process change.
Question 4

How do you write a test case someone else can run?

What it is testing
Reproducibility and clarity.
How to answer
Preconditions, steps, expected result, and the data. If a stranger cannot reproduce it, it is a note, not a test.
Question 5

Tell me about automating a manual suite.

What it is testing
Whether automation was targeted or exhaustive.
How to answer
What you automated first (high-volume, stable), what you kept manual, and the maintenance cost you accepted.
Question 6

A developer says it works on their machine. What do you do?

What it is testing
Evidence over argument.
How to answer
Reproduce with their build, capture environment differences, and file with logs rather than opinions.

Questions people also ask

Do QA interviews include a practical exercise?

Often a test-plan or bug-report exercise. Scoring favours risk reasoning and a reproducible report over exhaustive checklists.

How much automation is expected?

Enough to maintain a suite you own — typically one language plus a framework — and the judgement to know what should stay manual.

Practise this role

Run a qa engineer mock interview.

Questions one at a time, a five-category score, and a rewrite of every answer. Free during the beta.

Start practising
Other roles