35 questions to ask in an interview (that you actually want answered)

An interview is the only stage of hiring where you can interrogate the company as directly as it interrogates you — and most candidates waste it. The right questions to ask in an interview do two jobs at once: they extract information you genuinely need before accepting an offer, and they demonstrate that you think like someone already doing the work. This guide organizes 35 questions by who you're talking to — recruiter, hiring manager, future peers — because the same question that's perfect for one audience falls flat with another. As with everything in interviewing, calibrate to context: a five-person startup and a structured corporate panel leave different amounts of room for questions, and later rounds tolerate more directness than first screens.

Why "no questions" ends interviews badly

When the interviewer asks "what questions do you have for me?" and hears "I think you've covered everything," here's what they register: low preparation, low interest, or low curiosity — none of which they can distinguish from the others. Fair or not, the questions you ask are treated as a proxy for how you'd operate in the job: what you probe is what you care about.

The practical rule: bring five to seven prepared questions, expect two or three to get answered during conversation, and ask three or four at the end. Write them in a notebook and bring it — visibly consulting prepared questions reads as organized, not scripted. (Building this list is a 15-minute step in our 48-hour interview prep checklist.)

Questions for the recruiter screen: process, timeline, range

Recruiters own logistics and process. Ask them mechanical questions — they'll answer freely, and it saves your substantive questions for people who can answer them.

1. "What does the full interview process look like, and what's the rough timeline?"
2. "Is this a new role or a backfill?" — a genuinely load-bearing question. New role means growth but possibly undefined expectations; backfill means asking the follow-up: "What's the person who held it doing now?"
3. "What's the salary range for this position?" — where postings don't already say (many jurisdictions now require ranges in postings, though coverage varies), the recruiter screen is the normal place to align on money early. Our salary expectations guide covers exact phrasing.
4. "How long has the role been open?" — months of vacancy hints at either a very picky manager or an unattractive role; either is worth knowing.
5. "What can you tell me about the hiring manager and team?"
6. "When should I expect to hear about next steps?" — anchors your follow-up timing later.

Questions for the hiring manager: success metrics and team reality

This is the person whose expectations define your daily life. Prioritize these.

7. "What would this person need to accomplish in the first 90 days for you to consider the hire a success?" — the single highest-value question in interviewing. It surfaces real expectations, reveals whether they've thought them through, and gives you material to close on.
8. "What separates someone who's good in this role from someone who's exceptional?"
9. "What's the hardest part of this job that isn't in the posting?"
10. "How does the team get work — who sets priorities, and how often do they change?"
11. "What's the team's biggest challenge right now?"
12. "How do you prefer to work with your directs — cadence, communication style, autonomy?"
13. "Where have people in this role gone next, internally or externally?"
14. "What made you decide to work here — and what's kept you?"

A dialogue snippet showing why #7 earns its keep:

You: "What would the first 90 days need to look like for this to be a clear win?" Manager: "Honestly? The reporting backlog. If someone cleared that and rebuilt the monthly dashboard, the team would throw a parade." You: "That's useful — at my current job I inherited a similar backlog. Can I tell you how I approached it?"

You've just converted their answer into a targeted pitch. No generic question does that.

Questions for peers and skip-levels: culture without the brochure

Future teammates will tell you things managers won't — if you ask concretely. Vague questions ("what's the culture like?") get brochure answers; specific ones get truth.

15. "Walk me through what your last normal week looked like."
16. "When was the last time you worked a weekend, and why?"
17. "What's something the team has changed in the last year based on feedback?"
18. "Who's the longest-tenured person on the team, and what keeps them?"
19. "What do new people usually find hardest in their first month?"
20. "How do decisions actually get made day to day — consensus, manager call, whoever's loudest?"
21. "What would you change about working here if you could?"

For skip-levels and executives, zoom out:

22. "How does this team's work show up in what the company reports as success?"
23. "What's the biggest bet the company is making this year?"
24. "How has the company changed since you joined?"

Red-flag detector questions — phrased diplomatically

Each of these has a blunt version you're thinking and a diplomatic version you should say:

25. Thinking: "Is there turnover trouble?" Say: "How long do people typically stay on this team?"
26. Thinking: "Will I be doing three jobs?" Say: "How is the workload distributed across the team right now?"
27. Thinking: "Is the company in financial trouble?" Say: "How is the team's headcount planned to change over the next year?"
28. Thinking: "Is management chaotic?" Say: "How have priorities shifted over the past six months, and how were those changes communicated?"
29. Thinking: "Why did the last person really leave?" Say: "What's the story of this role — how has it evolved and who has held it?"
30. Thinking: "Are performance expectations unreasonable?" Say: "How is success measured, and how often is it reviewed?"

Questions to never ask (yet) and when they become fair game

Timing, not topic, is what makes these risky:

31. Vacation, benefits, perks — premature in round one; entirely fair once an offer is near. Asking about time off before demonstrating value inverts the sales order.
32. "What does this company do?" — never fair game. That's research you owed the interview.
33. Remote-work flexibility — fine to confirm what the posting says at the recruiter stage; negotiating specifics belongs at offer stage.
34. Promotion timelines for yourself — "How do people grow here?" works in any round; "When would I be promoted?" doesn't work in round one.
35. Anything answered on page one of their website — signals your research effort, in the wrong direction.

The general rule: information you need to evaluate the job is fair early; anything that assumes you've won the job waits until the offer conversation, where you'll have maximum leverage anyway.

Reading the answers: evasions that tell you everything

Asking is half the skill; hearing is the other half.

• The deflected turnover question. You ask how long people stay; they answer with how fast the company is growing. Growth is the polite explanation for constant vacancies — sometimes true, sometimes cover.
• The 90-day question that stumps them. A manager who can't describe success for the role hasn't defined it, which means you'd be inheriting ambiguity with a performance review attached.
• Uniform hesitation on "what would you change?" One diplomatic pause is normal; three interviewers who all go careful at the same question have all learned the same caution, and that's data.
• The hero schedule worn proudly. If "we all pitch in on weekends" is delivered as a selling point, believe them the first time.
• Vagueness about the last person in the role. People remember their departed colleagues. Fog here usually means the story is unflattering to someone still in the building.

None of these is disqualifying alone — interviewers get tired, companies have bad quarters — but patterns across multiple interviewers are the closest thing to truth you'll get before signing. Keep notes after each round; they'll also sharpen your answers to the standard questions in later rounds, since you can reference what earlier interviewers told you.

Frequently asked questions

How many questions should I actually ask?

Three or four at the end of a typical interview, drawn from a prepared list of five to seven (some get answered en route). If time runs short, ask your single best question and say you have others for a future conversation — that lands better than rushing through a list.

What if all my questions were genuinely answered during the interview?

Name that, specifically: "You've actually answered my main three — especially the 90-day expectations. The one I'd still love your take on is..." Referencing what was covered proves you were listening, and one fresh question is always findable: their personal "what's kept you here?" works in every situation.

Should I ask the same questions to every interviewer?

Asking one identical question across interviewers is a legitimate technique — comparing answers to "what's the team's biggest challenge?" reveals alignment or its absence. But vary the rest; panels compare notes, and five people reporting the same script dilutes each conversation.

Is it okay to ask about the interviewer's own experience?

Yes — "what's kept you here?" and "what did you find hardest when you joined?" are among the best-received questions in interviewing. People enjoy being asked about themselves, and their candor calibrates you on the culture. Just pair personal questions with substantive role questions so the conversation keeps weight.

Interrogate your own application first

The sharpest questions come from candidates who studied the role deeply — and that same study should shape your resume before the interview ever happens. Run yours through Workplacea's free resume checker to see whether it answers the questions employers are silently asking, then tailor it per posting in the editor.