Skip to content

Stories for a manager round

A behavioral story told from the manager's seat: the size and shape of the team, the cause you found behind the symptom, the plan you made with the person, and what happened to them, the team and the work.

On this page

What it is

A manager story is a behavioral example in which your actions were a manager's actions: what you noticed about a person or a team, what you decided, who you talked to and what you agreed. The shape is still STAR, but the Action beat holds conversations, plans and decisions instead of code. Google's structured interviewing guide says that for people managers it looks for the ability to empower a team, shape a longer-term vision and develop direct reports, and that its questions carry predetermined follow-ups meant to pull out detail. One published guide to engineering manager loops lists the prompts it sees most: an underperformer, tough feedback, a conflict between two engineers, influence over a team you didn't own, and growing someone into a leadership role.

What to includeWhat it sounds likeWhy it helps the interviewer

Scope

"Seven engineers, two of them senior, working with the platform and data teams."

They can weigh the story against the level they're hiring for.

The cause

"The missed deadlines turned out to come from a second project nobody had told me about."

They see diagnosis, not a template plan applied to a symptom.

Timing

"I raised it in our next one-on-one, about two weeks after I first saw it."

They learn whether you act on early signs or wait for a crisis.

The plan, with the person

"We agreed she'd hand back the second project and I'd take that conversation with the other manager."

They see what each of you committed to, and that it wasn't imposed.

Dignity

"I said it directly, in private, and the team heard about the change from her."

They see how you treat people when the news is hard.

Alignment

"Their goal that quarter was fewer pages, and the fix cut their pages too."

They see agreement built on the other team's goals rather than on your title.

Outcome

"She was back to pace in a month and led the next release; the team shipped on time."

They can tell what changed for the person, the team and the work.

Why the cause matters more than the fix. A drop in output is a symptom. Underneath it there is usually something specific: unclear priorities, a skills gap, a role the person has outgrown, a hidden second workload, or something at home. Amazon's leadership principles describe leaders who stay connected to the details and are skeptical when the metrics and the anecdote disagree. Our advice: say how you found out (a one-on-one, reading the work, asking a peer) and what you found, then let the plan follow from that. A plan that matches the cause shows judgment; a plan that would fit any underperformer shows a process.

Scope is the first thing to state. GitLab's description of its engineering manager role covers safeguarding the team's health, owning delivery of product commitments, and coordinating across departments. Those are three different axes of reach, and the interviewer can't place your story on any of them until you give numbers: how many people reported to you, at which levels, whether any of them managed others, and which teams outside yours were involved. One sentence is enough.

Candor and dignity are the same beat. Amazon's Earn Trust principle pairs speaking candidly with treating others respectfully, and asks leaders to be vocally self-critical even when it's awkward. In a story that means two things to say out loud: that you told the person plainly what you saw, and where and how you did it. A conversation held in private, with the person deciding what the team would hear, keeps their standing. Saying what you got wrong yourself (noticed late, assumed the wrong cause) reads as candor rather than weakness.

Influence stories turn on the other team's goals. The same principles ask leaders to act for the whole company rather than their own team, to challenge decisions respectfully, and then to commit once the decision is made. For a cross-team story that gives a clean structure: what the other team was trying to achieve, how your ask served it (or what you traded to make it serve it), where you disagreed, and what you did after the decision went against you. An escalation can be the right ending, but a strong answer shows what you tried before it.

When to use it

Use this shape when the prompt is about a person or a team you were responsible for: an engineer who was struggling, feedback that was hard to give, two reports in conflict, a promotion or a departure, a team you had to carry through a bad stretch, or another team you needed to move without owning it. Those are the prompts that one guide to engineering manager loops reports as recurring, and they share a property: the interviewer wants to see your judgment about people, which the symptom-and-fix version of the story hides.

Use it also when you're moving up a level. For a role that manages managers, the scope line changes: how many managers, how many engineers under them, and which of the decisions you made yourself versus through a manager. The cause-and-plan beats stay, but the person in the story is often a manager, and the plan is about how they'd handle their own report.

When not to

A hypothetical. "What would you do if an engineer on your team stopped delivering?" asks how you think about a new case, and Google's guide treats hypotheticals as a separate kind of question from behavioral ones. Lead with your approach (what you'd find out first, the options, how you'd choose) and offer a real case briefly as evidence. See Answering a hypothetical.

The technical round of a manager loop. The guide to engineering manager interviews cited above describes loops that keep a technical round alongside the people rounds. There, a story about a hard technical call should spend its time on the trade-off and the reasoning, and a people-process shape would bury it. Use Explaining a decision instead.

A story where you did the work yourself. Fixing the outage personally or writing the design doc is an individual contributor story even if you held the manager title. It can be the honest answer to some prompts, but in a people round it tells the interviewer little about how you manage. Pick a story where the work went through someone else.

You haven't managed anyone yet. A tech-lead story can carry a first manager interview, and the strong version says plainly what authority you did and didn't have. Don't dress it up as a management story: a follow-up about the performance review or the compensation conversation will find the gap.

A narrow follow-up. When the interviewer asks what the person said when you raised it, answer that. Restarting the whole arc spends the time they set aside for depth.

Compared

ChoiceWhat it looks likeWhen it's the right callWhen it isn't

Full arc in about two minutes

Scope, first sign, cause, plan, outcome, then stop.

An open prompt ("tell me about a time you managed someone who was struggling").

A narrow follow-up, where it repeats what they've already heard.

Headline, then let follow-ups drive

Two sentences on what happened and the outcome, then wait.

The interviewer has said they'll dig in with questions, as structured loops with preset follow-ups do.

An interviewer who doesn't follow up; the story then reads as thin.

Act at the first sign

You raised it within a week or two of noticing.

The sign is clear (missed commitments, a change in behavior) and the cost of waiting is a crisis.

One noisy data point. Then say how long you watched, and why.

Align on their goals

You framed the ask around what the other team needed that quarter.

The default for any cross-team story; it shows influence that doesn't depend on a title.

A deadline or a safety issue left no time. Then say what you tried first and why you escalated.

A story where the person left

The honest ending: a transfer, a managed exit, a resignation.

It's your clearest example of diagnosis, candor and follow-through, and you can say what you'd do earlier next time.

You can't name what you'd change. Then it's a story about an outcome, not about your judgment.

A tech-lead story

You led a team's work without being anyone's manager.

A first manager role, with the missing authority stated plainly.

A role that assumes you've run reviews, compensation and exits.

In a picture

Scope and reachFirst signCause, how foundTalk and planOutcomePersonTeamWork
The arc of a manager story: scope first, then the sign you acted on, the cause you found, the plan you made with the person, and three outcomes.

How to say it in an interview

The common mistake

Quiz

Which opening gives the interviewer the most to weigh your story against?
An engineer's output dropped. Which line shows the diagnosis the interviewer is after?
Another team wouldn't prioritize a fix your team needed. Which account shows alignment rather than authority?
Your clearest underperformer story ends with the person leaving the company. What should you do with it?

Related

Sources

  1. A guide to structured interviewing for better hiring practices (Google re:Work)
  2. Amazon Leadership Principles: Values and company culture
  3. Engineering Manager (The GitLab Handbook, job description library)
  4. Engineering Manager Interview Questions: leadership stories under the microscope (DEV Community)
Sign in to report a mistake