Questions to Ask the Interviewer

Why the last five minutes matter more than you think

By the time an interviewer says do you have any questions for us, they have already formed most of their view. What the question does is test whether that view survives contact with your curiosity.

Three things are being read at once. Whether you have thought about the job as work rather than as a title. Whether you are evaluating them, which strong candidates always are and weak candidates never do. And whether you listened, because the best question in any interview is one that could only have been asked after the conversation you just had.

That third signal is the one people underestimate. An interviewer can tell within about four seconds whether your question was written last night or thirty seconds ago, and the difference is whether it refers to anything they said. You mentioned the migration slipped twice, what changed the second time, is a better question than anything on any list, including this one.

The failure mode is asking a question you do not care about. Interviewers can tell, because when they answer it you have nothing to say back. A question you cannot follow up on is a performance, and it registers as one.

The questions, by what they are actually for

To find out what the job is really like

• What does a good first ninety days look like in this role.
• What is the thing about this job that surprises people who join.
• Which part of this role has been hardest to hire for, and why.
• Walk me through what happened to the last person in this seat.
• How much of this job is the thing in the description, and how much is everything else.

The last-person question is the most useful and the most avoided. The answer tells you whether the role is a backfill, a growth hire or a rescue, and those are three different jobs with three different definitions of success. It is also one of the few questions where the hesitation before the answer carries as much information as the answer.

Ask the ninety-days question of everyone you speak to, separately. When a hiring manager, a peer and a skip-level describe the same first quarter, the team is aligned. When they describe three different jobs, you have learned something no job description would have told you, and you have learned it before accepting rather than after.

To find out how decisions get made

• Who decides what this team works on next quarter, and how does that get communicated.
• When this team disagrees about priorities, how does it get settled.
• What is something the team pushed back on recently that changed the plan.
• How far ahead is the roadmap actually planned, honestly.

These separate organisations that make decisions from organisations that hold meetings. Listen for whether the answer contains a specific recent example. If it does not, that is information.

The pushback question is the sharpest of the four. Every company says it welcomes challenge, and a company where that is true can name an occasion in the last quarter when somebody junior changed a decision. A company where it is not true produces a general statement about culture and moves on. You are not looking for a perfect answer, you are looking for whether an example exists.

To find out what the manager is like

• How do you like to give feedback, and how often.
• Tell me about somebody on the team who has grown a lot. What did that look like.
• What do you do when somebody on your team is struggling.
• What would make you think, three months in, that hiring me was the right call.

That last one is the single highest-yield question in this entire list. It converts an abstract interview into a concrete contract, and a manager who cannot answer it has not thought about what they need, which is worth knowing before you report to them.

The feedback question matters more than candidates expect, because the answer is usually honest. Managers who give feedback constantly say so without prompting. Managers who do it once a year at review time tend to describe a process rather than a habit, and the difference between those two shows up in your first six months rather than your first six weeks.

To ask HR or a recruiter

Recruiters get a different set, because they know things hiring managers do not and they are usually more candid than people expect.

• What is the interview process from here, and what is the timeline.
• Is the salary band fixed or is there room at the top of it.
• What is the retention like on this team specifically.
• How long has this role been open.
• Is this a new headcount or a replacement.

A role open for five months with a fixed band tells you something a hiring manager will never say out loud, which is usually that the band is below market for what they are asking.

Recruiters are also the right people to ask about the shape of the process. Knowing there are four more rounds, that one is a take-home, and that the final decision sits with somebody you have not met changes how you spend your energy. Candidates routinely go into a fourth interview without knowing it is the last one.

Questions that make an interviewer stop and think

Candidates search for unique interview questions to ask employer because the standard list feels generic, and it is. What makes a question memorable is not novelty but specificity to the conversation you just had.

Still, these travel well:

• What is the company good at that it does not get credit for.
• What would you change about how this team works if you could change one thing.
• Is there anything about my background that gives you pause.
• What is the gap between how this company describes itself and how it actually feels day to day.

The third one is uncomfortable and it is the most valuable question on this page. It hands you the objection while you are still in the room and able to answer it, rather than after you have left and it has become a line in somebody's write-up.

Ask it plainly and then be quiet. The instinct is to soften it, or to start answering the concern before it has been stated, and both waste what the question bought you. Let the silence do its work. Most interviewers will tell you, because you asked directly and because it is easier to say to your face than to write down.

What to ask at the end, when you have two minutes

If time is nearly gone and you get one question, ask the one that produces information you would act on. Almost always that is what would make you think, three months in, that hiring me was the right call.

If you already know the job well, ask for the objection instead. Is there anything about my background that gives you pause. Then answer it, briefly, and stop.

Do not use your last question to signal enthusiasm. Interviewers read enthusiasm-signalling questions as filler, and they cost you the one slot you had to learn something.

There is one exception worth knowing. If the conversation has surfaced a genuine concern, your last question can be the one that addresses it: you mentioned the role needs somebody comfortable with ambiguity, and I want to check what that looks like here specifically. That is not enthusiasm-signalling. It is closing a loop the interviewer opened, and it lands well because it proves you were tracking the conversation rather than waiting for your turn.

What not to ask

Anything you could have found on their website. What does the company do, how many employees, when were you founded. This is the only category that actively damages you, because it demonstrates you did not spend fifteen minutes preparing for something you asked them to spend an hour on.

Money and holiday, in a first interview with the hiring manager. Ask the recruiter, who expects it and can answer properly. Ask the manager and you have spent your one question on something they will have to check.

Multi-part questions. Three questions stacked into one sentence get answered as one, usually the easiest of the three.

The question you have already been answered. If they covered it in the conversation, asking it proves you were rehearsing rather than listening.

Who you are asking changes the question

Most advice treats the interviewer as one person. In a real loop you meet three or four, and asking all of them the same thing wastes the only chance you get to triangulate.

The hiring manager knows what the job is and what they need from it. Ask about the first ninety days, about how they run the team, and about what would make the hire a success. They are the one person who can answer what would make you think, three months in, that hiring me was the right call.

A future peer knows what the job is actually like, and is usually the most honest person in the process because they are not the one making the decision. Ask what surprised them when they joined, what they would warn a friend about, and what the team complains about. Peers answer that last one properly more often than you would expect.

A skip-level or executive knows where the team sits in the company's priorities. Ask what this team needs to get right over the next year, and what would cause it to be reorganised. That second question sounds aggressive and almost never is; senior people think about it constantly and are usually glad somebody asked.

The recruiter knows the process, the band and the history of the role. Use them for anything commercial or procedural, and use them first, because it saves your hiring-manager questions for things only a hiring manager can answer.

The value is in the comparison. Ask two people what the first ninety days look like and you find out whether the team agrees with itself. That is worth more than any single answer.

Where these questions break

Asking a good question is the easy half. The hard half is what you do with the answer, and that is what is actually being assessed.

You ask how disagreements about priorities get settled. The interviewer gives you a slightly evasive answer about collaboration and alignment. Now what.

The weak move is to nod and move to your next question, which reveals that the question was a slot to fill rather than something you wanted to know. The strong move is one follow-up, asked lightly: can you give me an example from the last quarter.

Note how mild that is. You are not challenging them, you are asking for detail, which is what anybody genuinely interested would do. Interviewers almost never take it badly, partly because they spend their whole day doing the same thing to candidates and recognise the move.

That is the whole test. A candidate who follows up is evaluating the company. A candidate who reads the next item off their list is performing curiosity, and by the fourth question everyone in the room can tell which is happening.

The second failure is asking a question whose answer you cannot respond to. If you ask what the biggest technical challenge is and you have no view on the answer, you have created an awkward silence and learned nothing. Ask about things you have an opinion about, because the conversation that follows is worth more than the answer.

Bring five questions, expect to ask two, and let the conversation choose which. The three you do not ask were never wasted, because knowing you have them is what stops you reaching for filler when the room goes quiet.

Write them down and take the paper in. Nobody has ever been marked down for referring to notes, and the alternative is spending the last ten minutes of the interview trying to recall your own questions instead of listening to the answers.

Bringing it back to your own answers

The questions you ask and the answers you give are the same skill pointed in opposite directions. Both reward specificity, both collapse under vagueness, and both are assessed on the follow-up rather than the opening.

If you want to see what that looks like from the other side, the behavioral interview questions are grouped by what each one tests, and the STAR method covers the format underneath them. The same pattern shows up in showing leadership and working under pressure, where the prepared answer holds and the second question is where it is decided.