Questions to ask at the end of a job interview

Prepare six because two or three will be answered during the conversation, and "you've covered everything" is the weakest possible ending.

Ask three because it is enough to show thought without turning the last ten minutes into your interview of them.

Have one question you would never ask early, held back for the final round — usually something about the difficulties of the role that would be too pointed in a screening call and is exactly right with the hiring manager.

Four properties. Strong questions have at least two.

It could not be answered by the website. Asking what the company does signals you did not look.

It is about the work, the team or the decision — not about benefits, holidays or working hours at this stage. Those are offer-stage questions and asking them early reads as a different set of priorities.

It makes them think. The best questions produce a pause. That pause is the signal you want, because it means nobody asked that before.

It tells you something you need to decide. You are also choosing. A question you do not want the answer to is not a question, it is a performance.

Pick from these and adapt them to what you actually want to know. Do not read them off a list — three that fit your situation beat six that do not.

About the role itself

"What does success look like in this role at six months, and how would you know?" "What is the first thing you would want this person to fix?" "What is in this job that is not in the job description?" "Is this a new role or a replacement? What did the last person do well, and what would you want done differently?" "Which part of this job do people usually underestimate?"

About the team and how it works

"How does the team make decisions when there is disagreement?" "Who would I work with most closely outside my own team?" "How long have most of the team been here?" "What is the balance between planned work and reactive work in a normal month?"

About the manager

"How do you like to work with the people who report to you?" "What do you expect in the first thirty days that people often get wrong?" "How often would we meet, and what would you want to see in those conversations?"

About the organisation and its direction

"What is changing here over the next year that would affect this role?" "What is the hardest thing about working here that you would want a candidate to know?" "How does this function sit against the priorities in your published strategy?"

About the process

"What are the next steps, and when should I expect to hear?" "Is there anything in my background you would like me to expand on?"

The last one earns its place. It invites them to raise a concern while you are still in the room to address it, and it is the single most useful question available to a candidate who suspects there is a doubt.

These are legitimate and badly timed in a first interview:

• Salary, unless they raise it — and then it is its own answer
• Annual leave, working hours, flexible or remote arrangements
• Bonus mechanics
• Promotion timelines: "how quickly can I be promoted" reads as focus on leaving this job before starting it
• Notice periods and start dates, unless they ask
• Anything about benefits detail

They become excellent questions once an offer exists, and what to check in an offer letter covers all of them.

Do not choose questions from a list. Build them from what you actually do not know.

Row 2 is the most valuable and the most skipped. Everyone prepares questions that make them look good. Almost nobody prepares the question whose answer might make them walk away — and that is the one that protects you from accepting the wrong job.

Row 6 becomes question three in the room, almost always.

Generic

"What's the culture like here?"

Almost unanswerable, and the answer will be positive and useless.

Specific

"When something urgent lands on a Thursday afternoon, what usually happens?"

Same subject. This one produces an actual answer — who picks it up, whether it waits, whether the team expects to be reachable — and the answer tells you more about the culture than any description of it would.

Generic

"What are you looking for in the ideal candidate?"

You are at the end of the interview. They already told you, in the job description, and asking suggests you did not read it.

Specific

"You mentioned earlier that the reporting is fragmented across three systems. Is consolidating that part of this role, or is it something this person works around?"

Shows you listened, shows you understood the implication, and gets you a genuinely important piece of information about what the job is.

Examples are illustrative. The situations are invented.

Score your prepared questions before the interview.

13–16: ready. 8–12: usually criteria 3 and 8. Your questions are performing rather than asking. Below 8: you have collected questions rather than built them. Use the worksheet.

Ask, then listen. The most common failure is asking a good question and then talking over the answer.

Follow up once. "Can you give me an example of that?" is worth more than a fourth prepared question.

Take a note. Writing one line after an answer is normal and signals you are evaluating rather than auditioning.

Do not interrogate. Three questions in a conversation, not a list read aloud with a pen.

Know when to stop. If they are looking at the time, ask about next steps and close. Reading the room is itself being assessed.

On a panel, direct different questions to different people. Ask the manager about the work, the functional peer about how the teams interact, HR about the process. Directing everything at the most senior person is noticed.

In a structured public-sector or government-linked process, this section may be short and formal, and may still be recorded. Two well-chosen questions are better than three rushed ones, and the process question is always safe.

If a panel member has said very little, a question addressed to them specifically is usually welcome, and it tells you something about who actually decides.

What if they genuinely covered everything?

Then say so and add one anyway: "You've covered most of what I had — the one thing I'd still like to ask is…" Nothing prepared is the impression to avoid.

How many is too many?

Three is right. Five starts to feel like you are running the meeting, unless they have explicitly invited more.

Can I ask why the role is vacant?

Yes, and you should. It is one of the most informative questions available, and the answer — growth, replacement, someone leaving after eight months — changes how you read everything else.

Can I ask about their own experience there?

Yes, and it is often the best question in the room. "What made you stay?" or "what surprised you when you joined?" gets an unrehearsed answer, which is rare in an interview.

Should I ask about salary if they have not?

Not in a first interview. If the process is advancing and nobody has raised it, ask the recruiter between stages rather than the hiring manager in the room.

What if I am asked "do you have any concerns about the role?"

Answer honestly and specifically, then ask about it. A real concern raised well reads as seriousness. "No concerns at all" reads as either uninterested or not listening.

Build your six from the worksheet rather than picking from the bank — particularly row 2, the question whose answer might make you walk away.

Then: the interview question hub for the questions coming in the other direction, and what to check in an offer letter for the questions you are holding until an offer exists.

If you want to practise the whole conversation including this part — which is where most preparation stops — that is mock interview coaching, or work through it in the self-paced interview preparation course.