QA behavioural interview questions
// 32 QUESTIONS · UPDATED MAY 2026
Behavioural interview questions for QA engineers, framed for the STAR format. Covers conflict, prioritisation under deadline pressure, and leadership scenarios.
Showing 32 of 32 questions
- Tell me about a time you disagreed with a developer about a bug.Junior
Use STAR. Pick a real example where you held a position with evidence, listened to the developer's reasoning, and reached a decision base…
- How do you decide what to test when deadlines are tight?Mid
Risk × impact. Map features to (probability of breaking) × (blast radius if broken), test the top of that list, and explicitly document w…
- Tell me about yourself.Junior
Use a Past–Present–Future structure: how you got into testing, what you do now and the value you bring, and what you're looking for next.…
- Why are you interested in QA / testing?Junior
Lead with a genuine reason — typically a combination of analytical curiosity, user empathy, and systems thinking. Back it up with one con…
- Why do you want to leave your current role?Junior
Frame as 'pull' towards what's next, not 'push' away from what is. Be honest but professional — never criticise the current employer, eve…
- Walk me through a project you're proud of.Junior
Pick a project where your contribution had measurable impact, walk through it in STAR format, and end with what you'd do differently next…
- Tell me about a time you found a critical bug — what happened?Junior
Pick a real critical bug, walk through how you noticed it, what you did to confirm severity, how you escalated, and the outcome. Show met…
- Describe a time you had to test a feature with vague requirements. How did you proceed?Mid
Source the gaps, write down your assumptions, and confirm them with PM and engineer before testing. Don't try to test against a moving ta…
- Tell me about a time you missed a bug that reached production. What did you do?Mid
Take ownership without minimising. Walk through the bug's nature, the gap in your test coverage that allowed it through, the immediate fi…
- Describe a situation where you had to push back on shipping a feature.Mid
Pick a case where you raised concerns based on evidence and risk, not vibes. Show how you framed the trade-off in business terms (impact…
- Tell me about a time you had conflicting priorities. How did you decide?Mid
Walk through how you made the trade-off transparent — what the competing demands were, who the stakeholders were, what you used to decide…
- Describe a time you had to learn a new tool or language quickly for work.Mid
Pick a real example with a real timeline. Walk through your learning approach — not just 'I read the docs' but the structure: scope, hand…
- Tell me about a time you simplified a complex test suite or process.Mid
Pick a case where you measured before and after. Show that you investigated *why* the suite was complex (it usually grew that way for rea…
- Describe a time you had to give a developer difficult feedback.Mid
Pick a real case where the feedback was both honest and constructive. Show you led with the behaviour or pattern (not the person), gave i…
- Tell me about a time you advocated for testing investment when leadership wanted to ship faster.Mid
Lead with data: bug-escape rates, customer impact, dev hours lost to flake. Frame the investment in terms of speed, not against it — 'thi…
- Describe a time you made a mistake at work. How did you handle it?Mid
Pick a real mistake — not a humblebrag ('I worked too hard'). Show you acknowledged it quickly, communicated honestly to the people affec…
- Tell me about a time you worked with someone whose communication style was very different from yours.Mid
Don't paint the other person as the problem. Show you adapted *your* style to meet them, named the difference openly when useful, and fou…
- How do you handle a sprint where requirements keep changing?Mid
Show that you handle the volatility without panic. Track changes explicitly, re-prioritise testing as scope shifts, communicate impact to…
- Tell me about a time you joined a team and inherited a messy test suite. What was your approach?Mid
Resist the urge to rewrite. Investigate why it grew the way it did, talk to people, find the highest-pain points, and intervene surgicall…
- Describe a situation where you led a quality initiative that changed how a team worked.Senior
Pick an initiative where you owned both the proposal and the adoption. Show how you built coalition (not just got sign-off), measured imp…
- Tell me about a time you had to convince leadership to adopt a new testing approach.Senior
Show that you brought a business case, not just a technical preference. Concrete data, an honest framing of cost and risk, a pilot propos…
- Describe a time you saw a quality problem coming weeks or months before it manifested. What did you do?Senior
Pattern-recognition is real but the test is what you did with the signal. Show how you raised the concern early, sized the risk, proposed…
- Tell me about a time you had to deliver bad news to stakeholders about a release.Senior
Be honest, be early, lead with the headline. Bring options, not just the problem. Stakeholders trust you more when you bring bad news cle…
- Describe a difficult production incident you investigated. What was your role?Senior
Walk through the timeline in real time — what you did at each step, how you coordinated, what was unclear, and what you eventually pinned…
- Tell me about a time you mentored someone and what you learned from it.Senior
Pick a real mentee with a real growth arc. Show what you adjusted in your approach to fit them, what you learned about your own assumptio…
- How do you handle quality regression in a high-velocity release cycle?Senior
Don't slow velocity to fix it; rebuild the safety net while velocity continues. Quantify the regression first, intervene at the cheapest…
- Describe a time you reduced flakiness in a test suite. Walk me through the process.Senior
Investigation first — track flake rate per test, find the patterns. Most flakes come from a few causes: timing, shared state, third-party…
- Tell me about a project that failed. What did you learn?Senior
Pick a real failure where you had skin in the game. Be honest about the cause — process, communication, your own judgement. The lesson sh…
- How do you build a quality culture in a team that historically saw QA as a gate, not a partner?Lead
Reframe QA as upstream and shared. Embed early in design, share data engineers actually use, mentor not police, and replace gate moments…
- Describe a time you advocated for a structural change to how engineering and QA collaborate.Lead
Pick a structural change you championed (org structure, process, role definition) — not just a tactical improvement. Show the case-making…
- Tell me about a time you had to manage out a low performer or have a tough performance conversation.Lead
Show that you were direct and timely, gave them genuine support to improve, and made the call honestly when improvement didn't come. Perf…
- How do you set quality bars and metrics that actually motivate a team without burning them out?Lead
Bars should be objective, achievable, and connected to user impact. Use bands not points (e.g. 'pass rate ≥99%' not '100%'), avoid metric…