"Do you have any questions for us?"
Most candidates treat this as the exit door. It isn't. It's the last five minutes of an evaluation that is still running, and it's the only part of the hour where you choose the subject.
That's what makes it unusual. Everywhere else you're answering prompts someone designed to test you. Here you reveal what you find interesting — and interviewers read that far more literally than candidates expect. Ask three questions about holiday policy and you have told them, accurately, what was on your mind for the last hour.
The thing being measured
Not curiosity. Interviewers are not sitting there hoping you're inquisitive.
What they're reading is what you think the job is. A question is a claim about which part of the work you believe matters. Ask how decisions get made when two teams disagree and you've claimed that the hard part of the job is organisational. Ask what the test coverage looks like and you've claimed the hard part is engineering discipline. Neither is wrong. But one of them will match how the hiring manager privately describes their own biggest headache, and that's the one that lands.
So the useful preparation isn't memorising a list. It's deciding, before the call, which two or three things you would genuinely need to know to do this job well — and then asking those.
Questions that consistently land
Grouped by what they signal, because the signal is the point.
About the work itself
"What does the first ninety days look like for whoever takes this role — is there something specific waiting for them, or is it broader than that?"
This one does a lot of quiet work. It's forward-looking, it assumes you'll be doing the job rather than interviewing for it, and the answer is genuinely useful: a role with something specific waiting is a very different job from one that's a general capacity hire.
"What's the thing about this role that people tend to underestimate?"
Interviewers almost always have a real answer to this, and it's often something they've been unable to say out loud all process. You'll hear about the stakeholder who's difficult, the legacy system nobody wants to touch, the fact that the role is half support work. That's information you cannot get anywhere else.
About the team
"How does this team handle disagreement about priorities — what happened the last time two things both looked urgent?"
The general version of this question ("what's the culture like?") produces a brochure answer. Anchoring it to a specific event produces a real one. And you learn what you actually want to know, which is whether decisions get made or deferred.
"Who would I work with most closely, and what would they want from me that isn't in the job description?"
Senior-sounding because it takes the team's perspective rather than your own.
About the decision
"Is there anything in my background that gives you pause — anything I could address while I've got you?"
This one is uncomfortable and it is the highest-value question on the page. It surfaces the objection while you can still answer it, instead of letting it get discussed after you've left the room. Most objections are based on a misreading of a CV line, and thirty seconds of context kills them.
Ask it plainly and then stop talking. The silence after it is doing work.
Why the objection question works even when the answer is "no, nothing". You've demonstrated that you can invite criticism without flinching, which is a decent proxy for how you'd take feedback in the job. Candidates who can't ask it usually can't hear a "here's what went wrong" conversation either, and interviewers know that. The question costs you nothing and tests something they were trying to test anyway.
Questions that quietly cost you
Nobody will tell you these landed badly. They'll just note it.
| What you ask | What they hear |
|---|---|
| "What does the company do?" | You didn't spend ten minutes on the website |
| "How much holiday is there?" | Fine later — but you led with it, so it was your priority |
| "Is there flexibility on the salary?" | A negotiation opened before an offer exists |
| "What's the career path from here?" | Fine, unless it's your only question — then you're asking about the next job, not this one |
| "How did I do?" | Puts them on the spot and reads as anxious; the objection question above gets you the same information without the awkwardness |
| Nothing at all | The most common one, and the most damaging |
The holiday and salary questions are not forbidden. They're normal and you're entitled to answers. The issue is purely sequencing: those belong with the recruiter or at offer stage, not in the five minutes where the hiring manager is forming their last impression of what you care about.
When they say "I think we've covered everything"
You still ask something. "Nothing from me, you've been thorough" is the single most common way candidates end an interview flat.
Two reliable moves when the obvious questions are genuinely used up:
Make it personal to them. "What made you join, and is it still true?" Almost nobody asks this. It's disarming, people enjoy answering it, and the hesitation before "…yes, mostly" tells you a great deal.
Make it about them, not the company. "What's changed about this team in the last year?" Works even when the role has been described exhaustively, because it's about trajectory rather than description.
Politely declining
“No, I think you've answered everything — thank you, it's been really helpful.”
Courteous, forgettable, and it ends the conversation on your lowest-energy sentence. The interviewer writes their notes in the four minutes after you leave, and this is the moment they were most recently in.
One question, then a close
“One thing — what's the piece of this role you'd most want someone to be good at from day one? … That's useful, and it's the part I'd have been most confident about, because of X.”
You asked, you listened, and you connected the answer back to yourself in one sentence. That last clause is the whole trick, and almost nobody does it.
Saying it out loud
Two things go wrong in delivery, and both are fixable in about ten minutes of practice.
Reading from a list. Glancing at notes is fine and normal. Reading a question verbatim off a screen is not, because it makes the question sound like homework rather than something you wanted to know. Keep the list to three or four keywords, not sentences.
Asking and then filling the silence. You ask a good question, they pause to think, and the pause makes you nervous, so you add "…or, I mean, whatever you think" and the question collapses. The pause means it was a real question. Let it sit — it's the same skill as holding silence in the rest of the interview.
One more thing worth rehearsing: the follow-up. Most candidates ask a question, receive an answer, and say "great, thanks". A single follow-up — "Is that recent, or has it always worked that way?" — turns the exchange into the only genuine conversation of the hour.
What to have ready
Three questions, written down, in this shape:
- One about the work, specific to what you'd actually be doing.
- One about how the team operates, anchored to a real event rather than to culture in the abstract.
- The objection question, which you ask last.
Then drop any of them that got answered during the interview — and say so: "I was going to ask about X but you covered it." That tells them you were listening for an hour, which is its own signal.
If you're preparing for the earlier stage rather than the final round, the recruiter screen has a different shape and different questions worth asking: recruiter interview vs hiring manager interview.
Practical target: write your three questions, then say each one out loud once and cut every word before the actual question. "So I was just wondering, and this might be a silly question, but I was curious about…" is forty words of throat-clearing that makes a strong question sound tentative. The best version of almost every question on this page starts with a verb or a noun, and lands in under fifteen words.
