Probing Questions: How to Follow Up When an Interview Answer Is Vague

A probing question is a follow-up that asks for what the first answer left out: a real example, the candidate's own part in it, the result, or the reasoning. Most first answers are summaries ("I'm good at handling difficult customers"), and summaries can't be scored. The evidence is in the follow-up, which is why the probe is often the most useful question in the interview.

Below are 40 probing questions grouped by what's missing from the answer, the five signs that tell you which group to reach for, and how to probe without leading the candidate to the answer you want.

Why probe at all?

Two candidates can give the same first answer and have done completely different jobs. "I led the migration to the new system" might mean they planned and ran it, or that they were in the room when someone else did. Only the follow-up tells you which.

Probing also makes interviews fairer. Candidates who are nervous, new to interviews or simply modest tend to undersell themselves in their first answer. A good probe gives every candidate the same chance to show what they've done, rather than rewarding whoever is most practiced at summarizing.

In a structured interview, the main questions stay the same for every candidate, but the probes can vary, because they follow what each candidate actually said. What should stay the same is the goal: every answer ends with a specific example, the candidate's own actions and a result, or a note that the candidate couldn't give one.

What's missing from a vague answer?

Listen for which piece is absent, then pick the probe that asks for it:

40 probing questions, by what's missing

When there's no specific example

1. "Can you give me one real example of that?"
2. "Tell me about the most recent time that happened."
3. "When was the last time you did that? Walk me through it."
4. "Pick one case that stands out. What was the situation?"
5. "Who was involved, and what was at stake?"
6. "Roughly when was this, and what was your role at the time?"
7. "What made that situation hard?"
8. "Is there a time it didn't go well? What happened then?"

When you can't tell what the candidate did

9. "What did you do, specifically?"
10. "Which part of that was yours?"
11. "If I asked your manager what you did on that, what would they say?"
12. "What would have happened if you hadn't been there?"
13. "What did you decide on your own, and what did you check with someone?"
14. "You said 'we'. What was your piece of it?"
15. "What was the first thing you did when you found out?"
16. "Who did you have to persuade, and how did you do it?"

When there's no result

17. "What happened as a result?"
18. "How did you know it worked?"
19. "What changed afterwards, and how did you measure it?"
20. "What did the customer, team or manager say about it?"
21. "Is it still working that way today?"
22. "What would have happened if it hadn't worked?"
23. "What was the number before, and what was it after?"
24. "If it didn't work, what did you learn and do next?"

When the reasoning is missing

25. "How did you decide to do it that way?"
26. "What other options did you consider?"
27. "What information did you have at the time, and what was missing?"
28. "What was the trade-off, and why was it worth it?"
29. "What would have made you choose differently?"
30. "Who disagreed, and what was their argument?"
31. "Looking back, would you make the same call?"
32. "What would you do differently next time?"

When the answer sounds rehearsed or too polished

33. "What's a detail about that project that nobody would know unless they were there?"
34. "What went wrong along the way?"
35. "What tool or system were you using, and what was annoying about it?"
36. "Who else worked on it, and what were they like to work with?"
37. "What was the very first step you took?"
38. "What would you tell someone starting the same project tomorrow?"
39. "What surprised you about how it turned out?"
40. "If we spoke to someone else involved, what might they remember differently?"

The last group isn't an accusation. Practiced candidates often give polished answers to common questions, and a probe for an ordinary, specific detail is the quickest way to move from the rehearsed version to the real one. Someone who did the work can answer these easily; it's the answers that stay general that tell you something.

How not to probe

• Don't lead. "So you went to your manager first, right?" gives the candidate the answer. "What did you do first?" asks for it.
• Ask one question at a time. "What did you do, and how did the team react, and would you do it again?" gets an answer to whichever part the candidate prefers.
• Don't argue. A probe asks for more; it doesn't test whether the candidate can be talked out of their answer. Save your view for the scorecard.
• Don't interrupt the useful part. If a candidate is getting to the specifics, let them finish before probing.
• Know when to stop. If two probes don't produce a specific example, write down that the candidate couldn't give one and move on. A third probe rarely helps, and it turns the interview into a cross-examination.

How much to probe in each round

In a short screen, one well-chosen probe per question is enough. Our phone screen script builds that probe into each step.

Write the probes into the interview plan

The best probes are planned. For each main question in your interview, write the one or two follow-ups you expect to need, along with what a strong answer includes, so every interviewer probes for the same evidence. The free interview question generator gives a follow-up and a description of a strong answer for every question it suggests, and our competency-based interview questions post does the same for 60 questions. Then score what the probes produced against written anchors, as in our interview scorecard template.

Where does DIO fit?

DIO, Dio's AI interviewer, probes the same way in a structured voice interview: when an answer is thin or vague, it asks a follow-up question before moving on. The scorecard then quotes the candidate's own words for each rating, so you can see whether the follow-up produced a real example. When the evidence isn't there, the score is left blank rather than guessed, and a person on the team makes every decision. Watch how it works.