The STAR Method for Managers: How to Answer Leadership Interview Questions

By Rehearsa Team · 2026-08-18

A manager's behavioural interview is not a harder version of an individual contributor's. It is a different interview wearing the same clothes.

The questions look familiar — "Tell me about a time you handled conflict", "Describe a project you delivered under pressure" — but what the panel is scoring has shifted. They are no longer asking can you do the work. They are asking what happens to a team, a budget and a set of stakeholders when you are in charge of them.

The STAR method still works. You just have to point it at different evidence. If you need the fundamentals first, start with the complete STAR guide, then come back here.

What changes when you interview as a manager

The trap is obvious once you see it: managers who are proud of their hands-on skills answer like the senior IC they used to be. They describe the fix they made personally, not the decision that made the fix possible. The panel hears a strong doer and a question mark over the leadership.

The manager's version of each STAR beat

Situation — lead with scale, not story. Two sentences, and at least one number that sizes the problem. "I inherited a support team of eleven with a 40% annual attrition rate and an SLA we were missing three weeks in four." That is a situation a hiring manager can benchmark.

Task — state your remit and your constraint. Managers are judged on what they did given what they had. Name the mandate and the limitation in the same breath: "I owned the turnaround, with no budget for new hires until the following quarter."

Action — decisions, not tasks. This is where most manager answers fail. Structure the beat as three to four decisions, each with the reasoning behind it, and say who executed. "I ran a diagnostic week of 1:1s, then made three calls: reset the on-call rota, moved two engineers off the roadmap onto tooling for six weeks, and renegotiated the SLA with the commercial team to buy us runway." Delegation is not a weakness in the story — it is the evidence.

Result — three layers. Business result, team result, and what it taught you as a leader. "SLA compliance went from 61% to 94% in one quarter, attrition dropped to 9% over the year, and two of the engineers I moved onto tooling were promoted. It also taught me to renegotiate a commitment early rather than quietly miss it."

That last layer is what separates a manager's answer from a good IC's answer. You are showing that you learn at the level of systems, not tasks.

The eight stories every manager should have ready

Prepare one strong STAR story for each of these. Most manager interviews draw from this list.

1. Turning around an underperformer — the conversation, the plan, the outcome, including the ones that did not work out.
2. Managing out or making a redundancy — handled with candour and care. Panels want to know you can do the hard thing humanely.
3. Delivering under a constraint you did not choose — a cut budget, a lost headcount, a deadline pulled forward.
4. Conflict between two people on your team — how you diagnosed the real issue rather than mediating the surface one.
5. Disagreeing with your own leadership — how you pushed back, and what you did once the decision went the other way.
6. Growing someone — a promotion you engineered, with what you specifically did to make it happen.
7. A decision that was wrong — and the mechanism you changed afterwards so it could not recur.
8. Influencing without authority — the cross-functional win where you had no formal power.

Build them in a grid: question type, story, headline number. The STAR template worksheet gives you the structure to fill in.

Two worked examples

Question: "Tell me about a time you had to deliver with fewer resources than the plan assumed."

Situation. Six weeks into a nine-month platform migration, we lost two of six engineers to a reorg and the delivery date did not move.

Task. I owned the migration end to end, including the commitment made to two enterprise customers.

Action. I re-scoped rather than re-planned. I split the migration into a compliance-critical core and a convenience tier, took the convenience tier off the timeline entirely, and got that agreed with the account team before telling my own leadership. I paired the two remaining senior engineers with the juniors instead of running them separately, which cost throughput for three weeks and bought us competence for the rest. I moved our status update from monthly to weekly so the slippage risk was visible early rather than confessed late.

Result. We shipped the compliance core two days early, the convenience tier landed eight weeks later with no customer escalation, and the pairing decision meant both juniors were running their own workstreams by the next quarter. I now re-scope before I re-plan as a default.

Question: "Describe a time you had to manage someone who was not performing."

Situation. A mid-level analyst on my team of seven had missed three consecutive delivery dates and the wider team had started routing around her.

Task. I was responsible for either fixing the performance or exiting it, and for doing it without the team learning that underperformance is tolerated.

Action. I started with a diagnostic rather than a warning — two 1:1s to understand whether the issue was capability, clarity or circumstance. It was clarity: she had never been given a definition of "done" for her reports. I wrote one with her, set fortnightly checkpoints for eight weeks, and made the standard explicit for the whole team rather than singling her out. I also told my own manager the timeline up front so the outcome would not be a surprise either way.

Result. She hit every checkpoint and was still on the team eighteen months later at the next level up. The "definition of done" doc became the team standard and onboarding time for new analysts dropped by about a third. My lesson: I had assumed clarity existed because I understood it.

Mistakes that cost manager candidates offers

Saying "we" throughout. Managers do this more than anyone, because credit-sharing is a habit. In an interview it erases you. Use "I decided", "I chose", "I asked the team to" — and give the team credit in the Result beat, where it reads as generosity rather than hiding.

Only telling success stories. Senior panels distrust an unblemished record. One well-handled failure with a systems-level fix does more for you than three clean wins.

No numbers. Headcount, budget, timeline, retention, cycle time, revenue influenced. If your answer contains no figures, the panel cannot size you.

Answering at the task level. "I built the dashboard" when the story should be "I decided we needed visibility, scoped it, and had it built in a week." Same project, entirely different candidate.

Running long. Manager stories carry more context, which tempts a five-minute monologue. Keep it to 120 seconds and let the panel pull the thread. See the full list in STAR method mistakes.

How to prepare in a week

Day one, write your eight stories in bullet form with a headline number for each. Day two, cut every Situation to two sentences. Day three, rewrite each Action as decisions rather than activities. Day four, add the three-layer Result. Days five to seven, say them out loud, on camera, timed — reading them back is not practice.

Speaking them is where the gap shows. Practise them out loud with Rehearsa and get scored feedback on structure, clarity and delivery before the panel does it for you.

Related reading: STAR method examples · STAR vs CAR · Free STAR downloads

More STAR Method guides · Start free trial