Questions to Ask in an Interview, and How to Read the Answers

By Mustafa Tarabya, founder of CVBooster · Published 2026-08-01 · Updated 2026-09-15

8 min read

Every question you ask does two jobs. It gets you an answer, and it shows them how you think. So "do you have any questions for me" is not the end of the interview. It is the last scored round, dressed up as the door.

This covers one thing: the questions you ask them. How to structure your own answers, and how to prepare, are separate jobs covered elsewhere. What matters here is asking a few questions that return real information, and reading what comes back.

Every question does two jobs

A question signals what you care about, and it extracts information. Almost all advice stops at the signal, which is how candidates ask impressive sounding questions they do not want answered. Treat the answer as the point instead. You are deciding whether to give this company two years of your life on three hours of evidence.

How to read an answer

Specific beats fluent. Someone who names a project, a date or a person is describing something that exists. Someone who answers in adjectives is describing an idea of the company. The most polished answer often has the least in it.

Hesitation is information. A pause before "why is this role open" usually means the honest answer is uncomfortable. You do not need them to say it out loud. You need to notice, and ask one more question.

An honest negative is the best answer you can get. A manager who says the reporting stack is a mess and that fixing it is half the job is telling you the truth, and signaling they will be straight with you later.

What the work actually is

Job postings are written by committee and often describe a role nobody has done yet. Start with the days.

"What will this person spend most of their time on in a normal week?" A good answer is boring and concrete: three or four recurring activities with rough proportions. A bad answer restates the posting, which means the role was written to justify a headcount and the duties get assembled after you start.
"What does the first ninety days look like?" Good: a sequence, with people you will meet and something you own by the end of it. Bad: "onboarding, then you get up to speed." Nobody has planned for your arrival, and month one goes on finding your own work while being judged on it.
"Which parts of this role are new, and which are inherited?" Good answers split the job and tell you what is already running. If everything is new, ask who decided it was needed. Brand new scope with no sponsor above it gets cut in the first reorg.

How success is measured

Ask "what does the performance review for this role measure?" You want named metrics, a cycle, and who writes it. A manager who answers in one breath will judge you against something stable. If the answer drifts into qualities like ownership and being proactive, your review is a judgment call, and politics will decide your raise more than output does.

Then ask "what separates someone who meets expectations here from someone who exceeds them?" A strong answer describes a behavior: they surface problems before those problems land, or they take work off the manager unasked. "Going above and beyond" means the bar is invisible and moves. If they cannot name the difference, assume promotion is slow.

Tip: Ask the same question to two people on the panel. If the hiring manager and the team lead describe success differently, that gap is your finding. You would be reporting into it.

The manager and the team

Most people leave a manager, not a company. You get one hour to assess yours, so spend some of it here.

"How would we work together week to week, and in what format?" A good answer is specific: a standing thirty minutes on Mondays, a written update, messages when urgent. "My door is always open" means no structure, so you get attention when something is on fire and none otherwise.
"When was the last time someone on your team disagreed with you, and what happened?" The highest yield question you can ask a manager. A good answer names a real disagreement and an outcome, ideally one where they changed their mind. If they cannot recall one, either nobody pushes back or they did not notice.
"Who would I work with most closely, and what do they need from this role that they are not getting today?" Good answers come from real conversations with those people. If the manager does not know, you find that out yourself in month two.

Why the seat is open

Ask "how many people have held this role in the last three years?" It is factual, hard to dodge, and the number does the work. One person, promoted, is healthy. Three people in three years means the role itself is broken: impossible scope, no authority, or a stakeholder nobody will confront. That will not change because you arrived.

Follow with "what would the last person in this seat say was hardest about it?" Putting it in their voice makes it easier to answer honestly. A good answer is concrete and slightly unflattering to the company: the approval chain is long, the client list was too big for one person. An answer that criticizes the person rather than the job is how you will be discussed after you leave.

How the company actually operates

Every company calls itself fast moving and collaborative. Skip the self description. Ask about behavior.

"What did the company stop doing in the last year?" Organizations that can name something they killed have a working prioritization process. Ones that have never stopped anything are stacking initiatives on the same people, and you are about to be one of them. "We just keep growing" is not a good answer.
"When two teams want different things, how does that get settled?" You want a named forum, a named person, or a written process. If the answer is that it gets escalated, ask how long that takes. If nobody can describe the path, decisions go to whoever has the most social capital, and a new hire has none.
"What is the company betting on for the next twelve months?" Anyone at manager level should answer without a script, and it should match what the recruiter told you. A mismatch means the strategy has not reached the floor where the work happens.

The process and the offer

Ask "what are the remaining stages, who will I meet, and what is each one looking for?" Most candidates ask about timing and stop. The last clause is what makes it useful. A company that can say what each stage evaluates has a designed process. One that cannot is running interviews on instinct.

On money, ask one factual question early: "is the posted range the full range for this level, or does it move for a stronger candidate?" That is not negotiating. It checks whether the number is real before either side spends four more hours. Save the negotiating for the offer.

Different questions for different stages

A recruiter cannot tell you what good looks like in the role, and a VP will not discuss the salary band. Match the question to the person.

Recruiter screen: the salary range, the process and timeline, whether the role is remote, hybrid or on site, and what the hiring manager called the must-haves. Recruiters know logistics and constraints and will share both. Ask them about culture and you get a brochure.
Hiring manager: the work itself, how success is measured, how they manage, the first ninety days, and why the seat is open. The deep questions belong here, because this is the person who owns the answers.
Peers and panel members: what surprised them in their first month, how work reaches them, and what they would change. Peers give the most honest picture in the process, because they are not the ones selling the role.
Final round or executive: what the company is betting on, what it stopped doing, how this team fits the next year. Keep it at their altitude. Asking a founder about your review cycle wastes the one conversation that could have told you where the company is heading.

Tip: Bring eight questions on paper and expect to ask three. Most get answered along the way, and crossing one off in front of the interviewer shows you were listening rather than waiting.

What not to ask, and why

Anything answered on the careers page or in the posting. It reads as though you did not read what you were given, and it burns a slot you cannot recover.

Vacation, sick leave and working hours before an offer exists. Not because wanting them is wrong, but because the answer is fixed policy that HR sends in writing anyway. Asking early spends your ten minutes on information you get for free.

"What is the culture like?" The answer is the same everywhere: collaborative, fast paced, we work hard and have fun. It cannot be falsified, so it teaches you nothing. Ask about behavior instead. How disagreements get settled describes culture without inviting the script.

Gossip about your predecessor. "Why did they fire the last person?" leaves the interviewer no safe answer and makes you look like a risk. The turnover count gets the same signal without the cost. Same with "how did I do?", which asks someone to commit before a debrief they have not had.

And never ask a question you already know the answer to in order to look prepared. Experienced interviewers can tell curiosity from performance, and a question you do not care about produces an answer you will not remember.

When they genuinely covered everything

It happens, particularly with a thorough hiring manager. "No, you covered everything" is still the wrong answer, because it is indistinguishable from indifference and the interviewer still has to write something in the debrief.

Two clean ways out. Reopen something they said and go one level deeper: "you mentioned the team is absorbing the reporting work from finance. How settled is that, and would it sit with this role?" That proves you listened, and it usually gets the most candid answer of the hour.

Or make the emptiness useful: "you have answered everything I came in with. The one thing left is what you would want to see from me in the first month." That gets a concrete answer and ends on the work rather than on nothing.

Tip: Write down two questions during the interview itself, taken from something the interviewer said. Those beat anything you prepared at home.

The short version

Ask three or four questions chosen for what the answers reveal, not for how they sound. Find out what the week looks like, how you will be judged, how the manager handles disagreement, how many people have held the seat, and what the company stopped doing. Listen for specifics, notice hesitation, and never end with nothing.

Looking for a worked example for your job title? Browse the resume examples by job title.

Get your free ATS score · All articles