A release is due tomorrow and you have found a serious but rare bug. How do you decide and communicate whether it should block the release?

What the interviewer is looking for

• This question tests bug investigation & reporting. Reproduces issues, isolates conditions, writes clear reports with steps, evidence and impact, and judges severity sensibly.
• Strong answers: Assesses impact, frequency, workaround and risk of fixing, presents facts and options to decision makers, and documents the outcome.
• Likely follow-up: What would you do if you disagreed with the final decision?

Another way it may be asked: The night before launch you find a nasty bug that only hits a few users. Do you stop the release, and how do you tell people?

A structure to follow: Answer, explain, example, limits

1. Step 1

   Answer

   Give your direct answer in the first sentence so the interviewer knows where you are going.

2. Step 2

   Explain

   Say how it works or why you would do it that way, in plain words before jargon.

3. Step 3

   Example

   Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.

4. Step 4

   Limits

   Say when your approach would not be the right one. It shows judgement.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Reciting a definition without showing you have applied it.
• Using terms you cannot explain if asked a level deeper.
• Claiming experience beyond what you can discuss in detail.

How to practise it

Say the answer in 90 seconds, then answer the follow-up as if it were a new question.

Related questions

• You find a bug that only happens sometimes. What goes into a bug report so a developer can actually fix it?
• If I asked you to test a login page, what kinds of cases would you think about beyond just a correct username and password?
• How would you test a REST API endpoint that creates a new customer record? What would you check?
• What makes end-to-end browser tests brittle, and how do you write them with tools like Playwright or Cypress so they stay reliable?
• Your nightly test suite fails randomly about one run in five. How do you track down and deal with the flaky tests?

Browse all questions