aurate

Questions to ask in an interview: the close that works round by round

Updated 6 July 2026questions to ask in an interview

'Do you have any questions for us?' is the only interview question you write yourself — and interviewers read it exactly that way. Your questions reveal what you actually care about, how closely you listened for the last 40 minutes, and whether you are assessing them or just hoping to be chosen. A considered close can recover a shaky middle; a limp 'no, I think you've covered everything' hands back every point it took the hour to earn.

This page is a working set: the questions worth asking at each round — recruiter screen, hiring manager, final panel — with four fully worked closes marked against the same four criteria aurate uses in live sessions, plus the questions that quietly cost you and what to ask instead.

The standing rule for every round: ask questions whose answers you will actually use, and ask them like a colleague weighing a decision — because by the close, that is what you are.

Practise these questions out loud with a live AI interviewer — free. Start with Try Me

What interviewers are assessing

  • Direction of travel. Candidates who ask about the work, the team and the first six months read as people deciding to do the job; candidates who only ask about hours, perks and sign-off read as people deciding to accept an offer nobody has made yet.
  • Listening. A question that builds on something said in the room — "you mentioned the merger settling down…" — proves the conversation registered. A rehearsed set delivered regardless reads as a script, however polished each line.
  • Level calibration. The panel notices whose questions match the role's altitude: a would-be manager asking about team capability and inherited problems, not just personal progression. Your questions are the cheapest place to sound like the level you are applying for.
  • Judgement under a small decision. Three sharp questions beat seven adequate ones. Choosing what to leave unasked — and closing cleanly when time is tight — is itself a sample of how you will run meetings on their side of the table.

How the marking guidance works

Each model answer below is marked against the four criteria a live aurate session scores:

  • Logic — structure and reasoning: does the answer hold together as an argument?
  • Resilience — composure under pressure: what happens when the answer is pushed, interrupted or challenged.
  • Synthesis — connection: tying your evidence to this role and building on what you've already said.
  • Specificity — concreteness: named situations, numbers and outcomes that couldn't belong to anyone else.

See how a full session is scored

aurate is a practice tool. Marking guidance describes what strong practice answers show — it isn't an employability assessment.

1. 'What would separate a good first six months from a great one in this role?'

Why it's asked: The single most reliable close at any round. It converts the interview into a working conversation about the job itself, and the answer tells you what the scorecard really is — which is also exactly what your follow-up letter or final round should speak to.

Model answerFinal-round close, area manager, pharmacy retail

I've got three, if we have time. The first is the one I most want your read on: what would separate a good first six months from a great one in this role? You've described the eleven branches and the two that are struggling — I'd like to know whether fixing those two IS the brief, or the visible part of a bigger one.

Second — you mentioned the pharmacist recruitment freeze earlier. How is that changing what area managers spend their weeks on right now?

And last, a smaller one: when the regional director thinks about this appointment a year on, what's the thing she'd point to as the reason it worked?

That's me done — and thank you, this has been the most useful conversation I've had about the role, including the one where I decided to apply.

Marking guide

Logic:
The close is structured like an agenda — counted upfront ('I've got three'), sequenced from role-defining to situational to evaluative, and explicitly closed. The panel never wonders how long this will take or where it is going.
Resilience:
Naming the two struggling branches invites a blunt follow-up — 'how would you fix them?' — and the candidate has deliberately walked toward it. Ask nothing you are not prepared to be asked back.
Synthesis:
Both the branch numbers and the recruitment freeze come from earlier in the interview — each question is stitched to something the panel said, which is what makes it a conversation rather than a recital.
Specificity:
Eleven branches, two struggling, a named freeze, a one-year horizon. The generic version — 'what does success look like?' — asks the same thing and proves nothing about the asker.

2. 'What's the problem you're most hoping this hire takes off your plate?'

Why it's asked: Asked to a hiring manager, this is the question that turns them from assessor into future colleague — people answer it honestly and at length, because it is about their own week. The reply tells you the job's real shape, which is rarely quite the advert's.

Model answerHiring-manager round, payroll implementation consultant

Can I ask the selfish version of the usual question? Most role profiles describe the team's work — I'd like to know what YOU are most hoping this hire takes off your plate. You said you're leading four implementations at once while covering this role's vacancy, so I suspect the honest answer isn't in the job description.

And when you picture handing that over — say the two mid-size rollouts — what would I need to show you in the first month for you to hand them over properly, rather than checking everything behind me?

I ask because the handover pattern is where implementations go wrong in my experience: I'd rather agree what earned trust looks like in week two than discover it in month three.

Marking guide

Logic:
Two questions, one spine: what would you hand over, and what makes you comfortable handing it. The pair converts 'tell me about the role' into a concrete operating agreement.
Resilience:
Flagging the question as 'the selfish version' is a small deliberate risk — it works because it is honest about what is being asked. Expect 'why do you ask?' and have the month-three answer ready.
Synthesis:
The four-implementations detail and the vacancy coverage came from the interviewer — the candidate is reading the manager's actual situation back to them and building the question on it.
Specificity:
The two mid-size rollouts, week two, month three. Vague trust questions get vague answers; naming the handover unit gets you the real one.

Reading a strong close is easy — delivering one after 40 minutes is not

Two marked closes in, the pattern is visible: build on what was said, justify the question, absorb the answer. Doing it live at minute 42, against an interviewer who pushes back, is the part that needs practice — an aurate session ends with your questions to them, and marks the close on the same four criteria you've just read. Two free sessions. No credit card.

Try it free

3. 'How does the team take in work, and what's the current backlog honestly like?'

Why it's asked: The operational-reality question. Asked plainly and without edge, it signals someone who has run a workload before — and the answer (or the pause before it) tells you more about the next year of your life than anything in the advert.

Model answerScreen-stage close, wholesale account executive, coffee roastery

Two questions from me, both practical. First: how does work actually arrive for the account team — is there a queue and an owner, or does it come in from all directions? I'm asking because 'supporting sixty trade accounts' can mean two very different jobs depending on the answer.

Second, and you can be as honest as you like: what's the state of the backlog the new person inherits? Every role has one — the accounts that haven't been visited, the price reviews that slipped. I'd rather hear its shape now than discover it in week one.

Whatever the answer is, it won't put me off — I cleared a four-month visit backlog in my current patch across one quarter, and I liked the job more once I knew exactly what I'd taken on.

Marking guide

Logic:
Each question carries its own justification — 'I'm asking because…' — so neither reads as interrogation. Question, reason, reassurance: a shape worth stealing for any awkward-but-fair question.
Resilience:
'You can be as honest as you like' invites a difficult answer and commits the candidate to absorbing it well. If the recruiter says 'the backlog is bad', the response is already framed: good — now we both know.
Synthesis:
The closing line connects the question back to evidence — a cleared backlog in the current role — so asking about mess doubles as proof of having handled it.
Specificity:
Sixty trade accounts, a four-month backlog cleared in a quarter. At screen stage most candidates ask about "culture"; the one asking how work arrives sounds like they have already started.

4. 'Where does this role's budget authority actually stop?'

Why it's asked: For management and senior roles, the authority question separates candidates who have held a line of their own from those who have watched one held. Panels rate it because it is the question they wish more appointees had asked before accepting.

Model answerPanel close under time pressure, deputy head of estates, further education college

I know we're at time, so I'll make it one question rather than three. The role carries the maintenance programme and the contractor relationships — where does its spending authority actually stop? I mean in practice, not on the delegation schedule: if a boiler fails on the Friday of half-term, what can the postholder commit to without a call?

I ask because in estates the gap between paper authority and real authority is where weekends go. In my current post the written limit and the real one differed, and agreeing the true line with my director was the most useful conversation of my first month.

If it's easier, I'm equally happy with the honest version: what did the last person in the role wish they'd asked about authority before starting?

Marking guide

Logic:
One question, chosen aloud, with the reason for the choice shown — turning a time squeeze into evidence of prioritisation. The fallback phrasing at the end gives the panel two ways to answer the same thing.
Resilience:
'In practice, not on the delegation schedule' gently challenges the tidy answer before it is given. Expect a panel member to ask 'why, did authority go wrong somewhere?' — the current-post story is the prepared answer.
Synthesis:
The boiler-on-Friday case makes the abstract question concrete and college-specific — it shows the candidate has imagined operating inside their calendar, half-term and all.
Specificity:
A named failure scenario, a real first-month anecdote, 'the Friday of half-term'. The generic version — 'what's the level of autonomy?' — would earn a generic paragraph and no information.

5. 'What made the last person in this role successful — or why didn't it work out?'

Why it's asked: A steer, because the marked closes above often absorb it. Asked well, it is the highest-information question available about the role's real difficulty. Ask it neutrally and let the pause do the work: how they talk about a predecessor is also how they will one day talk about you.

6. 'What's genuinely hard about working here that the advert wouldn't say?'

Why it's asked: Use at most once, late, and only when rapport is real — it asks the interviewer to break register, which is precisely why the answer is valuable. If they wave it away, that is an answer too. Follow whatever they offer with interest, never with alarm.

7. Asking about development without sounding like you're already leaving

Why it's asked: Progression questions misfire when they read as 'how quickly can I stop doing this job?'. Anchor development to the role itself — 'what do people in this role typically get better at in year one?' — and the same curiosity lands as commitment rather than exit planning.

8. The questions to leave out — salary, holidays, hybrid days, and anything Google answers

Why it's asked: Not because pay doesn't matter — it does, and there is a right moment for it (usually the recruiter screen or the offer conversation, where it is expected and costs nothing). The close is the wrong slot: it spends your highest-attention minutes on things that were never in doubt, and anything answerable by the careers page announces you didn't read it.

9. Closing when they've already answered everything: the summary close

Why it's asked: Sometimes a thorough interviewer really has covered it. The weak move is inventing a question anyway; the strong one is a summary close — name the two things you learned that most confirmed your interest, flag the question you would have asked, and say you look forward to the answer emerging in the first month. Composed beats performed.

FAQ

How many questions should I ask at the end of an interview?

Prepare five or six, expect to ask two or three. The number that matters is the ones left standing after the interview answers some en route — walking in with only two prepared risks a flat close if both get covered by minute 20.

Is it acceptable to say 'no questions' if everything was covered?

A bare 'no' is a missed slot, but a summary close solves it: name what you learned that confirmed your interest, mention the question they already answered, and close warmly. That reads as engaged and decisive rather than passive — and it is honest.

Should I ask about salary at the end of an interview?

Not in the closing-questions slot of a hiring-manager or panel round — it spends your best minutes on something that gets settled elsewhere. Pay belongs in the recruiter screen or the offer conversation, where raising it is expected and reads as normal diligence.

Can I write my questions down and read them in the interview?

Yes — bringing a short written list reads as prepared, not weak, and interviewers routinely say so. The craft is in the delivery: glance at the list to choose, then ask while looking at the person, and strike through the ones the conversation already answered.

Do the questions I ask actually affect the hiring decision?

At the margin where decisions actually get made, yes. Panels comparing two close candidates consistently cite the close: one asked about the work, one asked about the perks. It is the last evidence you leave in the room, and the only part of the interview you fully control.

Keep practising

Sources and further reading

Ready to practise for real?

Two free sessions. No credit card.