Near the end of almost every interview comes "so, do you have any questions for us?" Treat it as a polite formality and you waste the one stretch of the conversation you control. Treat it as part of the evaluation, because it is, and you can shift how the room sees you in the last five minutes.
Good questions do two jobs at once: they tell you whether you actually want this job, and they show the interviewer how you think. Here's how to use them.
Why "no, I think you covered everything" is the wrong answer
Having no questions reads as low interest, even when you're genuinely curious and just nervous. Interviewers notice. The candidate who asks one thoughtful question about the team's real challenges looks more invested than the one who says they're all set.
It's also a missed chance to gather information. You're deciding whether to hand this company forty hours a week of your life. You should want to know things.
Questions that show you're thinking about the role
These signal that you're already imagining yourself doing the work, which is exactly the picture you want in their heads.
- "What does success look like in this role in the first ninety days?" This gets you a concrete picture of expectations and shows you think in outcomes.
- "What's the biggest challenge the person in this role will face?" Honest answers here tell you a lot, and asking it signals you're not afraid of the hard part.
- "How will my work connect to what the wider team or company is trying to do?" Shows you think past your own tasks.
Notice these are open questions. They invite the interviewer to talk, and people remember conversations they enjoyed.
Questions that reveal the real culture
The glossy version of a company is on its careers page. These questions get past it.
- "How does the team handle disagreement about a decision?" The answer tells you whether debate is healthy or political.
- "What's something that's changed here in the last year?" Reveals whether the place is static or moving, and how they talk about change.
- "Why is this role open?" Growth, backfill, or a person who left, each answer means something different about what you'd be walking into.
Ask these in a curious tone, not an interrogating one. You're a peer trying to understand, not an auditor.
Questions to ask the right person
Match the question to who's across the table. Ask your potential manager about expectations and how they lead. Ask a potential teammate what a normal week actually feels like. Ask a senior leader about where the team or product is heading. Asking a junior engineer about five-year company strategy, or asking the CEO about your daily standup format, wastes the access you have.
The best question is one you genuinely want answered. A memorized "impressive" question lands flat; honest curiosity about something specific to that conversation lands every time.
What not to ask (yet)
First interviews aren't the moment for salary, vacation days, or how soon you can work from home. Not because those don't matter, they do, but because leading with them suggests you're more interested in the perks than the work. Save logistics for when there's an offer on the table or HR raises it.
Also skip anything you could have answered with thirty seconds on their website. "What does your company do?" tells them you didn't prepare. Researching the company beforehand is what lets you ask the sharp version of a question instead of the basic one.
Bring more questions than you'll use
Prepare five or six, because two or three will get answered during the interview itself. Crossing a question off because they already covered it is fine, and you can even say so: "I was going to ask about onboarding, but you answered that earlier." That shows you were listening.
Keep them on a notepad or your phone. Glancing at a short list isn't unprofessional; it shows you took the conversation seriously enough to prepare for it. The questions are part of the same preparation that gets your stories and your CV straight before you walk in, and they're often the part people skip.