← 🧭 Ownership & Judgment
Core
On-Call Narratives That Land
Every infrastructure loop has a round where you are asked to tell an incident story, and the interviewer is not listening for drama. They are listening for the signal you read, the decision you made under time pressure with incomplete information, the evidence you had for it, and what you changed afterward so the same page never fires again. This page gives the structure that makes an incident story land in four minutes, two worked narratives from GPU fleet and serving work, the follow-ups that test whether the story is real, the version that sounds heroic and fails, and what separates the senior telling from the staff telling.
a free account unlocks the core curriculum tier · no card
RELATED CONCEPTS
PRACTICE THIS IN REAL QUESTIONS
Behavioral & OwnershipWalk me through the worst on-call incident you have handled.→Behavioral & OwnershipHow do you bring a junior engineer through their first serious incident?→Behavioral & OwnershipHow do you run a postmortem that actually changes something?→GPU Fleet Reliability & ObservabilityYou own the on-call rota for a GPU fleet. What is allowed to wake someone at 3am, and what must not?→GPU Fleet Reliability & ObservabilityHow would you build a postmortem practice that people take seriously and that actually reduces incidents?→GPU Fleet Reliability & ObservabilityWrite the postmortem for a training run that lost twelve hours. What goes in it, and what makes the action items stick?→
