The last ten minutes of most interviews are given over to "any questions for me?" The candidate asks three or four, the interviewer answers politely, the session ends. In the debrief the next day, those ten minutes rarely come up. They're treated as administrative overhead, not as signal.
That's usually a mistake. The questions a candidate asks you often tell you more about them than the fifty minutes of answers before it. The format just makes it hard to see.
What the question window reveals
When a candidate answers your questions, they're working inside a structure you built. The question has scope, a topic, a framing. They're responding to it. It's a useful signal, but it's a constrained one.
When they ask their own questions, your structure disappears. What they choose to ask about, in the moments they have agency, tells you what they actually prioritise — the parts of the job they're genuinely curious about, and the parts they assume are fine without checking.
A candidate who asks only about compensation and holiday policy has told you something. A candidate who asks about how decisions get made when engineering and product disagree has told you something different. Both might be valid things to care about. The pattern of questions is the signal, not any one question in isolation.
Question patterns worth watching
Questions that test your answers from earlier. "You mentioned earlier that the team is shipping weekly. How does that hold up when a bigger feature needs three weeks of runway?" This candidate is triangulating your claims. They're checking whether your description of the job matches the reality. That's someone who will not be surprised on day 90.
Questions about failure modes. "Has anyone joined this team and struggled? What was usually the reason?" The candidates who ask this are typically thinking about whether they specifically would struggle, and whether the team has the self-awareness to have noticed past struggles. Both are things you want in a senior hire.
Questions with no correct answer. "How do you feel about the direction of the product over the last year?" A candidate asking this genuinely wants your read. They're willing to open a conversation where you might be uncomfortable, because the answer actually matters to them. That's a candidate who will tell you uncomfortable things once they're on the team.
Questions about what happens after the offer. "How does the ramp-up usually go for this role?" A candidate who asks this is picturing themselves in the job rather than performing through the interview. It's a subtle tell, but it usually means they're thinking about the work, not about winning the process.
Patterns that are less reassuring
Only logistical questions. Start date, location policy, equipment, holiday. These are fine to ask, and you should answer them. A candidate whose entire question list is logistical is either very confident they want the job and isn't using the window to evaluate you, or isn't really evaluating the job at all. Either way, you didn't get useful signal in those ten minutes.
Only softball questions. "What do you love about working here?" "What's the culture like?" These tend to be questions the candidate hopes will produce a flattering answer they can use to sound excited in the next round. They're rarely asking because they want the information. If a candidate only asks softballs, you're probably talking to someone who is optimising for interview performance over actual decision-making.
Questions they clearly read off a list. You can usually tell. The phrasing is a touch too polished, the follow-ups don't quite track, and the candidate reacts to your answer as if checking a box rather than updating a view. This isn't disqualifying. Preparing questions is fine, and preparing them overly formally is a style more than a flaw. But it means you're not getting a real conversation in the window, and you should lean harder on the rest of the process.
One move that sharpens this window
About thirty seconds before you open the window, give the candidate permission to ask anything. Specifically. "We're going to leave about ten minutes for your questions. I want you to ask me the one you're most afraid to ask, not the safe ones. I'll answer honestly."
The effect tends to be significant. Candidates visibly recalibrate. Some ask the real question they came in with; a few ask something that catches you off-guard entirely. Either way you get more signal than the default opening would have produced.
You can read a lot from which group a given candidate falls into after the explicit permission has been granted.
One last thing to do with the answers
If a candidate asks a question that genuinely stumps you, note it down and bring it back to them in the offer conversation, or in a follow-up. That signals something a candidate will remember long after the offer: you took the question seriously enough to chase it down, and you're willing to say when you don't have the answer yet. Those are the candidates who tend to accept offers, and the teams that tend to keep them.