When an interviewer says “Tell me about a time you handled a crisis”, they want one real event in which something went badly wrong without warning, and they want to see what you did in the first minutes, the first hours and the days after. A strong answer shows three things: you kept people and the operation safe first, you kept the right people informed, and you made sure the same thing was less likely to happen again.
This guide uses annotated examples. Each one is illustrative, written to show technique rather than taken from a real candidate, and each is followed by notes on what the interviewer is likely to pick up.
First, check that your story is actually a crisis
Many candidates answer this question with a busy week or a tight deadline. That is a different question. A useful test comes from the UAE’s national business continuity standard, AE/SCNS/NCEMA 7000:2021, issued by the National Emergency Crisis and Disaster Management Authority. It defines an incident as an event or situation that deviates from what is standard, normal or expected, and a disruption as an incident that adversely affects an organisation’s normal course of operations.
For interview purposes, a crisis story usually has all of these features:
- It was unplanned. Nobody put it in the calendar.
- Normal work stopped or was at real risk. Customers, patients, guests, systems or colleagues were affected.
- Time mattered. Waiting an hour would have made it worse.
- You had to decide with incomplete information. This is the part interviewers care about most.
If your example is “the client moved the deadline forward”, it belongs under a deadline question. If it is “the payment system went down on a Friday evening”, you are in the right place.
The shape of a good crisis answer
The National Careers Service describes STAR as the situation, the task you were given, the action you took, and what happened as a result and what you learned. For a crisis, the Action section is easier to follow if you tell it in phases rather than as one long list:
- Stabilise: what you did first to stop the harm spreading or to keep people safe.
- Communicate: who you told, when, and what you said.
- Restore: how normal service came back.
- Prevent: what changed afterwards.
The fourth phase is where many answers stop short. The business continuity standard defines business continuity as an organisation’s capability to resume delivery of products and services during a disruption within acceptable timeframes at acceptable capacity. Interviewers in operations, IT, healthcare and hospitality often think in exactly those terms: how long were things down, and what did you change so recovery is faster next time?
Annotated example 1: the answer that sounds calm but says little
“I’m very good under pressure. Once our system crashed during a busy period and everyone was panicking, but I stayed calm and we worked as a team to fix it. In the end everything was fine and the manager thanked us. I think staying calm is the key in any crisis.”
Notes:
- “I’m very good under pressure” is a claim. The rest of the answer needs to prove it, and it does not.
- “We worked as a team to fix it” hides the candidate’s role. Amazon’s interview guide, for example, advises candidates to use “I” statements so their personal contribution is clear.
- “Everything was fine” gives no measure. How long was the system down? How many customers were affected?
- No prevention step. The interviewer cannot tell whether anything was learned.
Annotated example 2: retail operations, a till system failure
Situation: “I was shift supervisor in a supermarket on the Thursday evening before a public holiday weekend. At about 7pm, all six card terminals stopped authorising payments. Queues were already long and cash was the only option.”
Task: “The store manager was off site, so I was the most senior person. I needed to keep customers served, protect takings and get the terminals back.”
Action: “First I made two announcements: that cards were temporarily not working, and where the nearest cash machine was. I moved one colleague to the queue to tell people individually, so nobody waited 15 minutes and then found out at the till. I opened a second cash float from the safe so tills would not run short of change. Then I rang the payment provider’s support line, logged a fault and got a reference number. While I waited, I called the store manager to update her and agreed that customers with full trolleys who had no cash could leave items at customer service for up to an hour. I wrote down the time of each step on the back of a shift sheet.”
Result: “Terminals came back after about 50 minutes. We held around 20 trolleys and most customers returned for them. Afterwards I wrote up the timeline for the manager. Two things changed: we added the provider’s support number and reference process to the shift supervisor’s checklist, and we agreed a minimum cash float for evenings before holidays.”
Notes:
- The phases are visible: announce and protect the queue (stabilise), call provider and manager (communicate), terminals back (restore), checklist and float (prevent).
- Small, concrete decisions such as opening the second float show judgement without exaggeration.
- Escalation is handled properly. The supervisor acted within their authority and kept the manager informed rather than waiting for permission or ignoring her.
- The timeline on the shift sheet is a small detail that signals good habits. Interviewers often follow up with “How did you know how long it took?”, and this candidate can answer.
Annotated example 3: IT support, a ransomware warning
Situation: “I was one of two IT support analysts at a 120-person firm. On a Monday morning a user reported that files on a shared drive had changed names and could not be opened.”
Task: “I had to work out whether this was a fault or an attack, and limit the damage if it was an attack.”
Action: “I asked the user to unplug their network cable and leave the laptop switched on, which was what our incident procedure said. I checked the file server and saw the same renaming spreading across one folder, so I disconnected the server from the network. Then I called my manager and our managed security provider, because a suspected attack was above my authority to handle alone. I sent a short message to all staff saying the shared drive was offline, not to open unexpected attachments, and that we would update them by 11am. I kept that promise even though the update was only ‘still investigating’.”
Result: “The security provider confirmed malware on one laptop. Because the server was disconnected early, only one folder was affected and it was restored from the previous night’s backup. The shared drive was back by mid-afternoon. In the review, I suggested we test restores monthly rather than assume backups worked, and that became part of my monthly checklist.”
Notes:
- Following procedure is a strength here, not a weakness. The UK Civil Service behaviour “Changing and Improving” includes, at its entry level, responding in an effective and appropriate manner when emergencies arise. Knowing and applying the playbook is exactly that.
- Knowing your limits. The candidate escalated at the right point. The Civil Service “Making Effective Decisions” behaviour includes talking to relevant people for advice when unsure how to proceed.
- The promised update at 11am shows communication discipline. In a crisis, regular updates with nothing new still reduce noise and repeated questions.
- Avoid technical detail you cannot defend. If you mention a tool or method, expect a follow-up question on it.
Annotated example 4: hospitality, a guest medical emergency
Situation: “I was duty manager at a hotel restaurant during a Friday brunch for about 150 guests. A guest collapsed at a table near the buffet.”
Task: “My job was to make sure the guest got help quickly and that the rest of the restaurant stayed safe and calm.”
Action: “I sent one waiter to call the emergency number and another to bring the first aid kit and fetch our trained first aider from the lobby. I asked the guest’s family what had happened and whether he had any conditions, so I could pass that on. I moved nearby guests to other tables to give space and asked one team member to wait at the entrance to guide the ambulance crew. Once the guest was in the ambulance, I spoke to the family about their belongings and their bill, then wrote an incident report before the end of the shift.”
Result: “The ambulance arrived within about ten minutes and the guest was taken to hospital. Later the family thanked the team. In the debrief, we noticed nobody on the floor that day was first-aid trained, so the hotel scheduled training for restaurant supervisors and I was in the first group.”
Notes:
- Delegation by name and task. “I sent one waiter to call…” is far stronger than “we called an ambulance”.
- The candidate does not claim medical skills. In a medical or safety story, never exaggerate what you personally did beyond your training.
- Care after the event (belongings, bill, report) shows maturity.
- The guest’s identity is protected. Do not name people or share health details in an interview story.
Choosing your own example
| If your best story is… | Make sure you can explain… |
|---|---|
| A system or equipment outage | How long it lasted, who was affected, what you checked first |
| A safety or medical incident | What your role and training allowed, who you called, how you protected others |
| A supplier or logistics failure | What alternatives you found, how you told customers, what the cost was |
| A public or social media problem | Who approved the response, how quickly, what you did not say |
| A personal or academic emergency (if you have little work experience) | How you prioritised, who you informed, what you would do differently |
The National Careers Service notes that examples can come from work, home or volunteering. A student who managed a flooded venue during a society event, or a volunteer who handled a missing child at a community fun run, has a valid crisis story.
Follow-up questions to prepare for
The US Office of Personnel Management’s guide to structured interviews lists probes such as “What was your role?”, “What was the outcome?” and “Is there anything you would have done differently?”. For a crisis story, expect variants of these:
- What was the first thing you did, and why that first?
- What information did you not have at the time?
- Who did you tell, and who did you decide not to tell yet?
- What would have happened if you had waited?
- What, if anything, would you do differently now?
The last question deserves a real answer. “Nothing, it went perfectly” sounds defensive. A modest improvement, such as “I would have started the written timeline from minute one, not minute ten”, is more convincing.
Mistakes that weaken a crisis answer
- Making yourself the hero of a disaster you caused. If the crisis started with your mistake, say so briefly and answer it as a crisis question, or use the story for a “mistake” question instead.
- Blaming colleagues or management. You can describe a gap in a process without criticising named people.
- Breaching confidentiality. Leave out client names, patient details and anything covered by an NDA.
- Spending two minutes on the situation. Keep the scene-setting to three or four sentences.
- Ending at “it was fixed”. Always close with the prevention step.
Once you have a story you are happy with, it is worth turning the outcome into a short achievement line for your CV. The resume examples library shows how others phrase incident and continuity results, and the IT support resume builder has role-specific wording if your story is technical.
Frequently asked questions
What if I have never faced a real crisis at work?
Use the most serious unplanned problem you have handled, from work, study or volunteering, and do not inflate it. Say plainly that it was a smaller-scale event. Interviewers value honest scale over drama.
How long should my answer be?
As a working guide rather than a rule, about two minutes. Keep the situation brief and give the most time to your actions, told in order.
Can I use a crisis that ended badly?
Yes, if you can show sound decisions and a clear lesson. Explain what was in your control, what was not, and what changed afterwards.
Is “handled a crisis” the same as “worked under pressure”?
No. Pressure questions are often about workload and deadlines. Crisis questions are about an unexpected event that disrupted normal operations and required fast decisions.
Sources
- The STAR method, National Careers Service
- AE/SCNS/NCEMA 7000:2021 The National Standard for Business Continuity Management System (Specifications), National Emergency Crisis and Disaster Management Authority (published by ENEC)
- Amazon interview guide, Amazon
- Success Profiles: Civil Service Behaviours, GOV.UK (Cabinet Office)
- Structured Interviews: A Practical Guide, US Office of Personnel Management