Top 4 Postmortem Interview Questions
Browse 4 real-world technical and behavioral interview questions about Postmortem. Review scenarios, edge cases, and architectural best practices.
You are on call, a deploy went out twenty minutes ago and production is degraded. Talk me through what you do.
Stabilise first and diagnose second, which usually means reverting the change before you understand it. Take one artefact of evidence on the way out, time-box the decision aloud, communicate impact on a fixed cadence, and treat the incident as open until the damage the deploy caused is repaired.
Tell me about a time you broke something in production. What happened?
Own the change that caused it, walk the timeline from detection to recovery in real minutes, separate your mistake from the system that let it through, and say which fix is still in place today. Interviewers score the honesty of the timeline before the cleverness of the fix.
The line has been stopped for twenty minutes and everyone in the room believes it is your system. How do you run the next hour?
Your first deliverable is a fast, evidenced answer to whether you are in the path, measured at the station rather than on your own dashboards. Restoring production outranks diagnosis, so take a cheap evidence snapshot and then get yourself out of the path.
You get paged, the service is down, and nobody else is online yet. How do you run the incident?
Declare it, take the incident commander role explicitly, and mitigate before you diagnose - roll back or shed load first, understand later. Keep one channel as the record, publish updates on a fixed cadence, hand over rather than push through, and let the review produce owned actions instead of narrative.