Delegation questions ask whether you can hand over work and the accountability for it without losing quality. A strong answer names what you handed over, a decision as well as a task, what you kept and why, how you checked the result without taking the work back, and what the person can do now. This page gives thirteen questions with sample answers, then the failure modes, follow-ups, and variants for first-time managers and managers of managers.
Table of Contents
- 13 Delegation Interview Questi...
- How the interview is evaluated
- What delegation questions are ...
- Choosing what to hand over and...
- Handing over the decision, not...
- Checking quality without takin...
- When delegation goes wrong
- Delegating to grow someone
- If you have never had direct r...
- Managers of managers and role ...
- Practice the handover out loud
13 Delegation Interview Questions and How to Answer Them
Question 1
How do you decide what to delegate and what to keep for yourself?
What it tests
Whether you have criteria for the choice, rather than handing over whatever you find tedious and keeping whatever you enjoy.
What a strong answer includes
Gives the rule you actually use in one sentence, then proves it with one thing you handed over and one thing you kept during the same period, so the rule is seen cutting in both directions. Includes what the handed-over work gave the other person, not only the time it freed for you.
Sample answer
I ask two questions: would someone on the team grow by owning this, and would a mistake be recoverable within a day. When I managed a community pharmacy, reordering stock from our wholesaler passed both. It took me most of a morning each week, one of my technicians wanted more responsibility, and a wrong order could be corrected on the next delivery. I gave her the whole thing, including the call on how much safety stock to carry for the lines that ran out in winter. What I kept was the staff schedule, because it decided who worked weekends, and people needed to be able to bring a complaint about it to the person accountable for it rather than to a colleague. She has run the ordering for over a year, and she cut our write-offs for expired stock because she watched the dates more closely than I ever had.
Question 2
What is something you would not hand off, even to a strong person, and why?
What it tests
Whether keeping something is a reasoned judgment about accountability, or a reluctance to let go that you are presenting as a principle.
What a strong answer includes
Names one specific thing, not a category like "strategy" or "anything important", and gives a reason tied to accountability or to the people affected rather than to your own skill. Shows that you delegate the work around that thing, so it is clear the line is narrow and deliberate.
Sample answer
Telling a client that their schedule has slipped. As a site superintendent on commercial builds, I hand a lot to my assistant superintendent: running the morning coordination meeting, sequencing the trades, chasing late deliveries. On one interior build-out he was closer to the detail than I was and offered to call the client about a three week delay on the ceilings. I had him build the recovery plan and sit in on the call, but I made it. The client had signed with me, and bad news needs to come from the person who will still be answerable for it next month. The next time, he presented the recovery plan himself and I only opened the call with the date. I would not hand over the opening, but almost everything after it now belongs to him.
Question 3
Tell me about a decision you used to make that you now leave to someone on your team.
What it tests
Whether you have handed over decision rights and not only tasks, and whether you let the decision stand when it differed from yours.
What a strong answer includes
Names the decision precisely, including the boundary you set around it, such as a budget limit or the one condition under which the person comes back to you. Includes a moment when their decision differed from the one you would have made and says what you did. Ends with how the decision is made now, without you.
Sample answer
As head of a science department in a high school, I used to decide how the department's lab budget was spent each term. I handed that decision to our most experienced chemistry teacher, with one boundary: anything over a quarter of the budget came to me first. In her first term she spent a large share on a class set of data loggers I would not have bought, because I thought the older sensors were adequate. I said that to her once, and then left it. The loggers turned out to be what got two reluctant physics teachers running hands-on labs again, which I had not predicted. She has decided the budget for three terms now, and my only involvement is reading the summary she sends at the end.
Question 4
When you hand something over, how do you make sure the person knows what a finished job looks like?
What it tests
Whether your handover includes an outcome, a standard and a deadline, or only an instruction to go and do the work.
What a strong answer includes
Quotes what you told the person, as close to the words as you can, including what they were free to decide on their own. Gives the gap you found before they started and how you found it, and what the result looked like against the definition you set.
Sample answer
I describe done as something the person could check without me. As a regional sales manager, I handed one of my field reps the renewal for a farm cooperative that had been my account for years. Instead of telling him to look after them, I told him done meant three things: a signed renewal before their budget meeting in March, the two sites that had complained about delivery windows visited in person, and no discount beyond the range I gave him. Then I asked him to tell me back what he would do in his first two weeks. His plan skipped the site visits, so we talked about why they mattered before he started. He renewed the account a month early, and he found a third unhappy site that I had never visited.
Question 5
How do you keep track of work you have handed over without hovering?
What it tests
Whether your oversight is agreed in advance and focused on outcomes, or improvised and focused on how the person is doing the work.
What a strong answer includes
Names the specific measures you reviewed and how often, and how that cadence changed with this person over time. Admits a time you checked more than you had agreed to, and what you did once you noticed.
Sample answer
I agree the checkpoints when I hand the work over, so a check-in is expected rather than a sign I am worried. When I gave one of the engineers on my team ownership of our release process, we agreed I would look at two things each week: whether releases went out on the planned day and whether any were rolled back. I did not review how he ran them. Early on I broke my own rule and started reading the release thread every day, and he asked me, fairly, whether I was going to take it back. I stopped. After two clean months we moved the check to once a month, and now I only hear about a release when something goes wrong.
Question 6
Describe a time delegated work came back below the standard you expected. What did you do?
What it tests
Whether you respond to a quality gap by coaching the person to close it, or by quietly redoing the work yourself.
What a strong answer includes
Names the defect and who noticed it first. Shows the first instinct you had and what you did instead, what you learned about the cause, and whether any of the cause was yours. Ends with the work still owned by the same person.
Sample answer
I ran production at a wholesale bakery and handed the opening shift's quality check to one of my shift leads. In his second week, a batch of loaves went out underbaked to a café customer. My first instinct was to go back to doing the check myself. Instead I asked him to walk me through how he did it, and it turned out he was checking color, which is how he had been taught, and not the core temperature, which is how I checked. I had never told him that. I showed him once, he wrote it into the shift sheet himself, and he called the café to apologize. There has not been another underbaked batch from his shift, and the check is still his.
Question 7
Tell me about a time you delegated something and it did not work out.
What it tests
Whether you can describe a real failure, take your share of it, and show what you changed in how you delegate.
What a strong answer includes
Chooses a failure someone outside the team noticed, so the cost is real. Roughly quotes what you told the person when it went wrong, and names the one piece of the handover you would now set up differently, such as a written checklist or an earlier checkpoint.
Sample answer
I managed a small marketing team and gave a new coordinator our quarterly customer webinar, which I had run four times. I gave her the date and the speakers and told her to ask if she needed anything. She did not ask, because she did not know what she did not know. The invitations went out a week later than they should have, and attendance was about a third of our usual. That was mostly my failure. I had handed over a project I understood as a checklist I had never written down. I wrote it down afterwards, with the dates that actually matter, and for the next webinar we agreed a check-in three weeks out. She ran that one without help, and it had our best attendance that year.
Question 8
Have you ever taken work back after handing it over? Would you make the same call again?
What it tests
Whether you can tell the difference between taking work back because it was right for the team and taking it back because you were uncomfortable.
What a strong answer includes
Says yes if it is true, and gives the reason you gave at the time next to the reason you now think was real, if they differ. Covers whether and when the work went back to the person, and what you said to them when it did.
Sample answer
Yes. I managed the receiving dock at a distribution warehouse and gave the weekly stock counts to a team lead. During a peak month the counts started coming back with large gaps, and I took them back for the rest of the season. I told him it was because of the peak, but honestly it was also because our regional manager was asking me about the gaps and I wanted to be the one answering. Looking back, I would do it differently. The gaps came from two new hires scanning pallets twice, which he would have found if I had asked him to investigate instead of taking the work. When the season ended I gave the counts back to him, with an apology and the question I should have asked the first time.
Question 9
Tell me about a time you gave someone work they had never done before.
What it tests
Whether you use delegation to develop people, and how you set up a stretch so that the person can succeed at it.
What a strong answer includes
Makes the stretch concrete by naming what the person had never done and what could go wrong if they got it wrong. Describes the support you gave for the first attempt and the point at which you withdrew it, and names the responsibility the person now holds permanently.
Sample answer
I was practice manager at a veterinary clinic, and one of our veterinary nurses was excellent with worried owners but had never handled a formal complaint. Complaints came to me. When an owner wrote in angry about a bill that was higher than the estimate, I asked her to handle it, because she was the person on the team owners trusted most. I sat in on her first call and said nothing unless she looked at me. She did once, when the owner asked for a full refund, and we agreed off the call what she could offer. She resolved it with a partial credit and an explanation of what had changed during the treatment. She now handles billing complaints for the practice, and brings me only the ones that involve a refund above the limit we agreed.
Question 10
How do you hand work to someone who says they are already at capacity?
What it tests
Whether you treat capacity as a real constraint to solve, or override it and add the work anyway.
What a strong answer includes
Starts from the person's actual workload rather than your view of it, and names the specific item that came off, who absorbed it or why it stopped, and the conversation that required. Avoids a story where the person simply found the time.
Sample answer
I asked what was on her list before I asked her to take anything else. I led an accounts payable team, and I wanted one of my senior clerks to own supplier onboarding, which I was doing badly because I kept pushing it behind month end. She said she was full, and when we went through her week she was right. About a day a week went on chasing missing purchase order numbers for other departments. I took that off her by agreeing with the department heads that invoices without a number would go back to them rather than to us. With that day back, she took supplier onboarding, and the backlog of new suppliers waiting to be set up was cleared within the month.
Question 11
What do you do when someone does not want the responsibility you are offering?
What it tests
Whether you listen for the reason behind a refusal, and whether you can respect a no without writing the person off.
What a strong answer includes
Reports the reason the person gave, close to their words, and what you changed in the offer because of it: the scope, the support, or who carries the risk. If the answer stayed no, says how you protected the person's standing and who took the work instead.
Sample answer
I ran the grounds crew for a university campus and asked our most experienced groundsman to plan the seasonal planting schedule, which had always been mine. He said no. I asked why, and it was not the work he minded. The last time someone on the crew had planned anything, it went wrong and they were blamed in front of everyone at a team meeting, before my time. So I changed the offer. He would plan it, I would sign it off, and if anything went wrong it was mine to answer for in public. He agreed on those terms. After the first season he stopped asking me to sign it off, and last year he trained a younger crew member to plan the smaller beds.
Question 12
You have not managed people yet. How have you handed work to others?
What it tests
Whether you can find genuine delegation evidence in experience without the title, and state honestly what authority you did and did not have.
What a strong answer includes
Opens by saying you have not had reports, then goes straight to one situation, with the people named by role, the decisions that were yours, and the decisions that belonged to someone else. The result is something the other person could do afterwards, not only a project that finished.
Sample answer
I have not had direct reports, so this comes from training. I am a senior technician in a hospital laboratory, and for the past year I have been responsible for bringing two trainees through their sign-off on our analyzers. I did not choose them and I could not assess them formally, which the lab manager did. What I could decide was what they ran on their own and when. I gave each of them one analyzer's daily quality control to own outright, with a rule that any result outside range came to me before they did anything else. One of them caught a calibration drift before I did, in her third week. Both passed sign-off, and the lab now runs quality control on those analyzers without me.
Question 13
How do you know when one of the managers who reports to you is holding on to too much?
What it tests
Whether you can see delegation problems one level down, and whether you coach the manager rather than going around them to their team.
What a strong answer includes
Names one concrete sign you saw in the team's numbers or behavior, the request you made of the manager, and how you measured whether the change held. Includes what you told your own manager about any short-term dip.
Sample answer
I look at the team underneath, not the manager. As director of customer support, I had four team managers, and one team had the best resolution times and the worst engagement scores. Her agents rarely escalated anything to her, because she had already taken every hard case herself. She worked the longest hours of anyone, and she saw that as the job. I did not tell her agents to stop sending her cases. I asked her to pick the three case types she would hand back to her senior agents, and to track how long she spent on cases for a month. She was surprised by the number. Resolution times got worse for about six weeks, and I told my own manager in advance that they would. The engagement scores on her team rose at the next survey, and two of her senior agents now handle the cases she used to keep.
How the interview is evaluated
What delegation questions are testing
Delegation is easy to answer as a question about assigning tasks: split the work by strengths, set deadlines, follow up. That answer describes allocation. The competency underneath is handing over accountability, so that someone else owns an outcome and makes the calls inside it while you remain answerable for the result.
A delegation answer that holds up has five parts: what you handed over, what you kept and why, how you set the handover up, how you checked the result without taking the work back, and what the person can do now that they could not do before. The sections below take each part in turn, then cover delegation that failed, delegation as development, and how the questions change without direct reports or when you manage managers.
Delegation is one competency within the wider set of manager behavioral interview questions, and the management interviews guide covers the whole interview and how these competencies fit together.
Choosing what to hand over and what to keep
Question forms:
- How do you decide what to delegate and what to keep for yourself?
- What is something you would not hand off, even to a strong person, and why?
Before the handover comes the choice. A good answer gives criteria you can defend: who would grow from owning the work, how recoverable a mistake would be, and where your own accountability cannot move. It also shows that the line is narrow. Keeping one conversation is judgment; keeping every decision that matters is reluctance with a reason attached.
Failure modes: delegating only the work you dislike; naming a vague category like "anything strategic" as the thing you keep; and a list of criteria with no example of applying them.
Follow-ups to expect: "What did you keep last month that you could have handed over?", "Who on your team would disagree with where you draw that line?", and "Has the line moved since you started?"
Handing over the decision, not just the work
Question forms:
- Tell me about a decision you used to make that you now leave to someone on your team.
- When you hand something over, how do you make sure the person knows what a finished job looks like?
This is the center of the competency. Handing over a task means someone else does the work while you still decide. Handing over a decision means they choose, inside boundaries you set, and you live with choices you would not have made. A strong story names the decision rights plainly: what the person could decide alone, the one or two conditions under which they come back to you, and who they answer to for the result.
The handover itself deserves detail too. Describe the outcome you asked for in terms the person could check without you, the constraints, and the date. Asking them to repeat the plan back to you is a simple way to find a gap before it becomes a failure.
Failure modes: dumping work with no context and calling it trust; handing over the task and keeping the decision, so every choice still comes back to you; and overruling the first decision that differs from yours.
Handing over decisions is also how you lead through other people and grow them. The leadership interview questions page covers that side: setting direction and developing people with and without formal authority.
Checking quality without taking the work back
Question forms:
- How do you keep track of work you have handed over without hovering?
- Describe a time delegated work came back below the standard you expected. What did you do?
Oversight is part of delegation, not a sign it failed. The difference between checking and hovering is mostly timing and focus: checkpoints agreed at the handover, looking at outcomes rather than method, and loosening the checks as the person proves the work. When the result falls short, the strong move is to hand the gap back with a specific explanation, and to ask whether the standard was ever stated clearly before assuming it was ignored.
Failure modes: hovering, where you review the method daily; silent redoing, where you fix the work overnight and the person never learns it fell short; and no checks at all, discovered when a customer complains.
Follow-ups to expect: "How did the person react when you raised it?", "How often do you check now?", and "What would have happened if you had not caught it?"
Sometimes a quality gap is not a delegation problem at all. When the person has the standard, the support and the time, and still misses it, the story becomes one about performance, and the performance management interview questions page covers how to tell it.
When delegation goes wrong
Question forms:
- Tell me about a time you delegated something and it did not work out.
- Have you ever taken work back after handing it over? Would you make the same call again?
Prepare a story that went wrong as well as one that went right. The part worth the most time is your share of the failure: the context you did not give, the checkpoint you did not set, the standard you assumed was obvious. Then the change you made to how you hand work over, and ideally a later handover where it worked.
Reclaimed work deserves its own honest answer. Sometimes taking work back is right: a real deadline, a risk the person could not carry yet. Sometimes it is discomfort, or wanting to be the one who answers to your own manager. Being able to tell which one it was, in hindsight, is the point of the question.
Failure modes: a failure that is entirely the other person's fault; a "failure" that turned out fine; and a reclaim you still defend without looking at it again.
Follow-ups to expect: "What did you tell the person?", "Did you give it back?", and "What do you do differently at the start of a handover now?"
Delegating to grow someone
Question forms:
- Tell me about a time you gave someone work they had never done before.
- How do you hand work to someone who says they are already at capacity?
- What do you do when someone does not want the responsibility you are offering?
Delegation is also a way to develop someone: a piece of real work the person has not done, with enough support at the start and less as they go. A strong answer explains why that person and that work, where the stretch was, and the moment they struggled and what you did with it.
Two harder variants test whether you respect the other person's position. When someone says they are at capacity, check the claim with them and make a trade: something comes off before something goes on. When someone does not want the responsibility, ask why before you persuade; the reason may change what you should offer, and a no you respect costs less than a yes you forced.
Failure modes: development that means sending someone on a course; stacking work on the person who never says no; and treating a refusal as an attitude problem.
If you have never had direct reports
Delegation stories are easy to lack before your first management role, but the evidence may already exist. Look for times someone else did work you were answerable for: trainees you brought through sign-off, a project group where you owned the result, contractors or volunteers you coordinated, a peer who took over part of your work while you covered something else.
Be exact about the scope. Say who the people were, what you could decide, and whose authority you were working under. Then tell it with the same parts a manager's answer has: a clear handover, a check, and what the person could do afterwards. The first-time manager interview guide covers how to draw management evidence from experience that did not come with the title.
Managers of managers and role variants
When you manage managers, the delegation question moves one level down. You are handing over whole teams, and the question becomes how your managers delegate. The signals sit in their teams more than in them: escalations that never reach a senior person, a manager working the longest hours on the team, a team that stalls when its manager is away. A strong answer describes coaching the manager through letting go, not reaching past them into their team to fix it.
Question form:
- How do you know when one of the managers who reports to you is holding on to too much?
The core is the same across roles; what changes is the thing that is hardest to hand over.
- Engineering: technical decisions, where the pull to decide yourself is strongest because you may still be the most experienced engineer in the room. The engineering manager interview questions page covers how to show technical judgment while leaving the decision with your engineers.
- Operations: processes you built and know better than anyone, where handing over means accepting a different way of running them.
- Sales: accounts and relationships you own personally, where handing over means introducing someone else to a client who trusts you.
Practice the handover out loud
The place a delegation answer can go vague is the moment you describe what you actually said at the handover. "I set clear expectations" is a summary; the question behind it is what you said. Rehearse the handover conversation itself, in the first person, as well as the story around it, and prepare the failure story as carefully as the success.
A manager mock interview built for your target role can ask the delegation questions and the follow-ups that come after them, with feedback on each answer, so a vague handover or a missing check shows up before the interview does.
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.
