behavioral Hard Software EngineerGeneral

Tell me about a time you caused or contributed to a production incident. How did you respond?

How to answer this behavioral interview question: a complete STAR example, the mistakes interviewers watch for, and the follow-ups you should expect.

A strong STAR example answer

The pager went off minutes after my deploy finished. Checkout was down at peak traffic, and the cause was my migration — a NOT NULL column with no default, locking the orders table while it backfilled. My staging snapshot was months old and a fraction of production's size, so nothing had warned me.

Rolling back mid-migration felt riskier than letting it finish, so we held course while I prepared a fallback. I owned the incident channel from the first minute, posted status on a fixed cadence, and worked with support on customer messaging. The abandoned-checkout cost landed in the tens of thousands.

I wrote the postmortem myself and put my own mistakes at the top: stale staging data, no lock timeout, a review culture that treated migrations as routine. The fixes I drove — a check that flags blocking migrations, regular staging refreshes, mandatory lock timeouts — became standard, and that week's checklist is still used by teams beyond my own. Causing an incident is survivable. Hiding from one is not.

How to structure your own answer

  • Situation: Set up the system, the change you shipped, and the blast radius.
  • Task: State your role in both causing and resolving the incident.
  • Action: Walk through detection, mitigation, communication, and the postmortem.
  • Result: Quantify the impact and name the durable safeguards that resulted.

Common mistakes to avoid

  • Never claim you have never caused an incident — it reads as inexperience or evasion; pick a real one.
  • Candidates often narrate the heroics of the fix while glossing over their role in causing it.
  • The postmortem and preventive changes are what interviewers probe for; leave them out and the story is wasted.
  • State the customer or revenue impact plainly — minimizing it destroys credibility.

Follow-up questions to prepare for

Interviewers use follow-ups to verify your story is real. If you get this question in a real interview, expect probes like:

  • Walk me through the moment you realized it was your change — what did you do first?
  • How did you decide between rolling back and letting the migration finish?
  • How did this change the way you review other engineers’ risky changes?

Related practice questions

Keep drilling with these, or browse the complete question bank.

Next up

Practice this question on the clock

Reading an answer and delivering one are different skills. Run a timed round and rate yourself.

Start a practice round

Next up

Interview coming up?

Have your post-interview follow-up email ready before you need it.

Follow-up email generator