Situational Interview Questions and How to Answer a Hypothetical Well
Situational questions hand you an imaginary problem and watch you reason. The trap is that hypotheticals invite vague answers — and vague answers are exactly what these questions are designed to expose.
Situational Is Not Behavioural
They sound similar and are scored differently. Answering one as though it were the other is the most common mistake on this page.
Tell me about a time you missed a deadline. It is answered with a real story, usually in STAR form, and the evidence is what actually happened.
What would you do if you were about to miss a deadline. There is no story to tell, so the evidence is the quality of your reasoning and your priorities.
Judgement. Situational questions exist because interviewers want to test judgement in scenarios you may never have faced, or because you are early in your career and have fewer stories.
Answer the hypothetical properly, then add one sentence of real experience: this is close to something I handled at my last job, and here is what it taught me. That is the version that scores highest.
Clarify, then decide, then act, then check. Ask the one or two things you would genuinely need to know, state the judgement you would make and why, describe the concrete steps in order, and say how you would know whether it worked. Anchor it to something you have actually done, if you can — that is what turns a hypothetical answer into evidence.
Eight Ways to Prepare for Hypotheticals
You cannot memorise answers to invented scenarios, but you can absolutely prepare the material they are built from.
Situational questions are written from the risks of the role. A job that mentions competing stakeholders will produce a competing-stakeholders hypothetical. This is highly predictable.
Conflict, failure, deadline pressure, an unpopular decision, a difficult customer, a mistake you caused. You will graft these onto hypotheticals as evidence.
When safety, quality, cost, and speed conflict, what do you protect first? Knowing your own ordering in advance makes every situational answer coherent.
In their org, who owns what. Answers that name plausible roles rather than saying the relevant people sound like someone who has done the job.
One or two sharp questions is good judgement. Five is avoidance, and interviewers will tell you to just assume — which costs you the opening.
Hypotheticals tempt people into it depends. Say what it depends on, then pick a branch and answer it. The commitment is what is being scored.
Good interviewers change the scenario mid-answer: now imagine your manager disagrees. Expect it, and treat it as interest rather than a trap.
Hypotheticals sprawl because there is no natural ending. Two minutes is the ceiling, and it forces the structure that makes the answer good.
Eight Situational Questions and How to Answer Them
Each of these is testing one specific thing. Knowing which makes the answer much easier to aim.
"What would you do if you were given a deadline you knew was impossible?"
Testing whether you escalate early or fail quietly. Say you would confirm the scope and the constraint, quantify the gap, then go to the owner with options rather than a problem: cut scope, add people, or move the date. Never say you would just work harder and hope.
"What would you do if you disagreed with your manager's decision?"
Testing whether you can disagree and still commit. Raise it privately, with evidence, once. If overruled, support the decision publicly and ask what would change their mind. The second half is the whole answer — many candidates only give the first.
"What would you do if a colleague was not pulling their weight?"
Testing whether you escalate straight over someone's head. Talk to them first and assume a cause you cannot see. Only if it continues and affects delivery does it go to a manager, framed as impact on the work rather than as a complaint about a person.
"What would you do if you made a mistake nobody had noticed?"
Testing integrity, and the answer needs no hedging. You raise it immediately, with the impact quantified and a fix proposed. Add what you would change so it cannot happen again. Any hesitation here is fatal.
"What would you do if two senior stakeholders wanted opposite things?"
Testing whether you manage upward or freeze. Get both positions in writing, find the shared objective underneath, propose an option that serves it, and put the trade-off in front of both of them together rather than shuttling between them.
"What would you do in your first thirty days here?"
Testing whether you are humble and systematic. Learn first: the systems, the people, the current commitments. Then find one small thing to fix and ship it. Promising a transformation before you have seen anything is the wrong answer.
"What would you do if a customer asked for something you could not deliver?"
Testing whether you over-promise. Say no clearly and early, explain what is possible instead, and be specific about the timeline. Candidates who invent a way to say yes are showing you exactly how they would behave under pressure.
"What would you do if priorities changed halfway through a project?"
Testing whether you can stop cleanly. Confirm the new priority is real and comes from the right person, document where the current work stands so it can be picked up, then move. Quiet resistance is the failure mode being tested for.
Eight Ways to Keep a Hypothetical Concrete
Every technique here fights the same enemy: an answer that could have been given by anybody about any job.
One sharp question shows you scope before acting. A pile of them reads as reluctance to commit, and the interviewer will cut you off.
The product owner and the on-call engineer, rather than the relevant stakeholders. Specific roles make the answer sound lived rather than theoretical.
Order is the judgement. An answer listing five actions with no sequence tells the interviewer nothing about how you prioritise.
One sentence connecting the hypothetical to something you actually handled converts opinion into evidence, and it is the single strongest move available here.
Every decision costs something. Naming what you would give up is what separates a considered answer from an optimistic one.
It depends is a fine opening clause and a terrible answer. Say what it depends on, choose the likeliest case, and answer that.
How would you know it worked? Almost nobody answers this, and it consistently marks out the more senior-sounding candidate.
Hypotheticals have no natural end, so they sprawl. Finish with your check step and let them ask the follow-up they were already planning.
Four Questions Worth Asking Back
Situational questions are drawn from real friction in the team. You can ask about that directly.
"Was that scenario hypothetical, or does it come up here?"
Entirely fair to ask, often answered honestly, and it tells you what the job is really like.
"When priorities change here, how does that usually get communicated?"
Reveals whether the organisation is decisive or chaotic, which is the difference between two very different jobs.
"How are disagreements between senior stakeholders normally resolved?"
You will inherit whatever the answer is, and there usually is a well-worn pattern.
"What is the last thing that went wrong here, and what happened afterwards?"
The response to failure tells you more about a culture than any values page, and the pause before the answer is informative too.
"First I would check whether the date is fixed by something external or just inherited, because that changes everything. Assuming it is fixed, I would quantify the gap and take the product owner three options: cut the reporting module, add a second engineer for two weeks, or ship the core on time and follow with a second release. I would recommend the third, because it protects the launch and the trade-off is only a two-week delay on the part nobody uses in week one. I had almost exactly this at my last job, and shipping in two parts was what saved it. I would know it worked by whether the launch metrics held in the first fortnight."
Six Ways Hypotheticals Go Wrong
Name the variable, pick the likeliest branch, and answer it. Refusing to commit is read as an inability to decide.
I believe in open communication is not an answer. What would you do, in what order, on Monday morning?
In most people-related hypotheticals, going over someone's head immediately is the wrong first move and is exactly what is being tested.
One sentence of grounding turns a plausible answer into a credible one. Bridge to something you have actually done.
Questions about disagreement are really about what you do after being overruled. Questions about mistakes are really about prevention. Finish the arc.
No natural ending means you have to supply one. Two minutes, then stop and take the follow-up.