The last five minutes are yours

What these five minutes actually test

“Any questions?” is the judgment test of the hour. Your question shows what you think about when nobody hands you a script: the product, how the team works, growth, or nothing at all.

Nobody tells you this part is scored, but it is. Two things get read: how deep your homework went, and what you actually care about. The candidate who asks only about benefits and the candidate who asks how the team makes decisions do not land in the same row of the scorecard.

“No, I think you covered everything” is the most common answer and the worst one. It says exactly one thing: your curiosity about this job ran out in fifty minutes.

It is also your one chance to gather solid information about a place where you might spend years. Treat it as real research for your own decision rather than a performance.

The best questions come from the interview itself

The strongest question of the day quotes the interview itself: “You mentioned the team just went through a re-org. What changed most for this role?” It proves you listened, and it continues a topic the interviewer already cares about.

A prepared question, however good, is weaker than one that grew out of the last forty minutes. They mention a project that slipped two quarters. Ask what was actually blocking it, looking back. That kind of question shows you were listening and that you understood what you heard.

During the hour, note two things they said that surprised you, on paper or in your head. Those two notes beat any list you brought in. Memorize a list and it becomes the backup, used only when you caught nothing worth pulling on.

Who you ask matters more than what you ask

The same question — what is the team’s biggest bottleneck right now — gets a specific answer from the hiring manager and “we’re growing fast” from a recruiter. That is not evasion. The recruiter genuinely does not know. Spend a good question on someone who cannot answer it and you both sit through an awkward pause, and you have burned one of the few chances you get to see inside.

Before each round, ask one thing: what does this person have that nobody else on the loop can give me? Split your questions along that line.

• Hiring manager. They will answer for what you produce, so only they can tell you the real expectation, the resources, and the problem you are being brought in to solve. What would count as a good first three months, whether this headcount is new or a backfill, and which thing on their list they most want gone.
• Your future peers, at your level. They carry no scoring pressure, so what they say is closest to daily life. Ask what eats the most time in a week, how the last cross-team project actually ran, and where new people usually get stuck. You want the real friction in the process, not the vision.
• The skip-level, your manager’s manager. They see the org, not your day. Ask what this team owns inside the company, whether that scope grows or steadies over the next year, and how they judge whether the team is doing well. Asking them about daily detail is asking the wrong person.
• The recruiter. They own the process and the systems around it. Ask about timing, how many rounds are left, how the performance cycle and promotions work, and what career path this level maps onto. They are the only right audience for structural questions, and they are the window for terms at the end.
• The technical interviewer or the cross-functional one. Their interface with you is one specific thing. Ask where, from their side of that interface, the person in this seat most often slows them down. People answer this one carefully, because it is their own pain.

The backup list

• “What separates the people who do well here from the people who just do fine?” Every interviewer has a real answer, and it tells you how people actually get judged.
• “What would the person in this seat have to get right in the first three months for you to feel you hired well?” It is the fastest way to turn a job description into the real expectation.
• “What is the team’s biggest bottleneck right now — people, direction, something else?” The answer is usually far more honest than the posting.
• “What is the hardest part of this role that the job description doesn’t say?” This question invites honesty, and it shows you can handle honest answers.
• “How does the team decide what NOT to build?” For product and engineering rounds, no question reads the culture faster.
• “Why did you join, and is the reason you stay the same one?” The second half is the point. Many interviewers pause there, and then tell you something true.
• “How many people have left this team in the past year, and roughly why?” Few candidates ask it. Turnover is the hardest signal about culture you can get in an hour.
• “What would make you, personally, glad you hired the person in this seat a year from now?” It gives the interviewer a personal stake in your success.

Ask about what already happened

“Do people work late here?” will always get “it depends on the project.” The question asks about an abstract frequency, and any frequency can be explained away. Ask about something that already happened instead. When was the last stretch where everyone was busy for weeks? What did that period look like? Looking back, was the cause dealt with? Either you get a concrete story or they cannot produce one, and both carry information.

Turning a hypothetical into a past tense is the most useful habit available in these five minutes. “Do you value work-life balance?” is a values question, and nobody answers no. “Did anyone take a long leave last quarter, and how was the work covered?” is a factual question, and the answer cannot be improvised.

The other swap is replacing “is it good” with “how did it happen.” Do not ask whether the team gets along. Ask who made the call on the last significant decision, and what happens when people disagree. Once the process is described out loud, the atmosphere comes out with it.

Length counts too. One sentence per question, two at most. Lay out thirty seconds of background first and the interviewer has lost your point by the time you arrive at it, so they answer whichever part was easiest to answer.

Three kinds of questions to hold back

• Anything the website answers. It signals zero preparation, and that outweighs an hour of good answers.
• Salary, vacation, and remote policy in early rounds. These are fair questions, but they belong to the recruiter and to the offer stage, where they are a negotiation of their own.
• “How much overtime is there?” You can hear that answer inside the bottleneck question above, and asking it outright makes you sound like you are planning your exit before you have arrived.
• “Do you have any concerns about my fit?” It forces the interviewer to practice the case against you, out loud, right before they write your feedback.

The questions that cost you, and why

Questions rarely cost you because they offend. They cost you because they reveal where you are standing.

• “How did I do today?” It puts the interviewer in the position of grading you to your face, so all you can get back is a courtesy. Ask for feedback later if you want it. Asking now forces a polite lie.
• “How many people are you considering for this role?” You are asking about odds, not about the work. It reads as calculating whether to keep investing, rather than wanting to do the job.
• “What is the company’s view of the industry over the next three years?” It sounds impressive and treats the interviewer as an analyst report. There is no wrong answer, so there is no information, and it eats the time you could have spent on something real.
• Five questions in a row, each one followed to the bottom. You mean engaged. They receive an interrogation. Two or three questions, with one of them followed a level deeper, works far better than five asked a level shallow.
• A question that is really a boast. “At my last company I introduced X — is anything like that planned here?” The first half is your resume and only the second half is a question, and people hear the ratio. If you want to add to your experience, add to it directly instead of hiding it inside a question.
• Asking a third time when you will hear back. The first time is professional, the second is a reminder, the third is anxiety — and anxiety in the last five minutes is unusually memorable. When and how to chase is a separate subject.

Read the company from the answer

You ask questions to carry information away, not to look sharp. The real work begins once they start talking.

• Specificity. A good answer has dates, events and people in it. “We cut two projects last quarter and moved everyone onto retention” is information. “We care deeply about the user experience” is scenery. A company that is all scenery for an hour usually communicates that way internally too.
• Tense. Notice whether they describe what has happened or what is about to. We’re building that process, the new manager starts next quarter, we’ll have someone dedicated to it next year. Once or twice is honesty. An hour of future tense means the job is laying the floor rather than running on it. That can be the right job. You should just know which one you are taking.
• How they talk about people who left. When you ask about turnover, listen for where they put the cause. Someone who can name where those people went and why is usually still in touch with them. “They found better opportunities,” every time, may be true, or may be what they would rather not say. One follow-up — was that seat backfilled? — usually opens it up.
• How they complain. On a healthy team the interviewer will name a difficulty or two and then say how they work around it. Someone who admits no problem at all either does not know the team or has been told not to say. Both are worth noting.
• How they talk about their own manager. You cannot ask this one; you wait for it. If a decision their manager made comes up naturally, with a reason attached, that line is open. If no individual name comes up in the whole hour, you may be joining a place where people are not very connected to each other.
• Whether they ask back. Good interviewers often reply with “why do you ask?” That is a good sign. They care what you are trying to find out, rather than working through the last item on an agenda.

When they cannot answer

Silence is not automatically a red flag. What matters is why the answer is not coming.

The first kind is not being in a position to know. Ask a recruiter about the team’s technical debt and of course nothing comes back. Take the question to someone else and do not charge it to the company.

The second kind is never having thought about it. Ask a hiring manager what success looks like in the first three months, watch them freeze and start improvising, and you have learned that the expectation attached to this headcount has not been defined. Your first job will be to define it for them, and until you do, your performance is judged on impressions. That is survivable. It belongs in the conversation about terms.

The third kind is a dodge, and it has a signature: they restate your question, then answer a nearby, easier one. You asked about turnover and they tell you how much hiring they have done lately. Do not call it out, and do not let it go. Come at it once more from another angle — how long was the last person in this seat? People who are willing will answer the second time. If they steer around it again, you already have your answer.

One case to keep separate: the interviewer is new too. That is tenure, not culture. Point the question at what they can answer and ask how their own first month went. You often get something more useful than what you set out to ask.

The notes only become useful afterwards

Within ten minutes of the end, write down what they actually said. Not impressions — the specifics: how long the seat has been open, what got cut last quarter, when the new manager arrives. Memory goes faster than you expect, and a week from now you will need those lines to set against another company.

When two or three processes are running at once, put the same question’s answers side by side. You asked every one of them what a good first three months looks like. With the three answers together, which company has thought about what it wants becomes obvious. That is far more reliable than comparing on impressions later.

If what you heard convinces you that you do not want the job, do not show it in the room and do not wrap up carelessly. Finish the process and keep the manners. You can withdraw after an offer, which is the moment your position looks best, and the industry is smaller than you think.

Carry one or two of their exact words into the note you send afterwards. It lands better than any polite formula, though what belongs in that note is another subject.

Closing the conversation

Two or three questions is enough. Do not fill the five minutes just because they are there.

End with thirty calm seconds: “What I heard today made me more interested than when I walked in. I’d be glad to take this forward. What are the next steps?” It is clear without begging, the last sentence in their file is yours, and they get to leave on time.