Interview questions for judgment: 14 questions about what matters, when to act and when to escalate
On this page
- Judgment, defined as something you can observe
- Ten behavioral questions, with red flags and probes
- Four situational questions
- What strong and weak answers sound like
- A 1–4 anchored rating scale for judgment
- Judgment and integrity: where the line sits
- Common interviewer mistakes with judgment
- Questions people ask
Interview questions for judgment need to show whether a candidate's sense of proportion matches the job. Judgment rarely shows up as one big decision. It shows up in the small calls: whether to send the email now or sleep on it, whether a customer complaint is a one-off or the start of a pattern, whether a problem is theirs to fix or their manager's to know about. Below are fourteen questions, ten behavioral and four situational, each with what a strong answer contains, red flags and a follow-up probe, plus sample answers, a 1–4 anchored scale and the mistakes that lead interviewers to score agreement with their own instincts as good judgment.
Judgment has two close neighbors, and keeping them apart makes the scorecard sharper. Interview questions for decision making cover the process of choosing between options. Interview questions for critical thinking cover evaluating evidence and arguments. This page is about what comes before and around both: noticing that something needs a decision, sizing how much it matters, and deciding who should make the call.
Judgment, defined as something you can observe
Definition: judgment is the ability to read a situation accurately and respond in proportion: recognizing what matters, weighing risks and consequences for the people involved, choosing the right level of effort and the right person to decide, and acting at the right time. Listen for four behaviors:
- Sizing. Matching effort and caution to the stakes: quick on reversible, low-cost calls; careful on ones that are hard to undo.
- Escalating well. Raising issues to the right person at the right time, with a recommendation, rather than too early, too late or not at all.
- Reading context. Accounting for timing, relationships and who will be affected, not just the technical answer.
- Holding back. Recognizing when not to act, not to say something yet, or not to fix something that is not theirs.
Ten behavioral questions, with red flags and probes
| Question | A strong answer contains | Red flags | Follow-up probe |
|---|---|---|---|
| 1. Tell me about a problem you decided to escalate, and how you decided it was time. | The signal that changed their view, who they told, and what they recommended when they did. | Escalated everything, or escalated only after the damage was done. | "What would have happened if you had waited another week?" |
| 2. Describe a time you decided not to escalate something, and handled it yourself. | A clear reason it was within their authority and risk tolerance, and a check afterward that it was the right call. | Hid something that their manager would reasonably have wanted to know. | "Did your manager find out later? How did they react?" |
| 3. Tell me about a time you spent too long on a decision that did not deserve it. | Honest recognition, what made it feel bigger than it was, and how they size decisions now. | Cannot think of one, or the example is really about someone else's slowness. | "How do you tell a reversible decision from one that is hard to undo?" |
| 4. Describe a time you were right about the facts but chose not to push the point. | A reason grounded in timing, relationships or the bigger goal, and what they did instead. | Never lets anything go, or let it go when the consequences were serious. | "Did you come back to it later?" |
| 5. Tell me about a request from a senior person that you thought was a mistake. | Raised the concern privately and specifically, offered an alternative, then committed or escalated appropriately. | Complied silently, or refused publicly. | "How did you raise it, and where?" |
| 6. Describe a situation where the rules did not cover what was happening. | Worked out the purpose behind the rules, acted on that, and told someone who could update the rules. | Used the gap to do whatever was easiest. | "Who else did you involve?" |
| 7. Tell me about a time you had to decide quickly with incomplete information. | Identified what they most needed to know, made a proportionate call, and built in a way to correct it. | Either froze, or acted with no awareness of the risk they were taking. | "What would have changed your mind?" |
| 8. Describe a call you made that turned out badly. Looking back, was the judgment wrong or just the outcome? | Separates the quality of the reasoning from the luck of the result, and names what they would weigh differently. | Blames the outcome entirely on bad luck, or judges the decision only by how it turned out. | "With what you knew at the time, would you make the same call?" |
| 9. Tell me about a time you noticed a small issue that turned out to be a big one. | What made them take it seriously, and what they did before anyone else saw it. | Only spotted it in hindsight, or noticed it and did nothing. | "What was it about that issue that caught your attention?" |
| 10. Describe a time you had information you were not sure you should share. | Weighed confidentiality, the people affected and their own role, and checked with the right person. | Shared it casually, or withheld something others needed for safety or compliance. | "Who did you ask before deciding?" |
Questions 2 and 4 are the counterweights. Good judgment is not escalating and speaking up as often as possible. It is doing those things in proportion, which means sometimes not doing them.
Four situational questions
-
"An hour before a client presentation, you find a mistake in one chart. The overall conclusion still holds. What do you do?"
Probes: Do you fix it, flag it, or leave it? Who do you tell? -
"A colleague tells you, in confidence, that they are struggling and missing deadlines. Their delays are starting to affect your project. What do you do?"
Probes: What do you say to them? What, if anything, do you tell your manager? -
"You are new in the role and notice a process that looks inefficient. Everyone else seems used to it. What do you do in your first month?"
Probes: What would you want to understand first? When would you raise it? -
"A long-standing customer asks for a discount you are allowed to approve, but you suspect it will set an expectation with other customers. What do you do?"
Probes: What do you weigh? Who else should know before you answer?
Score the reasoning, not the action. Write down in advance what a proportionate answer would consider for each scenario, and accept more than one reasonable action.
What strong and weak answers sound like
Illustrative answers to question 1, written to show the difference in structure.
Weak: "I believe in transparency, so I always keep my manager in the loop. If anything looks like it could become a problem, I flag it straight away so there are no surprises."
This is a policy, not a judgment. Flagging everything immediately pushes the sizing work onto the manager, and there is no example of a specific call.
Strong: "A vendor missed two weekly data files. The first time I chased them myself, since it was a one-off and had no impact yet. When the second one was late I checked the contract and saw a third miss would push our month-end report past its deadline. That was the point where it stopped being mine alone. I sent my manager a short note: what had happened, the date it would start to hurt, and that I recommended we call the vendor's account manager. She agreed and made the call. If I had raised it after the first miss, it would have been noise; after the third, it would have been too late."
The strong answer sizes the problem twice, identifies the threshold where it needs someone with more authority, escalates with a recommendation, and can explain why the timing was right.
A 1–4 anchored rating scale for judgment
| Score | Anchor |
|---|---|
| 1 — No evidence | Treats all issues alike: escalates everything or nothing. Cannot explain why a call was right beyond "it felt right" or "it worked out". |
| 2 — Limited | Makes reasonable calls on familiar problems, but sizing is inconsistent and escalation timing depends on prompting. Judges decisions mainly by their outcome. |
| 3 — Solid | Matches effort and caution to the stakes, escalates at the right time with a recommendation, accounts for people and timing, and separates reasoning quality from outcome. |
| 4 — Strong | Everything at 3, plus spots small signals early, handles gray areas others avoid, knows when to hold back, and can explain the thresholds they use so others can apply them. |
Behavior-based anchors keep scores comparable across interviewers; see behavioral anchors for interview scores.
Judgment and integrity: where the line sits
Several judgment questions, especially 6 and 10, touch ethics. Keep the scoring separate. Integrity asks whether the candidate does the right thing when it costs them. Judgment asks whether they read the situation accurately and respond in proportion. Someone can be completely honest and still raise a sensitive issue in the wrong room. Someone can be tactful and well calibrated and still shade the truth. If an answer raises an integrity concern, note it under integrity and probe it there rather than folding it into a lower judgment score.
Common interviewer mistakes with judgment
- Scoring agreement. "That's exactly what I would have done" is not evidence. Score whether the reasoning considered the right risks and people, even if you would have chosen differently.
- Judging by outcome. A risky call that happened to work out is not good judgment. Ask what the candidate knew at the time.
- Using trick scenarios. Scenarios with a hidden single right answer test whether the candidate guessed your preference. Use realistic situations from the role.
- Equating caution with judgment. Candidates who check everything with someone else can look safe. In a role that needs independent calls, that is a gap.
- Writing "good judgment" in the notes. Record the call: "chased vendor alone after first miss; escalated with recommendation when third miss would breach month-end deadline."
Questions people ask
What is the difference between judgment and decision making?
Decision making is the process of choosing between options: gathering information, weighing trade-offs, committing and reviewing. Judgment is the sense that comes before and around that process: noticing that a decision is needed at all, sizing how much it matters, and deciding who should make it. A candidate can run a careful decision process on the wrong question, or spend a week on a choice that deserved five minutes. That is a judgment gap.
How is judgment different from critical thinking?
Critical thinking is evaluating evidence and arguments: spotting a weak source, a missing comparison or a logical leap. Judgment applies that, plus context about people, timing and risk, to decide what to do. Strong critical thinkers can still show poor judgment, for example by being right about the data and wrong about whether to raise it in front of a client.
Can you really assess judgment in a one-hour interview?
Only partly. You can collect evidence of how the candidate has sized problems, escalated issues and handled gray areas, and how they reason through a few realistic scenarios. Score that evidence, and use reference checks to confirm patterns. Avoid treating a single answer that matches your own instinct as proof of good judgment.
Should situational questions about judgment have one right answer?
Usually not. Write the scoring guide around the reasoning: what the candidate noticed, which risks they weighed, who they would involve and what they would do first. Two candidates can reach different actions and both score well if the reasoning is sound and proportionate.