Every article about questions to ask in an interview gives you a list. Some give you 10 questions. Some give you 38. Almost none explain why you're asking — what you're actually trying to find out, and what a good answer looks like versus a bad one.
That gap is where candidates go wrong. They pick three questions from a list they found online, ask them at the end of the interview, nod politely at the answers, and leave without the information they needed to decide whether to take the job.
This guide works differently. Every question here comes with the reasoning behind it — what to listen for, and what should make you pause.
What this part of the interview is actually for
"Do you have any questions for us?" isn't a formality. It's doing two things at once.
For the interviewer, it's a signal. Candidates who ask nothing, or ask obvious questions, read as unprepared or uninterested. Candidates who ask sharp, specific questions signal that they've thought seriously about the role — which is itself evidence that they'll think seriously on the job.
For you, it's your only structured opportunity to interview them. You've spent 45 minutes selling yourself. You now have 10 minutes to find out if this is actually somewhere you want to work. Most candidates waste it.
Prepare more questions than you'll need — six to eight. Some will get answered naturally during the conversation. Pick the ones that are still live at the end, and lead with the most important.
Questions about the role itself
These are the most worth asking, and the ones most candidates skip in favor of safer, more generic options.
"What does success look like in this role after the first six months — and how would you measure it?"
This forces the interviewer to be concrete about expectations, and it tells you whether the company has thought clearly about what the role is supposed to accomplish. Vague or inconsistent answers are a genuine red flag.
Listen for specific outcomes, not just activities. "Building relationships with stakeholders" is an activity. "Closing three enterprise accounts in the first two quarters" is an outcome.
"What's the hardest part of this role that probably isn't in the job description?"
Job descriptions are marketing documents. They describe what the role is supposed to be, not what it's like in practice.
A good interviewer will tell you something real — high pace, ambiguous ownership, a legacy system that's painful to work with. An interviewer who tells you the hardest part is "we work hard and expect a lot" is either not self-aware or not being straight with you.
"What happened to the last person in this role?"
You're allowed to ask this. The answer matters. Did they get promoted? Leave for a competitor? Were they let go? Each answer tells you something different about what the role actually offers and what the company is like to work for.
Evasiveness — pivoting to "we're growing the team" when you asked something specific — is worth noting.
Questions about the team and manager
Your direct manager is the single biggest factor in your day-to-day experience. This is where it pays to ask specific questions, even if they feel slightly uncomfortable.
"How would you describe your management style — and how does it adapt for different people on the team?"
A manager who has thought carefully about this will give you a nuanced answer. A manager who hasn't will give you a phrase: "I'm very hands-off" or "I like open communication." Follow up either way.
What matters is whether the answer matches what you need. If you do your best work with regular structured feedback and they say they're very hands-off, that's useful information before you accept an offer, not after.
"What do your most successful team members have in common?"
Every team has unofficial norms — the traits that get someone recognized, promoted, or given the best projects. This question surfaces them.
If every successful person they describe is someone who "takes a lot of initiative and doesn't need much direction," and you thrive in structured environments, that's worth weighing.
"How does the team handle disagreement — about approach, priorities, technical direction?"
Conflict is inevitable in any serious team. What matters is whether it gets worked out directly or just festers. This tells you whether there's psychological safety to push back, or whether disagreements get suppressed and show up sideways later.
Good teams can point to a real moment when someone pushed back and it led somewhere productive. Teams with a problem tend to give abstract answers about "healthy debate" without being able to say what that actually looks like.
Questions about the company
"What's the biggest challenge the company is navigating right now?"
Every honest company has at least one real challenge. A company that claims otherwise is either not self-aware or not being candid with candidates.
Listen for honesty and specificity. If the challenge they describe sounds like something the role you're interviewing for is well-positioned to help with, that's worth mentioning.
"How has the company's strategy changed in the past year, and what's driving it?"
Especially relevant at startups, but worth asking anywhere. Strategy shifts happen. Understanding what prompted the last one — and whether it was reactive or deliberate — tells you something about how leadership thinks.
Leadership that can explain clearly why the strategy evolved, what they learned, and where they're headed is worth working for. A muddled answer here often means a muddled strategy.
The question most candidates don't think to ask
"Is there anything from our conversation today that you'd like me to address or clarify?"
This one almost never gets used, which is exactly why it's worth asking.
Interviewers form impressions during the conversation that they rarely share. They may have a concern about a gap in your experience, an answer that didn't land the way you intended, or a question they forgot to follow up on. This surfaces it before you leave the room.
At worst, they say no and you've shown you're comfortable with direct feedback. At best, they surface a hesitation and you get to respond to it. Every other candidate walks out leaving that hesitation unaddressed.
Questions to skip
A few categories worth avoiding, at least until an offer exists:
Salary, benefits, and vacation. These are reasonable things to care about, but raising them before you have an offer weakens your position and signals you're thinking about what the company gives you rather than what you can contribute.
Anything on the company's public website. Asking about their founding year, product line, or stated values signals you didn't do basic research.
"What does your company do?" In any form. Never.
Leading questions that just want validation. "I read that you have a really strong culture — can you tell me more about that?" isn't a question. It's fishing for reassurance. Ask something that could actually surface a problem.
How many to ask
Three to four is the right number in most interviews. Fewer than two reads as disengaged. More than five starts to feel like you're running your own second interview.
Prioritize questions you don't already know the answers to. If the team dynamic got covered thoroughly during the conversation, skip those and go deeper on role expectations or company direction.
If you want to practice asking these questions out loud — and get comfortable with the follow-ups and silences that come with them — kalbeki can help you do exactly that.