Intervooh · Interview questions by job
QA Engineer interview questions (2026)
Researched, current questions asked in real qa engineer interviews (Technology & IT), with what a strong answer actually does. Questions marked 2026 are the newer, AI-era questions employers now ask.
Build my free day-by-day prep plan →
Tell it the company, role and date; it does the rest. Free, no card.
What they assess
- Test strategy & prioritisation
- Test automation
- Defect investigation & reporting
- Working with developers
The questions to expect
You can't test everything before a release. How do you decide what to test first?
Risk-based, said concretely: what changed, what's business-critical, what's broken before. Anchor it in a real release you triaged.
A developer says your bug is 'by design'. What do you do?
Reframe it around the user and the requirement, escalate with evidence if it matters, and accept the call gracefully if it doesn't.
Tell me about an automation suite you built or rescued. What did you automate first, and why?
Show ROI thinking: stable, high-value paths first, flake quarantined, suite speed protected. Name the stack without leaning on it.
Tell me about the best bug you've ever found. How did you find it, and how did you write it up?
Great testers show the instinct that led there, then a report so clear the fix was easy: steps, expected vs actual, impact, evidence.
When would you not automate a test?
The judgement question that separates candidates: one-off checks, fast-changing UI, exploratory testing, cost above value. Give examples.
How would you test a password reset flow? Talk me through your cases, including the unhappy paths.
Cover functional, security (token expiry, reuse, enumeration), usability and edge cases. Thinking aloud in categories impresses.
How do your automated tests fit into CI — what runs on every commit versus nightly, and what happens when a test is flaky?
Pipeline fluency is the 2026 baseline. Describe the layers (unit → API → E2E), gating rules, and your flake policy honestly.
Why testing and quality, rather than development?
Own it as a chosen craft — advocating for users, breaking things constructively — never as a stepping stone you settled for.
AI can now generate test cases and self-heal automation scripts. How do you see the QA role changing, and what have you tried?2026
Have an informed opinion: AI widens coverage, humans own risk judgement and quality strategy. One real experiment beats a hot take.
Tell me about a time you explained a technical problem to someone non-technical.
Pick a real audience and show the translation: the analogy you used, what you left out, and how you checked they got it.
Describe a production incident you were involved in. What did you do first?
Order matters: mitigate, communicate, then root-cause. Finish with the fix that stopped it happening again.
Walk me through a technical decision you made that you later reversed.
Reversing well is the skill. Show what new information arrived, how fast you acted on it, and what the reversal cost.
Preparation notes
[object Object]
Turn this into a plan
A list of questions is a start; a programme is what changes the outcome. Intervooh builds a day-by-day plan for your exact qa engineer interview — company research, story building with an AI coach, spoken practice with delivery feedback, and scored mock interviews.