How do you turn an interviewer's vague answer to your question into a concrete one?

## The move: policy out, episode in A vague answer is almost always a *policy-level* answer — how things are meant to work in general. The single most reliable repair is to ask for an *episode* instead: one real occurrence, recently, with an actor and an outcome. This works because the two require different things of the speaker. A policy answer can be assembled on the spot from what sounds right. An episode has to be recalled, and recall leaks detail — who was in the room, what was traded away, how long it dragged on. Three phrasings do most of the work: - **When did that last happen?** — forces a date-shaped answer and rules out aspiration. - **Who made that call?** — forces a role, which tells you where decisions actually sit. - **How did that one go?** — invites the cost, which is the part recruiting language removes. ## Worked example A candidate interviewing for a data platform role asks the skip-level leader how the team handles it when an ingestion job fails overnight. > *We take reliability really seriously. There's a strong ownership culture — people don't throw things over the wall here.* Policy, values, no episode. The follow-up: > *When was the last overnight failure, and what did the person on call actually do that morning?* A substantive answer now has to contain a shape: the job that failed, whether anyone was paged or it was found at standup, who fixed it, whether the fix was reverted, whether anything was written down afterwards. A leader who owns the team and cannot produce that shape has told you something real either about the team's memory or about their own distance from it. ## Register matters as much as wording The same follow-up can land as interest or as cross-examination. Three things keep it on the right side. First, **attribute the gap to yourself, not to them** — you are trying to picture it, so a concrete example would help. Second, **ask one, not three**; a rapid second and third probe on the same soft answer changes the room. Third, **accept the answer you get**. If the reply is an honest 'I'm not close enough to that to give you a good example', that is a real answer, and pressing further buys nothing except a worse impression. Budget one follow-up per hedge. It is enough to distinguish a thin answer from a thin subject, it is affordable inside the few minutes a candidate usually has at the end of a round, and it keeps the exchange feeling like a conversation between engineers rather than a deposition. ## Follow-ups that do not work - **Repeating the question in different words.** The same altitude produces the same abstraction. - **Asking a leading question** — a probe that supplies the answer you fear invites a denial and tells you nothing, because it is easier to say no than to describe reality. - **Asking for numbers you cannot interpret.** A count with no context is another abstraction wearing a different costume; an episode you can picture beats a figure you cannot check. - **Stacking a compound probe.** Two questions in one sentence lets the person answer the easier half, which is what the hedge was already doing. ## Recording what came back Write the follow-up and its answer into the notes column for that interviewer while it is fresh, and record the raw material rather than your verdict: the words you got, and whether an instance appeared. That distinction matters when you later compare the same question across the loop, because 'gave no example even when asked directly' is comparable across people, while 'felt cagey' is not. ## The failure mode this defends against Candidates rarely fail here because their follow-up was badly phrased. They fail because they never asked it: the answer felt incomplete, the silence felt awkward, the prepared list was sitting there, and the moment passed. Treat an unfinished answer as the live thing in the room and the next prepared question as expendable. The prepared question you skipped costs you nothing; the hedge you accepted is the one you will be guessing about after you sign.