A situational interview is a job interview built on hypothetical questions, such as "What would you do if two senior stakeholders gave you conflicting deadlines?", based on situations you are likely to face in the role. Instead of asking what you did in the past, it asks how you would think and act, and the interviewer scores your judgment, priorities and approach.
The US Office of Personnel Management describes situational questions as ones that ask applicants to describe what they would do, in contrast with behavioral questions, which ask about past behavior (OPM structured interview guidance). The format was formally described by Gary Latham and colleagues in a 1980 Journal of Applied Psychology paper, "The Situational Interview" (Latham et al., 1980), and it is now a common part of structured interviews.
How does a situational interview work?
A situational interview is rarely a separate meeting. More often, situational questions are mixed into a structured, panel or hiring manager interview. The process commonly works like this:
- The employer studies the job. Questions are drawn from real, recurring problems in the role, such as an angry customer, a missed handoff or a scope change.
- Every candidate gets the same scenarios. In a structured process, the wording is fixed so answers can be compared fairly.
- Answers are rated on a scale. Interviewers often have example answers for weak, acceptable and strong responses, prepared in advance.
- Follow-ups add pressure. Expect "And if that didn't work?" or "What if your manager disagreed?" to test whether your plan holds up.
Because the scenario is new to everyone, situational questions are useful for candidates with little work history, such as graduates and career changers. They let the interviewer see how you reason even when you have not met that exact problem yet. Our guide on answering without much work experience covers the same challenge from the behavioral side.
Situational interview questions by role
These are example questions we wrote to show the format. They are not taken from any specific company.
| Role | Example situational question | What it tests |
|---|---|---|
| Software engineer | A release goes out Friday afternoon and error rates double. Your lead is offline. What do you do? | Incident judgment, rollback vs fix, communication |
| Product manager | Sales promised a customer a feature that is not on the roadmap. What do you do? | Prioritization, stakeholder handling, saying no well |
| Data analyst | An executive wants a number by tomorrow, but the data has a known quality issue. How do you handle it? | Integrity, caveats, speed vs accuracy |
| Designer | User testing contradicts what the founder wants. What do you do? | Evidence-based persuasion, collaboration |
| Manager | A strong performer starts missing deadlines. How do you approach it? | Coaching, empathy, accountability |
| Customer service | A customer is shouting about a refund you cannot give. What do you say? | De-escalation, policy, options |
| Sales | A prospect says your price is 30% higher than a competitor's. How do you respond? | Objection handling, value framing |
| Project manager | A key team member resigns halfway through a project. What do you do first? | Risk management, re-planning, communication |
For a full bank of engineering scenarios, see our situational interview questions for software engineers, and for service roles, our list of customer service interview questions.
How do you answer a situational interview question?
Use the same five steps every time. This is a frame we wrote; it keeps you from jumping straight to an action before you have shown your thinking.
- Clarify. State one or two assumptions or ask a quick question: "I'm assuming the customer is on a paid plan. Is that right?" This shows you don't act on incomplete information.
- Prioritize. Say what matters most and why: "My first priority is stopping the impact on users; the root cause can wait an hour."
- Act. Describe the specific steps you would take, in order. Name who you would involve.
- Communicate. Explain who you would tell, when and what you would say. Many weak answers skip this step.
- Close the loop. Say how you would check the outcome and prevent a repeat. Then, if you have one, add a short real example: "I did something similar last year when…"
That last move is powerful. A real example turns a hypothetical answer into evidence, which is what a behavioral interview looks for. Keep it to two or three sentences, using the STAR method in miniature.
Example answer we wrote: product manager
Question: "Sales promised a large customer a feature that isn't on the roadmap. The account executive wants it in the next release. What do you do?"
Answer: "First I'd clarify what was actually promised. Often there's a gap between the customer's problem and the feature sales described, so I'd ask the account executive for the exact wording and join a call with the customer to understand the underlying need. My priority is keeping the customer's trust without breaking commitments to everyone else on the roadmap. If the need can be met with something we're already building or a workaround, I'd propose that. If it can't, I'd size the work with engineering and take the trade-off to my manager and the sales lead together, with what we would have to delay. Then I'd make sure the customer hears one consistent answer, with a date only if we can commit to it. Afterward, I'd suggest a simple check where sales flags roadmap promises to product before a deal closes. I handled a smaller version of this last year: a custom export the customer asked for turned out to be solvable with a saved report, and the deal closed on time."
Example answer we wrote: customer service
Question: "A customer is shouting about a refund that our policy doesn't allow. What do you do?"
Answer: "I'd let them finish without interrupting, then acknowledge the frustration in plain words: 'I can hear this has cost you time and money, and I want to sort it out.' Next I'd confirm the facts, the order, the date and what went wrong, because sometimes a refund is allowed under a different part of the policy. If it truly isn't, I'd explain why briefly and move straight to what I can do: a replacement, a credit or escalating to a supervisor who has more authority. I'd tell them exactly what happens next and when. Afterward, I'd log the case so the team can see if the policy is causing repeat complaints."
Situational vs behavioral interview: what's the difference?
| Situational interview | Behavioral interview | |
|---|---|---|
| Question form | "What would you do if…?" | "Tell me about a time when…" |
| Time frame | Hypothetical, future | Real, past |
| Main idea | Stated intentions predict behavior | Past behavior predicts future behavior |
| What is judged | Reasoning, priorities, judgment | Evidence of what you actually did and achieved |
| Best answer frame | Clarify, prioritize, act, communicate, close the loop | STAR: situation, task, action, result |
| Good for | Graduates, career changers, new kinds of work | Experienced candidates with relevant history |
OPM's guidance notes that both formats are effective and that behavioral questions show higher validity for highly complex work, such as professional and managerial jobs. In practice, many interviews use both. For more on how structured rounds rate these answers, see structured vs unstructured interviews.
Mistakes to avoid in a situational interview
- Giving the textbook answer. "I'd communicate openly with all stakeholders" says nothing. Name who, what and when.
- Acting alone on everything. Strong answers know when to escalate. Going around your manager or ignoring policy is a red flag.
- Escalating everything. The opposite mistake. Show what you would handle yourself before pulling others in.
- Skipping the communication step. Most workplace problems get worse through silence. Always say who you would tell.
- Arguing with the premise. "That would never happen at a good company" avoids the question. Accept the scenario and answer it.
- Going too long. Aim for 60 to 120 seconds, then let the interviewer push with follow-ups.
How to practice situational questions
Situational answers improve fastest when you say them out loud and hear where your reasoning skips a step. Write eight scenarios from the job description, then answer each with the five-step frame in under two minutes. You can also run hypothetical questions through an AI mock interview: CoPilot Interview's Mock Interview 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. It is free for 15 minutes a day, with no account. Follow each employer's rules, and use AI to prepare beforehand.
Situational questions are one format among many; our guide to the types of job interviews covers the rest, including the culture fit interview, which often uses "what would you do" questions about values.
Rehearse your "what would you do" answers
Answer scenario questions out loud and get a score out of 10 on each one, with what to fix and a model answer to compare. Free for 15 minutes every day, with no credit card.
Try a free AI mock interviewFAQ
What is an example of a situational interview question?
A typical example is: "A key team member resigns halfway through a project. What do you do first?" The question describes a realistic problem from the job and asks how you would handle it.
What is the difference between situational and behavioral interview questions?
Situational questions ask what you would do in a hypothetical scenario. Behavioral questions ask what you did in a real past situation. Situational answers show your reasoning; behavioral answers show evidence from your history.
Can I use the STAR method for situational questions?
Not directly, because there is no past situation or result. Use a frame such as clarify, prioritize, act, communicate and close the loop, then add a short real STAR example if you have one.
How long should a situational interview answer be?
Aim for about 60 to 120 seconds. Cover your priorities and steps clearly, then let the interviewer add complications with follow-up questions.
Are situational interviews good for candidates without experience?
Yes. Because the scenario is hypothetical, you can show sound judgment even if you have never faced that exact situation, which helps graduates and career changers.
How are situational interview answers scored?
In a structured process, each answer is commonly rated on a scale against example answers prepared in advance for weak, acceptable and strong responses. Interviewers look for sound priorities, specific actions and clear communication.