A situational interview question presents a candidate with a hypothetical work scenario and asks how they would handle it. Instead of asking what someone has already done, you describe a situation they are likely to face in the role and ask them to walk through their approach. This measures judgment, priorities, and reasoning rather than rehearsed history.
Key takeaways
- Situational questions ask candidates what they would do in a hypothetical future scenario, not what they did in the past.
- Behavioral questions probe real history, situational questions probe judgment, so use situational when a candidate has little relevant experience.
- A good situational question ties to a real job scenario, stays realistic, and comes with a defined model answer and scoring scale.
- Score every candidate against the same rubric so answers stay comparable and hiring stays fair.
What situational interview questions are
Situational questions start with a prompt like "What would you do if..." and put the candidate inside a realistic decision. They reveal how a person thinks through a problem: what they prioritize, who they involve, and how they weigh trade-offs.
Because the scenario is hypothetical, candidates cannot lean on a memorized story. You see their instinct and reasoning applied to a situation that matters for the job you are filling.
- Focus on judgment and decision-making, not past track record.
- Work well when every candidate has similar (or limited) experience.
- Let you standardize the scenario so answers are directly comparable.
- Surface how someone handles ambiguity, conflict, and competing priorities.
Situational vs behavioral questions
Both formats are structured and both are strong predictors, but they ask about different time frames. Behavioral questions look backward at real events. Situational questions look forward at a hypothetical.
| Dimension | Behavioral | Situational |
|---|---|---|
| Time frame | Past, real events | Future, hypothetical scenario |
| Typical opener | "Tell me about a time..." | "What would you do if..." |
| Measures | Proven history and habits | Judgment and reasoning |
| Best for | Experienced candidates | Graduates or career changers |
| Main risk | Rehearsed or exaggerated stories | Idealized "textbook" answers |
How to write good situational questions
A weak situational question is vague and invites a generic answer. A good one is specific to the role and has a clear picture of what strong looks like before you ask it.
- 1
Tie it to a real job scenario
Pull the situation from something the person will actually face in the role, such as a missed deadline, an unhappy client, or two urgent tasks at once.
- 2
Keep it realistic and specific
Give enough detail that the scenario feels concrete, but avoid trick setups or scenarios so unusual that no reasonable answer exists.
- 3
Define what a strong answer looks like
Write down the key elements a top response should include before interviews start, so you are scoring against a standard rather than a gut feeling.
- 4
Score consistently
Use the same rating scale and model answer for every candidate, and have interviewers rate independently before comparing notes.
Sample situational questions by competency
Group your questions by the competency they test so your interview covers the traits that matter for the role. Below are examples you can adapt.
- Prioritization: "You have three tasks due by end of day and cannot finish all of them. How would you decide what to do?"
- Conflict resolution: "A teammate disagrees strongly with your approach in front of the group. What would you do?"
- Customer focus: "A customer is angry about a problem that was not your fault. How would you handle the conversation?"
- Handling pressure: "A key deliverable is going to miss its deadline and your manager is unaware. What would you do?"
- Ownership: "You notice a mistake in work that has already been sent to a client. What are your next steps?"
- Collaboration: "You are assigned to a project with someone who is not pulling their weight. How would you approach it?"
How to score answers
Scoring is where situational interviews earn their reliability. Rate the quality of the reasoning, not how polished the delivery sounds.
| Rating | What it looks like |
|---|---|
| Strong | Names trade-offs, involves the right people, explains the reasoning, and lands on a sensible action. |
| Adequate | Reaches a reasonable action but skips trade-offs or communication steps. |
| Weak | Gives a vague or textbook answer with no reasoning, or ignores a key part of the scenario. |
If an answer is thin, probe once with "What would you do if that did not work?" before you score. That follow-up separates candidates with real judgment from those repeating a rehearsed line.
When situational beats behavioral
Situational questions are your best option when a candidate has little relevant past experience to draw on. Graduates, career changers, and people moving into a new type of role often cannot give a strong behavioral answer simply because they have not been in that situation yet. Asking what they would do lets you assess potential fairly.
- Early-career and graduate hiring where work history is thin.
- Career changers moving into an unfamiliar function.
- High-volume roles where you need one consistent scenario across many candidates.
- Situations where you want to test judgment on a scenario unique to your business.
Building a scoring rubric before you ask anything
A situational question without a rubric is a conversation, not an assessment. Write the rubric at the same time as the question, while you still remember why you are asking it. For each question, describe what a weak, an adequate and a strong answer contains, not in adjectives, but in the specific things a candidate would have to mention. If you cannot describe a strong answer in two sentences, the question is too vague to score and needs rewriting before it goes anywhere near a candidate.
| Level | What the answer contains | Score |
|---|---|---|
| Weak | Restates the situation, jumps to a solution, no mention of the people affected or the trade-off involved | 1 |
| Adequate | A sensible course of action, names one trade-off, but no check on whether it worked and no escalation point | 2 |
| Strong | Names the trade-off, chooses and justifies, says who they would involve and when they would escalate, and how they would know it worked | 3 |
Running the interview so answers stay comparable
Ask the same questions in the same order to every candidate, and resist the urge to help. The most common way a structured interview quietly becomes unstructured is the interviewer who likes a candidate and starts feeding them the answer: 'and presumably you would have spoken to the client?' That prompt is invisible in your notes and devastating to the comparison, because the candidate you did not warm to never got it.
- Read the question exactly as written, once, and then stop talking.
- Allow silence. The better answers often arrive after a pause, and filling it yourself is how you lose them.
- Use one neutral follow-up, agreed in advance and used for everyone: 'what would you do next?'
- Score immediately after each answer, before the next question, while the detail is fresh.
- Never compare candidates during the interview. Score against the rubric, compare afterwards.
What strong and weak answers actually sound like
Take a common question: 'A client emails at five on Friday saying the work delivered this morning is wrong, and the person who did it has left for the weekend. What do you do?' The weak answer fixes it heroically and says nothing about the client. The adequate answer replies to the client and picks the work up on Monday. The strong answer does something the other two do not: it separates the immediate response from the underlying problem. It acknowledges the client within the hour with a realistic timeline rather than a promise, checks whether the error affects anything else already delivered, and says what it would change on Monday so the same handover gap does not recur.
Notice that the strong answer is not the most enthusiastic one. Situational questions reward judgement, and judgement often sounds calmer than heroism. Interviewers who score on energy rather than content systematically prefer the first kind of answer, which is exactly the bias a rubric exists to catch.
Common mistakes that make the answers useless
- Scenarios so generic that any competent adult can answer them. If the answer does not require knowing the job, the question tests nothing.
- Scenarios with an obvious right answer. Ask about the case where two reasonable people would disagree, because that is where judgement shows.
- Too many questions. Four situational questions properly scored beat ten skimmed, and attention fades on both sides of the table long before you run out of questions.
- Leading detail in the question. If you describe the situation for ninety seconds, you have told them what matters and all they have to do is agree.
- Scoring from memory at the end. Notes written after five interviews are a record of who you liked, not of what was said.
Using situational questions in a recorded interview
Situational questions work unusually well recorded, because they need no follow-up to be useful: the candidate is given a scenario and answers it, and there is nothing an interviewer would have added beyond the neutral prompt. That makes them the natural content for a one-way round on a role with more applicants than you can interview live. Two situational questions, ninety seconds each, tell you more about judgement than a fifteen-minute phone call about someone's CV.
Recorded also solves the consistency problem by construction. Every candidate gets the same wording, the same time and no accidental coaching, and the answers are transcribed so you score from what was actually said rather than from what you remember. Score against the rubric you wrote, and keep the evidence next to the score so a hiring manager can check your reading.
