Interview questions for decision making: 14 questions, probes and a 1–4 scale
On this page
- Decision making, defined as something you can observe
- Ten behavioral questions, with follow-up probes
- Four situational questions
- What strong and weak answers sound like
- A 1–4 anchored rating scale for decision making
- Adjusting the questions for seniority
- Common interviewer mistakes with decision making
- Questions people ask
Interview questions for decision making should get the candidate to reconstruct one real choice: what the options were, what they gave up by choosing one, how quickly they decided and why, and what they did once the result came in. Below are fourteen questions, ten behavioral and four situational, each with follow-up probes, plus sample strong and weak answers, a 1–4 anchored scale and the mistakes that most often distort this score.
If you already use behavioral interview questions with a scoring rubric, its "problem solving and judgment" section covers four classic decision questions, such as deciding without full information. None of those are repeated here. This page goes further into three things that section touches only briefly: timing, reversibility and follow-through. For evaluating the information that feeds a decision, use the separate set of interview questions for critical thinking.
Decision making, defined as something you can observe
Definition: decision making is choosing a course of action between real alternatives, at a pace that fits the stakes, and owning the trade-off and the result. Four behaviors make that visible in an interview answer:
- Framing real options. Describing at least two genuine alternatives, including doing nothing, rather than a single path that was never in question.
- Naming the trade-off. Saying what was given up by the choice, and why that cost was acceptable.
- Matching speed to stakes. Moving quickly when a choice was cheap to reverse and slowing down, gathering input or testing first when it was not.
- Following through. Committing once decided, checking whether it worked, and changing course when the evidence said so rather than out of discomfort.
Ten behavioral questions, with follow-up probes
-
Tell me about a decision you made quickly, where you felt speed mattered more than getting it perfect.
Probes: What would it have cost to wait a week? How easy would it have been to undo? -
Tell me about a decision you deliberately slowed down.
Probes: Who was pushing for a faster answer? What did the extra time give you that you would otherwise have missed? -
Describe a decision where you had to give up something you genuinely wanted.
Probes: What exactly did you give up? How did you explain the trade-off to the people it affected? -
Tell me about a decision you made that some of your colleagues disagreed with.
Probes: What was their strongest argument? What did you do to keep them working with you afterwards? -
Walk me through a decision you reversed after you had announced it.
Probes: What told you it needed reversing? How did you tell people, and what did it cost you? -
Tell me about a time you had to decide between what a customer or stakeholder asked for and what you thought they needed.
Probes: How did you check your view before overriding theirs? What happened? -
Describe a decision you made that sat right at the edge of your authority.
Probes: Why did you decide rather than escalate, or escalate rather than decide? Would you make the same call now? -
Tell me about a time you set up a small test before committing to a bigger decision.
Probes: What result would have made you stop? Did the test change the final decision? -
Tell me about a decision you delayed longer than you should have.
Probes: What were you waiting for? What did the delay cost, and what do you do differently now? -
Describe a decision where the result was good but you think you got lucky.
Probes: What part of your reasoning was weakest? What would you change if you faced it again?
Questions 9 and 10 are the most useful for separating genuine reflection from a polished story. Candidates rarely prepare for them, and the answer shows whether they judge their own decisions by process or only by outcome.
Four situational questions
-
"You have two days to choose between two suppliers. One is cheaper, the other has a better record with firms like ours. Your manager is unreachable. How do you decide?"
Probes: What would you want to know in the first hour? What would make you pick the cheaper one? -
"Three weeks after launching a new process you chose, early numbers are slightly worse than before. What do you do?"
Probes: How would you tell a real problem from normal noise? What would make you roll it back? -
"Your team is split evenly on an approach, and they want you to decide today. Walk me through the meeting."
Probes: What would you say to the half who lose? How would you know, later, whether you chose well? -
"You are asked to make a hiring decision, and the two interviewers you trust most disagree. What do you do?"
Probes: What evidence would you ask each of them for? When would you decide not to hire either candidate?
What strong and weak answers sound like
Illustrative answers to question 5, written to show the difference in shape.
Weak: "We rolled out a new approval process, but people didn't like it, so we went back to the old one. I think it's important to be flexible and listen to feedback."
The weak answer has no decision in it. There is no sign of who decided, what the alternatives were, what signal triggered the reversal, or whether the reversal itself was the right call. "People didn't like it" may have been the right reason, or it may have been discomfort with change that would have passed in a month. The candidate does not say which.
Strong: "I moved our team from weekly to daily candidate reviews because offers were going stale. I told everyone we would look at it again after four weeks. By week three, review meetings were eating two hours a day and time to offer had only improved by a day. I called it: we went to twice a week, which kept most of the gain. I sent a short note saying what the data showed and that the original call had been mine, so nobody who had pushed back felt they had to say I told you so."
The strong answer shows the options, a checkpoint set in advance, the evidence that drove the reversal, a middle option rather than a full retreat, and the candidate owning the original call.
A 1–4 anchored rating scale for decision making
| Score | Anchor |
|---|---|
| 1 — No evidence | Describes outcomes but no decision: choices were made by others, or only one option was ever considered. Cannot say what was given up. Judges past decisions only by whether they worked out. |
| 2 — Limited | Describes a real choice between options, but the reasoning is thin or reconstructed after the fact. Uses the same pace for every decision. Follow-through stops at announcing the choice. |
| 3 — Solid | Names at least two real alternatives, the trade-off accepted and why. Explains why the decision was made fast or slow. Describes checking the result and what they did with it. |
| 4 — Strong | Everything at 3, plus sets a checkpoint or a condition for reversal before committing, separates the quality of the decision from the luck of the outcome when reflecting, and keeps people who disagreed engaged after the call. |
For the reasoning behind a four-point scale and how to add a "not assessed" option, see our guide to the interview rating scale. If you want this competency on a printable card with the others for the role, the scorecard builder will lay it out.
Adjusting the questions for seniority
The same competency looks different at different levels. For individual contributors, decisions are mostly about approach and sequencing within their own work, and the most useful probes are about when they escalated. For managers, ask about decisions that affected other people's work and how they handled the ones who disagreed. For senior leaders, spend more time on reversibility and on decisions they deliberately delegated; how to interview for leadership roles covers that level in more depth. Keep the anchors the same and change the scope of the examples you expect.
Common interviewer mistakes with decision making
- Scoring the outcome instead of the decision. A candidate who took a sound bet that failed can be a better decision maker than one whose careless call happened to work. Ask what they knew at the time.
- Mistaking decisiveness for judgment. Confident, fast answers are easy to like. Ask what the decision cost and how reversible it was. Speed only counts when it matches the stakes.
- Accepting "we decided." Group decisions are real, but you need the candidate's part in it. Ask what they recommended and whether the group followed it.
- Never asking about a reversal or a delay. Stories about good decisions are easy to prepare. The questions about calls they changed or put off too long are where you learn how they actually think about their own judgment.
- Rewarding your own preferred answer on situational questions. There is rarely one right supplier or one right process. Score the options they framed and how they weighed them.
One practical note on write-ups: record the trade-off the candidate named, in their words. It is the single most useful line in a debrief, because it shows how they weigh competing goals, and it is the detail most often lost when notes are written from memory an hour later.
Questions people ask
Should I score a candidate on whether their decision turned out well?
Only partly. Outcomes depend on luck and on things the candidate could not see. Score the quality of the process given what they knew at the time: the options they considered, the trade-off they accepted, how they timed the call and whether they checked the result. A good decision can have a bad outcome, and a careless one can work out.
How do I assess decision making for a junior role with little authority?
Ask about decisions inside their own scope: how they sequenced their work, which approach they chose for a task, when they escalated and when they did not. Deciding when to ask is itself a decision, and junior candidates usually have plenty of examples of it.
Is a fast decision maker better than a careful one?
Neither is better in general. The skill is matching the speed to the stakes: moving quickly on choices that are cheap to reverse and slowing down on ones that are expensive to undo. A candidate who describes the same pace for every decision is showing a habit, not judgment.
Should candidates be marked down for escalating a decision?
Not if the decision genuinely sat outside their authority or needed information only someone else had. Mark it down when escalation was a way to avoid owning a call they were expected to make, and ask what they recommended when they escalated.