Interview questions for delegation: 14 questions, an in-tray exercise and a 1–4 scale
On this page
- Delegation, defined as something you can observe
- Ten behavioral questions, with follow-up probes
- Four situational questions, including an in-tray exercise
- A ten-minute in-tray exercise
- What strong and weak answers sound like
- A 1–4 anchored rating scale for delegation
- Common interviewer mistakes with delegation
- Questions people ask
Interview questions for delegation have to get underneath two answers that sound good and often are not. "I trust my team completely" can mean the candidate hands work over and disappears. "I stay close to the detail" can mean they never really hand anything over. Delegation sits between the two: giving someone ownership of a piece of work, with a clear outcome and the authority to deliver it, and support that matches the risk. Below are fourteen questions, ten behavioral and four situational, with follow-up probes, plus a ten-minute in-tray exercise, illustrative strong and weak answers, a 1–4 anchored scale and common interviewer mistakes.
Delegation is easily blurred with two neighbors. Prioritization is deciding which work matters most; time management is how candidates organize their own hours. Delegation is deciding who should do the work and how to set them up to succeed, which is why it matters most for managers and senior individual contributors.
Delegation, defined as something you can observe
Definition: delegation is handing ownership of work to someone else with a clear outcome and the authority to deliver it, supporting them in proportion to the risk, and letting them do it their way. Four behaviors make it visible:
- Choosing what and to whom. Delegating for a reason, such as the person's development, their strengths or the candidate's need to focus elsewhere, and keeping work that only the candidate should do.
- Defining the outcome and decision rights. Saying what done looks like, by when, and which decisions the person can make alone.
- Matching check-ins to risk. Staying closer when the person is new to the work or the stakes are high, and stepping back as they show they can handle it.
- Letting go. Accepting a different approach that still meets the outcome, handling mistakes without taking the work back, and making sure the person gets the credit.
Ten behavioral questions, with follow-up probes
-
Tell me about the most important piece of work you delegated in the last year.
Probes: Why that person? What exactly did you tell them at the start? -
Describe a time you delegated something and it went wrong.
Probes: What did you do when you found out? What would you set up differently now? -
Tell me about work you kept for yourself that, looking back, you should have delegated.
Probes: Why did you keep it? What did keeping it cost you or the team? -
Describe delegating something to a person who had never done it before.
Probes: How often did you check in at first? When and how did you step back? -
Tell me about a time you took work back from someone.
Probes: What triggered it? What did it do to that person's confidence, and what did you do about that? -
Describe how you made clear what someone could decide without you.
Probes: What was outside their authority? Did they ever cross the line, and what happened? -
Tell me about delegating work you were very good at yourself.
Probes: How did they do it differently from you? What did you do when you would have done it another way? -
Describe delegating something mainly to develop a person rather than to save your own time.
Probes: What did they learn? How did you know? -
Tell me about a result delivered by someone you delegated to.
Probes: Who presented it? How did you make sure their part was visible? -
Describe what you handed off when you moved into a bigger role.
Probes: What did you give away first? What did you find hardest to let go of?
Four situational questions, including an in-tray exercise
-
The in-tray exercise, described below.
Probes: What would you tell the person taking the pipeline report? Which item would you be most nervous about handing off? -
"Someone you handed a project to is two weeks from the deadline and has not shared any progress."
Probes: What do you do today? What should you have set up at the start so this could not happen? -
"Your manager gives you a project and says, 'Just do it yourself, it's faster.'"
Probes: When would you agree? What would you say if you disagreed? -
"A new team member tells you they are overloaded, and you need to hand them a new project."
Probes: What would you ask them? What could come off their plate, and who decides?
A ten-minute in-tray exercise
Give the candidate a list of the week's work for the role and a short description of the team. For a recruiting manager role, an example list might be:
- Approve next quarter's hiring plan with the finance partner.
- Produce the weekly pipeline report for the leadership team.
- Run first-round interviews for two open roles.
- Hold a difficult performance conversation with a direct report.
- Update the team's interview question bank.
- Respond to a vendor's renewal proposal.
- Present hiring progress at the all-hands meeting.
- Onboard a new recruiting coordinator who starts on Monday.
Ask which items they would delegate, to whom, and what they would say when handing each one off. There is room for judgment, but some patterns are telling. The performance conversation should stay with the candidate. Delegating the pipeline report or the question bank to a team member who wants to grow is a reasonable development move if it comes with a clear standard. A strong candidate asks about the team's capacity and experience before deciding, and describes the handoff, not just the assignment. The same list format works for any role; swap in the real recurring work of the job.
What strong and weak answers sound like
These are illustrative answers to question 2, written to show the difference in shape rather than quoted from real candidates.
Weak: "I delegated a client presentation to a junior colleague and it didn't go well, so I took it back and did it myself. Lesson learned: some things you just have to do yourself."
The candidate drew the opposite of the useful lesson. There is no account of what the colleague was told at the start, no check-in before the presentation, and the fix was to stop delegating.
Strong: "I asked a recruiter on my team to run the intake meeting for a new senior role. I told her the goal and the deadline but not what a good intake looked like to me, and I didn't review her question list beforehand because I didn't want to hover. The meeting missed the compensation discussion entirely. I didn't take the role back. We wrote a one-page intake checklist together, I sat in silently on her next intake, and she ran the follow-up with the hiring manager herself. Now when I delegate something new, I share what good looks like and agree one checkpoint before the moment that matters."
The strong answer takes ownership of what was missing from the handoff, keeps the person in the role, adds support proportionate to the risk and changes the candidate's own practice.
A 1–4 anchored rating scale for delegation
| Score | Anchor |
|---|---|
| 1 — No evidence | Does the important work themselves, or hands off tasks they dislike with no outcome or authority defined. Takes work back when something goes wrong. |
| 2 — Limited | Delegates tasks but not ownership: the person executes while the candidate keeps every decision. Check-ins are the same regardless of person or risk, either constant or absent. |
| 3 — Solid | Delegates for a stated reason, defines the outcome and what the person can decide alone, and adjusts check-ins to the person's experience and the stakes. |
| 4 — Strong | Does everything at 3, delegates deliberately to develop people, handles a delegated mistake without taking the work back, and makes sure the person gets the credit. |
General guidance on anchored scales is in our guide to interview rating scales. Delegation often appears alongside coaching on manager scorecards; the coaching ability questions and the behavioral anchors library help keep the two lines distinct, and the free scorecard builder will put them on one card.
Common interviewer mistakes with delegation
- Treating dumping as delegation. Handing off work the candidate dislikes, with no reason or support, is not the competency. Ask why that task went to that person.
- Rewarding "I trust my team, I don't check in." With a new person or a risky task, that is abdication. Ask how they knew the work was on track.
- Rewarding control as rigor. "I review everything before it goes out" can be appropriate for some work, but as a blanket rule it means nothing was really delegated.
- Ignoring the hand-back. Taking work back is the most common delegation failure and the one candidates least often volunteer. Question 5 asks about it directly.
- Judging the in-tray by your own answer. Reasonable candidates will make different choices. Score the reasoning and the handoff, not whether they matched your list.
For a full manager loop that includes delegation alongside coaching, feedback and hiring, see the interview guide for people managers.
Questions people ask
What is the difference between delegation and prioritization?
Prioritization decides which work matters most and what gets dropped. Delegation decides who should own a piece of work, what authority they have and how much support they need. A candidate can rank work perfectly and still hold onto everything, or hand work off without the clarity the other person needs.
How do I tell good delegation from dumping unwanted work?
Ask why that task went to that person. Good delegation has a reason tied to the person's development, their strengths or the candidate's need to focus on work only they can do. Dumping has no reason beyond the candidate not wanting the task, and it usually comes with no clear outcome or authority attached.
Should individual contributors be asked about delegation?
Senior individual contributors often hand work to junior colleagues, contractors or agencies, so the same questions apply with a smaller scope. For entry-level roles, delegation is usually not worth a scorecard line.
Is a candidate who checks in often a poor delegator?
Not necessarily. Frequent check-ins are right for someone new to a task or for high-risk work. Score whether the check-ins matched the person and the risk, and whether they reduced as the person showed they could handle it.