Questions to Ask at the End of an Interview: 5 Compared Pairs

Not a list of twenty questions to memorise. Five pairs, each one a choice between a question that sounds good and a question that gets you something.

"Do you have any questions for us?" is the only part of an interview where you set the agenda — and interviewers read your choice as a sample of how you think. A candidate who asks about scope, constraints and failure modes sounds like someone who has shipped things. A candidate who asks what the culture is like sounds like someone reading a list they found online.

So this page is not that list. Each problem below puts two real questions side by side and asks which one is worth your turn. The reasoning matters more than the wording: once you see why one works, you can build your own from your own situation.

One test covers most of it — if the answer could be copy-pasted onto the company's careers page, the question is wasted.

Three situations, five pairs

What this moment is actually for

2 problems

The closing question is not a formality and it is not a test of enthusiasm. It is the only part of the interview where you set the agenda, and interviewers read it as a sample of how you think — a candidate who asks about scope, constraints and failure modes sounds like someone who has shipped things; one who asks what the culture is like sounds like someone reading a list. Two rules cover most of it: ask about things you could not have found on the careers page, and ask about the actual work, not about how nice it is to work there.

How it comes up: "Do you have any questions for us?" · "Anything you'd like to ask?"

Which closing question gives you more usable information?

A"What does a typical day look like in this role?"
B"What does the person in this role spend the most time on that isn't in the job description?"
C"What's the company culture like?"
D"Are there opportunities for growth?"

▶Show answer & reasoning

Better question: B. "What does the person in this role spend the most time on that isn't in the job description?"

🐱 The winning question is engineered to surface the gap between the posting and the reality — which is exactly where job dissatisfaction comes from. "A typical day" invites a rehearsed answer that matches the job description you already read. "Culture" and "growth" are questions whose honest answer no interviewer will give you in a first round, so they cost you a turn and return nothing. A useful test before asking anything: if the answer could be copy-pasted onto the careers page, the question is wasted.

You have time for exactly one question. Which is the better use of it?

A"How would you measure whether this hire was successful after six months?"
B"What are the next steps in the process?"
C"How long have you worked here?"
D"What do you enjoy most about working here?"

▶Show answer & reasoning

Better question: A. "How would you measure whether this hire was successful after six months?"

🐱 The six-month question does three things at once: it gets you the real success criteria (often different from the job description), it signals that you think in outcomes rather than tasks, and the answer tells you whether the team has actually thought about what they need — a hiring manager who cannot answer it is describing a role that is not yet defined, which is information worth having before you accept. "Next steps" is worth asking but belongs to the recruiter, not your one question with the hiring manager. The other two are pleasant and tell you nothing you can act on.

Questions for the hiring manager

2 problems

The hiring manager is the only person who knows what the job is really like, and the only one whose answers you can partly verify later. Spend your questions on the shape of the work: what is broken that this hire is meant to fix, what decisions you would own, what the team argues about. The last one is unusually revealing — every real team disagrees about something, and a manager who says "we don't really have conflicts" is either not paying attention or not being straight with you.

How it comes up: "What should I ask my future boss?" · questions about the team and the work

You want to know if this team is functional. Which question is most likely to get an honest answer?

A"Is the team collaborative?"
B"What does the team disagree about most often, and how does that usually get resolved?"
C"Do people get along?"
D"Is there a lot of politics here?"

▶Show answer & reasoning

Better question: B. "What does the team disagree about most often, and how does that usually get resolved?"

🐱 The winning version works because it presupposes disagreement rather than asking whether it exists — which makes describing it feel normal rather than disloyal. You learn two things: what the actual fault lines are (technical direction? priorities? scope?) and whether there is a real mechanism for settling them. The other three ask the interviewer to admit a problem to a stranger, which nobody does; "is there a lot of politics" additionally reads as a red flag about you. The general technique is worth stealing: to get an honest answer about something negative, ask about its shape, not its existence.

Which question best reveals whether the role has real ownership?

A"Will I have autonomy?"
B"What decisions would I be able to make without checking with anyone, and which ones would always need sign-off?"
C"Is this a senior role?"
D"How much oversight is there?"

▶Show answer & reasoning

Better question: B. "What decisions would I be able to make without checking with anyone, and which ones would always need sign-off?"

🐱 "Autonomy" is a word every employer will say yes to, so asking about it costs a turn and returns nothing. Naming the boundary forces a concrete answer, and the concrete answer is the actual job: a role where you can pick your approach but never the priorities is a different job from one where you own an outcome. Notice the pattern shared with the previous question — replacing an abstract noun (culture, autonomy, collaboration) with a request for a specific example or boundary is the single highest-leverage move in this whole page.

What not to ask, and the one honest exception

1 problem

Three categories reliably cost you: questions answered on the company's own website (signals you did not prepare), questions that are really requests for reassurance ("is the work-life balance good?"), and anything that frames the job as something to endure rather than do. Compensation is the interesting exception — it is not a forbidden topic, it is a timing question. Raising it with a recruiter early is normal and saves everyone time; raising it as your one question to the hiring manager in a first round spends your only agenda-setting moment on something the recruiter would have told you anyway.

How it comes up: "Is it bad to ask about salary?" · "What questions should I avoid?"

First-round interview with the hiring manager. You genuinely need to know the salary range. What do you do?

AAsk the recruiter separately — and use your question with the hiring manager on the work itself
BAsk the hiring manager directly; being upfront is always best
CDon't ask at all until an offer arrives
DHint at it by asking about "the overall package"

▶Show answer & reasoning

Better question: A. Ask the recruiter separately — and use your question with the hiring manager on the work itself

🐱 This is a routing question, not a courage question. The recruiter owns compensation, will answer it plainly, and expects to be asked — many will volunteer the band unprompted. Meanwhile your minutes with the hiring manager are the scarce resource, and they are the only person who can tell you what the job actually is. Waiting for an offer wastes everyone's time if the band is impossible, and hinting reads as exactly what it is. Where pay transparency laws apply, the range may already be posted — check before spending a question on it.

Before the closing question

Behavioral interview questions — strong vs weak answersThe other half of the non-technical round: what your stories actually reveal, two answers compared each time.System design interview questionsJudgement over recall, same as this page but for architecture decisions.Critical thinking test (20 Q, 15 min)The five-section format many employers run alongside the interview itself.

Questions to ask at the end of an interview — FAQ

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

Two or three is plenty, and one excellent question beats three filler ones. What matters is that they could not have been answered by the job posting — quantity signals nothing, while a single question about scope or success criteria signals how you think about work.

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

It is not forbidden, it is misrouted. The recruiter owns compensation, answers it plainly, and expects the question. Your minutes with the hiring manager are the scarce resource — spend them on what the job actually is, since they are the only person who can tell you.

What if I genuinely have no questions?

Then ask the six-month question: "How would you measure whether this hire was successful after six months?" It works in every role, gets you the real success criteria, and the answer tells you whether the team has defined the job at all. Saying "no questions" reads as low interest even when it isn't.

What questions should I avoid?

Anything answered on the company website, anything that is really a request for reassurance ("is the work-life balance good?"), and anything that frames the job as something to endure. Also skip "is there a lot of politics here" — no one will say yes, and it becomes a data point about you.

Should I ask different questions of the recruiter and the hiring manager?

Yes, and it matters more than most people realise. Recruiters own process, timelines and compensation. Hiring managers own the work: what is broken that this hire fixes, which decisions you would own, what the team argues about. Asking a recruiter about technical trade-offs — or a hiring manager about the interview schedule — wastes a turn with each.