There’s a moment near the end of most interviews where the hiring manager says “do you have any questions for me?” and the candidate either asks something reasonable or says “I think you’ve covered everything.” The second answer lands worse than most people think. A lot worse, actually.
I’ve talked to a few hiring managers over the past year and a surprising number of them report that candidates asking nothing, or asking something easily Googleable, is a yellow flag. Not an automatic no, but a signal. One engineering manager at a Series B company told me he’s passed on otherwise solid candidates who couldn’t articulate a single genuine curiosity about the team.
The reason this matters isn’t politeness. It’s that questions reveal how you think. A candidate who asks “what does success look like in this role at 90 days?” is demonstrating that they’re already thinking about execution, not just landing the offer.
Questions that reveal what you actually need to know
Most “questions to ask” lists trot out the same handful. “What does a typical day look like?” “What are the growth opportunities?” These are fine, but they’re generic enough that they don’t reveal much about you and they don’t get you particularly useful information.
Better questions are specific to the role and uncomfortable-ish to answer. For example:
“What’s the biggest gap on the team right now that this hire is meant to fill?” Forces the interviewer to describe the actual problem, not the job description.
“Can you tell me about someone who was in this role and didn’t work out, and what happened?” This one makes interviewers pause. That pause is informative. It also gets you real data about failure modes before you start.
“How does the team handle disagreements about direction?” The answer to this tells you more about culture than any values slide. Some teams debate openly, some escalate everything to the manager, some let things fester. You want to know which you’re walking into.
“What have you found most surprising about working here compared to what you expected when you joined?” A good manager gives you a real answer here, including things that weren’t ideal. If the answer is entirely rosy, either the interviewer is being careful or the culture doesn’t tolerate honest reflection.
Questions about the team specifically
The job might be great on paper and the team might be hard to work with. Those are two separate questions.
“How long has most of the team been here, and has there been much turnover in the last year?” Turnover at the team level is more informative than company-level attrition rates. High churn on a specific team usually traces back to a specific problem.
“How do decisions typically get made about priorities?” In some orgs this means engineering leadership calls the shots. In others, sales owns the roadmap. In others, it’s genuinely collaborative. None of those is wrong in isolation, but each one has implications for how much autonomy you’ll have.
The Bureau of Labor Statistics Occupational Outlook Handbook shows median job tenure across most professional categories hovering around four years. That means the person interviewing you has probably switched roles a few times themselves and is likely to have honest observations about what makes a team work if you ask the right way.
What to avoid asking
A few categories of questions reliably backfire.
Asking about salary and benefits in an early-stage interview before you’ve established fit reads as premature. Not because it’s wrong to care about compensation (you should), but because it signals to some interviewers that you’re evaluating the offer before understanding the role. Save that for the offer stage or a dedicated recruiter screen.
Questions with obvious answers from the company website. “What does your company do?” or “How large is the team?” signals that you didn’t prepare. The information was available; asking it wastes time.
Questions that are really thinly disguised complaints about your current job. “Do people here actually respect each other’s time?” probably has a backstory the interviewer doesn’t need to hear.
The preparation question nobody talks about
Going in with 5-7 prepared questions is better than 2, because you’ll often get several answered organically during the interview itself. If you only prepared 2 and both come up before the Q&A portion, you end up improvising under pressure, which is exactly when you’re likely to ask something generic or awkward.
Writing your questions down and having them visible is completely acceptable. Most interviewers see it as preparation, not a crutch. I’d actually argue it signals more intentionality than someone trying to recall their list from memory mid-conversation.
Some candidates use an AI interview tool like Craqly during live practice sessions to help surface gaps in their prep, including which questions they haven’t thought through yet for a specific role. That’s one approach. Whatever method you use, the goal is the same: walk into the room with questions that reflect what you genuinely need to know to decide if this job is worth taking.
The interview goes both ways
The framing that serves candidates best is this: the interview is a mutual evaluation. The company is deciding if you’re right for the role. You are deciding if the role is right for you.
That framing shifts how questions feel. You’re not trying to impress the hiring manager with clever questions. You’re gathering data you need to make a good decision. Some of the best interviews I’ve heard about ended with the candidate deciding not to pursue the role based on what they learned in the Q&A. That’s the system working correctly.
If you go in trying to land the offer at all costs and ask questions designed to sound good rather than get answers, you might succeed. And then you might spend six months at a job that was never the right fit, which is a much worse outcome than asking the uncomfortable question up front.