Ask the interviewer questions that do two jobs at once: signal that you're a serious, thoughtful candidate, and surface the red flags that tell you whether the job is worth taking. The best questions are tailored to who you're talking to — ask the hiring manager about success metrics and team challenges, ask peers what the work actually feels like day to day, and ask a skip-level or executive about strategy and where the team is headed. Come with five or six prepared questions, because some will get answered before it's your turn. Skip anything you could have learned from the company's website.
The questions are part of the test
Most candidates treat "do you have any questions for me?" as the wind-down — the part where the interview is basically over. It isn't. Interviewers use your questions as a final data point: did this person dig in, do they understand what the job actually is, and are they evaluating us as hard as we're evaluating them? Strong candidates ask questions that could only come from having thought seriously about the role. Weak candidates ask nothing, or ask about vacation days.
There's a second, more self-interested reason to ask well. You are about to spend years of your life at this place. The interview is your one structured chance to find out whether the job is what the posting claims, before you accept it. The right questions do double duty: they make you look sharp and they protect you from a bad fit.
Match the question to the interviewer
A modern interview loop puts you in front of several people, each of whom knows something the others don't. Asking all of them the same generic question wastes the rounds. Ask each one what only they can answer.
| Who you’re talking to | What they uniquely know | Best questions to ask |
|---|---|---|
| Recruiter (screen) | Process, timeline, comp range, must-haves | What does the interview process look like end to end? What’s the salary band for this role? What are the two or three non-negotiables for this hire? |
| Hiring manager | Success metrics, team gaps, why the role exists | What would success look like in the first 90 days and the first year? Why is this role open — is it growth or a backfill? What’s the hardest problem the team is facing right now? |
| Peers / future teammates | Day-to-day reality, team culture, the manager | What does a normal week actually look like? What do you wish you’d known before you joined? How does the team handle disagreement or a missed deadline? |
| Skip-level / executive | Strategy, funding, where the team is headed | Where do you see this team in two years? How does this team’s work connect to the company’s top priorities? What would make you consider this hire a great investment? |
| Cross-functional partner | How the role works with other teams | How does this role partner with your team? Where does collaboration tend to break down today? What would make your job easier if this person nailed it? |
Questions that surface red flags
Some questions are valuable precisely because the answer — or the discomfort with the question — tells you something the job posting won't. Ask these calmly and listen to how they're handled.
- "Why is this role open?" A backfill where the last person was promoted is a good sign. A backfill where they "moved on" after eight months, or a brand-new role with no clear charter, deserves a follow-up. Roles created to absorb a problem nobody will name are a classic trap.
- "What's turnover been like on this team?" You won't always get a straight number, but you'll learn a lot from how the question lands. Evasion is itself an answer.
- "How are priorities decided when everything feels urgent?" Reveals whether the team has a functioning process or runs on constant fire drills.
- "What does the path to promotion look like from this role?" If no one can describe it, the level above you may be a ceiling.
- "How would you describe the manager's style?" Ask peers, not the manager. The gap between how a manager describes themselves and how their reports describe them is where a lot of bad jobs hide.
Questions to avoid
A bad question can undo a strong interview. These are the ones that consistently cost candidates:
- Anything answered on the website. "What does the company do?" or "Who are your competitors?" signals you didn't prepare. Show up having read the basics.
- Logistics-first questions. Leading with time off, remote-work policy, and start dates before you've shown any interest in the work reads as checked-out. Ask these, but ask them later and ideally through the recruiter.
- "Did I get the job?" It puts the interviewer on the spot and signals you don't understand the process. Ask about next steps and timeline instead.
- Yes/no questions you could research. "Do you offer 401(k) matching?" is a benefits-page question. Spend your limited airtime on things only a human can tell you.
- Nothing at all. "No, I think you covered everything" is the worst answer on this list. It is read as indifference, and it's entirely avoidable.
As Indeed's interview guide notes, the goal is to ask questions that demonstrate genuine engagement with the specifics of the role rather than generic curiosity. Indeed's career guidance makes a similar point: the strongest closing questions are the ones tailored to the particular job and the particular person in front of you.
How to deliver them
Don't read from a list like you're filling out a form. Weave your questions into the conversation when they fit, and hold the rest for the end. When something the interviewer says sparks a real follow-up, ask it on the spot — a spontaneous, specific question is the strongest signal of all that you were actually listening. Take a notebook; jotting their answers shows you care about them, not just about being hired.
The honest summary
The questions you ask are a graded part of the interview and your best tool for vetting the job before you take it. Prepare five or six, tailored to whoever is across the table, lead with the work rather than the logistics, and keep one strong question in reserve so you're never empty-handed. Done well, your questions leave the interviewer thinking you'd be a sharp hire — and leave you with a clear-eyed read on whether you actually want the job.
Common questions
- How many questions should I prepare?
- Prepare five or six, expect to ask two or three. Interviews run long, and a good interviewer will answer some of your questions in the course of describing the role. Over-preparing means you're never caught flat-footed when they ask 'what questions do you have for me?' — which is itself a tested question.
- Is it bad to ask about salary or benefits in the first interview?
- In a recruiter screen, compensation is fair game and often expected — that's partly what the call is for. With the hiring manager or peers in a later round, it's usually better to let the recruiter own that conversation and keep your questions focused on the role and team. You're not avoiding the topic, you're routing it to the right person.
- What if I genuinely have no questions left?
- Never say 'no, I'm all set.' It reads as disinterest, and it's the easiest unforced error in the interview. Keep one durable question in reserve that almost never gets pre-answered, like 'What's something about working here that surprised you?' or 'What does someone need to do in the first 90 days to be considered a strong hire?'
- Can my questions actually hurt me?
- Yes. Questions that reveal you didn't research the company ('So what does this company do?'), that center entirely on time off and remote policy before you've shown interest in the work, or that put the interviewer on the defensive can leave a bad taste. The fix is easy: ask about the work and the team first, logistics later and through the recruiter.
Sources
Keep reading
How to answer "tell me about yourself"
Answer "tell me about yourself" with a 60-90 second present-past-future pitch tailored to the role. The structure, a before/after example, and what not to do.
How do I prepare for a behavioral interview?
Prepare for a behavioral interview with the STAR method, a bank of 6-8 stories mapped to common competencies, and practicing out loud. Examples included.
Why is my job application getting ghosted?
Most applications get filtered out by an ATS before any human reads them. Here's what actually happens, why, and how to know if your resume is the bottleneck.
Why am I not hearing back from job applications?
Not hearing back is usually the funnel, not you: ATS filtering, recruiter triage, pre-filled roles, and the channel gap. Here is how to fix what you control.