"Do you have any questions for us?" is the last five minutes of nearly every interview, and it is the only part of the process where you are the one gathering information.
Most candidates waste it. Some say no. Some ask about working hours and leave policy, which is fair but tells them nothing they could not read in the handbook. And some ask a question they found on a list, which the interviewer has heard nine times this month and recognises immediately.
The segment does two things at once. It signals what you care about — a candidate who asks how the team decides what to build is understood differently from one who asks about the appraisal cycle. And more importantly, it is how you find out whether you actually want the job, at the only moment when someone is obliged to answer you.
Ask the right person
The single most common mistake is asking everyone the same three questions. Each interviewer knows different things, and asking outside their knowledge produces a vague answer that helps nobody.
The recruiter knows process, band, timeline, and how the role came to exist. Not the technical detail.
The hiring manager knows the work, the team, the expectations and the problems. This is the highest-value conversation you will have, and most candidates under-use it.
Peer interviewers know what it is actually like — the day-to-day, the tooling, the meetings, whether the stated process is the real process. They are also the most candid, because they are not selling.
Senior leadership, if you meet them, knows direction and priorities. Ask about the business, not the team.
Questions for the hiring manager
These are the ones worth the time.
"What does the first ninety days look like for whoever takes this role?" A good answer is concrete — a specific thing to learn, a specific thing to ship. A vague one ("get up to speed, meet the team") frequently means the role is not clearly defined yet, which is a real and common problem.
"Why is this position open?" Growth, backfill, or a new function. All three are fine; the useful part is the follow-up. If it is a backfill: what did the previous person go on to do? An internal move is a good sign. A quick exit that the manager is uncomfortable discussing is worth noticing.
"What is the hardest part of this job — the thing that makes it not straightforward?" The best question on this list. Every role has one. A manager who names it honestly is someone you can work for. A manager who says there isn't one either does not know the role or is selling, and both are informative.
"How is success measured for this role at six months and at a year?" If there is no answer, there is no clear expectation — which sounds like freedom and usually turns into a performance conversation about criteria nobody stated.
"How does the team decide what to work on?" Tells you where the role sits: executing a defined roadmap, or shaping one. Neither is wrong, but a candidate expecting the second and getting the first is a resignation in eighteen months.
"What is your management style — how often do we speak, and how do you like to hear about problems?" Practical, appropriate, and answered honestly more often than you would expect.
"What happened to the last person who was promoted out of this team?" Slightly pointed, and worth asking anyway. If nobody has been, that is a fact about the team's growth ceiling.
Questions for peer interviewers
"What does a normal week look like — how much of it is meetings?" Concrete and hard to spin.
"What is the thing that most frustrates you about working here?" Ask this. Almost everyone answers honestly, because it is a relief to. What matters is not whether they have a complaint — everyone does — but whether it is something you can live with. "The build takes twenty minutes" is different from "you can't tell who decides anything".
"How long have you been here, and what has kept you?" Two useful signals in one question.
"What is the on-call or crunch situation, realistically?" Ask a peer, not a manager. And ask about the last incident, not the policy.
"How does code review / handover / approval actually work here?" Substitute your function's equivalent. You are asking whether the process is real.
Questions for the recruiter
"What is the budgeted range for this role?" Ask early rather than late. Most Indian recruiters have a band and will share it, because a mismatch wastes their time too. The rest of that conversation is in how to negotiate salary in India.
"What do the remaining rounds look like, and what does each one cover?" Lets you prepare for the correct format, which matters more than most preparation. See preparing for a technical interview.
"What is the fixed-versus-variable split, and how did variable pay out last year?" The single most useful compensation question, and the answer is often revealing. Detail in variable pay and joining bonuses.
"What is the timeline for a decision?" Sets expectations and gives you a legitimate reason to follow up.
"What is the policy on remote and hybrid — and has it changed recently?" The second half is the real question. Policies have been moving in one direction for three years, and "three days in office" agreed verbally is worth less than the same in the offer letter.
Questions about the company
Worth one or two, and only if you have done the reading. A question that reveals you have not looked at the product is worse than no question.
"What is the biggest change in the business over the last year?" "Who do you lose deals to most often?" — for a commercial role, an excellent question. "How is this team funded — is it a cost centre or attached to revenue?" — unglamorous and genuinely predictive of headcount stability.
What their answers tell you
The content matters less than three other things.
Whether they can answer at all. Vagueness on scope, success criteria or why the role is open is the most reliable warning sign available to you. It usually means the role has not been thought through, and the cost of that lands on whoever joins.
Whether the answers are consistent across interviewers. Ask two people what the team's priority is this quarter. Matching answers indicate a functioning team. Three different answers indicate something you will inherit.
How they respond to a slightly uncomfortable question. "What's the hardest part of this job" is mildly awkward and completely fair. A manager who engages with it is showing you how disagreement will go later. One who deflects is showing you that too.
Specific things worth treating as warnings: describing the team as "a family" and then not being able to describe a boundary; unprompted emphasis on how hard everyone works; talking about the previous occupant of the role with visible irritation; being unable to name a single thing that is difficult.
The ones to skip
- Anything answered on the careers page. It reads as not having looked.
- Leave, holidays and perks in the first round. Legitimate questions, wrong timing. Ask the recruiter once an offer is close.
- "What is the company culture like?" Too broad to produce a real answer. Ask a specific behavioural question instead — how disagreements get resolved, what happens when a deadline is going to be missed.
- "Do you have any concerns about my candidacy?" Popular advice, and it puts the interviewer in an awkward position at the worst moment. If you want feedback, ask the recruiter afterwards.
- Six questions when there are four minutes. Two or three good ones, then stop.
How to actually do it
Write four questions down before the interview and bring them on paper or in a notebook. Nobody has ever thought less of a candidate for referring to notes; several interviewers have thought more.
Cross off any that were already answered during the conversation — and say so: "I had a question about how the team prioritises, but you covered that when you described the quarterly planning." That is a better signal than asking it anyway.
Then listen to the answer properly and ask one follow-up. The follow-up is the part that makes it a conversation rather than a checklist, and it is where the useful information lives.
The rest of the round — what is being assessed and how the standard questions are read — is in the HR round, question by question.