QA Engineer interview questions
QA engineer interviews test how you think about risk, not just how you write test cases: expect a 'how would you test X' design question, automation strategy questions (what to automate, what not to), a bug-advocacy scenario, and — for automation roles — a coding exercise. Interviewers want engineers who prevent defects, not just find them. These questions recur across manual, automation, and SDET loops.
Behavioral
- Tell me about the best bug you ever found. Why did everyone else miss it?
- Describe a time developers pushed back on a bug you rated critical. How did it resolve?
- Tell me about a release that shipped with a defect you'd flagged. What happened afterwards?
Role-specific
- The release is tomorrow and you've had one day to test two weeks of changes. What do you actually do?
- How do you decide what belongs in the automated regression suite versus manual exploratory time?
- How do you test a feature when the requirements are one sentence long?
Technical
- How would you test a login page? Keep going until you run out of ideas.
- Your UI test suite is flaky — passing locally, failing in CI. How do you stabilise it?
- How do you test an API without any UI — walk me through your approach to a new endpoint.
- What makes a good bug report? Show me the structure you use.
Culture & motivation
- Why QA — and how do you respond to people who see it as a stepping stone to development?
- What does quality mean beyond 'no bugs'?
Want the questions for your exact job — with answers?
The list above is the common set for QA Engineer roles. Paste the job description you're actually applying to and the free tool generates the questions that specific posting is likely to ask. Then adapt your CV to that job to unlock full answers grounded in your own experience — so you walk in ready, not rehearsing generic lines.
QA Engineer interview FAQ
What questions are asked in a QA engineer interview?
A test-design question ('how would you test a login page'), a time-pressure prioritisation scenario, automation strategy (what to automate and why), flaky-test debugging, and bug-advocacy behavioural questions. Automation roles add a coding exercise — usually writing or reviewing a test.
How do I answer 'how would you test X'?
Organise out loud: happy path, negative cases, boundaries, security (injection, auth), accessibility, performance, and state (what happens on refresh, timeout, double-click). Interviewers score breadth of categories and risk-based ordering, not raw case count — say which you'd run first and why.
How do I prepare for a specific QA role's interview?
Paste the posting into AdaptMyCV's free Interview Questions tool for questions matched to the manual/automation mix and domain, then adapt your CV to that job to unlock answers grounded in your own testing record.