Questions to Ask the Interviewer (And What Their Answers Tell You)

"Do you have any questions for us?"

It arrives at the end, when you're tired and relieved and want to be agreeable, and it is the only question in the entire interview that can undo everything that came before it. "No, I think you've covered everything" is a polite way of saying I have not thought about this job beyond wanting it.

It's also the only stretch of the interview you control. For thirty-odd minutes they've been steering; now the floor is yours, and what you choose to point it at says more about you than most of your prepared answers did.

Two things are happening at once, and most candidates only notice the first:

1. They're still evaluating you. Your questions reveal what you think matters about the work.
2. You're supposed to be evaluating them. This is the part people forget, and it's why the second half of this post is about reading the answers rather than asking the questions.

(For the questions coming the other direction, we covered the twelve you'll almost certainly get asked and the opener specifically.)

How many, and when

Bring five, ask three. You'll lose one or two to being answered naturally during the conversation, and having spares is what stops you freezing when that happens.

Ask them at the end, unless a natural opening appears earlier — if it does, take it. A question asked in context lands better than the same question read off a list twenty minutes later.

And ask at every stage. Recruiter screen, hiring manager, panel, final round: different people can answer different things, and asking the recruiter about technical architecture wastes both of you.

The questions, by what you're actually trying to learn

About the role itself

• "What does the first ninety days look like for this person?" The strongest general-purpose question there is. A crisp answer means they've thought about the role; a vague one means you'd be defining it yourself, which is either an opportunity or a mess.
• "What separates someone who's great in this seat from someone who's fine?" Forces specifics about their actual bar rather than the job description's wish list.
• "Is this a new role or a backfill?" New roles come with ambiguity and room. Backfills come with a predecessor's reputation, good or bad. Both are workable; not knowing which you're in is not.
• "What's the part of this job people underestimate?" Usually gets you the honest, unglamorous truth — the reporting burden, the stakeholder wrangling, the on-call.

About the team

• "How does the team make decisions when people disagree?" The single most revealing team question. Every team has conflict; healthy ones have a mechanism.
• "Who would I work with most closely, and what do they need from this role?" Shows you're thinking about the job as a set of relationships rather than a title.
• "How long have most people on the team been here?" Tenure tells you a lot, and it's a fair, neutral thing to ask.

About the manager

If you're talking to your prospective manager, this is the most valuable use of your questions. You're choosing a manager at least as much as a company.

• "How do you like to give feedback?" Their answer tells you whether feedback exists as a practice or an annual event.
• "What's something your team does differently because of you?" Gets past management platitudes into actual behavior.
• "How do you prefer to be kept up to date — and how much detail do you want?" Practical, and signals you intend to manage upward properly.

About success and failure

• "How will you know in six months that hiring me went well?" Makes them state the actual success criteria out loud, which is useful to you and slightly clarifying for them.
• "What's the biggest thing standing in the way of the team hitting its goals right now?" Invites honesty about the mess. The willingness to answer is as informative as the answer.

About the company

Only ask what you genuinely can't find out yourself. Asking something googleable is worse than asking nothing.

• "What's changed most about working here in the last year?" Better than "what's the culture like," which produces a brochure answer every time.
• "What's a decision the company made recently that you disagreed with?" A bold one — read the room. But the answer is enormously revealing, and the willingness to answer even more so.

About the process

Always ask one of these. It's practical, and it prevents the awkward follow-up email later.

• "What are the next steps, and what's your timeline?"
• "Is there anything about my background that gives you hesitation?" Slightly brave, and it hands you the one chance you'll get to address an objection before it becomes a rejection you never hear about.

“The best question to ask at the end of an interview: 'Is there anything about my background that gives you hesitation?' It's the only chance you'll get to answer an objection before it quietly becomes a rejection.”

Share on X→

What to leave out

Anything googleable. "What does your company do?" ends interviews. So does anything answered on their About page or in the job description you supposedly read.

Compensation, in the first conversation. Not because it's rude — because it's not the moment. If they raise it, engage honestly with a researched range. If they don't, it belongs to the recruiter conversation or the offer stage.

Time off, hours, and remote policy — as your only questions. They're legitimate and you should absolutely know the answers before signing. But if they're the only things you ask, you've told them your first interest in the job is leaving it. Ask one, alongside questions about the work.

"How am I doing so far?" Puts them on the spot, mid-process, with a question they can't answer usefully. The hesitation question above gets you the same information without the awkwardness.

A list of ten. Reading through a phone-notes list turns the conversation into a deposition. Three good ones, delivered like a person talking, beats ten recited.

Reading the answers

This is the half nobody prepares for, and it's the half that decides whether you should take the job.

Vagueness on the first ninety days usually means the role is under-defined. That's fine if you're senior and want to shape it, and rough if you're junior and needed direction.

"We're like a family" is worth a follow-up rather than a warm feeling. Ask what happens when someone underperforms. Family language is sometimes genuine closeness and sometimes cover for blurry boundaries and unpaid overtime.

No mechanism for disagreement — "oh, we all get along" — usually means conflict happens somewhere less visible than a meeting.

Nobody on the team has been there long deserves a gentle "what's driven the turnover?" A good answer exists (rapid growth, a reorg, an acquisition). A defensive one is data.

Hesitation on "what's in the way of the team's goals" is not automatically bad; some people are just careful. But an answer that admits a real constraint is a strong sign you're talking to somewhere honest.

They can't say what great looks like versus fine. Then performance review season is going to be a surprise, every time.

The five to walk in with

If you want a default set that works for almost any role, take these and swap one for something specific to the company:

1. What does the first ninety days look like for this person?
2. What separates someone who's great in this seat from someone who's fine?
3. How does the team handle disagreement about the work?
4. What's the biggest thing in the way of the team's goals right now?
5. Is there anything about my background that gives you hesitation?

Then add the live one — the thing they said twenty minutes ago that you actually want to know more about. That's the one they'll remember.

Before any of this matters

All of the above assumes you're in the room. The resume is what gets you there, and it's also what generates the questions you'll be asked once you arrive — the gap, the short stint, the bullet that invites "walk me through this."

The free roast grades your resume in about 30 seconds and, on the results page, generates the two questions a recruiter is most likely to ask you based on what's actually on it. If you want the full prep, interview prep explains how the personalized questions work and what the Career Bundle adds.

Prepare their questions, prepare yours, and treat the last five minutes as the part of the interview you get to run.