Questions to ask the interviewer, by stage and by person

Ask two or three questions you actually want answered, matched to the person in front of you: process and timing for a recruiter, success and the team's problems for a hiring manager, daily work for a peer engineer, direction for a senior leader. Good questions are specific, open and about the job. Then listen, and ask one follow-up on the answer.

Why interviewers ask "Do you have any questions for me?"

The question is still part of the interview. The interviewer learns what you care about, whether you prepared, and whether you listened for the last forty minutes. A specific question about the team's work says more about your interest than a closing line about being excited.

It is also the one scheduled moment where you get to check the job. You will spend most of your working week on this team. The end of each round is where you find out what that week looks like, who decides what you work on, and what the team is struggling with right now.

How many questions should you ask?

Prepare five to eight and expect to ask two or three. The clock decides the rest. With two minutes left, ask your best question and let them finish on time. With ten or fifteen minutes left, ask more and follow up on the answers. Ending early with time to spare reads as low interest.

Some of your questions will be answered during the interview. Drop those, or build on what you heard: "You mentioned the team moved to weekly releases. What changed when you did that?" That shows you were listening, which a fresh question from your list does not.

Questions to ask a recruiter

Recruiters own the process. Ask about steps, timing and logistics here, so you don't spend an engineer's time on them.

• What are the remaining steps, and what does each round focus on?
• Is there anything in my background you'd like me to clarify before the next round?
• What is the timeline for a decision?
• Is the role open because the team is growing, or is it a backfill?
• How is the team's time split between building new things and maintaining existing systems?
• What level is this role, and what is the range for it? Recruiters expect this question. A peer engineer usually can't answer it.

Questions to ask the hiring manager

The hiring manager decides what success looks like and what you will work on. Ask about expectations, the team's problems and how they manage.

• What would you want someone in this role to have done by the end of their first three months?
• What is the biggest problem the team is working on this quarter?
• What separates the people who do well on this team from the ones who struggle?
• How do you decide what the team works on, and how much say do engineers have?
• How do you give feedback, and how often?
• What does growth to the next level look like here, and who has done it recently?
• What is one thing you would change about how the team works today?

Questions to ask a peer engineer

A peer interviewer does the job you are applying for. They can tell you what a normal week looks like, which the job description can't. Keep these concrete.

• What did you work on last week?
• How does code get from a branch to production here?
• What does code review look like, and how long does a typical review take?
• How does on-call work, and how often are you paged outside working hours?
• Which part of the codebase do people avoid, and why?
• How are technical decisions made when two engineers disagree?
• What surprised you most after you joined?

Questions to ask a senior leader

A director, VP or founder has less time and a wider view. Ask about direction and how this team fits into it. Skip details they would have to look up.

• Where do you want this group to be in a year, and what stands in the way?
• How does this team's work connect to the company's main goals right now?
• What is a recent decision you'd like engineers to understand better?
• What do you look at when you decide whether a team is doing well?

Which questions fit which stage?

The stage matters as much as the person. Early rounds are about fit and process. Later rounds are about the actual work and the actual offer.

• Phone screen. Process, timeline, why the role is open, what the next rounds test. One or two questions is enough. More on this stage in phone screen interview questions.
• Technical rounds. The engineering practices behind the problem you just solved: testing, review, deployment, on-call. A good bridge is the problem itself: "Is this close to something your team actually deals with?"
• Hiring manager round. Expectations, the first few months, how the team is run and how people grow.
• Final round or offer stage. Whatever would change your mind about the role: team stability, who you would report to, start date, the details of the offer. This is also the point to ask to meet a future teammate if you haven't yet.

How do you turn their answer into a follow-up?

The question you prepared opens the conversation. The follow-up is where it actually happens, and it is the part interviewers remember. It also gets you a more honest answer than the first, practiced one.

1. Listen for one specific detail. A tool, a number, a problem, a change. Not the general tone.
2. Name it back. Use their words, briefly: "You said reviews can take a few days."
3. Ask one level deeper. Why, what changed, or what they tried: "What's slowing them down?"
4. Connect it to your experience. One sentence, and only if it fits. Then stop and let them talk.

Here is an invented example exchange with a hiring manager.

Candidate: What's the biggest problem the team is working on this quarter? Manager: Honestly, flaky tests. CI takes forty minutes and fails about one run in five for reasons that have nothing to do with the change. Candidate: One in five is a lot. Do you know yet whether it's the tests themselves or the environment they run in? Manager: Mostly shared state between tests. Nobody has owned it. Candidate: That's close to something I worked on last year. Our integration tests shared one database, and giving each test its own schema is what made the failures reproducible. I'd be glad to dig into that here.

The candidate asked one prepared question, followed up on one detail, and connected it to a real experience in two sentences. The manager now has a reason to remember them. The same skill runs the other way when the interviewer probes your answers, which how to answer follow-up questions covers.

Questions to avoid

• Anything the careers page answers. "What does the company do?" tells them you didn't look.
• Yes or no questions. "Do you like working here?" gets "Yes." Ask "What has kept you here?" instead.
• "Did I get the job?" or "How did I do?" It puts the interviewer on the spot, and most can't answer. Ask about next steps instead.
• Salary, leave and benefits in a technical round. Save them for the recruiter or the offer stage.
• Questions that signal you want less of the work, such as how soon you can switch teams, asked as your first question.
• Five questions in one breath. Ask one, then wait.
• Gotcha questions. You can ask about layoffs or turnover, but ask neutrally: "How has the team changed over the last year?"

Common mistakes

• Reading from a list without looking up. Glance at your notes, then ask the question as if you care about the answer, because you should.
• The same three questions for every interviewer. By the fourth round of the day, they sound like a script.
• Not listening. If your next line ignores what they just said, the question was a formality.
• Turning a question into a speech. Two minutes about yourself followed by "What do you think?" is not a question.
• Running over time. When they mention a hard stop, ask one question and thank them.
• "No, I think you covered everything." If your list is used up, name one thing they said and ask one level deeper about it.

A practice loop for the last five minutes

Most people rehearse their answers and improvise their questions. A short loop fixes that.

1. Write two per interviewer. For the role you're interviewing for, write two questions each for a recruiter, a hiring manager, a peer engineer and a leader. Eight in all.
2. Say them out loud. Questions that read well can sound stiff. Cut any that you can't say in one breath.
3. Invent an answer. Write a plausible one-line answer for each question. Then say your follow-up to it out loud.
4. Time the close. Set a five-minute timer and run two questions with follow-ups. Notice when you start talking about yourself.
5. Update after each round. After a real interview, note which question got the most useful answer and which fell flat. Replace the weak one.

Practice the conversation on the Verbal surface

The closing questions are part of the conversational round, so they sit with the Verbal surface in HIDEA AI. Verbal, Live coding, System design and Project are four separate surfaces. Verbal is the one for behavioral and conversational rounds, grounded in your resume and the job description.

A mock interview flips the roles: the app asks the questions out loud, listens to your spoken answers and scores the round. Mocks are verbal-only, 20 or 30 minutes, on Pro and Pro+. The Report tab scores a saved session, so you can see which answers ran long and ate the time you wanted for your own questions. Fifteen session minutes a day is free, with no credit card, on the desktop app for macOS and Windows.

You speak or type every answer, and the questions you ask are yours too. If you plan to open any tool during a live round, check what some employers publish first. The interview copilot overview and the pricing page cover what each plan includes.

Where to go next

• Practice the full spoken round: verbal interview practice.
• Prepare the answer that often comes just before your questions: why do you want to work here.
• Follow up in writing after the round: thank-you email after an interview.
• Ready to rehearse? Download HIDEA AI.