Killer Questions to Ask at the End of an Interview
Twenty questions for the last few minutes of a job interview, covering what the first three months should produce, how work arrives and who signs it off, how reviews and promotions actually run, and the logistics of the decision itself.
The questions
Open any question for the note
What would you want me to have done by the end of my first three months?
Why ask it
A hiring manager who has thought about the role answers in deliverables. Vague answers about learning the systems and meeting people usually mean the work has not been scoped, and you would be defining the job yourself once you arrive.
Is this a new role or a replacement? If it is a replacement, where did they go?
Why ask it
An internal move is a good sign. A departure nobody wants to describe, or a role that has been open for months, is worth one careful follow-up. If it is genuinely new, ask who was doing the work until now.
What does the team actually spend its week on that is not in the job description?
Why ask it
This is where support tickets, reporting, and one demanding stakeholder tend to surface. If the answer differs sharply from the posting, the posting was written by someone who does not do the work.
Which decisions would this role own outright, and which need sign-off?
Why ask it
Tells you the real seniority behind the title. If everything of consequence needs approval, expect the frustration that follows, and ask who gives that approval and how quickly they respond.
How does work reach me: a queue, straight from you, or requests from other teams?
Why ask it
Distinguishes a planned workload from an interrupt-driven one. Hearing that anyone can walk up with a request, with no filter and no prioritization, predicts most of what your days would feel like.
Who outside this team would I need on side to get anything finished?
Why ask it
Names are what you want. A crisp answer means the manager understands the dependencies and probably shields you from them. If they cannot name anyone, either the work is self-contained or they have never had to unblock it.
What has the team already tried here that did not work?
Why ask it
Protects you from proposing in month two the thing that failed last year. It also shows whether failure gets discussed openly. A claim that nothing has been tried usually means nothing has been examined.
What is the part of this job that people find hardest to stay with?
Why ask it
Phrased this way it is harder to deflect than asking about challenges. Interviewers who answer honestly, on-call weeks, a difficult client, slow procurement, are giving you the trade you would be accepting.
How often would you and I meet, and what would those meetings be for?
Why ask it
A regular one to one with a purpose beyond status reporting is the single best predictor of whether you get support. A manager who has to think about whether they hold them probably does not.
How much of a normal week goes on meetings?
Why ask it
Ask for a number. Twenty hours of meetings and a full delivery load is a real answer that people give without hearing it. Compare it with what they said the first three months should produce.
How do performance reviews work here: who writes them, on what cycle, and does the outcome affect pay?
Why ask it
You are looking for whether the process is documented or improvised. If pay is decided separately from the review, ask what does drive pay, because the answer is often a budget cycle nobody mentions to candidates.
When was someone on this team last promoted, and what did it take?
Why ask it
One concrete example beats any statement about growth opportunities. If the last promotion was years ago, or people mostly move by leaving and coming back, you have learned the actual path.
How is the team funded, and is headcount settled for the year?
Why ask it
Reasonable to ask and rarely asked. Discomfort here can mean a hiring freeze pending, a contract up for renewal, or a team funded by one client. Ask it evenly, as planning rather than suspicion.
Has the office or remote arrangement changed recently, and is another change likely?
Why ask it
The current policy matters less than its stability. If it has moved twice in two years, treat today's arrangement as temporary and think about whether the commute works at the stricter end.
What do you like least about working here?
Why ask it
Everyone has something. A candid gripe suggests you would get honest answers as an employee too. A polished answer with no downside at all is the mildest of red flags, and usually means the culture rewards enthusiasm over accuracy.
How long have you been here, and was there a point where you nearly left?
Why ask it
The near-miss story is where you learn what the organization does when someone is unhappy: it either fixed something or it did not. It also breaks the script, since almost nobody asks the interviewer about themselves.
A year from now, what would make you say this hire had not worked out?
Why ask it
The failure mode they name is the one they have seen before. Pace, writing, pushing back on stakeholders, whatever it is, you now know the specific risk to address in your closing minutes and your follow-up note.
Do you have any hesitations about my background? I would rather answer them now.
Why ask it
Your only chance to address a doubt before it is discussed without you in the room. Most interviewers will name something small. Answer it in two sentences, without arguing, and then stop talking.
Who makes the final decision on this role, and is there anyone else I would meet?
Why ask it
Tells you whether the person in front of you is the decision maker or a gatekeeper, which changes how you follow up. An unexpectedly long list of remaining interviews is also a schedule you can plan around.
What are the next steps, and when do you expect to decide?
Why ask it
Gives you a date, which is what you need if another process is running in parallel. Vagueness at the end of a final-stage interview is itself information about how the decision is being made.
Using the last five minutes well
Practical guidance for the conversation itself
Choosing which ones to ask
Pick three or four, not twenty
You usually have five to ten minutes. Choose one about the work, one about how you would be managed, one that tests something specific you are unsure about, and close on next steps.
Match the question to the person
A recruiter can answer process, pay bands and timelines. The hiring manager can answer scope, decisions and the first three months. A future peer is the only one who will tell you what the week really feels like, so save the honest-downside question for them.
Ask about the risk you actually have
If your concern is burnout, ask about meeting hours and on-call. If it is career stalling, ask about the last promotion. Questions chosen to sound impressive waste the only slot where you get to gather evidence.
How to ask them
- 1Say up front how many you have. 'I have three, and one is about next steps' keeps you inside the time you are given.
- 2Ask one at a time and let the answer finish. Stacked questions get the easiest one answered and the rest dropped.
- 3Follow up once with a specific. 'Who was that?' or 'How long did that take?' turns a general answer into a usable one.
- 4Take short notes. It reads as serious, and you will need the detail to compare two offers a fortnight later.
- 5Finish by saying you want the role, if you do. The questions gather information, the closing line does the persuading.
Reading the answers
- Watch for the pause before an answer about a departed employee, a reorganization, or funding. Reluctance is data, not proof.
- Compare the manager's answer with a peer's on the same subject. Divergence on workload or promotion is the most useful signal in the whole process.
- Prefer examples to descriptions. 'We promoted two people last cycle' is worth more than a description of a career framework.
- Notice who says 'we' about problems and who says 'they'. It tells you where the team sits in the organization.
- An interviewer who cannot describe the first three months is telling you the role is undefined, whatever else they say about it.
Common mistakes
Asking what the website already answers
Founding date, product list, published values. It burns your slot and suggests you did not prepare. Ask instead about how something on the website works in practice.
Avoiding problems to seem positive
Asking what is hard is not negativity, and good managers respect it. The mistake is the tone, not the topic: ask as someone planning to fix things, not as someone auditing the place.
Raising pay at the wrong stage
Bands and benefits belong with the recruiter or at offer, not at the end of a technical interview with a future colleague. If nobody has mentioned a range by the final stage, ask the recruiter directly rather than the panel.
Saying you have no questions
This reads as indifference more than confidence. Even in a short screen, ask what the next step is and what they would want done in the first three months.