"What would you do if two managers gave you conflicting priorities on the same day?" It is a strange kind of question. There is no story to reach for, because it has not happened, at least not in that exact shape. So you float there, inventing a version of yourself on the spot, hoping the invented version sounds hireable.
Situational questions feel harder than behavioral ones precisely because there is nothing real to stand on. But there is a technique that puts the ground back under you: reason through the hypothetical, then bridge to the nearest true thing you have actually done. This article shows you how, and covers the trap that catches most candidates: describing a perfect process you have never once followed.
Why do interviewers ask hypotheticals instead of asking about your past?
Situational questions exist for good reasons, and knowing them changes how you answer:
- They level the field. A new grad has no "tell me about a time you managed a vendor dispute" story. A hypothetical lets interviewers compare candidates with unequal histories.
- They test the actual job. The scenarios are often lifted from the team's real life: the difficult customer they actually have, the outage that actually happened. Your answer is being compared to what good performers actually did.
- They expose reasoning. A past-tense story shows what you did; a hypothetical shows how you think when there is no script. Interviewers get to watch you prioritize in real time.
That last point is the key to answering well. The deliverable is not a correct answer. It is visible, sensible reasoning. Which is good news, because reasoning is something you can do out loud without inventing anything.
The two-step bridge: reason, then anchor
Here is the whole technique.
Step one: reason through the hypothetical out loud. Do not jump to a conclusion. Walk the interviewer through your process in three or four moves:
- What you would want to know first ("First I'd find out whether both deadlines are actually fixed, because often one isn't.")
- Who you would involve ("I'd go to both managers together rather than relay messages between them.")
- How you would decide ("If they can't align, I'd ask which one owns my priorities and get the call made explicitly, in writing.")
- What you would do to prevent the repeat ("And I'd suggest a standing priority check so this doesn't become monthly.")
Step two: anchor it to the nearest true thing. Then say the bridge sentence:
"The closest real situation I've faced was..."
And tell that story briefly: 30 seconds, real details, real outcome. It does not need to match the hypothetical exactly. A conflicting-priorities hypothetical can be anchored by any real moment you had too much work and had to force a prioritization conversation. The anchor's job is to prove your reasoning is not just theory, that some version of this thinking has actually run in production.
This is why a prepared story bank pays off twice: the same six to eight true stories that answer behavioral questions become your anchors for situational ones. If you have not built one, the mining process is in behavioral interview prep: build a story bank.
The perfect-process trap
Here is how honest candidates accidentally lie in situational answers: the hypothetical invites you to describe best practice, so you do. "I would document everything, escalate through proper channels, schedule a retrospective..." You have never done any of that. You are describing a textbook, not yourself.
Interviewers catch this two ways. First, the follow-up: "Have you actually done that?" If the honest answer is no and you say yes, you are now defending fiction, and it unravels the way all interview fiction does. Second, texture: real process descriptions include friction ("in practice the hard part is getting time on both calendars") and textbook recitals do not. Experienced interviewers hear the difference immediately.
The fix is not to hide the ideal; it is to be honest about the gap between ideal and practice:
"The textbook answer is to escalate immediately. Honestly, in my experience the escalation lands better if I've first spent an hour confirming the problem is real, so that's what I'd do first."
That answer is more impressive than the clean version, because it could only come from someone who has been in the room. If a follow-up does catch you past the edge of your experience, say so and reason from there; there are exact scripts for that moment in what to say when you don't know the answer.
Common situational questions and where their anchors hide
Some frequent hypotheticals, and the kind of true story that anchors each:
- "What would you do if you disagreed with your manager's decision?" Anchor: any real disagreement, even a small one, where you voiced it and then either changed a mind or committed to the decision anyway.
- "What if you saw a coworker doing something wrong?" Anchor: a time you gave difficult feedback or flagged a problem, even informally.
- "What if a customer demanded something impossible?" Anchor: any real expectation-setting conversation, with a customer, a stakeholder, or even a teammate.
- "What if you were falling behind on a deadline?" Anchor: the real crunch, and specifically the moment you raised the flag early instead of hoping.
- "What if you were given a task with no instructions?" Anchor: any ambiguous assignment where you drafted an approach and got it sanity-checked before building.
Notice the pattern: the anchor is almost never a dramatic match for the hypothetical. It is a smaller, ordinary moment that shares the same muscle. Interviewers accept that trade happily; they are checking that the muscle exists.
Keep your anchors short and structured
When you cross the bridge into a real story, do not let it sprawl. Use a compressed three-beat shape: one sentence of setup, two or three actions in first person, one concrete result. That is a light version of the STAR structure, and the full version is worth knowing for when interviewers dig deeper; see STAR method answers from your real experience. Then hand the conversation back: "...so faced with your scenario, I'd start the same way."
That closing loop, hypothetical to reasoning to real story back to hypothetical, is what a complete situational answer sounds like. It typically runs 60 to 90 seconds. Longer means you are narrating; shorter usually means you skipped the anchor.
Know your experience cold before you need to reach for it
The bridge technique has one dependency: you have to be able to find your nearest true story in about two seconds, mid-interview, under pressure. That recall does not come from talent. It comes from having audited your own history recently enough that it is all within reach, the same discipline behind being able to defend every line on your resume.
Start with the free Bounce scan at careerbounce.io. It runs on your device, private, and shows you your resume exactly as the hiring bots and interviewers read it: every claim you have made, every experience you can draw on. Rehearse from what is actually on the page, attach a true story to each line, and the next "what would you do if" stops being a void. It becomes a question you answer standing on solid ground. No promises about offers; just no more floating.