Killer Questions to Ask at the End of an Interview
Good questions to ask at the end of an interview, for the moment the interviewer says 'do you have any questions for us?' There are 60 questions in six groups: the role, the manager and team, growth, culture, the company, and the closing ones about your candidacy and next steps. Each has a note on what a good or an evasive answer tells you. The killer ones are rarely clever. They are the ones whose answers you would act on.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The role
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.
Can you walk me through an ordinary week in this job?
Why ask it
Ask for last week in particular, since a described 'typical' week tends to be the tidy version. Listen for which days are fixed by meetings or deadlines and which would be yours to plan, and whether the interviewer knows the week well enough to describe it at all.
What do the people who do this job best do differently from the rest?
Why ask it
The answer is the real person specification, usually shorter and more honest than the posting. If it is a skill you have, say so in your closing line. If it is stamina for long hours, you have learned that too.
What do people find hardest about this job once the novelty wears off?
Why ask it
Asking about month ten instead of week one makes this harder to deflect than a question about challenges. An interviewer who names on-call weeks, a difficult client or slow procurement is telling you the trade you would be accepting.
Is this a new role, or would I be taking over from someone?
Why ask it
A predecessor who was promoted or moved teams is a good sign. A departure nobody wants to describe, or a seat that has been empty for months, is worth one careful follow-up. If the role is new, ask who has been doing the work until now.
What takes up the team's time that is not in the job description?
Why ask it
This is where support tickets, monthly reporting and one demanding stakeholder tend to surface. If the answer is a long way from the posting, ask who wrote the posting and when, because the job may have moved since.
If I started on Monday, what would I be working on first?
Why ask it
A named project means the need is real and somebody has planned for your arrival. 'We would work that out together' is fine at a small company and a warning at a large one, where it can mean a month of reading documents.
Which problem on your desk would you most like this hire to take away?
Why ask it
This is the plainer version of asking what keeps a manager up at night. Whatever they name is what you would be judged on first, whatever the posting lists. Tie one piece of your experience to it before the conversation ends.
Which decisions would this role own outright, and which need sign-off?
Why ask it
The split shows the real seniority behind the title. If everything of consequence needs approval, ask who gives it and how quickly they answer, because that person's inbox would set your pace.
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.
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.
What would I have to work with: budget, tools, other people's time?
Why ask it
A role handed goals and no means is set up to disappoint, and the gap rarely shows in a posting. If you would have to make the case for everything, ask who approved the last request like that and how long it sat.
Is there a plan for my first week, or would I be shadowing someone and picking it up?
Why ask it
Either can work. What matters is whether anyone has thought about it: a named person to sit with, accounts set up before you arrive, a first task small enough to finish. Ask who trained the most recent hire and how long it took them to work alone.
Manager and team
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 clearest sign that you would get support. A manager who has to think about whether they hold them probably does not.
How would the people who report to you describe working for you?
Why ask it
It gets further than asking about management style, which invites a label like 'hands-off'. A manager who can quote a real complaint from the team has asked for feedback at some point. One who offers only compliments may never have.
Who would I work alongside every day, and what does each of them do?
Why ask it
Count the people and note their roles: you learn whether you would be one of five doing the same thing or the only one who does yours. Being the only one means more freedom and nobody to check your thinking with.
What does someone on your team do that makes your own job easier?
Why ask it
Managers tend to answer this one quickly, because they are picturing a real person. Written updates, bad news delivered early, not needing to be chased: whichever habit they name is the one to show in your first month.
What would you say is the team's biggest challenge right now?
Why ask it
Expect a deadline, a backlog or a system being replaced, and whichever it is would shape your first six months. Follow with 'which part of that would be mine?' If the answer is 'nothing major', ask what the new hire is meant to relieve.
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.
How does the team settle a disagreement about the right way to do something?
Why ask it
You are listening for a method: a decision owner, a trial of both, a vote. 'It rarely comes up' can describe a harmonious team or one where the loudest person wins by default, so ask for the last example.
When something urgent lands, how do you decide what the team stops doing?
Why ask it
Every team says it prioritizes. Few can name something they dropped. A manager who answers 'we find a way to do both' is describing your evenings, so ask what happened to the last piece of work that got bumped.
What happened the last time someone on the team made an expensive mistake?
Why ask it
Ask for the story, not the policy. If the telling ends with what the team changed, mistakes are survivable there. If it ends with whose fault it was, people will be hiding theirs, and you would learn to do the same.
How long have the people on the team been here, and when did someone last leave?
Why ask it
Tenure is hard to dress up. Long-timers alongside recent joiners suggests people stay and the team is still growing. Everybody under a year, on a team that has existed for five, deserves a plain follow-up about why.
Is the team all in one place, and if not, when do everyone's hours overlap?
Why ask it
Worth asking even for an office job, since a manager in another city or time zone changes how you get answers. A few shared hours a day is workable. Standing meetings at seven in the morning or nine at night need to be known before an offer, not after.
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.
Growth
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.
How would I know in an ordinary month whether I was on track?
Why ask it
Formal reviews can be many months apart, which is a long time to guess. A good answer names something visible: a number, a dashboard, a standing conversation. If the honest answer is 'you would hear if there was a problem', expect silence to be the only praise.
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.
Where have the people who held this job gone next?
Why ask it
Up, sideways into another team, or out of the company are three different jobs wearing one title. If nobody has held it long enough to move on, ask what the manager imagines the next step being and whether that step exists today.
If I did this job well, what would it look like in two years?
Why ask it
Some roles widen as the person earns trust and some are a fixed seat that stays the same size. Both are legitimate. You only need to know which one this is before you weigh it against another offer at the same pay.
Is there time and money set aside for training, and who decides how it gets spent?
Why ask it
A budget nobody has time to use is common, so ask what the interviewer or a teammate last spent it on. If the answer is a course two years ago, development here is something you would arrange yourself.
What feedback did the last person in this job hear most often?
Why ask it
It shows what the manager notices and corrects, which is often not what the posting stresses. If they cannot recall giving any, set that beside what they said about reviews. For a brand-new role, ask it about the team instead.
Culture
What is your favorite part of working here?
Why ask it
Nearly every interviewer has been asked this, and it still earns its slot because it lets them talk about themselves for a minute. A manager they learn from or a problem they are not finished with is a convincing answer. 'The people', with no example attached, is what everyone says everywhere, so ask for one.
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: it can mean the place 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. Save it for an interviewer who has warmed to you, and take a short 'no' as the whole answer.
How would you describe the culture here to someone who had never seen the careers page?
Why ask it
The clause at the end is the point: it asks for their words and not the company's. Follow any adjective with 'what does that look like on a Tuesday?' Collaborative can mean generous colleagues or nine people copied on every email.
Which of the company's values would I see in action if I worked here?
Why ask it
Read the values on the website first, so you are asking how the list works in practice and not what is on it. An interviewer who picks one and tells you about a decision it changed is describing a value in use. One who recites all of them may be reading the wall.
What surprised you most in your first few months here?
Why ask it
Surprises are the gap between how a company presents itself in interviews and how it is, described by someone who crossed it. A pleasant one is good news. If the interviewer joined too long ago to remember, save the question for the newest person you meet.
When did you last work a weekend, and what was it for?
Why ask it
A date is harder to fudge than a statement about balance. Once a quarter for a launch is a job with deadlines. 'Most of them lately' tends to come with a laugh, and you should take it at face value.
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.
Who tends to struggle here, even when they are good at the work?
Why ask it
Every workplace has a type that does not thrive in it, and a thoughtful interviewer can describe theirs: people who need quiet, people who wait to be asked, people who dislike changing direction. Be honest with yourself about whether the description is you.
What was the last thing the team celebrated?
Why ask it
A light one for a future colleague, and more telling than it looks. A shipped project, someone's ten years, a customer's thank-you note: what gets marked is what is valued. A long pause suggests good work mostly passes without comment.
The company
What does the company most need to get right this year, and where does this team come into it?
Why ask it
A team close to the main priority gets attention, budget and pressure. One far from it gets left alone, which suits some people. If the interviewer cannot name the priority, strategy is not reaching their level, and it would not reach yours.
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.
Who do you see as the main competition, and what do they do better than you?
Why ask it
Look up the competitors beforehand so you can tell a frank answer from a rehearsed one. Someone who can credit a rival with a real strength works at a company that looks at itself clearly. 'We do not really have competitors' is seldom true.
What is the company betting on for the next five years?
Why ask it
A sharper way to ask where the company is headed, since a bet can be named and a vision usually cannot. Ask what would have to go wrong for it to fail. Someone who believes in the plan can usually answer that part without getting defensive.
How did last year go against what the company set out to do?
Why ask it
For a public company you can check the answer afterward, which makes it a quiet test of candor. At a private one, listen for specifics about customers gained or lost. Growth figures quoted with no starting point tell you little.
What is changing in the company at the moment that I would feel in this job?
Why ask it
New leadership, a reorganization, a system being replaced, a merger: any of them can reshape a role within months of your starting. Change is not a reason to walk away. Finding out about it in your second week is a reason to wonder what else went unsaid.
I read the company's latest announcement before coming in. How has it gone down inside the team?
Why ask it
Name the launch, funding round or new office you actually read about, and the question does two jobs: it shows you prepared, and it gets you the inside view of a public story. Leave layoffs and other sore subjects out of it with a junior interviewer, who may not be free to discuss them.
Closing
What was it in my application that made you want to talk to me?
Why ask it
Their answer is what they believe your main strength is, and it may not be the one you have been pushing. Build your closing line on it. It also puts a point in your favor back in the interviewer's mind just before they write their notes.
What would the ideal person for this job have that you have not found yet?
Why ask it
It surfaces the gap in the whole field, not only in you. If you have the missing thing and did not mention it, you have just been handed the opening. If you lack it, say how you would cover it and leave it there.
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
Often your only chance to address a doubt before it is discussed without you in the room. If they name one, answer it in two sentences, without arguing, and then stop talking. If they say there is nothing, thank them and move on, since pressing for a doubt can plant one.
Who should I talk to about the salary range, and when?
Why ask it
Asking who and when gets pay onto the table without making it the last thing a future colleague hears from you. A recruiter will often simply tell you the range. Whether an employer has to disclose one depends on where the job is, so check the rules for that place.
If you made an offer, how soon would you need the person to start?
Why ask it
Mention your notice period here so nobody is surprised later. An employer that needs someone in two weeks has a gap hurting them now, which is useful to know when you negotiate and a hint about the workload waiting.
Would references or a sample of my work be useful to you at this point?
Why ask it
Offer only what you can send within a day. A yes gives you a reason to follow up with something of substance. Warn your referees before you hand over their names, and tell them which job it is.
What should I have asked you today that I did not?
Why ask it
Interviewers sometimes use this to mention the thing they were unsure whether to raise: a restructure, a difficult stakeholder, a travel requirement. Ask it second to last, while there is still time for a real answer, and keep quiet while they think.
Who makes the final decision on this role, and is there anyone else I would meet?
Why ask it
You learn whether the person in front of you decides or advises, which changes who your follow-up note should be written for. 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.
If I have not heard by the date you mentioned, is it all right to email you directly?
Why ask it
Getting permission now makes the follow-up feel expected instead of pushy. It also settles whether to write to the interviewer or the recruiter. Give it a working day or two past the date before you send anything.
Using the last five minutes well
Practical guidance for the conversation itself
What questions to ask at the end of an interview
Pick three or four, not the whole list
Expect five to ten minutes, sometimes less. Choose one from The role, one about how you would be managed, one that tests something specific you are unsure about, and close on next steps.
Prepare twice as many as you will ask
A good interview answers some of your questions before you reach them, and repeating one shows you were not listening. Bring six or seven from different groups, cross them off as they get covered, and say so if they all were: 'you have covered the first week and the team, so I have two left.'
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 likeliest to tell you what the week really feels like, so save the question about what they like least for them.
Ask about the risk you actually have
The best questions to ask at the end of an interview are the ones aimed at your own doubt about the job. 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.
When there is time for only one
If the interviewer is glancing at the clock, ask about next steps and nothing else, and offer to send the rest by email. With two, add the hesitations question from Closing: it is the one most likely to change how this interview is remembered.
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 shows you mean to use the answers, and you will need the detail to compare two offers a couple of weeks 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. A gap between the two on workload or promotion tells you more than either answer alone.
- 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 hints at whether the team feels part of the company's decisions or on the receiving end of them.
- An interviewer who cannot describe the first three months is probably telling you the role has not been defined yet, 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 can read as indifference, however confident you feel. Even in a short screen, ask what the next step is and what they would want done in the first three months.