Tell me about a time you were on call and it went badly.
What they are really testing: Self-awareness about your own limits under pressure. The best answers show escalating early and asking for help, which juniors often see as failure and seniors see as judgement.
A real interview question
Tell me about a time you were on call and it went badly.
What most people say
drag me
“It was stressful but I stayed calm and eventually fixed it on my own.”
It answers a different question, the one about a success. It shows no reflection and quietly signals that you would rather struggle alone than escalate, which is exactly the trait that lengthens outages.
The follow-ups they ask next
How do you decide when to escalate now?
A hard rule rather than a feeling: a time box, or the moment the impact crosses a threshold. Rules beat judgement at 3am when you are tired and reluctant.
What makes a runbook actually useful during an incident?
Symptom-first entry points, concrete commands you can paste, links to the right dashboards, and escalation contacts. Written for a tired stranger, not for the author.
What the interviewer is listening for
- Names their own mistake specifically
- Reframes escalation as judgement
- Turns it into a personal rule plus a systemic fix
What sinks the answer
- Tells a success story instead
- Pride in solving it alone
- No reflection on behaviour, only technology
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“I was paged for [X] on a service I did not know. I [anchored on the wrong theory for N minutes] and [did not escalate because I did not want to wake someone]. When I did, [they found it in minutes]. I learned [escalation is judgement, not failure], so now [I escalate on a time box], and we [added the runbook and the missing timeout].”
Keep going with behavioural
Mid
Tell me about a time you broke production. What happened and what did you do?
Mid
Tell me about a time you disagreed with a developer about how something should be deployed.
Mid
Tell me about a mistake that cost the company money.
Mid
Walk me through a time you inherited a system nobody understood. Where did you start?
Mid
Tell me about something repetitive you automated. How did you decide it was worth it?
Mid
Tell me about a time you did not know something important and had to act anyway.
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free