What Questions Should You Ask at the End of an Interview?

Most candidates treat this as the polite end of the interview. It is not. It is the last thing the interviewer will remember, and in many hiring debriefs it is written down alongside your answers. A candidate who asks what the first 90 days look like reads very differently from one who says "no, I think you covered everything."

This moment does two things at once. It gives the interviewer one more data point about how you think, and it gives you your only real chance to find out whether you actually want the job. Both matter, and the questions below are chosen to serve both.

Why the Last Five Minutes Carry Weight

Interviewers are trying to answer a specific question: will this person be effective here? Everything you asked earlier was in response to their prompts. The questions you raise at the end are unprompted, so they show what you care about when nobody is steering you.

Three things get read from your questions, whether or not the interviewer says so out loud:

• Preparation. Did you look into the company, or are you asking something the homepage answers?
• Level. Junior candidates ask about tools and tasks. Stronger candidates ask about priorities, tradeoffs, and how success is judged.
• Genuine interest. Someone who has pictured themselves doing the job asks different questions than someone collecting offers.

You do not need to be clever. A plain, specific question about the actual work beats a rehearsed one every time.

What Makes a Question Worth Asking

A good closing question has three properties.

It cannot be answered by the job posting. If the answer is on the careers page, asking signals you did not read it. "What does this team do?" is a bad question. "The posting mentions supporting two product lines — is the work split evenly, or does one take priority this quarter?" is a good one.

It is answerable by the person in front of you. A recruiter usually cannot tell you how technical decisions get made. A hiring manager usually cannot quote the exact benefits schedule. Match the question to the role of the person answering it.

The answer would change something for you. Ask things you actually want to know. If the answer would not affect how you feel about the offer, the question is decoration, and it tends to sound like it.

Questions About the Role Itself

These work in almost any interview, and they are the safest place to start.

• What does success look like in the first 90 days?
• What are the two or three priorities this role owns in the first six months?
• Is this a new position, or am I replacing someone? What prompted the opening?
• What does a normal week look like — how much is planned work versus reactive?
• Which parts of this job do people find harder than they expected?

That last one is quietly the most useful. It gives the interviewer permission to be honest, and the answer tells you where the real friction is. If they cannot name anything difficult, that is information too.

Questions About the Team and the Manager

If you are speaking to your prospective manager, this is the most valuable ground you can cover. Your manager affects your daily experience more than the company brand does.

• How is the team structured, and who would I work with most closely?
• How do you like to give feedback, and how often?
• How does the team make decisions when people disagree?
• What is your management style in one or two sentences?
• How do you protect the team's time when priorities shift mid-quarter?

Listen for specifics. "We're very collaborative" is a value statement. "We do a 30-minute weekly review where anyone can push back on the roadmap" is a practice. Practices tell you how a team actually runs.

Questions About How You Will Be Evaluated

Asking how performance is measured shows you plan to be accountable, not just employed. It is also how you avoid a job where expectations are never made explicit.

• How is performance reviewed, and on what cycle?
• What separates someone who is doing well in this role from someone who is doing exceptionally well?
• What does growth from this position usually look like?
• Are there metrics this role is responsible for? Which ones?

If nobody can describe what good looks like, that is a real risk. Vague expectations tend to become moving expectations.

Questions About the Company's Direction

Use these in later rounds, or with senior interviewers. They demonstrate that you are thinking beyond your own desk.

• What is the biggest challenge the team is facing right now?
• How has the team's focus changed in the past year?
• Where does this team's work show up in the company's priorities?
• What is something the company is betting on that an outsider would not know?

Keep these grounded. A question about strategy is strong; a question that implies you have already diagnosed their problems is not.

Questions to Ask a Recruiter Instead

Recruiters are the right person for process, timeline, and logistics. Save these for them so you do not waste hiring-manager time on things they cannot answer.

• What are the remaining steps, and who would I meet?
• When are you hoping to make a decision?
• Is the salary range for this role flexible, and what is it based on?
• Is the position remote, hybrid, or in-office, and is that fixed?
• Is there anything in my background you would want me to clarify for the team?

That final question is worth asking every time. It surfaces doubts while you can still address them, instead of after the debrief.

Questions That Work Against You

Some questions are not just weak — they actively cost you ground.

Anything answered on the careers page. "What does the company do?" or "How many employees do you have?" reads as unprepared.

Salary or time off in a first-round interview with the hiring manager. These are fair questions, but they belong with the recruiter, or after there is mutual interest. Leading with them shifts the conversation before you have established value.

"How did I do?" It puts the interviewer on the spot and asks them to evaluate you before they have compared notes with the panel. Ask about next steps instead.

Questions that assume the offer. "When would I start?" or "Which desk would I sit at?" can read as presumptuous early on.

A long list. Three thoughtful questions land better than eight rushed ones. When time is short, ask one and offer to follow up by email.

How to Prepare Questions You Will Actually Use

Do not walk in with a memorized script. Walk in with a short, flexible list.

1. Write five questions, expect to ask three. Interviewers often answer one or two of yours during the conversation, so redundancy is protection.
2. Tie at least one to something specific about this company — a recent launch, a line in the posting, something the interviewer said earlier. This is what proves the question was written for them and not copy-pasted.
3. Sort by who can answer them. Group your questions by recruiter, hiring manager, peer, and skip-level. Reuse the good ones across rounds where relevant.
4. Keep one question in reserve for the round where everything else has already been covered.
5. Take notes on the answers. It reads as serious, and you will need the details when you compare offers.

If They Have Already Answered Everything

This happens in thorough interviews, and "no questions" is still the wrong answer. Two clean options:

Reference what you learned, then go one level deeper. "You mentioned the team is moving from quarterly to monthly planning — has that changed how much of the work is reactive?"

Ask about them. "What made you join, and has it turned out the way you expected?" People answer this warmly, it is impossible to have covered already, and it usually gives you the most honest read on the culture you will get all day.

Either way, close by confirming next steps. It is a small thing that leaves the conversation feeling finished.

Frequently Asked Questions

How many questions should I ask at the end of an interview?

Two to three. Prepare five so you have replacements for the ones that get answered during the conversation. If time runs out, ask your best one and offer to email the rest.

Is it bad to ask about salary at the end of an interview?

Not bad, but usually mistimed with a hiring manager. Ask the recruiter, who owns compensation ranges, and ideally once there is mutual interest. If the interviewer raises it first, answer directly.

What if I genuinely have no questions?

Then you are missing information you will want when deciding on an offer. Fall back to a reliable pair: "What does success look like in the first 90 days?" and "What do people find harder in this role than they expected?"

Can I ask the same question to different interviewers?

Yes, and it is often useful. Asking three people what success looks like in this role and getting three different answers is one of the most valuable signals you can collect.

Should I write my questions down and bring them?

Bring them. Reading from a short list looks prepared, not unpolished — in person or on video. Just look up while you listen to the answer.

Put It Into Practice

Strong closing questions come from having your own material organized before the interview, not from a list you skim in the parking lot. Use Vibe ID™ to keep your projects, results, and career stories in one place, so you walk in knowing exactly which evidence fits the role — and which questions will tell you whether it fits you.