Behavioral questions for managers use the same "tell me about a time" format as any behavioral interview, but the evidence to show is different: what you did with a person, what your team did as a result, and what the decision cost. A strong individual contributor can answer every one of them well and still lose the interview by describing their own work. This page organises manager behavioral questions by the competency each one probes, explains what a manager-level answer contains, lists the follow-ups and the failure modes for each, and shows how three to five stories can cover all of them.
What makes a behavioral answer a manager answer
A behavioral question asks for a real example, told in order. STAR, or any similar structure, gets you the order. It does not get you the management part. Two candidates can give perfectly structured answers to "tell me about a time you handled a difficult situation" and only one of them sounds like a manager.
Three things make the difference, and they apply to every question on this page:
- Your own role, including what you contributed to the problem. A manager answer owns the setup, not only the resolution.
- What you did with a person. The expectation you set, the conversation you had, the decision you made and told someone about. Manager answers have a person in them, named by role, and a conversation you can recount.
- What changed for the team. Not what you delivered, but what the team did differently afterwards and what happened to the people involved.
An easy trap for a strong individual contributor is to answer every question with their own work: the deal they closed, the system they built, the problem they solved alone. Those answers can be true and impressive and still miss the question. The management interviews guide explains the evaluation model behind this in full; the sections below apply it competency by competency.
Leadership and direction
Question forms:
- Tell me about a time you set a direction your team did not agree with.
- Describe a time you had to lead without formal authority.
Manager-level evidence: what you decided, how you explained it, who pushed back and what you did with the pushback, and what the team did as a result. Leading without authority counts fully if the story shows people changing what they did because of you.
Follow-ups to expect: "What did the people who disagreed do afterwards?", "Were you right?", and "What would you do differently?"
Failure modes: describing a direction you were given rather than one you set; a story with no disagreement in it; and "I got everyone aligned" with no account of how.
Deeper treatment, including examples that work with and without authority and the seniority differences, is on the leadership interview questions page.
Performance and accountability
Question forms:
- Tell me about a time someone on your team was not meeting expectations.
- Describe a time you gave feedback that was hard to hear.
Manager-level evidence: the expectation you set and when, the conversation you had and how soon, the plan and the support, and the outcome whichever way it went. An answer that ends with someone leaving can be a strong answer if the process was fair and the learning is concrete.
Follow-ups to expect: "How did the person react?", "What did the rest of the team notice?", and "What would you do differently?"
Failure modes: fixing the process instead of talking to the person; escalating to HR or your own manager before the direct conversation; and answers where nothing was ever hard to say.
The performance management interview questions page covers underperformance, feedback, accountability and escalation scenario by scenario.
Conflict
Question forms:
- Tell me about a conflict on your team and what you did about it.
- Describe a time you disagreed with a decision from above.
Manager-level evidence: your own part in the conflict, the conversation you had privately and soon, the decision you made, and what changed for the people and the team. For disagreements with leadership, the evidence is making the case with evidence and then committing to the decision.
Follow-ups to expect: "What would you do differently?", "How did you tell your team?", and "Were you right in the end?"
Failure modes: stories in which you won; stories in which you avoided the conversation; and stories in which the other person is the whole problem.
Conflict questions come in five families, each asking for different evidence; the conflict management interview questions page covers all of them with the failure modes and follow-ups for each.
Delegation and developing people
Question forms:
- Tell me about something you delegated that you could have done faster yourself.
- Describe how you developed someone into a bigger role.
Manager-level evidence: what you handed over, including the decision and not only the task, what support you gave, what went wrong and how you handled it, and what the person can do now that they could not before.
Follow-ups to expect: "What did you do when they did it differently from how you would have?", "What did it cost you in the short term?", and "Who else on the team noticed?"
Failure modes: delegating tasks but never decisions; taking the work back at the first mistake; and development described as sending someone on a course.
The delegation interview questions page goes deeper, with particular attention to first-time managers, for whom a delegation story is easy to lack.
Prioritization and decisions under pressure
Question forms:
- Tell me about a time you had to decide what your team would not do.
- Describe a decision you made with incomplete information.
Manager-level evidence: the reasoning, not the choice. What you weighed, whom you consulted, what you dropped and how you told the people affected, and what you would decide now with hindsight.
Follow-ups to expect: "What did you drop, and what happened to it?", "Who disagreed?", and "How did you communicate it?"
Failure modes: presenting a decision as obvious; deciding alone when the story needed a conversation; and priorities that changed without anyone being told.
The prioritization interview questions page covers this competency, including how it is asked of product and project roles as well as people managers.
Stakeholders and influence
Question forms:
- Tell me about a time you had to get another team to change its plan.
- Describe a disagreement with a senior stakeholder.
Manager-level evidence: understanding the other side's constraint before responding, starting from the shared goal, agreeing a path rather than winning an argument, and what you told your own team while it was unresolved.
Follow-ups to expect: "What did you do when they said no?", "Did you escalate, and how?", and "How is the relationship now?"
Failure modes: going around the other person; framing the other function as the problem; and promising what you could not deliver to end the conversation.
The stakeholder management interview questions page covers influence over people you do not manage, across management, product and project roles.
Matching your stories to the questions
The management interviews guide covers how to build a story bank. What this page adds is the matching step: when a behavioral question arrives, decide which competency it is aiming at before you pick the story, because the same story told for the wrong competency loses its point.
A practical way to prepare is a short table of your own: one row per story, one column per competency above, and a tick where the story can honestly serve that competency. Rows with only one tick are fragile stories; columns with no tick are competencies you need another story for. Three to five stories, each with several ticks, cover the page. Keep one row for a story that did not end well: told with what you would do differently and what you have changed since, it serves accountability as well as its own competency.
If you have never held formal reports, the first-time manager interview guide shows how to draw these stories from project leadership, mentoring and peer situations without overstating your role.
How expectations change with seniority
- First-time manager: one real people outcome, told in order, with the conversation in it. Readiness is the question, not track record.
- Experienced manager: patterns and prevention. How you notice problems early, what you do consistently, how the people under you got better.
- Senior manager: system-level answers. Conflicts between managers, organisational causes, and changing the system rather than resolving the instance.
The questions above stay the same at every level; what changes is which story you pick and how far up the causes you go.
Practice the follow-ups
A behavioral answer tends to hold up on the first question and give way on the follow-up, when "what would you do differently" or "how did the person react" arrives and the story has no more detail in it. Rehearse each story spoken, with a follow-up asked immediately after, and notice where the detail runs out.
A manager mock interview built for your target role asks those follow-ups and gives feedback on each answer, so the story that has no second layer shows up before the real interview.
Practice these questions out loud
Reading a list is silent rehearsal. Run a mock interview for your target role and get feedback on every answer.
Start a mock interview
About the author
Mock Interview Pro team · Interview coaching and practice
Mock Interview Pro runs mock interviews and practice sessions with per-answer feedback. Our guides are built from the questions and answer patterns we see in those sessions and reviewed against the platform's coaching standards.
