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. This page gives twelve manager behavioral questions with sample answers, organised by competency, then explains what a manager-level answer contains, the follow-ups and failure modes for each competency, and how three to five stories can cover all of them.
Table of Contents
- 12 Manager Behavioral Intervie...
- How the interview is evaluated
- What makes a behavioral answer...
- Leadership and direction
- Performance and accountability
- Conflict
- Delegation and developing peop...
- Prioritization and decisions u...
- Stakeholders and influence
- Matching your stories to the q...
- How expectations change with s...
- Practice the follow-ups
12 Manager Behavioral Interview Questions and How to Answer Them
Question 1
Tell me about a time you set a direction your team did not agree with.
What it tests
Whether you can make a call your team dislikes, explain the reasoning behind it, absorb the pushback without either caving or steamrolling, and still get the work done.
What a strong answer includes
Names the decision and the reason behind it, says who objected and what their objection actually was, describes the conversation where you heard it and what you changed or held as a result, and ends with what the team did once the work started and how the people who disagreed behaved. It also says plainly whether the call turned out to be right.
Sample answer
I managed a restaurant with a kitchen team of nine, and I decided to cut the weekend menu from two pages to one, because the kitchen kept falling behind on Saturday nights and tables were waiting too long for food. My head chef and one of the senior cooks pushed back hard in the pre-shift meeting, so I sat down with them after service and heard the real objection: the dishes being cut were ones they had created, and nobody had asked them which should stay. I held the decision but changed how we made it. They chose which dishes stayed, and I took the complaints from regulars about missing dishes myself for the first month. The shorter menu held, plates went out on time on Saturdays, and the head chef went on to run the tasting that picked the next season's dishes. The call was right, but if I did it again I would have talked to them before the meeting rather than after it.
Question 3
Tell me about a time someone on your team was not meeting expectations.
What it tests
Whether you had set a clear expectation before the problem appeared, addressed the gap directly and early with the person rather than around them, and stayed accountable for the outcome either way.
What a strong answer includes
Names the gap in output or behaviour rather than the person's character, says when you first noticed it and how quickly you had the conversation, describes the plan and the support you put in place, and gives the outcome honestly, including the case where the person left. A strong version also says what the rest of the team saw and what you did about that.
Sample answer
I ran a retail store, and one of my shift supervisors was leaving the closing cash-up and the stock handover incomplete about half the nights she closed. The opening team had started quietly redoing her work each morning. I talked to her that week rather than waiting for her review. It turned out she had been covering the evening stockroom delivery since a colleague left, and had not told anyone. I moved the delivery to the day shift, and we agreed a specific standard: handover sheet complete and cash-up signed before she left, for four weeks, checked at our weekly catch-up. She met it on all but one night, and on that night she called me before leaving, which was the behaviour I actually wanted. I also told the opening team to stop covering silently, because that was what had kept the problem invisible for a month.
Question 4
Describe a time you gave feedback that was hard to hear.
What it tests
Whether you can say the difficult thing directly to the person, in words specific enough to act on, and whether you stayed with them afterwards instead of delivering it and walking away.
What a strong answer includes
Quotes roughly what you actually said, so prepare that line in words rather than as a paraphrase. Gives the evidence you had, the setting you chose, how the person reacted in the moment, what you asked them to do differently, and what changed over the following weeks. Be honest about a reaction that was not gracious; it is part of the story.
Sample answer
A team lead of mine was excellent technically and was shutting down juniors in design reviews, to the point where two of them had stopped proposing anything. I had sat in on three reviews, so I had specific moments to cite. I told him privately that in those three sessions he had answered his own question before anyone else spoke, and that two people had gone quiet as a result. He did not take it well and said they were simply wrong on the technical points. I agreed that they often were, and said the cost was that we now heard nothing at all. We agreed he would ask two questions before giving his own view. It was awkward for a few weeks. About six weeks later one of the juniors brought a proposal we shipped, and he was the one who backed it.
Question 5
Tell me about a conflict on your team and what you did about it.
What it tests
Whether you moved on the conflict quickly and privately, handled your own part in letting it build, and repaired the working relationship rather than only settling the immediate argument.
What a strong answer includes
Describes what the two people were really disagreeing about underneath the surface argument, what you did first and how soon, the conversation you had with each of them and then together, the decision you made if they could not agree, and how the two worked together afterwards. Own the part you played in letting it grow, and say what you would do earlier next time.
Sample answer
I was the ward manager on a hospital ward, and two of my senior nurses had stopped agreeing on anything at shift handover. It had spread far enough that newer staff were asking to be rostered away from both of them. The surface argument was how handover should be run. Underneath it, one had been made shift lead over the other six months earlier and nobody had said so out loud, including me. I spoke to each of them alone that week, then brought them together with one narrow question: what does a handover look like that both of you would sign off on. We wrote down three rules and I said I would decide any tie. I also told the nurse who had been passed over what the shift lead decision was based on and what would change it, which was a conversation I should have had at the time. Handover went back to being routine, which was the point.
Question 6
Describe a time you disagreed with a decision from above.
What it tests
Whether you can argue a case upward with evidence and then carry the outcome in front of your own team, without either rolling over silently or undermining the decision afterwards.
What a strong answer includes
Says what the decision was and what your objection rested on, how and where you raised it, and what evidence you brought. Spend most of the answer on what happened once the decision stood: what you told your own team, and whether you presented the decision as yours to carry rather than as something imposed on you.
Sample answer
Leadership moved our launch date forward by five weeks to line up with a partner announcement. I thought the quality risk was real, so I asked for twenty minutes with my director and brought the two areas that would be untested at that date, with the specific failure that would show up in each. I asked for one of the two to be cut from scope rather than for the date to move, because I already knew the date was fixed. We cut one. Then I told my team the date, the reason for it, and that I had argued for the cut and got it. I did not tell them I had disagreed with the date itself, because that would have invited them to work as if it might still move. We shipped on the new date, and the cut feature followed six weeks later.
Question 7
Tell me about something you delegated that you could have done faster yourself.
What it tests
Whether you hand over the decision rather than only the task, tolerate a slower and different result while someone learns, and resist taking the work back at the first sign of trouble.
What a strong answer includes
Names what you handed over and, specifically, what you gave up control of. Says what support and what boundaries you set, describes the moment it went differently from how you would have done it and what you did in that moment, and ends with what the person can now do without you. Stating the short term cost plainly is part of the answer.
Sample answer
Our quarterly capacity plan was mine every quarter and took me about two days. I gave it to one of my leads, including the call on which team absorbed the overflow, which was the part that actually mattered. She got the previous three plans, an hour of my time up front, and one rule: talk to the other leads before deciding, not after. She came back with a split I would not have chosen, putting the overflow on the team I thought least able to take it. I asked why instead of reversing it, and her reason was a person on leave that I had missed. I let it stand. It cost me roughly three days of review time that quarter and none in the next one, and she has run the plan four times since without me in the room.
Question 8
Describe how you developed someone into a bigger role.
What it tests
Whether development in your hands means real work with real stakes attached, or courses and encouragement, and whether you were honest with the person about the gap they had to close.
What a strong answer includes
Starts from where the person actually was and what was missing, names the specific work you put in their way to close that gap, describes the honest conversation about what was not there yet, and ends with the role they hold now and what they did to earn it. A case that stalled is worth telling too, if you say what you would change.
Sample answer
One of my support engineers wanted a team lead role and was not close, because he had never had to hold anyone else to a standard. I told him that plainly and named the one gap rather than handing him a list. Over the next two quarters I gave him the on call rota to own, which meant asking peers to swap shifts and telling people when their handover notes were poor. He hated the first month of it. I sat in on two of those conversations and gave him feedback the same day. He also ran our new starter onboarding twice. When a lead role opened about eight months later he applied and got it on his own evidence, and I was not on the panel. He still runs the rota.
Question 9
Tell me about a time you had to decide what your team would not do.
What it tests
Whether you can say no on a stated basis, tell the people who wanted the work what the trade off was, and live with the consequence rather than quietly keeping everything half alive.
What a strong answer includes
Gives the criterion you used, not only the choice you made. Names what you dropped and who wanted it, describes how you told them and what you offered instead, and says what happened to the dropped work afterwards. If the request came back and you had to hold the line again, include that part.
Sample answer
We had four workstreams and enough people for two and a half. I ranked them on a single question: which of these, if we do nothing, costs us a customer this quarter. Two cleared that bar and the internal tooling refresh did not, even though it was the one my team enjoyed most. I told the person who had requested the tooling work myself rather than letting it die quietly, gave her the reason, and offered a two week slot the following quarter if the picture held. She escalated to my director, we had the conversation together, and the decision stood. Both funded workstreams landed on time. The tooling work started eleven weeks later and I made sure the same engineer got it, because I had told him he would.
Question 10
Describe a decision you made with incomplete information.
What it tests
Whether you can decide on a timeline instead of waiting for certainty, what you did to reduce the uncertainty cheaply before deciding, and how you would have known you were wrong.
What a strong answer includes
States what you knew, what you did not, and what it would have cost to find out. Names the deadline that forced the call, the person you consulted, and the smallest thing you did to narrow the risk inside it. Says what your reversal plan was and what you told the team, then gives the outcome honestly, including what changed for the team afterwards and, if the call was wrong, what you did next.
Sample answer
I managed a team of about twenty agents in a customer contact center. One Monday morning the billing queue started building far faster than usual, and nobody could yet tell me why. I had about half an hour to decide whether to move agents off the general queue to cover billing, which would lengthen waits for every other caller, or hold and treat it as a spike. What I knew was that the callers were all asking about the same letter. What I did not know was whether more of those letters were still going out. I called the billing team lead, who could not confirm either way, and asked him to find out by noon. Meanwhile I moved six agents across and told the floor team leads what I had done and that I would move them back at noon unless billing confirmed more letters. Billing confirmed a second batch that afternoon, so the move held. Afterwards I sat down with the agent who had first flagged the pattern, because she had spotted it before our reports did. We made her check part of the morning huddle, and billing agreed to tell us before any bulk letter went out.
Question 11
Tell me about a time you had to get another team to change its plan.
What it tests
Whether you start from the other team's constraint and the shared goal or from your own deadline, and whether the agreement you reached actually held after the conversation ended.
What a strong answer includes
Shows you understood what the other team was being judged on before you asked them for anything, names what you offered or gave up, describes the conversation with the person who owned the decision rather than an email chain, and says what changed in their plan and what the relationship looked like afterwards. If you escalated, say how you did it and who you told first.
Sample answer
We needed an API change from a peer team whose roadmap was full for the quarter. Rather than asking for the change, I asked their lead what the quarter was being judged on, which was latency on their main endpoint. Our request touched that endpoint, so their real objection was risk, not effort. I offered to write the change and the tests myself and to take the on call for that endpoint for two weeks after it shipped. Their lead agreed and put it in the following sprint. It shipped three weeks later and their latency did not move. While it was still unresolved I told my own team we might be waiting a quarter, so nobody built plans on top of it. We have gone back to that team twice since and it was easier both times.
Question 12
Describe a disagreement with a senior stakeholder.
What it tests
Whether you can hold a position with someone more senior, keep the disagreement about the substance rather than the status, and then either move them or commit properly once the decision is made.
What a strong answer includes
Names what the disagreement was about and what was at stake, describes how you made the case, including what you brought and where you had the conversation, and says how you handled the moment they said no. The strongest version shows you moved your own position where their argument was better, and says what you told your team afterwards.
Sample answer
A senior stakeholder wanted a bespoke report built for our largest account, which would have taken roughly six weeks of one engineer. I disagreed and asked for a call rather than arguing over email. I brought two things: what those six weeks would displace, and three questions about what the account actually needed the report to answer. Two of the three answers were already in a dashboard nobody had shown them. He still wanted a version of the third, which was a fair point I had not credited, so we built that one thing in about four days. I told my team the reduced version and that the request had been reasonable, because I did not want them treating that stakeholder as an obstacle.
How the interview is evaluated
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: questions 1 and 2 in the list above are the typical ones. A variant you may hear: "Tell me about a change you had to bring your team through."
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. A story about leading without authority serves here as well, provided it 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: questions 3 and 4 in the list above are the typical ones. A variant you may hear: "Tell me about a time you had to hold someone to a standard they were not used to."
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 is still worth telling 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, except for harassment, safety and other protected issues, which go to HR straight away; 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: questions 5 and 6 in the list above are the typical ones. A variant you may hear: "Tell me about two people on your team who could not work together."
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: questions 7 and 8 in the list above are the typical ones. A variant you may hear: "Who on a team you managed can do more now than when you started, and why?"
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: questions 9 and 10 in the list above are the typical ones. A variant you may hear: "Tell me about a time you had more work than people and had to choose."
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: questions 11 and 12 in the list above are the typical ones. A variant you may hear: "Tell me about a time another team's priorities blocked yours."
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, so you can rehearse questions like these out loud before the real interview.
