“Do you have any questions for us?” is not the end of the interview. It is the last section of it, and it is scored like the rest — often more heavily than candidates expect, because it is the only unscripted part where the interviewer learns what you actually care about.
It is also the only part of the process designed for your benefit. You are deciding whether to take this job, on evidence that is deliberately thin. These fifteen minutes are the best chance you get to make that decision on something better than the job description.
How to use it
- Prepare six to eight questions; you will ask three or four
- Ask about the work and the team, not about benefits, at this stage
- The best questions are ones only this interviewer could answer
- Listen to what they avoid answering — that is information too
Why “no questions” costs you
Saying “no, I think you have covered everything” is read one of three ways, none of them good: you are not that interested, you have not thought about the job in any depth, or you are not the kind of person who interrogates a decision before making it. For any role involving judgement, the last one is a genuine concern.
If the interview genuinely did cover everything, you still ask something. There is always a question about how the team works, what the first six months look like, or what the person before you found difficult.
Questions that produce useful answers
About the role as it actually is
- “What does a good first six months look like in this role?” If they cannot answer this concretely, expectations are unclear, which will become your problem.
- “Is this a new role or a replacement? What happened with the person before?” New means undefined and possibly under-resourced. Replacement means you can ask why they left, and the answer — including how comfortably it is given — is informative.
- “What is the part of this job that people underestimate?” Consistently the highest-yield question on this list. It invites honesty and usually gets it.
- “How much of the week is the core work, and how much is meetings, reporting, and administration?” The split between the job as advertised and the job as lived.
- “What would make you decide, a year from now, that this hire had worked?” Forces a concrete definition of success.
About the team and the manager
- “How is the team structured, and who would I work with most closely?”
- “How does your team handle disagreement about priorities?” More revealing than asking about culture, because it is specific enough to be hard to answer generically.
- “How often would we speak, and in what format?” Reveals management style without asking “are you a micromanager?”
- “What has changed in the team over the last year?” Turnover, restructuring, and growth all surface here.
- “How long have you been here, and what has kept you?” Personal, appropriate, and the hesitation before the answer is itself data.
About the company’s situation
- “What is the biggest constraint on the team hitting its goals this year?”
- “How does this team’s work connect to what the business is measured on?” Teams far from the revenue line are cut first.
- “What is the funding position / how is the business performing?” Entirely reasonable at a startup or a company in a difficult sector.
About the process
Save these for the end of your questions:
- “What are the next steps, and what is the timeline?”
- “Is there anything in my background you would want me to expand on?”
That second question is quietly one of the most useful things you can ask. It surfaces a doubt while you are still in the room and able to address it, rather than after you have left.
Questions to avoid, and why
- Anything answered on the website. “What does the company do?” ends the interview in substance.
- Salary and benefits at first interview. Not because it is impolite — because the leverage is worse before they have decided they want you. If they raise it, engage; do not introduce it at stage one.
- “How much holiday do I get?” / “Can I work from home?” at first interview. Legitimate questions, wrong moment. Ask at offer stage, when they are answerable in writing anyway. The exception: if remote or flexible working is a genuine dealbreaker, ask early rather than waste both parties’ time.
- “How quickly could I be promoted?” Reads as more interested in the next job than this one. Ask about progression paths instead.
- The manufactured clever question. “If you were a tree, what tree would your culture be?” Interviewers find these tiresome.
- Questions that are statements. “I noticed your competitor launched X, don’t you think that puts you at risk?” is a challenge dressed as a question, and it rarely lands as insight.
Ask different questions to different people. If you meet a recruiter, a hiring manager, a potential peer, and a senior leader, they know different things. Ask the peer what the work is actually like day to day; ask the leader about direction and constraint; ask the recruiter about process and timeline.
Reading the answers
The questions are only half of it. What you do with the answers is the part that protects you.
Signals worth taking seriously
- Nobody can define success in the role. Vague answers to “what does good look like in six months” usually mean nobody has agreed what this person is for. You will be judged against an unstated standard.
- Discomfort about the predecessor. “It just wasn’t a good fit” delivered with a pause is worth one gentle follow-up.
- Repeated turnover. “We have had three people in this seat in two years” is the role telling you about itself.
- “We work hard and play hard” / “we’re like a family.” Frequently precedes long hours and blurred boundaries. Ask what time people actually leave.
- Evasion on hours or workload. If “how many hours does the team typically work?” produces a deflection, that is the answer.
- They cannot say what the constraint is. Either the team has no real goals, or your interviewer is not close enough to the work to know.
Signals that things are healthy
- Specific, concrete answers, including about difficulties
- Willingness to name what is not working — a manager who says “our reporting is a mess, that is partly why we are hiring” is being straight with you
- Long tenure among the people you meet, freely explained
- The interviewer asks you questions back about how you would approach something — it means they are picturing you in the job
Adjusting by stage
| Stage | Ask about | Avoid |
|---|---|---|
| Recruiter screen | Process, timeline, whether the range fits, why the role exists | Deep technical detail they cannot answer |
| Hiring manager | The work, the team, success criteria, the predecessor | Salary, benefits, holiday |
| Peer interview | What the week is actually like, what is frustrating, tooling | Questions about their manager’s competence |
| Senior leader | Direction, constraint, how the team is viewed internally | Day-to-day process detail |
| Final stage / offer | Package, flexibility, review cycles, notice, start date | Nothing — this is when logistics belong |
Practical delivery
- Write them down and bring them. Reading from a notebook is fine and reads as preparation.
- Prepare more than you need. Half will be answered during the interview. Having eight means you still have four.
- Reference the conversation. “You mentioned the reporting is rebuilt by hand each month — is that the first thing this role would take on?” Better than any prepared question, because it proves you listened.
- Ask three or four, not ten. This is a conversation, not an audit. Watch the time and the room.
- Follow up on a thin answer, once. “Can you give me an example?” is fair. Pressing a second time turns it adversarial.
Common questions
How many should I actually ask?
Three or four, unless the interviewer is clearly happy to keep talking. Quality over volume — one question that produces five minutes of honest detail beats six that produce short answers.
Is it acceptable to ask why the last person left?
Yes, and it is a normal question. Ask it neutrally: “Is this a replacement role? What did the previous person move on to?” You may get a partial answer for confidentiality reasons, which is fine.
When can I ask about remote or hybrid working?
At offer stage for the detail. Early, if it is genuinely a dealbreaker — there is no sense in four rounds of interviews for a job you cannot take. Frame it as logistics rather than preference: “The posting says hybrid — can you tell me what that means in practice here?”
What if they ask whether I have questions and I have already asked everything?
Ask about them. “What has kept you here?” or “What is the thing you would change about how the team works?” Both are always available and both produce genuine answers.
Should I ask about progression?
Yes, framed around capability rather than title: “What does someone need to be doing well for this to become a senior role?” That reads as ambition rather than impatience.
