Decisions are easy to talk about in retrospect. By the time a candidate is describing a decision in an interview, they know how it turned out. They've had time to edit the story. They can frame their thinking to sound more deliberate, more balanced, more prescient than it probably was in the moment. What you actually want to know is how someone decides when the outcome is genuinely uncertain, when the information is incomplete, when there's pressure to go one way. That's very hard to get at through retrospective storytelling.
It's also worth being honest about the social dynamics at play. In an interview, a candidate describing a decision they made has every incentive to present it as thoughtful, well-reasoned, and successful. They'll remember it that way, even if it wasn't. The messy middle, the moments of doubt, the information they ignored or got wrong, tends to get edited out.
Despite all that, there are questions worth asking. Below are five that at least get beneath the surface, alongside an explanation of why interviews struggle with this trait, and what tends to work better.
5 decision making interview questions
These questions are designed to get at how someone actually decides rather than how they'd like to be seen deciding. Listen carefully for whether they describe a genuine process or just a good outcome. The two aren't the same thing.
"Tell me about a time when you had to make a significant decision without having all the information you needed."
This question is specifically about decision-making under uncertainty, which is where real decision-making skill shows up. Strong answers will be honest about what was missing, how the candidate decided anyway, and how they felt about the remaining uncertainty. You want to hear about their process for coping with incomplete information, not a story that magically resolved once they'd gathered enough data.
Watch out for answers where the missing information was actually quite minor, or where the candidate found a way to gather it all before deciding. That's a different skill. The interesting question is what they do when they genuinely can't know enough.
Probing questions
- What was the most important thing you didn't know, and how did you work around that?
- How did you decide when you had enough information to proceed?
- Looking back, were there things you wish you'd weighted differently?
"Describe a time when you reversed a decision after realising you'd got it wrong."
This is harder to answer well than it sounds. Admitting you got something wrong in a job interview is uncomfortable, and most candidates will reach for an example where the reversal was clearly the right thing and everyone agreed. Strong answers go further: they're specific about what the candidate originally missed, what made them realise it, and how they managed the awkwardness of changing course.
The ability to reverse a decision is genuinely important. People who can't do it tend to throw good effort after bad, and that shows up in roles at every level.
Probing questions
- What was the original reasoning, and what specifically turned out to be wrong about it?
- How quickly did you realise, and what triggered it?
- How did you communicate the reversal to the people affected?
"Tell me about a time when you made an unpopular call that you stood behind."
Good decision-making sometimes means disagreeing with the room. This question is asking about the experience of making a decision that others pushed back on, and holding to it. Strong answers will be clear about why the candidate stood firm (not just stubbornness, but a genuine assessment of the evidence), how they managed the interpersonal dimension, and what happened in the end.
Be a little sceptical of answers where the candidate stood firm and was completely vindicated. Real situations tend to be more ambiguous. An honest answer might acknowledge that the pushback had some merit, even if the decision was ultimately right.
Probing questions
- What was the nature of the disagreement? Were others seeing something you weren't, or were they reacting to something else?
- How did you manage the relationship with the people who disagreed?
- Would you make the same call again in the same circumstances?
"Describe a situation where you had to weigh up competing priorities to decide where to focus limited resources."
Resource allocation decisions are common in almost every professional role, and they're genuinely hard. Strong answers will be specific about what the competing priorities were, what criteria the candidate used to make the call, and how they handled the people or projects that didn't get what they wanted. This is a good question for surfacing how someone thinks about trade-offs, rather than just how they deal with difficult choices once they've been framed for them.
Probing questions
- What were the competing options, and why was it hard to choose between them?
- What criteria did you use to make the call?
- How did you manage the expectations of the people whose priorities didn't get prioritised?
"Tell me about a decision you made that had consequences beyond your immediate team or area."
This question is asking about systemic thinking: whether the candidate considered second-order effects, stakeholders they weren't directly accountable to, or downstream consequences they weren't responsible for managing. Strong answers show awareness that decisions don't exist in isolation, and some deliberate thought about ripple effects. Weak answers tend to describe the decision in isolation, as if nothing beyond the immediate context existed.
Probing questions
- How did you become aware of the broader implications? Was that part of your original thinking or did it emerge later?
- Did you involve anyone from outside your immediate team in making the decision?
- Were there any unintended consequences you hadn't anticipated?
Why interviews aren't the best tool for this
The main problem is that decision-making in an interview is entirely retrospective. Every answer describes a decision that's already been made, whose outcome is already known. That context changes everything about how the story is told. Candidates don't describe their uncertainty, their wrong turns, the moments where they nearly went a different way. They describe the path that led to the outcome, and the outcome was good enough for them to be using it as an interview example.
There's also a strong selection effect at play. People choose examples where they decided well. They don't describe the time they made a poor call at a critical moment, misread the available information, or held to a position that turned out to be wrong. The sample you're drawing from is self-selected in a way that systematically overstates capability.
And interview skills themselves muddy the picture. A candidate who is confident, structured, and persuasive will describe any decision in a way that sounds considered and rigorous, even if the actual decision-making was reactive or poorly thought through. The reverse is also true: someone who decides carefully but explains themselves hesitantly can come across as less capable than they are.
Interviews are late in the process to be discovering someone isn't who you thought they were.
What actually works for measuring decision making
The best tool for measuring decision-making directly is a situational judgement test (SJT). Unlike interviews where candidates describe past decisions, an SJT presents realistic work scenarios and asks candidates to choose between possible courses of action. This gives you actual decision-making behaviour in context, not a curated story about it.
The scenarios in a well-designed SJT reflect the kinds of decisions that actually come up in the role, which makes the results meaningfully predictive of how someone will perform in that specific job. You're measuring decision quality, not narrative quality, and the two are not the same thing. Candidates can't easily prepare for an SJT the way they can prepare interview stories, which gives you a more honest read on how they actually think when they're working through a problem.
We cover this in much more depth in our article on how to assess soft skills, but the core idea is that presenting candidates with realistic decisions to make gives you better information than asking them to describe decisions they've already made.
Conclusion and next steps
Behavioural interview questions about decision-making can surface useful material, particularly around how candidates handle reversals, unpopular calls, and decisions with broader consequences. But they're inherently limited by the fact that you're hearing about decisions after the fact, from someone who's had time to construct a flattering account.
If you want a more reliable read, our situational judgement tests are designed by business psychologists and validated against job performance data. They put candidates in realistic decision-making situations rather than asking them to narrate past ones.
Ben Schwencke
Chief psychologist at Test Partnership. MSc in Organisational Psychology with over ten years experience in psychometric testing.
