Almost every interview ends the same way: "Do you have any questions for us?" And the most frequent answer ("no, everything's clear") is also the one that costs the most. To the interviewer, a candidate with no questions is a candidate with no real curiosity about the role, and that impression lands right at the end, when the conversation is wrapping up and everything is fresh in memory.
This guide collects 12 questions that work, grouped by what they help find out, with an explanation of what each one reveals. It also covers the ones that are better saved for later in the process.
In this guide
Why "I don't have any questions" costs points
The close of the interview flips the roles for a few minutes, and that reversal is one more test. The questions a candidate asks show what they researched, what they care about, and how they think. Whoever asks nothing wastes the only part of the interview they fully control.
There is a second, less obvious reason: the interview runs in both directions. The candidate is also deciding whether they want to work there, and the right questions reveal things no posting publishes, from the real state of the team to the reason the position is open. Not asking is accepting blind. Writing these questions down the day before is part of any solid interview preparation.
Questions about the role
These show that the person is already picturing themselves in the job, which is exactly the signal an interviewer wants to see:
- "What does a typical week look like in this role?" Brings the posting down to reality. The answer shows whether the job is what the posting paints or something different.
- "What would you expect the person to accomplish in the first six months?" Reveals the real priorities and the criteria performance will be judged by. The answer is also useful for a follow-up note or a second interview.
- "What are the hardest challenges in this role right now?" Invites a conversation about the problems, not the brochure. An evasive answer here is a data point in itself.
- "Is this a new position or a backfill?" A new opening means building; a backfill means inheriting. Both are fine, but it is worth knowing which one it is.
Questions about the team and the manager
Day-to-day life depends less on the company than on the immediate team, and these questions shed light on it:
- "How is the team I'd be working with structured?" Size, seniority, and roles. It helps anticipate how much support there will be and how much autonomy is expected.
- "How is performance measured on the team?" Distinguishes cultures with clear goals from cultures with fuzzy evaluation.
- "What sets apart the people who do best on this team?" The answer describes the real culture better than any mission statement, and along the way it signals which profile gets rewarded.
Questions about the process
Short, practical, and always well received, because they simplify coordination for everyone:
- "What are the next steps in the process?" The safest question in the repertoire. It shows interest and removes the uncertainty of waiting.
- "How many rounds are left, and who would they be with?" Makes it possible to prepare each stage (a technical interview is prepared differently from one with the director) and to estimate realistic timelines.
- "When are you hoping to fill the position?" Useful for managing other processes in parallel without drifting.
The answers to these three questions are worth writing down as soon as the meeting ends: dates, names, and next steps are exactly the kind of detail that gets lost across several simultaneous applications. A job application tracker handles that follow-up.
Questions about the company
These work best when they build on prior research, because they show the homework was done:
- "I saw you launched [recent product or initiative]. How does that affect this team?" The most powerful of the group. It combines research with genuine interest and often opens the richest part of the conversation.
- "How would you describe the work culture, beyond the official version?" The final qualifier invites an honest answer instead of the corporate line.
The three that never miss, if there is only time for three: what they would expect in the first six months, what the hardest challenges of the role are right now, and what the next steps in the process are. They cover performance, the reality of the job, and continuity, and none of them lands badly in any context.
Which ones to avoid in the first round (and when to ask them)
None of these questions is illegitimate. The problem is timing: in the first interview, when the company has not yet confirmed its interest, they put the focus on conditions before contribution.
| Question | Why wait | When it is fine |
|---|---|---|
| Salary and benefits | In the first round it suggests that is the only interest | When the interviewer brings it up, or from the second round on |
| Vacation and PTO | Same effect: conditions before contribution | With an offer on the table, before accepting |
| Remote work and flexible hours | Acceptable if the posting mentions it; otherwise, better later | Second round, or earlier if the arrangement is a dealbreaker |
| "What does the company do?" | Reveals that not even five minutes of research were done | Never in that form; the informed versions are always better |
| Future promotions and raises | Premature before demonstrating any initial contribution | In the final stage, framed as interest in professional development |
One reasonable exception: if the process is advancing and nobody has mentioned the salary range, asking before investing in more rounds is legitimate and increasingly well regarded. Several states now require pay ranges in postings, which makes the topic less delicate than it used to be. The wording matters ("could you share the range budgeted for this position?"), and the best moment is the close of the second conversation.
How to bring the questions to the interview
It helps to arrive with five or six questions written down, knowing the conversation will answer some of them before the end. Bringing them on paper does not make a bad impression; the opposite is true: checking the notepad at the close communicates preparation.
The symmetrical mistake also exists: turning the close into an interrogation. Three or four questions is the right measure for a 30-to-45-minute first interview. And if everything really was answered, say so with substance ("I had planned to ask about the team and next steps, but we've covered both") to make it clear the questions existed. This final part is trained like the rest: the guides on common interview questions and strengths and weaknesses cover the rest of the conversation, and an interview simulator makes it possible to practice the full back-and-forth.
Frequently asked questions
How many questions should I ask at the end of an interview?
Three or four in a standard first interview. It helps to bring five or six prepared in writing, because the conversation usually answers some before the close, and checking a notepad communicates preparation, not improvisation.
Is it bad to say "I don't have any questions"?
It costs points, because it is read as a lack of real interest in the role. If everything was genuinely answered, say so with substance: mention which questions were prepared and note that they were covered during the conversation.
Can I ask about salary in the first interview?
It is better to wait for the company to bring it up or for the second round. The exception: if the process advances without anyone mentioning the range, asking naturally before investing more time is legitimate and reasonable, especially now that many states require ranges in postings.
Which questions make the best impression?
The ones that build on prior research (mentioning a launch or recent news about the company) and the ones that show the person projecting themselves into the role, such as what they would be expected to accomplish in the first six months or what the current challenges of the position are.
Are these questions useful for evaluating the company?
They are the best tool available for it. Questions about why the position is open, how the team is structured, or what the real challenges of the role are reveal information no posting publishes, and the interview is a two-way decision.