The worst question I’ve heard a candidate ask at the end of an interview was “So what does a typical day look like for someone in this role?” The interviewer spent four minutes describing a day that had nothing to do with the job being hired for. The candidate nodded politely. Neither of them learned anything useful.
End-of-interview questions are not a politeness ritual. They’re the one part of the interview where you set the agenda. Done right, they signal that you’ve thought about this job seriously. Done badly, they cost you nothing except time you can’t get back.
Here’s a set of questions that actually work, grouped by what you want to find out.
Questions about how the team actually works
Generic culture questions get generic answers. Specific process questions get real ones.
- “How does a feature go from idea to shipped? Walk me through the last one.”
- “When something breaks in production, what happens? Who gets paged, and what does the next 24 hours look like?”
- “Who makes the final call on technical decisions: the engineering lead, the PM, or someone else?”
- “How often do engineers have to work on things they think aren’t worth building?”
That last one is uncomfortable. That’s the point. A team where the answer is “rarely, because we push back and it gets heard” is different from one where the answer is a five-second pause followed by “it happens sometimes.” Both answers tell you something real.
Questions about the specific role
You want to understand what success looks like before you take the job, not three months into it.
- “What does the person in this role need to accomplish in the first 90 days to be considered a good hire?”
- “What’s a real example of a mistake the previous person in this role made, and what happened after?”
- “Is the scope of this role likely to expand, stay the same, or narrow over the next year?”
- “What’s the biggest gap between what the team has now and what you’re hoping to hire for?”
The question about mistakes is one I’d recommend for almost every interview, but ask it carefully. Some interviewers find it direct to the point of being uncomfortable. Most good ones appreciate it. The answer tells you a lot about whether the team has a blameless post-mortem culture or a scapegoating one.
Questions for the hiring manager specifically
If you’re meeting with the person who’ll be your direct manager, the questions shift. You’re not just evaluating the company, you’re evaluating a working relationship.
- “How do you prefer to give feedback: in the moment, in 1:1s, or written?”
- “What’s something you’re still figuring out about managing this team?”
- “What do engineers on your team say they wish you did differently?”
- “How often do people on your team get promoted, and what does that path look like?”
The third question is genuinely risky. Some managers will give you a thoughtful, self-aware answer. Others will get defensive. Either response is useful information. I think it’s worth asking and calibrating on the reaction, even if the answer itself is vague.
Questions for a technical screen with a senior engineer
When you’re talking to a potential peer rather than a manager, the dynamic is different. You can be more technical and more direct about trade-offs.
- “What’s a technical decision the team made in the last year that you’d reverse if you could?”
- “How much of the codebase would you describe as actively maintained vs. inherited and avoided?”
- “What’s the thing that slows down your work the most day-to-day?”
These questions work because most senior engineers want to be honest about the real state of the codebase. They’re not always allowed to be in formal settings. Asking in the last five minutes of a technical screen often gets a more candid answer than you’d expect.
Questions for sales or customer-facing roles
If you’re interviewing for account executive, solutions engineer, or similar roles, the question set needs to reflect the commercial reality:
- “What’s the typical sales cycle, and what part of it has the highest drop-off rate?”
- “What objections do reps hear most often, and how does the team handle them?”
- “How does the company respond when a competitor undercuts on price?”
- “What percentage of reps hit quota last year?” (This one is blunt. Ask it anyway.)
The quota attainment question is the one I’d prioritize for any revenue-generating role. According to LinkedIn Economic Graph research, quota attainment rates vary significantly by industry and company stage. A team where fewer than 40% of reps hit quota tells a very different story than one where 70%+ do.
Questions to avoid
Some questions that sound thoughtful actually signal the wrong things:
- “What’s the company culture like?” Too broad to get a useful answer, and signals you haven’t done your homework.
- “Is there anything that concerns you about my candidacy?” Well-intentioned but puts the interviewer in an awkward spot. Save it for the final round if you’ve built real rapport.
- “When will I hear back?” Fine to ask, but don’t make it the last thing you say. It ends on logistics, not substance.
Also, don’t ask about salary or benefits in a first interview unless the interviewer brings it up. It doesn’t disqualify you, but it shifts the conversation in a direction that rarely helps at that stage.
How many questions to actually ask
Most people ask two. That’s fine. Three is better if the conversation is flowing. Four is too many if you’re working through a list while the interviewer is clearly watching the clock.
Pick two before the interview. Have a third as backup. Use the ones that came up naturally in the conversation if anything was left unresolved. The best ending to an interview isn’t you finishing your list. It’s the interviewer saying “that’s a good question” and meaning it.
If you’re preparing for multiple interviews in parallel, Craqly can help you run practice reverse-interview rounds so you hear how your questions land before the real thing. It’s not magic, but hearing yourself ask the questions out loud catches more awkward phrasing than reading them silently ever does.
The single most useful question across almost every interview type is some version of: “What do people who succeed in this role have in common?” It’s direct, it’s answerable, and the response almost always tells you something the job description didn’t.