What questions should I ask the interviewer?

Prepare a handful across a few categories and ask two or three that fit the conversation. Strong areas: the role itself ('what does success look like in the first six months?'), the team and how it works ('how does the team make decisions?'), the real challenges ('what's the hardest problem the team is facing right now?'), and the interviewer's own view ('what do you enjoy most about working here?'). The best questions show you've thought about the work and let the answer reveal whether the job is right for you too.

Is it bad to have no questions for the interviewer?

Yes. 'No, I think you've covered everything' is one of the weakest ways to end an interview, because it reads as low interest, even when you're genuinely just satisfied. The closing question is still part of the evaluation, and having thoughtful questions signals engagement and that you're assessing the role seriously, not just hoping to be picked. Always go in with at least three prepared, and keep one in reserve in case the others get answered during the conversation.

What questions should I avoid asking?

Avoid anything you could have answered with a quick search (basic facts about the product or company), and avoid leading with salary, benefits, time off, or remote policy in early rounds, which can read as more interested in the perks than the work. Save the logistics for the recruiter or the offer stage. Also skip questions that are really about whether you'll have to work hard. The questions to ask are the ones that show you're thinking about doing the job well.

How many questions should I ask?

Two or three is usually right for the time you're given, so prepare more than that (four to six) and pick the ones that fit, since some will get answered earlier in the interview. Quality matters more than quantity: a couple of sharp, specific questions land better than a long list of generic ones. Read the room on time, and it's fine to say you have a few but are happy to follow up by email if they're short on time.

Interview prep · the questions you ask

Questions to ask the interviewer

“Do you have any questions for me?” sounds like the interview winding down. It isn't. You're still being evaluated, and what you ask says as much about you as your answers did. Good questions signal genuine interest and good judgment, and they double as your chance to work out whether you actually want the job. Here are the ones worth asking, and the ones to skip.

The short version

It's still part of the evaluation. Always go in with at least three prepared questions.
Ask about the role, the team, the real challenges, and the interviewer's own view.
Skip anything you could Google, and save salary and perks for later rounds.

Why this is still being evaluated

The closing question is a soft test of how interested and how thoughtful you are. Candidates who say “no, you've covered it” look disengaged next to ones who ask something sharp, even when both want the job equally. Your questions also reveal how you think: what you choose to ask shows your priorities and whether you understand the work. And it genuinely is your interview of them, your chance to find out if the role, team, and manager are what you want.

The categories worth asking about

The role and success, “What does success look like in the first six months?” or “What would make someone great in this role versus just good?”
The team and how it works, “How does the team make decisions?” or “How do you handle disagreement on technical direction?”
The real challenges, “What's the hardest problem the team is facing right now?” or “What's slowing the team down today?”
The interviewer's own view, “What do you enjoy most about working here?” or “What's surprised you since you joined?”

Prepare four to six across these, and ask the two or three that fit, since some get answered as you go. The strongest questions are specific to this team and this conversation, not a list you'd ask anyone.

The questions to avoid

Skip anything a quick search would answer, because it signals you didn't prepare. Hold back on salary, benefits, time off, and remote policy in the early rounds, those belong with the recruiter or at the offer stage, and leading with them reads as more interested in the package than the work. And avoid questions that are really asking “how hard will I have to work?” The aim is to sound like someone thinking about doing the job well.

Tailor them from your research

The best questions come from having done your homework, so they're built on the same company research that powers your “why this company” answer. If you noticed they recently shipped something, reorganised, or wrote about a hard problem, ask about it. A question that shows you've actually looked is worth ten generic ones.

The fast way: a company snapshot to mine for questions

Calibrd's company snapshot gives you concrete material to ask about. Paste a real job description and it summarises what the company does, how it works, and recent signals, so you can turn those into specific, informed questions instead of generic ones. The same scan predicts the questions you'll be asked and lets you practise the whole round.

So what do you actually do

Prepare four to six questions across role, team, challenges, and the interviewer's view.
Tailor at least one to something specific you found in your research.
Ask the two or three that still fit, and never end with “no questions.”
Save salary and perks for the recruiter or the offer stage.

End the interview strong

Get a company snapshot to ask from

Paste a real job description and Calibrd builds a company snapshot you can turn into sharp, specific questions, then predicts the questions you'll be asked and lets you practise the round. Free to install.

Add to Chrome Or scan one JD →

Free to install · Preview every posting · Paid plans from $3.99