Situational interview questions — why "what would you do" is harder to fake than it looks
Situational questions feel easier than behavioral ones because you can just make up a reasonable-sounding answer. That's exactly what interviewers are trained to notice.
Situational and behavioral questions get lumped together constantly, and they're not the same thing. Behavioral asks about something that actually happened: "tell me about a time you missed a deadline." Situational asks about something hypothetical: "what would you do if you disagreed with a deadline you thought was unrealistic." The second one feels easier to answer, because there's nothing to remember — and that's exactly the trap.
Why situational questions are harder to fake than they seem
A behavioral question is checked against reality — the interviewer can ask a follow-up that only makes sense if the story is true. A situational question has no reality to check it against, which is precisely why interviewers listen for something different: not whether your answer sounds reasonable, but whether it sounds like your reasoning, built in real time, rather than a generic best-practices answer assembled from things you've read.
The tell is genericness. "I would communicate with the stakeholders and try to find a solution that works for everyone" answers nothing — it could be the answer to almost any situational question ever asked. A real answer names the actual first move, the actual tradeoff being weighed, and usually a version of "here's what I'd do, and here's the risk I'd be accepting by doing it."
The most common situational questions, and what they're really testing
"What would you do if you were given a project with an unrealistic deadline?" The weak answer is "I'd work extra hours to make it happen" — which avoids the actual decision the question is testing: do you escalate, renegotiate scope, or just absorb the risk silently. A strong answer picks one of those, explains why, and acknowledges what it costs. Silently absorbing an unrealistic deadline without saying anything is often the wrong answer, even though many candidates think it sounds like dedication.
"How would you handle disagreeing with your manager's decision?" This is checking whether you can push back without either capitulating instantly or being combative. The answer worth having ready: state your concern once, clearly, with reasoning — then commit to the decision once it's made, unless it's a genuine ethical or safety issue. Interviewers are listening for whether you'd actually say something, not just for the right words about "healthy disagreement."
"What would you do if you noticed a coworker taking credit for your work?" There's no universally correct answer here, but there's a clearly weak one: an answer that skips straight to escalating to a manager without first describing a direct conversation. The stronger answer shows a sense of proportion — address it directly first, escalate only if it continues or the stakes are high enough to justify it.
"How would you prioritize if you were given three urgent tasks at once?" This question is really asking whether you have an actual method, or just a feeling. A strong answer names a real prioritization approach — impact, dependency, and who's blocked by what — rather than "I'd just figure out what's most important," which explains nothing about how.
"What would you do if you strongly disagreed with a company policy?" The trap answer is either extreme: silent compliance, or "I'd push back until it changed." The stronger answer distinguishes between policies you can influence through the normal channels available to you, and policies you can't — and is honest that some things aren't worth quitting over and some things are.
What actually separates a strong answer from a weak one
Not the conclusion — there's rarely one "correct" action. What separates them is whether the reasoning behind the choice is visible and specific, or whether the answer is a string of things that sound responsible without committing to an actual tradeoff. Interviewers have heard the safe, vague version of every situational question hundreds of times. The version that stands out is the one that picks a side and explains the cost of picking it.
If you want to practice situational questions out loud and get a real follow-up when your answer stays too generic, try role-specific mock interviews — free to start.