An interview technique that presents candidates with hypothetical workplace scenarios and evaluates how they would handle each situation.
Key Takeaways
A situational interview asks candidates to respond to hypothetical scenarios they might encounter on the job. Instead of asking about past experience ("Tell me about a time when..."), the interviewer describes a realistic workplace situation and asks, "What would you do?" The candidate's response reveals their judgment, problem-solving approach, communication style, and how they'd handle the pressures and trade-offs that come with the role. The concept was formalized by Gary Latham and colleagues in the 1980s, building on John Flanagan's critical incident technique from the 1950s. Their research showed that questions based on actual critical incidents from the job, combined with a standardized scoring guide, predict future job performance better than free-form interview conversations. The predictive validity of situational interviews (0.47) makes them significantly more reliable than unstructured interviews (0.31) for predicting job performance (Schmidt & Hunter meta-analysis). They're not quite as strong as work sample tests (0.54) or assessment centers (0.37 for broader constructs), but they're easier to implement and scale across multiple candidates and interviewers.
Both methods are structured and competency-based, but they approach assessment from different angles. Behavioral interviews ask candidates to describe real situations from their past: "Tell me about a time you had to manage a conflict between team members." This works well for experienced candidates who have a track record to draw from. Situational interviews present a hypothetical: "Imagine two members of your team are in a conflict that's affecting the team's output. What would you do?" This works well for anyone, but it's particularly valuable for entry-level candidates, recent graduates, and career changers who may not have directly relevant past experiences to reference. Research shows both methods have similar predictive validity (behavioral at 0.48, situational at 0.47), so the choice often comes down to the candidate population. Many organizations use both types within the same interview.
Effective situational questions don't come from Google searches or "top 50 interview questions" lists. They come from analyzing the actual challenges the role faces.
Interview the hiring manager and top performers in the role. Ask: "What are the most common challenging situations someone in this role faces?" and "What situation separates a great performer from an average one?" You're looking for moments that require judgment, prioritization, or interpersonal skill. A customer success manager might face: "A client threatens to cancel their contract because of a bug your engineering team says won't be fixed for 3 months." A people manager might face: "Your highest performer consistently misses team meetings and doesn't respond to feedback about it." These scenarios should be realistic, not bizarre edge cases.
The scenario needs enough detail for the candidate to engage meaningfully, but not so much that it becomes a reading comprehension test. Include the setting (who's involved, what's at stake), the tension or trade-off (conflicting priorities, time pressure, incomplete information), and a clear question ("What would you do?"). Avoid hypotheticals that have one obvious right answer. The best situational questions create genuine trade-offs where multiple approaches could work, and the candidate's reasoning matters as much as their conclusion.
For each question, create a 3-5 point scoring guide that describes what a poor, acceptable, good, and excellent response looks like. The rubric should focus on behaviors and reasoning, not specific answers. A scoring rubric for a conflict management scenario might look like: 1 point (avoids the conflict or escalates to management immediately without attempting resolution), 2 points (addresses the conflict but only considers one perspective), 3 points (gathers information from both parties before proposing a resolution), 4 points (addresses the root cause, involves both parties in the solution, and establishes a follow-up plan). Without a rubric, different interviewers will score the same answer differently based on their own preferences and biases.
Here are examples of well-constructed situational questions with scoring guidance, organized by common role categories.
| Role Type | Scenario | What It Assesses |
|---|---|---|
| People Manager | Your team has two members who consistently disagree during meetings, and the tension is starting to affect the rest of the team's morale. How would you handle this? | Conflict resolution, team leadership, communication |
| Customer-Facing | A long-term client calls to say they've received a competitor's proposal that's 30% cheaper. They want to know why they should stay with you. How do you handle the conversation? | Client retention, negotiation, value articulation |
| Technical/Engineering | You discover a security vulnerability in production code on Friday at 4 PM. The fix requires a change to a core module. What's your approach? | Prioritization, risk assessment, communication under pressure |
| Project Manager | You're 3 weeks from a launch deadline when the lead developer tells you a critical feature won't be ready. The stakeholder doesn't know yet. What do you do? | Stakeholder management, problem-solving, transparency |
| Sales | A prospect tells you they love the product but need to get budget approval from their CFO, who you've never met. How do you move this deal forward? | Sales methodology, stakeholder mapping, deal progression |
| Entry-Level | Your manager assigns you a project but gives you incomplete instructions. When you ask for clarification, they say they're busy and to "figure it out." What do you do? | Initiative, resourcefulness, professional communication |
The value of situational interviews depends entirely on how consistently you score them. Without standardized evaluation, you're just having a conversation.
The gold standard is a Behaviorally Anchored Rating Scale (BARS), where each score level is tied to a specific, observable response pattern. For the conflict management scenario above, a BARS might define: Level 1 (poor): candidate ignores the problem, avoids direct conversation, or immediately punishes one party. Level 2 (below average): candidate addresses it but makes assumptions without gathering facts. Level 3 (acceptable): candidate meets with both parties separately, asks questions, and proposes a resolution. Level 4 (strong): candidate identifies the root cause, involves both parties in creating the solution, and establishes checkpoints. Level 5 (exceptional): candidate also considers team dynamics, addresses the broader impact, and creates preventive measures. Each interviewer scores independently before discussing, to prevent anchoring bias.
Don't score based on confidence or presentation skill unless the role specifically requires those (sales, public speaking, client-facing). A thoughtful candidate who pauses before answering may give a better response than a polished candidate who answers instantly but superficially. Don't penalize candidates who ask clarifying questions before answering. In real work, seeking clarification is a sign of good judgment, not weakness. Don't give extra credit for answers that match how you personally would handle the situation. The rubric exists to prevent this exact bias.
Like every interview method, situational interviews have trade-offs that HR teams should understand.
| Strengths | Limitations |
|---|---|
| High predictive validity (0.47) for job performance | Candidates can give "textbook" answers that don't reflect their actual behavior |
| Reduces interviewer bias through standardized questions and rubrics | Doesn't verify past behavior the way behavioral interviews do |
| Works well for candidates without directly relevant experience | Hypothetical responses may not account for emotional pressure of real situations |
| Easy to train interviewers to use consistently | Requires upfront investment in question design and rubric development |
| Can assess judgment and problem-solving that resumes can't reveal | Cultural and language differences may affect how candidates frame hypothetical responses |
| Legally defensible because the same questions and criteria apply to every candidate | Some candidates perform better with "tell me about a time" than "what would you do" format |
Practical guidance for integrating situational questions into your interview workflow.
Situational questions work best in the mid-stage interview (second or third round), after you've already screened for basic qualifications and before the final executive or culture-fit interview. Don't use them in a quick phone screen (they need time for the candidate to think and respond). Don't pile 10 situational questions into one interview: 3-4 per 45-minute interview is the right density. Each question should map to a different competency. If you use both situational and behavioral questions, pair them on the same competency. Ask the behavioral version first ("Tell me about a time...") to hear about real experience, then follow with a situational question on a related but different scenario to test judgment and adaptability.
Most hiring managers haven't used situational interviews before. Training should cover how to deliver the scenario (read it exactly as written, don't paraphrase or add details), how to handle candidate questions (answer clarifying questions about the scenario, but don't hint at the "right" answer), how to use the scoring rubric (score each question independently, avoid adjusting scores based on your overall impression), and how to take notes (capture the candidate's reasoning, not just their conclusion). A 60-minute training session with practice rounds is sufficient for most interviewers. Provide reference cards with the questions, rubric, and scoring instructions.
Key research findings that support (and qualify) the use of situational interviews.