Situational interview questions with a scoring rubric: 12 scenarios and 1–4 anchors

Situational interview questions describe a realistic, job-related scenario and ask the candidate what they would do. They are scored against anchors written in advance, ideally from what strong performers actually did in the same situation. Use them when candidates are unlikely to have relevant past examples, such as new graduates, career changers or the first hire in a new kind of role; for experienced candidates, behavioral questions about what they actually did usually give firmer evidence. Below are twelve scenarios across six competencies, each with what a strong answer shows, a follow-up probe and 1–4 anchors, and guidance on writing your own.

The past-behavior equivalent of this page is behavioral interview questions with a scoring rubric, and the background on behavioral interviewing is in what is a behavioral interview.

What is a situational interview question?

The U.S. Office of Personnel Management's guidance on structured interviews describes situational questions as asking applicants what they would do in a situation, relying on their ability to project what they might do in the future, and notes that both situational and behavioral formats have proven effective. The format was set out by Latham, Saari, Pursell and Campion in "The situational interview" (Journal of Applied Psychology, 1980).

Do situational questions predict job performance?

Yes, though behavioral questions have the edge where candidates have relevant experience. Taylor and Small's meta-analysis, "Asking applicants what they would do versus what they did do" (Journal of Occupational and Organizational Psychology, 2002), found that both formats yielded high validity estimates. Where both used descriptively anchored rating scales, past-behavior questions had a higher mean validity estimate (.63 against .47), and inter-rater reliability was similar for both (.79 and .77). It found no support for the idea that situational questions are less valid for highly complex jobs.

The practical reading: anchored scales matter for either format, prefer behavioral questions when the candidate has done the work, and use situational questions when they have not. Decide which format each question uses before the interview, so every candidate for the role is scored the same way.

When should you use situational questions instead of behavioral ones?

• New graduates and early-career candidates, who have not managed a client or a team; see how to interview new graduates.
• Career changers, whose past situations look different from the new job; see how to interview career changers.
• New kinds of roles, such as the first hire in a function or work built on a new technology, where nobody has a directly comparable past.
• Rare, critical events, such as a safety incident or a data breach, that most candidates should never have faced.
• Your own context: a scenario lets you test how someone handles your specific constraints, which a past example from a different company cannot.

How do you write a situational question that is hard to fake?

1. Start from a real incident. Ask strong performers in the role about a moment that separated good from poor work, and what they did.
2. Build in a dilemma. Two reasonable goals in conflict, such as a client deadline against a promise to your manager, so there is no obvious right answer.
3. Give enough detail to decide, without requiring company-specific knowledge.
4. Do not signal the answer. "A customer is understandably upset" tells the candidate what tone you want.
5. Write the anchors before the first interview, from what the strong performers did.

Weak: "What would you do if a customer was angry?" Everyone says "listen and stay calm". Strong: question 2 below, where the customer wants something the candidate is not allowed to give and the person who made the promise is away.

Customer and stakeholder scenarios

1. "At 4 p.m. a long-standing client asks for a report by 9 a.m. tomorrow. You have already promised your manager a different piece of work for the same time. What do you do?"
   • Strong answer shows: finding out what the client actually needs and why, telling both people, and offering options rather than silently dropping one commitment.
   • Probe: "The client says it has to be the full report. Now what?"
   • 4: Clarifies the real need first, informs both, proposes options such as a partial delivery, and asks the manager to set the priority with a recommendation. 3: Informs both and agrees a plan. 2: Works all night to do both without telling anyone. 1: Drops one without saying so, or refuses the client outright.
2. "A customer is upset because a colleague promised something that did not happen. The colleague is on leave, and the customer wants a refund you are not authorized to give."
   • Strong answer shows: acknowledging the failure on behalf of the company, saying what they can do now, getting a decision on the refund quickly, and following up.
   • Probe: "Your manager is unavailable until tomorrow."
   • 4: Owns it without blaming the colleague, commits to a time for the decision, keeps it, and finds out what went wrong. 3: Apologizes, escalates and follows up. 2: Explains it was the colleague's promise. 1: Gives the refund without authority, or refuses with no follow-up.

Teamwork and conflict scenarios

3. "Two days before a deadline, a colleague tells you their part will be late. Your part depends on it."
   • Strong answer shows: finding the cause, re-planning together, offering help or cutting scope, and telling the people affected early.
   • Probe: "They ask you not to tell the manager."
   • 4: Understands the cause, re-plans, and makes sure the manager hears it from the colleague or with them, before the deadline. 3: Re-plans and informs the people affected. 2: Quietly absorbs the work. 1: Escalates without talking to the colleague, or lets the deadline slip silently.
4. "In a client meeting, a senior colleague quotes a figure you are fairly sure is wrong."
   • Strong answer shows: weighing whether the client will rely on it, correcting it tactfully before they do, and checking the figure afterwards.
   • Probe: "What if you are only 70% sure?"
   • 4: A proportionate approach, such as a quiet word in a break or a follow-up email, which ensures the client gets the right figure before acting on it. 3: Raises it with the colleague promptly. 2: Raises it only if asked. 1: Contradicts the colleague bluntly in front of the client, or lets it go.

Prioritization scenarios

5. "It's Monday. You have five tasks due this week, and your manager adds an urgent sixth. You can realistically finish four."
   • Strong answer shows: estimating the work, telling the manager early, recommending what to move, and agreeing new dates.
   • Probe: "Your manager says all six matter."
   • 4: Lays out the trade-off with a recommendation, asks the manager to choose, and tells the owners of moved work. 3: Raises it early and agrees priorities. 2: Tries to do all six and misses two. 1: Picks what to drop without telling anyone.
6. "You find that a process your team has used for a year occasionally causes small errors. A proper fix would take a week you do not have."
   • Strong answer shows: sizing the impact, adding a simple interim check, and proposing when the fix could be done.
   • Probe: "Who would you tell, and what would you say?"
   • 4: Quantifies the risk, contains it now, and brings a costed proposal to the manager. 3: Reports it with a suggested fix. 2: Mentions it informally. 1: Ignores it because it is small.

Integrity and judgment scenarios

7. "You notice a teammate has been rounding up their hours by about an hour a week."
   • Strong answer shows: checking the facts, raising it with the teammate or through the policy, and not ignoring it.
   • Probe: "The teammate is also a friend."
   • 4: Checks first, gives the teammate a chance to correct it, and escalates if it continues, regardless of the friendship. 3: Raises it with the teammate. 2: Unsure; would probably leave it. 1: Ignores it, or reports it publicly without checking.
8. "After you close a deal, the client offers you tickets to a sold-out final."
   • Strong answer shows: checking the gifts policy, disclosing the offer, and declining or getting approval.
   • Probe: "There is no written policy."
   • 4: Discloses and asks, considers how it would look to others, and declines gracefully if in doubt. 3: Checks the policy before accepting. 2: Accepts if nobody objects. 1: Accepts without a thought.

Problem-solving scenarios

9. "Orders for one product fell sharply last month. You are asked to find out why by Friday."
   • Strong answer shows: confirming the data first, splitting it by segment, testing the quickest explanations, and reporting with a stated level of confidence.
   • Probe: "The data team says the numbers are right. Where do you look next?"
   • 4: A structured plan, checks cheap hypotheses first, and separates what is known from what is suspected. 3: A sensible plan. 2: Jumps to one explanation. 1: No approach beyond asking others.
10. "A new tool your team adopted is creating more work than it saves. Your manager chose it."
    • Strong answer shows: gathering evidence, raising it with options, and respecting the decision.
    • Probe: "Your manager disagrees with you."
    • 4: Brings evidence and fixes to try, agrees a review date, and commits to the decision. 3: Raises it with evidence. 2: Complains to peers. 1: Stops using the tool quietly.

Leading-others scenarios

11. "You have just taken over a team. A strong performer has missed three deadlines this month."
    • Strong answer shows: a private conversation, asking before assuming, restating expectations, offering support and setting a follow-up.
    • Probe: "They say it is a personal matter they would rather not discuss."
    • 4: Respects their privacy, points them to HR or support resources, focuses on what work adjustment would help, and agrees a check-in. 3: Talks privately and sets expectations. 2: Waits to see if it improves. 1: Presses for personal details, or starts formal action at once.
12. "Two people on your team want the same development opportunity. Only one can have it."
    • Strong answer shows: criteria stated in advance, a transparent decision, and a plan for the other person.
    • Probe: "The one you did not choose asks why."
    • 4: Clear job-related criteria, an honest explanation, and a concrete next opportunity. 3: A fair decision explained. 2: Chooses on instinct. 1: Avoids deciding, or gives no reason.

A general 1–4 scale for situational answers

How to write question-specific anchors is covered in behavioral anchors for interview scores; the same method works for scenarios.

How do you stop candidates giving the textbook answer?

• Twist the scenario. The probes above remove the easy way out; the second answer usually scores more accurately than the first.
• Ask for the words. "What would you actually say to them?" separates a plan from a slogan.
• Ask about the cost. "What does your choice give up?" A candidate who cannot name a downside has not seen the dilemma.
• Score the reasoning, not confidence. A hesitant answer that weighs both sides beats a fast one that ignores half the problem.

Common mistakes with situational questions

• Obvious answers. If every candidate gives the same answer, the question measures nothing.
• Insider knowledge. Scenarios that need your systems or jargon reward people who already work somewhere similar.
• Changing the scenario between candidates. Read it from the kit, word for word, as in any structured interview.
• Using them for everyone. An experienced candidate's real example is better evidence than their hypothetical one.