Question 1

Three critical bugs found at sprint end, release is tomorrow. Your steps?

Accepted Answer

(1) Reproduce and document all three with evidence; (2) assess impact — which flows, how many users, any workaround; (3) present it structured to the lead/PO: fix + retest time, with options of partial release / feature flag / postponement; (4) after the decision, verify fixes and run focused regression on affected areas; (5) in retro, analyse why these bugs surfaced so late.

Question 2

Two tasks are "urgent" at once and you can't do both. How do you choose?

Accepted Answer

My criteria: business impact (release blocker > internal task), deadline reality, whether I'm blocking someone. I don't choose alone — I transparently inform both sides and align the priority with stakeholders. That's both the right call and expectation management.

Question 3

A bug you missed was found in production. How do you react?

Accepted Answer

I own it without defensiveness and act immediately: assess impact, inform the team, verify the hotfix. Then root-cause analysis: why wasn't this scenario in the test scope? Based on the answer I make a concrete change — a new regression case, checklist update, or a new refinement question. Telling a real example (STAR) makes this answer much stronger in interviews.

Process & scenario questions