How to find candidates who can make tough decisions

Ask a candidate to walk you through a hard decision and you’ll usually get a polished story. The setup, the options, the call, and the happy ending where it all worked out. It sounds great. It also tells you almost nothing.

That’s the problem with most decision-making interview questions. They test how well someone narrates a decision, not how well they make one. Anyone who has interviewed a few times knows the move. Pick a win. Frame the stakes as high. Make the reasoning sound deliberate in hindsight. The story is built to land, and a prepared candidate can deliver it without ever showing you how they actually think under pressure.

Real decisions aren’t tidy. They get made with half the information you’d want, on a deadline, knowing some people won’t like the outcome. So the signal you’re hiring for isn’t a clean narrative. It’s what happened in the messy middle. What they gave up to choose. What they got wrong and how they caught it. Whether they’d defend the call today or quietly admit they’d do it differently. The questions below are built to drag that out, and the follow-ups matter more than the openers.

Why this is worth screening for

A bad decision-maker doesn’t usually blow up in a dramatic way. They stall. They wait for more data that never comes, escalate calls that were theirs to make, or lock onto a plan and refuse to move when the facts change. None of that shows up on a resume, and a degree or a job title won’t predict it. The cost lands later, on your team, in missed windows and projects that drift.

You’re looking for the opposite pattern. Someone who can act on incomplete information without being reckless about it, hold the call when it gets uncomfortable, and update when they’re wrong instead of digging in. That’s a behavior, and behaviors are best read from specifics, not from how confident someone sounds describing themselves.

Five questions that surface real decision-making

These work in a live interview or as prompts in a structured screening process when you’re moving through a lot of candidates at once. The framing matters. Each one is built to deny the candidate an easy win and make them show the tradeoff.

1. Tell me about a decision you made with information you knew was incomplete.

Most candidates default to a story where they had all the facts and chose well. This question takes that off the table. You want to hear what they did when the data ran out. Did they make a reasonable bet and own the uncertainty, or did they freeze and wait for someone else to decide? The tell is whether they can name what they didn’t know and still explain why they moved.

2. What’s the toughest call you’ve had to make at work, and how did you get there?

This one does double duty. What they pick as “tough” tells you the altitude they operate at. A scheduling conflict and a layoff are not the same calibration. Then listen to the reasoning. You’re after the options they weighed and why one won, not a dramatic retelling of the stakes.

3. Walk me through a time you had to choose between two genuinely good options.

Right-versus-wrong is easy. Good-versus-good is where judgment actually lives, because there’s no obvious answer to hide behind. The strong version of this answer names a clear tiebreaker, the thing they decided mattered most for the team or the project. The weak version is “I went with my gut,” which is a non-answer dressed as decisiveness.

4. How do you decide what to handle first when everything’s urgent?

A live problem most of your hires will face weekly. You’re not grading their time-management vocabulary. You want the actual logic they use to rank competing fires, and ideally a real example where they let something burn on purpose because something else mattered more. Anyone who claims it’s all equally important is telling you they don’t prioritize.

5. Tell me about a decision that wasn’t popular, and how you handled the fallout.

Plenty of people can make a call when everyone agrees. The harder skill is holding one that some of the room hates. Look for two things at once: that they stood behind a decision they believed was right, and that they handled the people side like an adult. Stubbornness and conviction look identical until you ask how the fallout went.

What to actually listen for

The instinct is to grade whether the story had a good ending. Resist it. Outcomes are noisy, and a candidate doesn’t control most of what happens after they decide. Score the process instead. Four things separate a real decision-maker from someone telling a good story about one.

• Did they think, or did they react? You want to hear options that were considered and rejected, not a straight line from problem to answer. The phrase you’re listening for is some version of “I almost went the other way, but.” If every decision they describe was obvious in hindsight, they’re narrating, not reasoning.
• Will they own the bad ones? Push on a decision that didn’t pan out. Strong candidates take the hit cleanly and tell you what they learned. Weak ones reroute the blame to a manager, the market, or a teammate. How someone talks about their misses is more honest than how they talk about their wins.
• Can new facts move them? Decisiveness without adaptability is just stubbornness with good posture. Listen for a moment where they changed course because the situation changed, and whether they can do it without treating it as a personal failure.
• Are they confident, or just loud? You want someone who can commit to a call and defend it. You don’t want someone who confuses volume with judgment. The difference shows up in whether their confidence is attached to reasoning or floating free of it.

When the answer stays generic

A lot of answers come back vague. “I weigh the pros and cons.” “I trust my team.” That’s a prompt to dig, not a reason to move on. Three follow-ups usually crack it open.

If they stay abstract, make them get specific. “Walk me through one time you actually did that, start to finish.” A real example has texture a rehearsed line doesn’t, and you’ll hear the difference fast.

If they describe the decision but skip the reasoning, ask what they ruled out. “What other options were on the table, and why did you pass on them?” The rejected options tell you more than the chosen one, because they show you what the candidate was actually weighing.

If their past examples run thin, hand them one of yours. Give them a real situation from the role and ask how they’d work the decision. It’s harder to fake on the spot than a story they’ve told before, and it shows you how they reason when they can’t reach for a script. For high-volume hiring, the same logic powers scenario-based assessments, which put every candidate through the same realistic situation and surface how they approach it. That’s a signal a candidate can’t outsource to a chatbot, because there’s no single right answer to look up.

Pairing the questions with the rest of your screen

Asked one at a time in a live interview, these questions work well. The trouble is time. If you’re sitting on 200 applicants for one position, you can’t run a 45-minute conversation with each just to find the handful worth a real interview. That’s where the questions earn their keep upstream of the live round.

Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments. Drop these prompts into a one-way interview and candidates answer on camera, on their own time. AI transcribes each response, scores it against the criteria you set, and clips the most revealing 30 seconds so you’re not watching every full answer to find the moment that matters. It surfaces the evidence. You still make every call.

The point isn’t to outsource the judgment. It’s to spend it on the right people. Read decision-making across a recorded answer and a scenario assessment before you book a call, and the live interview stops being a filter. It becomes the conversation you have once you already know the person can think.

The shift worth making

The deeper change here isn’t a better question bank. It’s what you treat as evidence. A confident story about a past decision is the cheapest signal in the room, and it’s getting cheaper as candidates rehearse with the same AI tools you’re using to screen them. The durable signal is reasoning you can watch happen: the tradeoff named out loud, the miss owned without flinching, the answer that moves when you add a new fact.

Hire for that, and you stop selecting for people who interview well about decisions. You start selecting for people who make them, which is the only version of this skill that shows up after the offer is signed.