Questions to Ask at the End of an Interview (Organised by Who's in the Room)

The best questions to ask at the end of an interview are the ones you actually need answered before you could say yes. Ask about the work, the manager, and how success gets measured — not about anything already published on the careers page.

What the closing question is really for

"Do you have any questions for us?" is not a courtesy. It is the one stretch of the interview you control, and interviewers read it two ways at once: as evidence of how you think about the job, and as a preview of what you will be like to work with once the offer is signed.

That double reading is why generic questions cost you. A question you could have answered by reading the job posting signals that you did not read the job posting. A question that reveals you have already imagined yourself doing the work signals the opposite. But the more important audience for these questions is you: this is your only structured chance to gather the information you need to accept or decline intelligently.

So run the closing minutes with two goals in mind. First, buy information you genuinely need. Second, let the questions themselves demonstrate the way you approach problems. When those two goals conflict, choose information — a job you accept blind is far more expensive than an interview where you failed to look clever.

The two questions worth asking in every interview

Most advice hands you a list of fifty questions. In practice, two belong in every conversation regardless of company, level or round, because they surface the two things that most reliably determine whether a job goes well: what success actually looks like, and what is currently hard.

1. 1"What would a great first six months look like in this role — what would I have delivered?" This forces a concrete answer. If the interviewer can describe the outcome crisply, the role is well-defined and someone has thought about why it exists. If you get vague language about "getting up to speed" and "being a team player", the role is either new, contested, or nobody has decided what it is for.
2. 2"What is the hardest part of this job that isn't obvious from the outside?" Every job has one. An honest interviewer will name it — the legacy system nobody wants to own, the stakeholder who changes their mind, the on-call rota. An interviewer who claims there isn't one is either not being candid or does not know the work well enough to be assessing you for it.

Both questions are safe to ask at any stage and with any interviewer. Both give you something to compare across companies. And both produce answers you can quote back later — in the second conversation, in a follow-up note, or when you are weighing two offers against each other.

Ask by who is in the room, not from a list

The same question lands differently depending on who is answering it. A recruiter cannot tell you how code review works; a peer engineer cannot tell you the compensation band. Matching the question to the person is the single biggest upgrade you can make to your closing minutes, and it takes no extra preparation.

The recruiter screen

The recruiter owns process, timeline and money. They rarely own the work. Use them for logistics you would otherwise waste a hiring manager's time on, and for a candid read on where the process stands.

• "What does the rest of the process look like, and who would I meet at each stage?"
• "Is this a new role or a backfill?" — a backfill invites the natural follow-up of what the previous person went on to do.
• "How long has the role been open?" A role open for six months usually means an unclear spec, a difficult hiring manager, or a compensation band that is out of step with the market.
• "What is the band for this level?" In much of the US this is now published on the posting itself, but where it is not, the recruiter is the right person to ask — and asking early saves both sides weeks.

The hiring manager

This is the person whose judgment will shape your daily experience more than the company's brand, perks or mission statement. Spend your best questions here, and aim them at how the manager operates rather than at how they describe themselves.

• "How do you run one-to-ones, and what do you use them for?"
• "When someone on your team is struggling, how do you usually find out?" The answer tells you whether feedback travels or festers.
• "What decisions would I own outright, which would I recommend, and which would you make?" Vague scope at interview stage becomes contested scope at work.
• "What has changed about this team in the last year?"

Potential peers

Peers will tell you what the job is actually like, but only if you ask questions they can answer honestly without sounding disloyal. Keep the framing practical and specific — how work moves, not whether they are happy.

• "Walk me through what happened with the last significant project — how did it start and how did it end?"
• "Where does work get stuck most often?"
• "What do people here do when they disagree about a technical or creative call?"
• "What surprised you in your first month?"

The skip-level

A skip-level interview exists to test whether you make sense in a bigger picture. Ask about direction and priority, not detail — you are checking that the story you were told two rounds ago still holds one level up.

• "What is this group expected to have accomplished a year from now?"
• "Where does this team's work show up in what the company cares about most this year?"
• "If you could fix one thing about how this org works, what would it be?"

The founder or executive

With a founder, you are buying information about durability and judgment. Keep questions grounded in trade-offs they have actually made rather than inviting a pitch you have already heard on the website.

• "What did you get wrong in the last two years, and what did you change as a result?"
• "What are you deliberately choosing not to do right now?"
• "How is the company funded through its next stage?" — phrased plainly, this is a normal question at any startup, and evasiveness is itself an answer.

Questions that surface a bad manager without sounding accusatory

You cannot ask "is this a healthy team?" and expect a useful answer. What works is asking for a specific, recent, concrete example — because dysfunction is easy to hide in generalities and very hard to hide in a story about last quarter.

• "Tell me about the last time a project here missed its date. What happened next?" Healthy answer: a description of what changed in planning. Warning sign: a named individual who is no longer with the company.
• "How does someone on this team get promoted? Who was the last person, and what did they do?" Healthy answer: a real name and a real path. Warning sign: a description of the framework with no example of anyone travelling through it.
• "What does a typical week look like — and what does a bad week look like?" Healthy answer: an honest peak-and-trough. Warning sign: enthusiastic descriptions of heroics, or a joke about never leaving.
• "Who has left this team in the past year, and what drew them away?" Turnover is not automatically bad; unexplained turnover is.

Notice that none of these are accusations. They ask for a fact, and let the fact do the work. If the interviewer answers with a story that reflects well on the team, you have learned something real. If they cannot produce an example at all, you have learned something too.

Role-specific probes worth adapting

Once the universal questions are asked, one or two questions specific to your function show that you understand the mechanics of the job rather than its title. Pick a single probe and adapt the language rather than reciting all of them.

• Engineering: "What does the path from a merged pull request to production look like, and how long does it take?" Deployment friction predicts daily frustration better than any stack choice.
• Sales: "What does the current team's quota attainment distribution look like — how many people hit it last year?" Ask about ramp, territory and how leads are sourced, not just the headline number.
• Marketing: "Which channel is working right now, and what is the current cost of acquiring a customer through it?" Then: "Who decides what gets tested next?"
• Operations: "What process here is still held together manually, and whose job is it to fix that?" You are looking for whether improvement work is anyone's mandate or everyone's spare time.

The questions to save for the offer stage

Some questions are entirely legitimate but land badly early, because they ask the company to invest in your comfort before it has decided it wants you. They lose nothing by waiting, and once an offer exists you have both leverage and a counterpart whose job is to close you.

• Detailed compensation structure: bonus mechanics, equity refresh, vesting cliffs, how the strike price was set.
• Time off in practice — not the policy, but how much the team actually takes and whether anyone covers.
• Remote and travel expectations that go beyond what the posting says.
• Start date flexibility, relocation support, and equipment.

The exception is the salary band itself. Where a range is not published, asking the recruiter early is not pushy — it protects both parties from spending four rounds discovering a gap that was visible in week one.

How many to prepare, how many to actually ask

Prepare more than you will use and accept that you will ask fewer than you prepared. Interviews run late, and the closing window is often three minutes rather than ten. The skill is not having a long list — it is choosing well under time pressure and leaving cleanly.

1. 1Prepare six to eight questions, ranked. Two universal, two aimed at this specific person, two role-specific, and a couple you would only ask if the conversation opens the door.
2. 2Ask two or three. That is what a normal closing window holds without the interviewer starting to watch the clock.
3. 3Cross off anything already answered during the interview. Asking a question that was covered twenty minutes earlier is worse than asking nothing.
4. 4Keep one in reserve for the follow-up email, where a single thoughtful question is a legitimate reason to write.

If the interviewer says they are out of time, take the exit gracefully: name one question, ask if they would rather answer it by email, and stop. Insisting on your list when someone has a hard stop is the last impression you leave.

How to read the answer you get

A question is only worth asking if you know what a good answer sounds like. Before the interview, write the one-line version of what you would expect a well-run team to say — then you are listening for a match rather than nodding through anything fluent.

• Specific beats polished. Dates, names, numbers and last-quarter examples are evidence. Values language with no example attached is not.
• Consistency across interviewers is the real test. Ask two people the same question about priorities. Alignment is a good sign; two incompatible answers tells you what the first month will feel like.
• Watch what happens after an honest admission. "Our documentation is bad and here is what we are doing about it" is a good answer. "Our documentation is bad" followed by a shrug is a preview.
• Hesitation is data, not rudeness. A pause before answering a question about turnover or promotion is worth a gentle follow-up: "Is that unusual?"

Questions to avoid, and why

A weak closing question does more damage than no question at all, because it is the last thing the interviewer hears before writing feedback. Four categories are worth striking from your list entirely.

• Anything answerable from the careers page or the job posting. "What does the company do?" or "Is this role remote?" reads as unprepared.
• Compensation in a first screen with the hiring manager. Ask the recruiter instead — it is their job, and it keeps the manager conversation about the work.
• The gotcha. "What is your company's biggest weakness?" asked as a challenge invites a defensive non-answer and reads as a trick you saw online.
• Questions that are really statements. "Don't you think the industry is moving toward X?" is a pitch wearing a question mark. If you have a view, offer it as a view.

One more to retire: asking how you did. It puts the interviewer in an awkward position, and the answer is almost never candid enough to be useful. If you want a read on where you stand, ask about next steps and timeline instead — a concrete answer there is the honest signal.

How you ask matters as much as what you ask

Delivery decides whether a good question reads as curiosity or as interrogation. Say why you are asking before you ask it, keep it to one sentence, and then stop talking. The pause after a question is the part that produces the honest answer.

• Frame, then ask. "I've had one manager who ran one-to-ones as status updates and one who ran them as coaching — how do you use yours?" The frame makes the question specific and gives the interviewer permission to be specific back.
• One question at a time. Stacked questions get the easiest one answered and the rest quietly dropped.
• Follow up once. "Can you give me an example?" is the highest-yield sentence in any interview.
• Take a note. Writing down an answer signals you asked because you wanted to know, not to perform.

On video, the mechanics get harder: lag eats the pause, and people talk over each other. Leave a beat longer than feels natural before speaking, and make sure you are legible on camera while you do it — our guide to video interview appearance covers framing and lighting, and what to wear to a video interview covers the wardrobe half. For in-person rounds, interview outfits by company type is the more useful reference.

The rest of the conversation is worth preparing with the same care. The opening minutes set the frame your closing questions land in — see how to introduce yourself in an interview for the first ninety seconds — and everything you hear at the end becomes material for the note you send afterwards.

Using the answers after you leave

The closing questions keep paying out after the call ends. What you heard is the raw material for your follow-up note, your comparison between offers, and your first ninety days if you take the job — provided you write it down while it is still accurate.

• Within an hour, write the answers down verbatim where you can. Memory rewrites them into what you hoped to hear.
• Quote one specific answer in your follow-up email. It proves you listened and it restarts the conversation on substance — our follow-up sequence guide has the timing and templates.
• Keep a single comparison sheet across companies with the same three rows: what success looks like, what is hardest, and how decisions get made. Comparing like for like beats comparing vibes.
• If you accept, bring the answers to your first one-to-one. "You mentioned the hardest part of this job is X — where should I start?" is an unusually strong opening move.

And if the answers were bad — vague success criteria, unexplained turnover, a manager who could not describe a promotion — treat that as the interview working. Declining a job for a reason you can articulate is a better outcome than accepting one you never asked about.