Tell me about yourself for a manager interview

Managing is a result that showed up in other people's work. The opener should have your decision and their output.

Build your answer

Target role The job you are interviewing for. Years of experience Years in this kind of work. Use 0 for a first role or a career change. Current role or background A field, a path, or a short phrase.

Win 1 Include a number. Win 2 Optional. Win 3 Used in the long version.

Key strength One habit, not five adjectives. Why this company or role A reason that would be wrong for a different employer.

Runs in your browser. Nothing you type is uploaded.

30-second version

About 37 seconds · 92 words

A short cut for a recruiter screen.

Stop after one result. A short screen does not need the second story.

60-second version

About 58 seconds · 145 words

The default. Present, then past, then future.

If they lean in, drop the second result and spend the time on how the first one happened. Leave duties from the job description out.

90-second version

About 89 seconds · 222 words

A longer cut when they ask you to walk through it.

I'm looking for an engineering manager role. For the past 4 years I've worked as an engineering manager of a 7-person backend team. Before that, this is the work that got me here. One result was split one overloaded team into two pods and lifted on-time delivery from 70% to 91%. I also promoted two engineers into scope they now own without me. I then cut regrettable attrition to zero over the last four quarters. None of that is a title. It is the work I can walk through. The through-line is making the priority obvious so people can disagree with it early. The future I'm aiming at is an engineering manager role, because this team is growing its first managers, and I want to build that bench. The first thing I'd measure is the constraint the team already feels. The numbers in those results are ones I can defend, including what I owned. The engineering manager role is the move, and the results are how I know I can do the work. I can say any of those results more slowly, with the owner and the number intact. I would use the same judgment on the next engineering manager problem. The work I want next is still engineering manager work: a clear owner, a number, and a decision I can explain.

They can interrupt. Go present, then proof, then why this role. When they ask, go from the headline number to the decision you made.

When you can say the minute without the page, practice it live with Luna. It hears the question and helps you keep a line. 24 hours free.

How to answer it for this role

Do not spend the minute on your individual-contributor highlight reel unless you are interviewing to be a player-coach and you say so. A manager answer names the team, the hard call, and what changed: delivery, quality, attrition, a person who grew into scope.

Be careful with credit. "I grew revenue 30%" is often the team's number. "I split the team into two pods, and the on-time rate went from 70% to 91%" is closer to a management result. You should be able to say what you did on the Tuesday it was going badly.

The future beat is the team you want to lead, including the hard part: hiring, a turnaround, a first-time manager bench, a team that has to work with sales. Generic "I love developing people" fits every packet.

What to emphasize

Team size and what they were accountable for.
A decision that was unpopular or costly.
The kind of team this job is.

What to leave out

A list of reports as status.
Taking a team metric with no mechanism.

Sample 60-second answer

This is the sample loaded into the builder above. About 58 seconds, 145 words. Replace every fact with yours before you practice it.

I'm looking for an engineering manager role. For the past 4 years I've worked as an engineering manager of a 7-person backend team. Before that, this is the work that got me here. One result was split one overloaded team into two pods and lifted on-time delivery from 70% to 91%. I also promoted two engineers into scope they now own without me. The through-line is making the priority obvious so people can disagree with it early. The future I'm aiming at is an engineering manager role, because this team is growing its first managers, and I want to build that bench. In the job I'd bring that strength to the team's current goal, and I'd report what moved. I have the detail under each number, including what I would measure again. That is the minute: the engineering manager work, the proof, and the reason.

The 30-second cut is about 37 seconds. The longer cut is about 89 seconds. Both use the same facts in the same order. Read the longer structure guide if you want the timing rules in full: how long the answer should be.

Tips before you say it

Say the 60-second version out loud before you edit it. A sentence that looks fine on the page often runs long or sounds like a memo.
One number per win. “Improved the process” is a claim. “Cut hold time from 6 minutes to 2” is a result you can be questioned on.
Stay in order: present, past, future. If you start with where you grew up, the interviewer is waiting for you to arrive.
Leave a door open and then stop talking. The extra story you add in the silence is usually the one you did not prepare.
Keep your part separate from the team’s. “We launched” collapses the first follow-up. “I cut the scope, engineering shipped it” survives.

Other roles

Questions people ask

What if I am a first-time manager?

Say first-time. Use the project where people already followed your plan, and be honest that the title is new. Borrowed executive language is easy to spot.

Should I mention someone I had to let go?

Not in the opener, unless the job is a turnaround and you can discuss it with discretion. It is a follow-up story, not the hello.

How do I avoid sounding like I don't do the work anymore?

One clause on how you still engage with the craft, then back to the team result. The mix depends on whether the job is a pure manager role.