Manager Interview Questions to Ask Candidates: 20 Scorable Questions

Ask manager candidates about teams they actually ran, not their philosophy of leadership. The questions that predict performance cover developing a specific person, handling a specific underperformer, choosing what the team stopped doing, hiring and losing people, and disagreeing with their own boss. A strong manager screen is 30 to 40 minutes, uses the same eight to ten questions for every applicant to the req, and scores each answer against anchors written before anyone applied. The single most useful probe in the whole interview is "what happened to that person afterwards?"

Manager hiring fails in a way individual contributor hiring does not. When you hire a bad engineer you get less code. When you hire a bad manager you get attrition, and it arrives six months later attached to three people who were doing fine before. The cost is real and it is delayed, which is exactly the combination that stops teams from investigating it properly.

The other problem is that management is the easiest subject in the world to talk well about. There is a large public vocabulary of good-sounding management ideas, and any candidate who has read two books can deploy it fluently for forty minutes without ever having run anything. Ask "what is your management style?" and you will get a competent answer from a person who has never had a direct report. The questions below are built to be difficult to answer well without the experience.

What questions should you ask a manager candidate?

Ask for a specific person, a specific decision, and a specific outcome, then probe for what the candidate personally did. Management questions drift toward the general faster than any other function, because the honest answer is often "it depends," so the interviewer accepts a framework instead of an example. Pick eight to ten questions from the groups below based on what the role actually requires, and ask the same set of every applicant so the answers can be compared side by side.

One structural note before the list. A first-line manager of four people and a director running three teams through other managers are different jobs, not the same job at different volumes. The first is about coaching individuals, the second is almost entirely about systems, delegation and choosing which fires to ignore. Decide which one you are hiring before you pick questions, because the strongest answer to a coaching question can come from someone who will drown at the director level.

Developing people

• Tell me about someone on your team who got materially better while you managed them. What did you actually do?
• Who is the best person you ever hired, and who is the worst? What did you miss on the second one?
• Describe a time you gave someone feedback they did not want to hear. What did you say, and what happened next?
• What is the hardest thing about managing a person who is more technically skilled than you?
• How do you know whether someone on your team is struggling before they tell you?

The development question is where most candidates reveal themselves within ninety seconds. A strong answer names a person, describes where they were weak, describes something concrete the manager changed about how they worked together, and knows what that person is doing now. A weak answer describes a process: weekly one-to-ones, a development plan, a template. Processes are how the work happens, but they are not evidence that it happened, and a candidate who cannot get past the process usually ran the process without the outcome.

The follow-up that does the real work is unglamorous: "where is that person now?" Managers who genuinely developed someone tend to know, often in detail, and frequently still hear from them. It is one of the few things in a management interview that is difficult to manufacture on the spot.

Performance management and hard conversations

• Tell me about someone on your team who was not performing. Walk me through what you did, month by month.
• Have you ever had to let someone go? What was the gap between you knowing and you acting?
• Describe a conflict between two people on your team. How did it end?
• When did you last change your mind about someone, in either direction?

This group is the most predictive and the most commonly skipped, because it is uncomfortable to ask and uncomfortable to answer. The underperformance question should be asked with the phrase "month by month," which forces a timeline. What you are scoring is the gap: almost every manager waits too long, and the good ones know they waited too long and can tell you how long. A candidate who says they addressed it immediately and cleanly is either exceptional or describing a case that never got difficult.

Listen for whether the person was told, plainly, in words they could act on. A surprising number of managers manage underperformance by hinting, escalating to HR, and then presenting the outcome as inevitable. That pattern will reproduce itself on your team, and it is expensive.

Delivery, prioritization and what the team stopped doing

• What did your team stop doing under you, and who was unhappy about it?
• Tell me about a deadline you were going to miss. When did you tell your stakeholders, and what did you say?
• How do you decide what your team works on when three people all want something urgently?
• Describe the last thing you delegated that you were tempted to do yourself.

The stop-doing question is the best single question in this set for mid-level and senior managers, and almost nobody asks it. Anyone can add work. Removing work requires having a view, defending it to someone senior, and accepting that a stakeholder will be annoyed. A candidate with a crisp answer here has genuinely owned a team's priorities. A candidate who cannot name anything has probably been running a queue rather than managing it.

On the deadline question, the timing is the signal, not the outcome. Managers who tell stakeholders in week two of a four week slip are a different species from managers who tell them in week four, and the difference does not correlate with how good the plan was.

Hiring, and working across the organization

• Walk me through the last hire you made, from writing the role to their first ninety days.
• Tell me about a time you disagreed with your own manager. What did you do?
• Describe something your team needed that you had to get from another team. How did you get it?
• What did you inherit when you took over your last team, and what state was it in?

The disagreement question is the one to protect time for. Managers sit between their team and the organization, and the job includes pushing back upward, then committing to the decision either way. A strong answer contains a real disagreement, a real conversation, and a clear account of what happened after the decision went against them. Two weak patterns show up: candidates who have never disagreed with anyone, and candidates who disagreed by going quiet and letting the plan fail. Both are costly in different ways.

The inheritance question is a quiet favorite because it is nearly impossible to answer well from theory. Someone who has actually taken over a team can describe the specific mess: the person who should have been promoted a year ago, the meeting nobody needed, the two people who were not speaking. Candidates without the experience describe an abstraction.

Which questions should you cut?

Cut anything that asks for a philosophy, a self-assessment or a hypothetical. "What is your leadership style?" invites a rehearsed label. "How would you handle a difficult team member?" is answered correctly by everyone who has ever read an article about difficult team members, which is everyone. "What are your weaknesses?" has been a negotiation over how to appear humble for about thirty years.

Also cut the questions that quietly measure background rather than capability. Asking where someone learned to manage, or what their manager at a famous company taught them, rewards a career path rather than a skill, and it narrows your pool in a direction you did not intend. If a criterion cannot be scored the same way for a candidate who managed a warehouse shift and a candidate who managed a product team, it probably is not measuring management.

How do you score manager interview answers consistently?

Write three anchored levels per criterion before the first application arrives, describing what a weak, adequate and strong answer contains rather than how the candidate came across. For the underperformance question, a strong anchor might read "names the person and the specific gap, told them directly within weeks, describes a concrete intervention and its outcome, acknowledges what they would do faster." That is scoreable by two different interviewers. "Showed good judgment" is not.

Manager interviews need this more than most, because the failure mode is charisma. Confident, warm, articulate people are overrated in management interviews by almost every panel, and confidence is precisely the trait that a scoring rubric anchored to answer content will neutralize. Our interview scorecard template covers the structure, and candidate interview scoring goes through how anchored scoring works when several people are interviewing for the same req.

How do the questions change by type of manager?

The core set above holds for any people-management role. What changes is the fourth and fifth competency you add on top, and it is usually one or two questions, not a different interview.

• Project manager: add scope and dependency questions. "Tell me about a project where the scope changed after you started" and "how do you track something that depends on a team you do not control."
• Product manager: add a decision-under-uncertainty question and a killed-feature question. "What did you decide not to build, and how did you explain that to the person who wanted it?"
• Office manager: add vendor and logistics ownership. "What did you renegotiate or replace, and what did it save?"
• Finance manager: add budget ownership rather than budget reporting. There is a real difference between a candidate who owned a number and made cuts against it and one who watched spend arrive in a spend management system and reported on it afterwards. Ask what they cut, who objected, and what it cost them internally.
• HR manager: add a question about a decision they made that was correct and unpopular, and one about advising a manager who was handling something badly.
• Assistant manager or first-time manager: drop the hiring questions, which they will not have done, and add "what did you do when you had responsibility without authority."

For first-time manager candidates specifically, resist the urge to soften the interview into a personality conversation. Ask about informal leadership: training a new starter, running a shift, owning a process other people depended on. The evidence exists, it is just not labeled as management on the resume.

How long should a manager interview be?

Thirty to forty minutes for a first-round screen, which is longer than the twenty to thirty you would give an individual contributor, because every answer here needs a follow-up to be worth anything. Eight to ten questions with probes is realistic in that window. Anything past forty-five minutes in round one starts costing you employed candidates, who are fitting this into a lunch break.

Protect the follow-ups over the question count. Six questions asked properly, with "what did you personally do" and "what happened next" on each, beats twelve questions asked once. If you are running out of time, cut questions rather than probes. Our guide to first round interview screening covers what belongs in round one and what should wait.

How do you ask these questions consistently when you are hiring many managers?

Consistency is easy with four candidates and effectively impossible with forty, which is where most structured interview programs quietly fall apart. The questions are written down, everyone agrees to use them, and then a hiring manager runs a call on a busy Thursday, skips three questions, and scores from memory that evening. The rubric still exists. It just is not being applied.

This is the case for moving the first round to something that runs identically every time. An AI interview agent asks every applicant the same eight questions in the same order, follows up where an answer skipped the how, and scores each response against your anchors, so what reaches your panel is a ranked shortlist with transcripts rather than forty sets of notes of varying quality. Recruiters still read the transcripts and decide who advances, which is the part worth their judgment. If you are weighing up vendors for that, our video interview software comparison is honest about which platforms conduct the interview and which only record it, and pre-screening interview questions covers the general first-round set to adapt.

What is the single best interview question for a manager?

"Tell me about someone on your team who got materially better while you managed them, and what you actually did." It is difficult to answer well without the experience, it is specific enough to score, it opens naturally into two or three probes, and it measures the part of the job that produces compounding value. The follow-up about where that person is now is the closest thing to a verification step you get in an interview.

If you only have room for a second, make it the stop-doing question. Between them you learn whether this person can grow individuals and whether they can defend a priority, which covers most of what separates a manager who helps a team from one who simply sits above it.