PricingHelpSign in

Questions to ask the interviewer (three, not thirty)

Three questions that get concrete answers, matched to whoever is in the room, and the four that quietly cost you something. Never say “no, I think you covered it”.

Last reviewed

Ask three. Make at least one of them about the actual work — what the person in this role did last month — and at least one about how success is judged. Never say “no, I think you covered everything”.

This is not a courtesy round. It is the part of the interview where the interviewer finds out whether you were evaluating them back, and candidates who ask nothing consistently read as candidates who would take any job.

Three that work almost anywhere

  1. “What did the person in this role spend last month doing?” Forces a concrete answer. Job descriptions are aspirational; the previous month is not. You will learn more from this than from anything on the posting.
  2. “What would a good first six months look like?” Tells you whether there is a plan, and what they will actually judge you on. A vague answer here is a real signal.
  3. “What’s the hardest part of this job that isn’t obvious from the outside?” Good interviewers enjoy this one. It also surfaces the thing you would otherwise discover in week three.

Match the question to who is in the room

  • Recruiter: process, timeline, who you meet next, how many stages. Do not ask them about the technical work — they usually cannot answer, and it wastes your slot.
  • Hiring manager: priorities, how the team is measured, what the last hire found hard, how decisions get made.
  • A peer on the team: the honest ones. What annoys them, what they would change, what surprised them when they joined.
  • A skip-level or executive: where this team fits in what the company is trying to do next year.

Questions that cost you something

  • “What does the company do?” Anything answered by the homepage reads as not having looked.
  • Leave, hours and holidays — at first round. Legitimate questions, wrong stage. Ask the recruiter once an offer is in motion, where they are ordinary rather than telling.
  • A question you obviously memorised from a list. “What is the culture like?” gets the same answer at every company on earth and therefore transmits nothing.
  • Five questions when they have run over. Read the clock. Ask one, offer the rest by email.

Ask about the thing you actually care about

If you are leaving your current job because of on-call, ask about on-call. If you were laid off and cannot afford another surprise, ask about the team’s funding and headcount plans — plainly. It is a fair question and the answer, including a bad answer, is worth more to you than a polished one.

The reason list-of-thirty pages are useless is that they are written to make you sound engaged. Three real questions do that as a side effect.

Write them down

On paper, visible, and glance at it. Nobody has ever been marked down for having prepared. Every second candidate has forgotten every question they had by the time the hour is up, which is where “no, all good” comes from — not from disinterest.

Where this site fits

Not at all — this one is free of any product angle. If you are earlier in the process than this, the silence post is about getting into the room, and the follow-up note is about what happens after you leave it.

Read next

  • Answering the salary expectations question

    Deflect once, then give a researched range floored at what you want. Includes the expected-CTC box on an Indian application form, which is a different problem with no conversation in it.

  • The thank-you email after an interview

    Within 24 hours, under eight lines, one piece of new evidence. A version you can send, the rules that keep it from reading as a template, and when to stop following up.

  • Laid off: what to do in the first two weeks

    Paperwork, runway and ten messages come before the resume. The week-one checklist including PF, gratuity and full-and-final, and the two things people get wrong immediately.