'Do You Have Any Questions for Us?' Is the Question You're Being Scored on Hardest

The short answer: ask three questions, not five. Make them practical, forward-looking, and presupposing that you’ll succeed in the role. The best three to choose from: what does the first ninety days look like for this role, what did the last person in the seat find hardest, and when you’ve seen someone succeed here, what did they do in their first month that the average person didn’t. Save salary, holiday and remote-policy questions for the recruiter.

The interviewer glances at the clock, leans back, and says the line that every candidate hears as a release valve: “So — do you have any questions for us?” You exhale. You think the test is over. It isn’t. The interviewer has spent forty-five minutes trying to triangulate how you think. Now they’re handing you five minutes to tell them the same thing yourself, unprompted, with no script to lean on. Most candidates squander it.

The reason this slot is scored so hard is structural. Everything before it was the interviewer choosing the terrain — their competency framework, their case study, their behavioural matrix. This is the one stretch of the conversation where you set the agenda. What you ask says more about how you process the role than what you answered about the role itself.

When two candidates are level on capability, the questions they ask at the end are the tiebreaker that final-round debriefs reach for most often. It is the only stretch of the conversation that is genuinely unrehearsed, which means it is also the only stretch where you can move yourself either way in a single sentence. That tells you what to optimise for. Not curiosity for its own sake. Not the question that flatters the interviewer. The question that signals how you’d operate from week one.

What recruiters and hiring managers are actually scoring

In the room, three things are being assessed in this final stretch, and none of them are written down on the scorecard explicitly:

• Seniority calibration. Do your questions sound like someone who has run a role like this, or someone who has only read about one?
• Operating instinct. Do you reach for the practical edges — handovers, dependencies, what's broken — or do you reach for the brochure?
• Interest in the actual job, not the actual offer. Salary and remote policy questions in this slot read as transactional. Save them for the recruiter.

A good question makes the interviewer hesitate before answering. That hesitation is the signal you want. It means you’ve asked something they hadn’t pre-baked an answer to — which means you’ve asked something the role actually contains.

The five questions that do the work

These aren’t clever or contrarian. They’re built to extract information you genuinely need and to signal how you’d think on day one. Use any three of them. Don’t recite all five — it starts sounding like a checklist.

• What does the first ninety days look like for the person who takes this role? Signals you're already thinking about delivery, not just about getting the offer. Also surfaces whether the team has actually planned the onboarding, or hopes you'll figure it out.
• What's the one thing you'd most want to change about how the team works today? Forces an honest answer. The hesitation alone tells you what the culture is really like. It also signals you're someone who notices process, not just output.
• Whose work in the organisation is the most critical input to this role's outputs? Signals systems thinking. You're asking about the dependencies, not the org chart. The answer tells you who you'll actually need on your side.
• What did the last person in this role find hardest? The most underused question in the catalogue. It politely surfaces the bear traps without you having to ask whether the role is a graveyard.
• When you've seen someone succeed in this role, what did they do in their first month that the average person doesn't? The tiebreaker. It signals you're already mapping the gap between competent and excellent.

Each one is doing two jobs. It’s a real question — you’d benefit from the answer — and it’s a signal about your calibration. That’s the trick. A question that only signals (without giving you usable information) sounds rehearsed. A question that only gathers information (without signalling seniority) sounds junior. The five above thread the needle.

In a typical hiring debrief, the question you asked is one of the few pieces of evidence everyone in the room can recall verbatim. The candidate who asked something the interviewer is still thinking about a day later is the candidate the panel remembers. The candidate who asked about the benefits package is the one they remember as having asked about the benefits package.

Why the last question is the offer-maker

That fifth question — what did successful people do in their first month — is the one that lands hardest in final-round debriefs. It does something the others don’t: it presupposes you’ll succeed and asks the interviewer to imagine you doing it.

That presupposition matters more than it should. Interviews are mostly forecasting exercises, and humans are bad at forecasting in the abstract. When you ask a question that forces them to picture you in the role, succeeding, they start running the simulation in real time. By the time they answer, they’ve already done some of the work of advocating for you in the debrief.

The “before” is fine. It’s also vague, and the interviewer will give you a vague answer — “hit the goals in the JD” — which tells you nothing and signals nothing. The “after” forces specificity. It forces them to think about a real person, not the role description. The answer is almost always more useful, and the way they answer tells you whether they have ever watched somebody be excellent in this seat.

What never to ask in this slot

There’s a softer version of the same mistake: the question that’s secretly about you, not the role. “How much flexibility is there in the role for someone wanting to move into management?” You can ask this. Just not now. Now is when you’re proving you’d be excellent at the role on the table. Career-trajectory questions in the first interview signal that you’re already looking past it.

When you’re running out of questions

You’ll sometimes get to the final round and find that the earlier interviews answered all your questions. Don’t pretend otherwise. The clumsy move is to ask a question you don’t care about because the silence feels wrong. The strong move is to say so explicitly: “Honestly — the previous conversations covered most of what I wanted to know. The one thing I still want to test is X.”

That sentence is doing several things at once. It tells the interviewer their colleagues did a good job. It tells them you were listening. And it tells them you have one specific outstanding question, which is far more interesting than five generic ones.

The question you ask the most senior person in the loop

If you’re in a multi-stage process and you land in front of someone two levels above the hiring manager — a VP, a director, a founder — the rules shift slightly. They’ve delegated the operational assessment to the people below them. What they’re scoring is whether you can hold a strategic conversation.

For that seat, the strongest single question is some version of: “Where do you want this function to be in eighteen months that it isn’t today, and what would have to be true for this role to be a meaningful part of getting there?” It’s a long sentence. It’s also the only kind of question that matches the altitude of the person across the table. Match the altitude. Don’t ask the founder about your onboarding plan; ask the line manager.

A note on the close

After your questions, you get one more move: the close. Most candidates miss it entirely. The interviewer will usually signal the end with “Anything else from your side?” — and that is the moment to say, briefly, that you’re interested. Not desperate. Interested. One sentence. “Based on this conversation, this is the role I’d want — I hope the answer is yes.”

The reason this works isn’t that the sentence is magic. It is that most candidates leave the room without ever stating, out loud, that they want the job. The hiring manager is then left to infer it — and on the margin, ambiguity costs you. Stating it explicitly removes the inference. Don’t make them guess.

The closing question slot pairs naturally with the opening one. If you want the rest of the cluster: how to structure the ‘tell me about yourself’ answer that opens the conversation, what hiring managers actually weigh in the first five minutes, and how to follow up afterwards without sounding desperate.