Situational questions in an AI interview ask what you would do in a scenario, such as an upset customer, a bug found the day before a release or a teammate who keeps missing deadlines. Answer them in five short moves: clarify the situation, name the realistic options, choose one and say why, explain how you'd check it worked, and back it up with a time you did something similar. Many AI scoring tools compare your words against a rubric of the judgment the employer wants, so one clear decision with a stated reason is worth more than a list of everything you might do.
How AI interviews use situational questions
Situational questions are a standard part of AI-led interviews. As of October 2026:
- HireVue's candidate FAQ describes three question types: situational judgment questions, where you say what you would do in a hypothetical situation; scenario-based simulations, where you act out your response instead of explaining it; and past-behavior questions.
- micro1 says its AI interviewer, Zara, asks scenario-based questions that assess judgment, problem-solving and communication.
- HireVue says its AI Interviewer suggests questions and answer rubrics from the job description, can score skill questions on a custom 1-to-5 rubric, and that recruiters make the final call.
So the scenario usually comes from the job itself, and the rubric reflects what the employer values in that role: ownership, following sensible rules, putting the customer or the team first, and deciding with incomplete information. Read the job description for clues. Phrases like "customer-first," "comfortable with ambiguity" or "safety-critical" tell you what a scenario is really testing. For the basics of the format, and how it differs from behavioral questions, see what a situational interview is.
The five-step answer for situational questions
| Step | What to say | Example line |
|---|---|---|
| 1. Clarify | Restate the core problem and one assumption you're making | "I'm assuming the customer has already waited a week and contacted us before." |
| 2. Options | Name two realistic options in one sentence | "I could refund right away, or find out why the order stalled first." |
| 3. Decide | Pick one and give the reason, tied to what the role values | "I'd apologize, give a firm answer today and trace the order during the call, because the customer needs one person to own this." |
| 4. Check | Say how you'd confirm it worked or follow up | "I'd call back on the day I promised, even if the news is still a delay." |
| 5. Prove | One or two sentences on a time you did something similar | "Last year I handled a similar case for a long-time account, and they renewed." |
Keep steps 1 and 2 brief; the decision and its reason are the heart of the answer. Most situational answers fit in about 60 to 90 seconds. If a recorded interview gives you think time before recording, use it to choose your decision first, then build the other steps around it.
Example answers for three roles
These are examples we wrote to show the shape. Swap in your own experience for step 5.
Customer service
Question: "A customer says their order is a week late and demands a full refund. What do you do?"
Example answer: "First I'd apologize and confirm the order number, so the customer knows someone owns the problem. I'd assume they've already been told 'it's on its way' once. My options are to refund immediately or to find out what happened first. I'd check the tracking while we talk: if it's lost, I'd offer a reship or a refund within our policy that day; if it's moving, I'd give an honest date and tell them I'll call back. Then I'd call back on that date. I handled a case like this in my last job. A customer was ready to cancel, and the follow-up call, more than the discount, is what kept her."
Software engineer
Question: "The day before a release, you find a bug that affects a small number of users. What would you do?"
Example answer: "First I'd pin down how small 'small' is and whether the bug loses data or just looks wrong, because that decides everything else. If it corrupts data or touches payments, I'd recommend delaying the release and fixing it, even for a few users. If it's cosmetic, I'd ship on time, document the issue, and schedule the fix for the next release. Either way, I'd tell the release owner within the hour with the facts, not just a feeling. I did this on a mobile release last year: I flagged a sync bug that affected about one percent of users, we held the release for a day, and the fix shipped clean."
Team or project lead
Question: "A teammate keeps missing deadlines and it's affecting the project. How would you handle it?"
Example answer: "I'd talk to them privately before assuming anything, because missed deadlines are often a symptom: unclear scope, too much work, or something personal. I'd ask what's getting in the way and agree on one concrete change, like splitting their next task into two smaller deliverables with their own dates. I'd check in at the first date. If nothing changed after that, I'd bring in our manager with specifics. On my last project, the cause turned out to be two managers giving the same person conflicting priorities, and one conversation fixed it."
Simulation questions: answer in character
When a prompt asks you to act out a response, for example "Respond to this customer as you would on the phone," speak to the customer directly in the first person instead of describing what you'd say. "I'm sorry this has taken so long. Let me check where your order is right now" scores as a demonstration; "I'd probably apologize and look into it" is only a description. If the time limit allows, finish with one sentence that steps out of character: "After the call, I'd log the delay so the shipping team sees the pattern."
Before and after: a situational answer rewritten
| Version | Answer to the late-order question (example) | Why it scores the way it does |
|---|---|---|
| Before | "It depends on the situation. I'd probably talk to the customer, see what's going on, maybe check with my manager, and try to find a solution that works for everyone. Customer satisfaction is really important to me." | No decision, no reason, no follow-up and no evidence. Every line could come from any candidate. |
| After | "I'd apologize, confirm the order and check the tracking during the call. If it's lost, I'd reship or refund within policy that day; if it's moving, I'd give a firm date and call back on it. I did exactly that for a customer last year, and she stayed." | A clear decision with conditions, policy awareness, a follow-up step and a past example. |
Other patterns that weaken situational answers: going straight to your manager for something you could handle, promising things outside company policy, listing five options without picking one, and giving a purely hypothetical answer when you have real experience to point to. Our guides to showing problem-solving in an AI interview and conflict questions in an AI interview cover the neighboring question types.
How to practice situational questions for an AI interview
- Collect eight scenarios. Pull them from the job description and the role's everyday problems. Engineers can borrow from these situational questions for software engineers.
- Pair each scenario with a real story for step 5. The free STAR story builder helps you outline it, and a guide like making a difficult decision shows the matching behavioral answer.
- Answer out loud against a timer. Decision first, then the other steps, in under 90 seconds.
- Get scored. Our free AI interview assistant includes a Mock Interview mode that builds questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10 with what to fix and a model answer. The free plan includes 15 minutes every day. For single questions with nothing to install, the browser demo at /try has 145 real interview questions across 10 tracks, graded by AI.
- Re-answer your weakest one the next day, in your own words.
Take the assessment yourself and follow the employer's rules — use CoPilot Interview to practice beforehand.
Rehearse "what would you do" out loud
Mock Interview asks role-specific questions, scores each spoken answer out of 10 and shows what to fix, so your decision and reasoning come through clearly when it counts.
Try a free AI mock interviewFAQ
What is a situational question in an AI interview?
It is a hypothetical "what would you do" question about a scenario from the job, such as a difficult customer or a deadline at risk. The AI interviewer records or transcribes your answer, and many tools score it against a rubric of the judgment and skills the employer wants for the role.
How is a situational question different from a behavioral question?
A situational question asks what you would do in a future or hypothetical case; a behavioral question asks what you did in a real past case. The best situational answers combine both: a clear plan for the scenario, then one or two sentences on a time you did something similar.
How long should a situational answer be?
About 60 to 90 seconds works for most situational questions: a brief clarification, your decision and reason, a follow-up step and a short past example. Check the time limit in your invitation, since some recorded interviews cap each answer.
Is it okay to say I would ask my manager?
Sometimes, but not as your whole answer. Escalating is right for decisions above your authority or outside policy. For problems you could reasonably handle, say what you would do yourself first and when you would loop in your manager.
What if I have never faced the situation in the question?
Answer the scenario with a clear decision and reason, then link it to the closest real experience you have, such as a school project, a part-time job or a similar problem in a different setting. Say plainly that it is a related example rather than the same situation.
Is there one right answer to a situational question?
Rarely one exact answer, but usually better and worse ones. Answers that take ownership, follow sensible rules, consider the people affected and include a follow-up step tend to match what employers put in their rubrics. Saying "it depends" without deciding tends to score poorly.