Interview Recipes
Menu

Leadership & developing others

How a candidate multiplies other people: setting direction others can act on, delegating real ownership instead of tasks, and coaching people measurably beyond where they started.

Leadership interview questions carry the highest fluff risk of any competency: vision, style, and philosophy all interview beautifully and predict nothing. The usable evidence is in what a candidate has actually done with responsibility for other people, especially when it was uncomfortable.

That is what this set asks for. The questions walk through the unglamorous core of the job: telling someone their work isn't good enough, staying with a performance problem that didn't improve on the first try, noticing a strong person quietly slipping, and investing in someone's growth they can now point to. Others test the edges of authority, like moving people who don't report to you, or forcing a decision through and paying for it. The call they would take back is often the most revealing answer in the set.

Match seniority before you pick: several cards are marked senior or junior, and their anchors assume that level. Two or three questions is enough when you use the probes.

Interview for it when

They set direction for other people, or are expected to grow them.

Where this competency comes from

Leadership is not our invention: it shows up, under different names, in every major validated competency framework. Our ten-competency taxonomy keeps what at least three of the four agree on. The full reasoning is in why structured interviews work.

The Great Eight (Bartram, 2005)
Leading & Deciding
UK Civil Service Success Profiles
Leadership, Developing Self and Others
US OPM general competencies
Leadership
Google’s four attributes
Leadership (emergent)

In the O*NET content model it maps to the work activities Developing and Building Teams · Training and Teaching Others · Guiding, Directing, and Motivating Subordinates · Coaching and Developing Others and the work styles Leadership Orientation.

O*NET mapping adapted from the O*NET content model (U.S. Department of Labor), used under CC BY 4.0.

The questions

All 12 cards in full: the question, why it works, the follow-up probes, and the anchors to score against. Still choosing competencies? Plan the interview first.

leadership

Walk me through a time you set direction for a team. What did you do to make it something people could act on?

Why this works

Anyone can write goals; the leadership work happens between the statement and someone's Tuesday morning — translating, involving the team, checking what actually landed. Asking how the direction became actionable exposes whether it ever lived anywhere outside the document.

Follow-up probes

  • How did the people doing the work shape it?
  • What call did someone make without you because the direction made it obvious?
  • How did you notice when it stopped guiding decisions?

What good looks like

The team involved in shaping the direction rather than receiving it, goals framed as choices and trade-offs instead of slogans, a concrete decision someone else made correctly from it, and an adjustment when it went stale.

Red flags

Direction that existed only in a document or kickoff meeting, team members who couldn't have repeated the goal a month later, or every subsequent decision still routed through the candidate personally.

Card page · add to recipe

leadership

Tell me about a change you had to carry to your team knowing they wouldn't welcome it. How did you bring people along?

Why this works

Leading change isn't announcing it — resistance to a decision people didn't make is the default, and managing it can't be answered with change-management vocabulary alone. The signal is whether objections got engaged or waved off, and whether anything in the rollout actually moved in response while the destination held.

Follow-up probes

  • What was the loudest objection, and what did you do with it?
  • What did you adjust in response — and what stayed non-negotiable?
  • Who came around last, and what finally moved them?

What good looks like

The strongest objection stated fairly and answered on its merits, something real adjusted in response to feedback, the core decision held without apology, and the team observably working the new way — not just no longer complaining.

Red flags

Compliance mistaken for buy-in, resistance explained away as people fearing change, or the candidate distancing themselves from the decision — "I told them it came from above" — to stay liked.

Card page · add to recipe

leadership

Describe a piece of work you handed over completely — decisions included — when doing it yourself would have been faster. How did you set the person up?

Why this works

Handing over tasks is easy; handing over decisions is the real transfer, and "faster to do it myself" is precisely the moment weak delegators take work back. What was set up front — context, boundaries, check-ins — separates real ownership from both hovering and abdication.

Follow-up probes

  • Which decisions were genuinely theirs, and which did you keep?
  • When they hit trouble, what did you do — and deliberately not do?
  • What was harder to let go of than you expected?

What good looks like

A real outcome at stake rather than busywork, the boundaries of ownership made explicit at handover, trouble met with questions instead of a takeover, and the person visibly more capable at the end than at the start.

Red flags

Delegation that was task assignment with every decision retained, a quiet takeover at the first wobble, work tossed over the wall with no context and called empowerment, or the result presented upward as the candidate's own.

Card page · add to recipe

leadership

Tell me about a time you delegated something and it went wrong. Where did the failure actually start?

Why this works

Failed delegation gets retold as the other person's failure; asking where it started forces the harder audit — the match of person to work, the context withheld, the check-in skipped. Whether the candidate changed how they hand work over afterward is the durable signal.

Follow-up probes

  • What did the person need that you didn't provide?
  • When did you first sense trouble, and what did you do?
  • What do you now do differently when handing work over?

What good looks like

Their own contribution named without prompting — a rushed handoff, missing context, the wrong match of person to work — early warning signs acknowledged, the recovery handled without scapegoating, and a changed handover habit since.

Red flags

A story entirely about the other person's shortcomings, a first check-in that turned out to be the deadline, or the lesson drawn being "do the important things yourself".

Card page · add to recipe

leadership

Tell me about telling someone on your team their work wasn't good enough. How did you say it?

Why this works

Most managers describe the feedback model they were taught, not the conversation they had; asking for the words surfaces whether the message survived delivery or was softened past recognition. What happened in the following month shows whether the feedback was an event or the start of a plan.

Follow-up probes

  • What did you actually say, as close to word-for-word as you can?
  • How did they respond in the room?
  • What changed in their work in the month after?

What good looks like

The problem stated plainly and about the work, not the person, the reaction absorbed without retreating from the point, concrete next steps agreed, and a specific improvement visible afterward.

Red flags

Feedback so cushioned the person left unaware there was a problem, a conversation that happened months after the issue first appeared, or "the conversation" turning out to have been an email.

Card page · add to recipe

leadershipsenior

Tell me about a person you managed whose performance stayed low despite your efforts. Walk me through what you tried, in order.

Why this works

One good feedback conversation is rehearsable; a months-long marginal performer tests the whole toolkit — diagnosis, explicit expectations, real support, and the honesty to conclude it isn't working. The order of what they tried reveals whether there was a plan or just accumulating frustration.

Follow-up probes

  • What did you check first — expectations, skills, or workload?
  • What did you put in writing, and when?
  • Where did it end up, and was that the right outcome?

What good looks like

A work-focused diagnosis before any judgment, expectations made explicit and documented early, genuine support given a fair window, and a clear endpoint reached — improvement, a role change, or a managed exit — rather than years of drift.

Red flags

Straight to formal process with no real coaching attempt, the mirror case — low performance absorbed by the rest of the team while the conversation never happened — or a diagnosis that never got past "they just weren't motivated".

Card page · add to recipe

leadershipsituational

One of your strongest people has gone quiet, and their work has visibly slipped over the past month. What do you do?

Why this works

There's no procedure for this dilemma: move too fast and it reads as surveillance, wait and the slide compounds — and the wrong move of prying into someone's private life is temptingly close. It also works for candidates stepping into their first lead role, who have no management history to describe.

Follow-up probes

  • What do you say in that first conversation, and where does it happen?
  • They say everything's fine. Now what?
  • What do you watch for afterward, and for how long?

What good looks like

The change raised early, privately, and factually — observations about the work, not theories about the person — an open door offered without prying into causes, support aimed at the work itself, and a follow-up planned rather than assumed.

Red flags

Waiting for the next review cycle to mention it, opening with guesses about the person's private life, treating "everything's fine" as case closed, or reaching for formal warnings on a previously strong performer as the first move.

Card page · add to recipe

leadership

Tell me about someone whose growth you deliberately invested in. What can they do now that they couldn't before?

Why this works

"I develop my people" is a value statement; a name, a plan, and a before-and-after is evidence. The closing clause forces the measurable — coaching either moved someone's capability or it didn't — and what the investment cost the candidate shows whether developing others was a priority or a byproduct.

Follow-up probes

  • What did you do beyond encouragement — assignments, coaching, protection?
  • How did you pick the stretch for that particular person?
  • What did it cost you — time, delegated work, risk?

What good looks like

A specific person and a deliberate plan — stretch assignments with a safety net, coaching in the moment, visibility passed on — a before-and-after an outsider could verify, and a real cost to the candidate accepted along the way.

Red flags

Development that amounts to approving a course, credit claimed for someone who grew on their own, growth described only in confidence gained rather than capability, or no specific person coming to mind.

Card page · add to recipe

leadership

Tell me about a time your team's morale genuinely sank — a bad stretch, a loss, a departure. What did you do about it?

Why this works

Motivation is where interviews produce the most theater — pep talks and pizza. Real morale repair starts with finding the actual cause and usually costs something: an irritant removed, pressure absorbed, a workload renegotiated. Genuine fixes are specific; theater is generic.

Follow-up probes

  • What was actually behind the dip, and how did you find out?
  • What did you change, as opposed to say?
  • How did you know it was working?

What good looks like

The cause diagnosed by asking and watching rather than assumed, at least one structural change alongside the encouragement, bad news still delivered straight through the rough patch, and a believable account of when and how the team turned.

Red flags

Morale treated as an events problem — team lunches while the cause stayed untouched — relentless positivity that ignored what everyone in the room knew, or the dip blamed entirely on the people feeling it.

Card page · add to recipe

leadershipjunior

Describe a time you ended up leading people who didn't report to you and didn't have to listen. How did you get them moving?

Why this works

Removing authority isolates the actual leadership: credibility, clarity, and follow-through are all that's left to work with. It travels well to early careers — project and student work counts — and how the group came to accept the candidate's lead says more than any title would.

Follow-up probes

  • Why you — what made the others go along with it?
  • Tell me about the person who was hardest to bring along.
  • What did you do when someone didn't do their part?

What good looks like

Legitimacy earned through visible work — a plan others could follow, blockers cleared, first hand up for the worst task — resistance met with persuasion and adjustment, and delivery without ever borrowing someone else's authority.

Red flags

"Leading" that was assigning tasks nobody had agreed to, escalation as the only tool for a lagging peer, or the group's outcome quietly retold with a single protagonist.

Card page · add to recipe

leadershipsenior

Tell me about a time you overruled your team and used your authority to force a decision through. What did that cost you?

Why this works

Sometimes consensus fails and rank is the tool left. The signal isn't whether the candidate used it but whether they knew its price — trust spent, dissent driven underground — and paid it deliberately. A leader who reports no cost either didn't notice or overrules too often to feel it.

Follow-up probes

  • What had you tried before pulling rank?
  • How did you deliver the decision to the people who disagreed?
  • What did you do afterward for the relationship — and did it work?

What good looks like

Persuasion genuinely exhausted first, the overrule delivered with reasons and without triumph, the cost named honestly, and deliberate repair afterward — including revisiting the call when the team turned out to be right.

Red flags

Rank as the first resort, "no negative consequences" delivered with a straight face, dissenters recast as not team players, or a decision that never really stuck because nobody believed in it.

Card page · add to recipe

leadership

Tell me about a call you made while leading people that you'd take back. What did it cost the team?

Why this works

Leadership mistakes have a blast radius — other people absorbed the cost of this one, which makes the honest version harder to tell than an individual failure. Whether the candidate names that cost plainly, and what they run differently now, separates reflection from a rehearsed humble-brag.

Follow-up probes

  • Who bore the consequences, and what did that look like for them?
  • When did you realize, and what did you say to the team?
  • What do you run differently today because of it?

What good looks like

A decision with real stakes owned in the first person, its cost to others stated without flinching, some repair attempted at the time, and a specific changed practice today — not just "I learned to listen more".

Red flags

A mistake chosen for being flattering, the cost to others glossed over, blame drifting to circumstances or the team by the end of the story, or a lesson that stays abstract.

Card page · add to recipe

Often assessed alongside

A good interview covers four to six competencies, chosen for what the job turns on. Roles that need leadership usually also lean on:

Hiring for a role that turns on leadership?

Plan the interview and three short steps will work out which competencies your role needs, no account required. Or subscribe and get new vetted questions and interview guides as we publish them.