Situational Interview Questions: 12 Scenarios With Sample Answers

TL;DR — Situational questions ("what would you do if…") are the forward-looking half of an interview: you get a scenario you haven't lived, and you're graded on how you think. Answer in four moves — state what you'd assume, name what's at stake, walk two or three concrete steps out loud, and land on a decision. Use a real example when you have one. And don't stop at the obvious fix; the answers that score highest keep going.

Behavioral questions ask what you did. Situational questions ask what you would do, and that change of tense changes everything. There's no story to retrieve, no result to quote, and usually no clean right answer — just a scenario, often an uncomfortable one, and an interviewer watching you reason through it live. Candidates who prepared only stories stall here. Below: what these questions measure, the answer shape that works, and twelve scenarios with sample answers.

What situational questions are actually testing

The U.S. Office of Personnel Management, which sets the federal government's hiring-assessment standards, draws the line precisely. Situational interview questions "ask applicants to describe what they would do or how they would behave in a situation similar to those encountered on the job." Behavioral questions work the other way, on the principle that past behavior predicts future behavior. OPM's practical guide to structured interviews spells out the premise: situational questions "give the candidate realistic job scenarios or dilemmas and ask how he/she would respond," because "a person's intentions are closely tied to his/her actual behavior."

They aren't filler. OPM notes both formats "have proven to be effective," and that more structured interviews "show higher levels of validity, rater reliability, rater agreement, and less adverse impact." A "what would you do" question is often a scored rubric item, not small talk.

Which raises the part almost nobody prepares for: many employers grade these answers against written proficiency levels. OPM's guide publishes a worked example — an investigator is offered a car far below market value by a suspect. Unsatisfactory: accept it. Satisfactory: "say no to the offer and continue the investigation; document the incident in your report." Superior: probe how the dealership can offer that price, try to get contact information for others involved, decline, and document the details. Both passing answers refuse. The superior one refuses and keeps going. That gap is where most candidates quietly lose points.

Expect follow-ups. OPM's sample probes for a situational item include "What factors would affect your course of action?" and "What would you do if your action was not received well?" Your first answer is rarely the whole answer.

How to structure a situational answer

Cal State LA's career-center worksheet on "What Would You Do If…" questions uses a compact three-part frame — Action, Reasoning, Considerations: what you'd do, why you'd do it that way, and "what factors shaped your decision to take that action." That third beat is the one candidates skip, and it's exactly where judgment becomes visible.

Two other career offices supply the bookends. Northwestern's Public Interest Center interviewing guide coaches students facing hypotheticals to "spot any legal, ethical, or factual issues out loud, including the issues for which you have limited information," because doing so "demonstrates that you have good instincts." It adds a line worth stealing for any job: "you do not exist in a vacuum" — say you'd gather more facts and raise the issue with your supervisor before recommending a path.

Then actually decide. The University of Connecticut's guidance on hypothetical ethics questions is blunt about it: acknowledge both points of view, but "be sure to decisively choose one point of view to support and explain why you chose that path," and "articulate all present and future implications of your decision." A thoughtful tour of the considerations that never lands anywhere reads as an evasion.

Four moves, in order:

1. Assume out loud. One sentence naming what you don't know and what you'll assume. It buys thinking time and scores points.
2. Name the stake. What actually matters here — the customer, the deadline, the money, the relationship.
3. Walk two or three concrete steps. In order, first person. Not "I'd communicate" — who you'd talk to and what you'd say.
4. Land it. Commit, then say what would change your mind.

Use a real example when you have one

Western Governors University's guide to situational interviews is right that when you have no direct experience with the scenario, "you can still provide a logical, well-reasoned response" — outline a step-by-step approach and draw on related experiences even when they aren't identical. But when you have lived something close, tell that instead: a real outcome beats a hypothetical, and the shape for it is the STAR method. The formats are closer than they look — OPM's guidance on writing structured interview questions applies STAR to both, defining the Action beat as "exactly what was done or what would be done." Same skeleton, different tense. The strongest answers do both: the reasoning, then "I've had a version of this, and here's how it went."

You'll usually meet these in the interview proper rather than the opening call, which stays closer to logistics and fit; that earlier round is covered in phone screen questions and answers.

12 situational questions and sample answers

Deadlines, priorities, and scope

1. "What would you do if you realized you were going to miss a deadline?"

Testing: whether you escalate early or go quiet and hope. Silence is the failure mode here.

"The moment I'm confident I'll miss it — not the day it's due — I'd tell whoever's depending on it, with three things ready: a realistic new date, what caused the slip, and what I can still deliver on time in case a partial handoff unblocks someone else. Then I'd ask whether they'd rather cut scope or move the date, because that's their call. Flagging early is usually the whole difference between a problem and a non-event."

2. "Two projects are due the same day and you can't finish both. What do you do?"

Testing: prioritization, and whether you make the tradeoff visible instead of silently picking one.

"First I'd check whether they're actually equal, because usually they aren't — one has a hard external date and the other is internal and movable. If I truly can't tell, I'd ask both requesters which one gives if I can only land one; that question alone tends to resolve it. Then I'd clear anything short that's blocking another person, protect one uninterrupted block for the bigger piece, and send both a one-line status so nobody is guessing."

3. "A project's scope changes a week before delivery. How do you handle it?"

Testing: adaptability without martyrdom — can you renegotiate rather than absorb?

"I'd ask what changed, because the reason usually tells you what to protect. Then I'd re-price the work out loud: here's what's still possible by the original date, here's what moves, here's the first thing I'd cut. I'd rather hand someone options than a warning. What I wouldn't do is quietly absorb it and hope, because that's how you ship late and surprise everyone. Adjust the plan visibly instead of the quality invisibly."

4. "A colleague is out unexpectedly and you're asked to cover. What's your approach?"

Testing: triage and communication under a workload you didn't plan for.

"I'd find out what's genuinely time-critical in their queue rather than trying to be them. Anything with an external deadline or a waiting customer, I'd handle or hand off. Anything that can wait, I'd note and leave. I'd tell my own manager what's slipping on my side so the coverage isn't invisible work, and keep a short log of what I touched so the handback takes ten minutes."

People and conflict

5. "What would you do if you had a conflict with a coworker?"

Testing: whether you go to the person or around them.

"I'd separate the disagreement from the person. Usually we're clashing because we're optimizing for different things — they want it shipped, I want it right — and naming that out loud takes most of the heat out. I'd go to them directly and in private, ask what they're seeing that I'm not, and agree on the criteria before arguing about the answer. If it's still blocking the work, I'd bring in whoever owns the decision."

6. "What if you disagreed with your manager's decision?"

Testing: whether you can push back once, professionally, and then commit.

"I'd make the case once, properly — privately, with my reasoning and whatever evidence I have, framed as a risk rather than an objection. I'd also ask what I might be missing, because managers usually have context I don't. If they hear it and still choose their path, I commit and execute it well; a decision everyone relitigates is worse than a merely imperfect one. The exception is anything unsafe, dishonest, or against policy — that I'd escalate."

7. "Your teammates are goofing off and the project is falling behind schedule. What would you do?"

Testing: close to OPM's own published example. They're watching whether you diagnose before you accuse.

"I'd check my assumption first, because 'not pulling weight' can also be someone blocked, overloaded elsewhere, or unclear on what they own — and those get fixed very differently from not caring. So I'd ask, without the accusation: here's where we are against the deadline, what's in your way? If it's a blocker, I'd help clear it. If the work still isn't happening, I'd raise the schedule risk with whoever owns the project, framed around the deadline rather than the person."

8. "An angry customer says they never received something you sent days ago. What do you do?"

Testing: composure, ownership, and whether you close the loop. OPM uses almost this exact scenario to assess interpersonal skills.

"I'd let them finish, then repeat the problem back so they know I heard it — a lot of the anger comes from being passed around, not from the delay. Then I'd own the next step out loud: I'll find out where it is, and here's when I'll come back to you, even if the answer that day is 'still looking.' If we were late, I'd say so plainly, and flag what caused it so the next person doesn't get the same call."

Ambiguity and judgment

9. "What would you do if you were given instructions you didn't understand?"

Testing: whether you ask early — and whether you can ask a good question.

"I'd much rather ask a slightly dumb question on day one than deliver the wrong thing on day five. But I'd make it specific instead of 'I'm confused' — something like 'I'm reading this as X, and I'd start with Y, is that right?' A concrete guess is far easier for someone to correct than an open-ended ask. If they aren't available, I'd write down my interpretation, send it, and start on the part I'm confident about."

10. "You have to make a decision and you don't have enough information. What do you do?"

Testing: bias toward action, tempered by reversibility.

"I'd first ask whether it has to be decided now or can wait an hour while I find out. If it can wait, I'd get the missing facts and check with whoever owns it. If it can't, I'd take the reversible option — the one that's cheapest to undo if I'm wrong — write down what I assumed and why, and tell my manager the same day so it isn't a surprise later. Stalling is itself a decision, just with worse odds."

11. "What if you made a mistake that couldn't be undone?"

Testing: accountability, containment, and whether you fix the system afterward.

"Report it fast, and lead with impact rather than explanation: what broke, who's affected, what I've already done. Then contain it — even when the mistake itself is permanent, the consequences usually aren't finished spreading. I'd take the fix as far as it goes and own it without excuses. Then I'd change whatever let it happen: a checklist step, a second pair of eyes. 'I'll be more careful next time' isn't a fix."

12. "What would you do if you were asked to do something you believed was unethical?"

Testing: integrity under authority — and, per OPM's rubric, whether you stop at "no" or follow through.

"I'd assume good faith and ask a clarifying question first, because sometimes what sounds wrong is a badly worded request or context I'm missing. If it is what it looked like, I'd decline on the substance rather than on feelings — not 'I'm uncomfortable' but 'this would tell the client something that isn't true' — and offer the version I can do instead. I'd follow up in writing so there's a record of what was asked and what I proposed, and if it kept coming, I'd raise it with my manager or the company's reporting channel. Going along and hoping it stays small isn't an option."

UConn's advice on ethics hypotheticals is to explain the thought process behind the judgment call, address any legal issues directly, and weigh the downstream implications. Interviewers aren't looking for someone merely uncomfortable with wrongdoing — they want someone who will name it, document it, and route it to the right person.

Mistakes that sink situational answers

• Answering with a policy instead of a person. "I'd follow the process" tells them nothing. Say who you'd talk to and what you'd say.
• Never landing. Weighing both sides is the setup, not the answer. Choose, and say why.
• Skipping the assumption. These scenarios are always underspecified. Name the missing piece instead of quietly inventing it.
• Stopping at the obvious fix. In OPM's rubric, the superior answer does the obvious right thing and then investigates, documents, and prevents the repeat.
• Being the only competent person in the story. Escalating and looping people in are strengths here, not admissions.
• Forgetting the follow-up. "What if that didn't work?" is a standard probe. Have a second move ready.

These prompts work in reverse, too: if you want to know how a team really handles a scope change, ask them — good questions to ask the interviewer get graded much like your answers do.

Situational questions reward a different kind of rehearsal than behavioral ones. You're not memorizing a story; you're practicing a shape until reasoning out loud stops feeling like floundering. Take three of the twelve above, say them aloud, and time yourself — 60 to 90 seconds each is plenty. Then build the rest of the interview around them with the 50 common interview questions.

Sources

• U.S. Office of Personnel Management — Structured Interviews (assessment method overview)
• U.S. Office of Personnel Management — Structured Interviews: A Practical Guide (September 2008)
• U.S. Office of Personnel Management — How do I create structured interview questions?
• California State University, Los Angeles — "What Would You Do If…" Answering Situational Questions
• University of Connecticut Center for Career Readiness and Life Skills — Ethical Interview Question Tips
• Northwestern Pritzker School of Law, Public Interest Center — Interviewing with Public Interest Employers
• Western Governors University Career & Professional Development — Situational Interviews