Questions to Ask the Interviewer, and How to Read the Answer

Almost every guide to this topic gives you the same thing: twenty questions, arranged in a list, with no instruction about what to do once someone answers them. That is the wrong half of the problem. The questions are easy. Reading the answers is where the value is, and it is the part nobody teaches.

This article answers one question: what should I ask, and what do I do with what I hear? If you want a full preparation routine for the interview as a whole, that is in the interview preparation guide. If you want the questions they will ask you, those are in common interview questions. This one is about the twenty minutes that run in the other direction, and it treats them as an information-gathering exercise rather than a politeness ritual.

Your questions are still being scored

There is a comfortable myth that the interview ends when they stop asking. It does not. Interviewers form a large part of their opinion in the final stretch, partly because it is recent and partly because your questions reveal something your prepared answers cannot: what you actually pay attention to.

A candidate who asks how success is measured at six months is thinking about delivery. A candidate who asks only about holiday allowance is thinking about the package. Neither is wrong as a human being, but they produce very different notes in the debrief.

So your questions are doing two jobs at once. They gather information you need in order to decide whether to take the job. And they signal the level at which you think about work. The good news is that a question which genuinely helps you decide is almost always a question that signals well. You do not need to perform curiosity. You need to actually have some.

The test every question should pass

Before you write a question on your list, ask yourself: if they answer this honestly, would the answer change anything for me?

If the answer is no, the question is decoration. "What is the company culture like?" fails this test badly. Nobody has ever answered it with "quite toxic, actually", and even a sincere answer arrives as adjectives you cannot verify. "Do you have opportunities for growth?" fails for the same reason.

The fix is almost always to replace the abstraction with an event. Instead of asking what the culture is like, ask about the last time something went wrong and what happened afterwards. Instead of asking about growth, ask where the two people who were in this role before are now. Culture is a pattern of events, so ask about events and infer the pattern yourself.

That one move, abstraction to event, upgrades roughly eighty percent of the questions people bring to interviews.

Who to ask what

The single biggest error is asking every interviewer the same three questions. Different people in the process have different information, and asking someone about something they cannot see produces a polite non-answer that tells you nothing.

The recruiter or HR screen. They know the process, the timeline, the salary band, the reason the role is open, and how many people are in the pipeline. They usually do not know the day to day work. Ask them about mechanics: how many stages, who you will meet, when they want someone to start, whether the band is fixed. This is also the correct place for compensation, which we come back to below.

The hiring manager. They know the work, the priorities, the team, and what will make them think they hired well. This is where your strongest questions go: what success looks like, how work gets decided, what the hardest part of the job is, what happened to your predecessor. This person is also your future boss, so you are evaluating them as much as the job.

Peers and team members. They will tell you the truth, more than anyone else in the process, because they are not accountable for selling the role. Ask them what surprised them when they joined, what they would change, what a bad week looks like. They also know whether the manager described in the previous interview resembles the manager who exists.

Senior leadership or the final round. They know why this team is funded, what it is expected to produce, and whether it is growing or being held flat. Ask about direction: what would make the leader consider this team a success in a year, what is likely to change, where the pressure is coming from.

HR again at offer stage. Process, package, and anything you did not want to ask while you were still being evaluated.

The questions worth asking, and what each one produces

Here is the part that lists usually skip. For each question: what it is really for, and how to read what comes back.

"What would a good first six months look like?" Produces: whether the role has a defined outcome or is a vague set of duties. Read it like this. A good answer names two or three specific things and roughly when. A worrying answer describes activity rather than results, "getting up to speed, building relationships, understanding the systems", with no destination. Vagueness here often means the role was created because the team is busy, not because anyone decided what it should produce, which is exactly the situation where nobody can tell whether you are doing well.

"Why is the role open?" Produces: growth, backfill, or churn. Growth means budget and momentum. A backfill is fine and normal. What you are listening for is discomfort. If the answer is short and moves quickly to another subject, follow it gently: "and where did they go?" A team that has churned through three people in this seat in two years is telling you something about the seat, not about the three people.

"How does work get decided and prioritised here?" Produces: the actual operating model, which matters more to your daily happiness than almost anything else on the job description. Listen for whether there is a mechanism at all. "It comes from the roadmap, which we set quarterly with the commercial team" is a mechanism. "It depends, things come in from a few directions" means you will spend a lot of your time negotiating instead of working.

"What is the hardest part of this job for the person doing it?" Produces: the real friction. Most interviewers answer this one honestly, because it feels like a fair question and they want to be fair. It is the single best question for finding out what you would be signing up for. If the answer is "nothing really, it is a great team", either they have not thought about it or they are selling, and both are worth noting.

"How will you know in a year that you hired the right person?" Produces: the evaluation criteria, in the words of the person who will apply them. This is the question to ask when the first-six-months answer was vague, because it forces the same information through a different door.

"What has changed in the team in the last year?" Produces: stability, reorganisations, direction changes. Also produces, incidentally, an honest description of the manager's own experience of the last year, which is often revealing.

"Who will I work with most outside this team?" Produces: the political shape of the job. Every role has a relationship that is difficult. Finding out which one it is before you accept is worth a great deal. A follow-up that works well: "and how is that relationship at the moment?"

"What is the thing people underestimate about working here?" Produces: an answer that is hard to rehearse, which is the point. Ask it of peers rather than the hiring manager.

"Can you tell me about a time something went badly on the team, and what happened afterwards?" Produces: the culture, in event form. Blame, quiet burial, or a change to how the work is done. This is the question I would keep if I could only keep one.

"What are you hoping to see from the person in this role that you have not been able to do yourselves?" Produces: the gap you are actually being hired to fill, which is not always what the job advert says.

Reading the answers

Collecting answers is the easy half. Here is what to do with them.

Compare across interviewers. Ask two or three people the same question, deliberately. "What would success look like at six months" answered three consistent ways means the team has a shared plan. Answered three different ways means it does not, and you will be arriving in the middle of an unresolved argument about your own job.

Notice the shape of the answer, not just the content. A specific answer that includes a date, a name or a number is worth more than a fluent answer made of adjectives. Fluency is not evidence. Detail is.

Watch what happens to follow-ups. Anyone can produce one good answer. Ask one layer deeper, "what made that hard?", and you will learn whether the first answer was lived or prepared.

Treat hesitation as information, not as a scandal. A hiring manager who pauses and says "honestly, the reporting line is a bit unresolved right now" has just done you a large favour. Reward it by engaging with the substance rather than looking alarmed.

Write it down. Not during every sentence, but a few words after each answer is fine and reads as diligence rather than rudeness. You will be comparing three companies in two weeks and you will not remember which one had the unresolved reporting line.

Questions that cost you

Not all questions are free.

Compensation, benefits, holiday and remote policy in the first interview with the hiring manager. Not because these are shameful, they are the reason we work, but because they belong to the recruiter, who is the person with the answer and the person who cannot be put off by hearing them asked. Ask the recruiter early, then leave it alone until the offer conversation. The full negotiation is its own subject and is covered separately.

Anything on the first page of the company website. "So what does the company do?" is not curiosity, it is a research failure with a question mark on the end.

Questions that are actually statements. "I noticed you do not have a formal onboarding process, is that something you are planning to fix?" You may be right. You are also, in the fourth minute of a first meeting, telling a stranger their team is badly run.

"Do you have any concerns about my application?" This one is genuinely contested, so here is a straight answer. It can work, and it can also hand a wavering interviewer an invitation to articulate a doubt they had not yet formed. Use it when you have a specific gap you know is on their mind and you have a good response ready, and phrase it forward: "the role leans more on stakeholder work than my last job did, is that a concern from your side?" That is a targeted question with a prepared follow-up. The open-ended version, asked hopefully at the end, mostly creates risk.

Too many questions. Two or three good ones, asked properly with follow-ups, beat eight asked at speed. If the meeting is running over, ask your best one and offer the rest by email.

What to do when they have answered everything

This happens with good interviewers, and freezing at that moment is a common way to end an otherwise strong hour on a flat note. Two reliable exits.

The first is to build on something they said earlier: "you mentioned the team is picking up the reporting work from finance next quarter, is that a permanent shift or a stopgap?" This shows you were listening, which is worth more than any question from a list.

The second is honest and works better than people expect: "you have covered most of what I had. The one thing I would still like to hear is what the hardest part of this job is for the person doing it." Nobody has ever thought less of a candidate for that.

What you should not say is "no, I think you have covered everything", followed by silence. Even if it is true, it lands as indifference.

A worked closing exchange

Here is roughly how the last five minutes should sound with a hiring manager.

Interviewer: "We have about ten minutes left. Anything you would like to ask me?"

You: "Yes, three things if there is time. First, if you look back in six months and this hire went well, what has happened?"

Interviewer gives an answer that names two deliverables and one relationship.

You: "That is useful. On the second of those, the supplier reporting, what makes it hard at the moment? Is it the data or the people?"

Interviewer: "Honestly, both. The data comes in three formats and the person who owns one of them does not report to us."

You: "That is the part I would want to understand early. Which brings me to my second question, who would I be working with most outside this team, and how is that going right now?"

Notice what happened. You asked two questions and got a picture of the job, the obstacle, and the political geography, because you followed up instead of moving down a list. That exchange also demonstrated more competence than any answer you gave in the previous forty minutes.

Common questions

How many questions should I prepare? Prepare six, expect to ask three. Half of a good list gets answered during the interview itself, and you want spares rather than a scramble.

Is it acceptable to read my questions off a notebook? Yes, and it looks organised rather than unprepared. Read the question, then look up and listen. What looks bad is reading while they answer.

Should my questions be different in a phone screen? Yes. Keep them short and mechanical: process, timeline, why the role is open, whether the band matches your expectation. Save the substantial ones for people who do the work.

What if the interviewer cannot answer my question? That is data too, and it is usually forgivable in a recruiter and less so in a hiring manager. You can also ask who would know, and follow up with them in a later round.

Should I ask about the previous person in the role? Yes, but neutrally: "is this a new role or a replacement?" then, if replacement, "where did they move on to?" Asking why someone left, framed as an accusation, gets a defensive answer.

Can I send questions afterwards if I forgot? One or two, in your follow-up note, phrased as genuine interest rather than an afterthought. That note is worth writing anyway, and there is a full guide to it in the thank you email after an interview.

The short version

Ask questions whose answers would change your decision. Convert abstractions into events. Match the question to the person who actually holds the information. Follow up once, always, because the second answer is the honest one. Compare what different interviewers tell you about the same thing. And remember that this part of the hour is still being scored, so ask about the work.

CvLaunch can help with the other side of the same conversation: it reads your CV the way an interviewer will, shows you which claims are likely to be tested, and helps you walk in with your own evidence ready.