QA Engineer interview questions
Grouped by interview stage, with what a strong answer actually sounds like — the part most question lists leave out.
When interviewing a qa engineer, structure questions by stage and assess against the role's actual requirements. QA engineers are responsible for finding problems before users do and for building the automation that keeps finding them. The questions below cover screening through final round, each with what a strong answer sounds like and the warning signs of a weak one.
How to use these
Pick four to six for a 45-minute interview — not all 7. A well-followed-up question takes six to eight minutes, and the information is almost always in the follow-up rather than the first answer. Ask the same core questions of every candidate so you can actually compare them; vary the follow-ups.
Screening questions
How do you decide what to automate?
Why ask it: Over-automation produces slow, flaky suites nobody trusts.
A strong answer: Automates repetitive, stable, high-risk paths; keeps exploratory testing human.
A weak answer: Automate everything, or coverage targets as an end.
Tell me about a bug that reached production. What did you change afterwards?
Why ask it: Escapes are inevitable; the response is what matters.
A strong answer: Understood why testing missed it and changed the approach, not just added one test.
A weak answer: Blames developers or insufficient time.
Core questions
Your test suite is flaky. What do you do?
Why ask it: Flakiness is the most common reason automation gets abandoned.
A strong answer: Treats flakes as defects, quarantines and fixes rather than reruns.
A weak answer: Adds retries until it passes.
How do you write a defect report a developer can act on?
Why ask it: Poor reports waste large amounts of engineering time.
A strong answer: Exact reproduction steps, expected versus actual, environment, evidence, severity.
A weak answer: "It doesn't work."
How do you test something with no written requirements?
Why ask it: Very common in practice.
A strong answer: Derives expectations from users, existing behaviour and conversation; documents assumptions.
A weak answer: Refuses to test without a specification.
Final questions
How do you push back when a team wants to ship something you think is risky?
Why ask it: QA has responsibility without authority, so influence is the core skill.
A strong answer: Frames it as specific risk and likelihood, lets the team decide with clear information.
A weak answer: Blocks unilaterally, or signs off on everything.
What does good collaboration with developers look like?
Why ask it: Adversarial QA relationships damage quality more than they help.
A strong answer: Involved early, tests as design feedback, shared ownership of quality.
A weak answer: Receives finished work and looks for faults.
Red flags for this role
- Manual testing only with no interest in automation
- Adversarial framing of developers
- Cannot explain a test strategy
What a qa engineer actually does
QA engineers are responsible for finding problems before users do and for building the automation that keeps finding them. The role is judged on escaped defects and on how much confidence the team has in shipping.
See the full qa engineer job description, including how to assess each requirement.
Generate questions specific to your role — and that account for what previous interviewers already asked — with the free interview question generator.