Skip to content
All posts

The Interview Isn't Over When They Ask "Any Questions for Us?"

The last five minutes of an interview are the only part you fully control. Most candidates waste them on a polite 'no, I think you covered everything.' Here's how to use them instead.

Harshil Moradia

4 min read

The Interview Isn't Over When They Ask "Any Questions for Us?"

Almost every interview ends the same way: "So, do you have any questions for us?" Most candidates hear it as a sign that the interview is winding down, ask something safe about remote work or the tech stack, and start packing up mentally.

That's a mistake. This is the only part of the interview where you set the agenda. Everything before it was the interviewer testing you. These last few minutes let you show how you think about the job, and they let you find out whether you actually want it.

Why "no questions" hurts you

"I think you covered everything" sounds polite, but the interviewer hears something else: you haven't thought much about what working here would be like. Or you're not that interested. Or you'll take whatever comes along.

None of that is fatal, but it's a missed chance at the moment they're forming their final impression. People remember the end of a conversation better than the middle.

Questions that show you're already thinking like a team member

The best questions are the ones you'd ask in your first week on the job. They show you're already picturing yourself doing the work.

  • "What would a great first 90 days look like in this role?" You learn what they actually expect, and you hear what success means to them in their own words.
  • "What's the hardest problem the team is working on right now?" People like talking about their real problems. You also find out whether the work sounds interesting to you.
  • "How does a piece of work go from idea to production here?" The answer tells you about code review, testing, deploys, and how much process sits between you and shipping.
  • "What does the on-call or support load look like?" It's a practical question, and asking it suggests you've worked somewhere it mattered.

Questions that help you decide

An interview runs in both directions. Some questions are there mainly to protect you:

  • "Why is this position open?" Growth is a good sign. A string of people who left in under a year is a warning.
  • "What's something you'd change about how the team works, if you could?" An honest answer is a good sign. If they say "nothing, it's perfect," that tells you something too.
  • "How do you give feedback to someone who's struggling?" This tells you how they'll treat you on your worst week, not your best.

Watch the reaction as closely as you listen to the answer. A long pause, a nervous glance at a colleague, or a vague answer to a simple question often tells you more than the words.

The question that closes the loop

Save one question for the very end:

"Is there anything about my background that gives you hesitation about me for this role?"

It feels uncomfortable to ask, and that's why it works. If the interviewer has a doubt, like "we're not sure you've worked at this scale," it will come up when they compare candidates later and you won't be there to answer it. Asking now gives you the chance to address it: "Fair point. The largest system I've owned handled about 2 million requests a day, and here's how I approached the scaling problems there."

At worst they say "no, nothing comes to mind," and you've still come across as confident and open to feedback.

Questions to skip

  • Anything you could have found on their website. "So what does the company do?" tells them you didn't prepare.
  • Salary and vacation in the first round. Those questions are fair, but the recruiter call is the place for them, not a conversation with a future teammate.
  • "Did I get the job?" It puts the interviewer in an awkward spot and won't get you an honest answer anyway. Ask about next steps and the timeline instead.

Prepare more than you need

Bring five or six questions and expect to use two or three. Some will get answered during the interview, and asking one of those anyway shows you weren't listening. If that happens, build on it instead: "You mentioned the migration to the new billing system earlier. How far along is that?"

That kind of follow-up shows you were paying attention the whole time, and that's what you want the interviewer to remember at the end.

Thanks for reading. If this was useful, the newsletter below is the best way to catch the next one.

Keep reading

More essays