Tell me about the most stressful incident you have worked on. How did you keep yourself and others focused?

What the interviewer is looking for

• This question tests composure under pressure. Stays methodical during high-stakes incidents, prioritises calmly, and helps others stay focused.
• What to bring out: Stayed methodical, clarified roles, avoided thrashing, took breaks or handed over when needed, and kept the team calm.
• Expect a follow-up like: What did you learn about yourself from that incident?

Another way it may be asked: Think of a time production was badly broken and everyone was tense. What did you personally do to keep things on track?

A structure to follow: STAR, with the weight on Action and Result

1. Step 1

   Situation

   One or two sentences: where, when and what was at stake. Pick a real example you were close to.

2. Step 2

   Task

   What you personally were responsible for. Say "I", not only "we", so the composure under pressure you showed is visible.

3. Step 3

   Action

   The two or three things you did and why you chose them over the alternatives. This should be about half your answer.

4. Step 4

   Result

   What changed, in your own measure of it, and what you would do differently. Only use numbers you can stand behind.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Describing what the team did without saying what you did.
• Choosing an example with no clear outcome, or one you cannot answer detailed questions about.
• Ending on the action and skipping the result and what you learned.

How to practise it

Write two bullet points for each STAR letter, then say the answer aloud in about two minutes.

Related questions

• What is the difference between a service level indicator, a service level objective and a service level agreement, and why would a team care about the difference?
• A Linux server is suddenly very slow. What are the first things you would check, and what would each one tell you?
• You are on call, and at two in the morning you get paged that the checkout page is returning errors. What do you do in the first ten minutes?
• How do you decide what deserves to page a human at night versus what can wait for a ticket in the morning?
• Your service has burned most of its error budget halfway through the month. What happens next, and how do you talk to the product team about it?

Browse all questions