Tell me about yourself as an engineering manager

EM loops want three things in the opener: a system you still understand, a team result, and how you hire or coach.

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 36 seconds · 89 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 · 146 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 · 223 words

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

I'm looking for an engineering manager role. For the past 11 years I've worked as an engineering manager of a 7-person payments team. Before that, this is the work that got me here. I led a billing migration with zero downtime and no weekend page. I also grew two engineers into on-call owners so I was no longer the only debugger. I then cut incident pages in half by deleting a noisy dependency. None of that is a title. It is the work I can walk through. The through-line is keeping the technical tradeoff visible while the team is tired. The future I'm aiming at is an engineering manager role, because this org is in the middle of a payments rewrite, which is a mess I have already run. 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

You do not have time for the full staff-plus-manager biography. Pick the team, the operational result, and one people result. A migration that landed and an engineer who grew into on-call ownership is a complete past.

Keep a technical detail so they believe you can still be in the review. One clause. The system design round will go deep. The opener should not become a design review.

Why this org should mention the hard part of their team: scale, a rewrite, a new manager bench, on-call pain, a product bet. Read the posting and use their noun.

What to emphasize

Team size and charter.
One technical result and one people result.
The specific mess this job is.

What to leave out

A pure people answer with no system.
A pure coding answer with no team.

Sample 60-second answer

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

I'm looking for an engineering manager role. For the past 11 years I've worked as an engineering manager of a 7-person payments team. Before that, this is the work that got me here. I led a billing migration with zero downtime and no weekend page. I also grew two engineers into on-call owners so I was no longer the only debugger. The through-line is keeping the technical tradeoff visible while the team is tired. The future I'm aiming at is an engineering manager role, because this org is in the middle of a payments rewrite, which is a mess I have already run. 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 36 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

Should I say I still code?

If you do, say how: reviews, a small change, incident command. If you do not, do not claim a weekend hobby as the job.

What if I managed managers?

Say so and reduce the story to the org result. Skip the nested team chart. One number and one decision.

How long is too long?

Past 90 seconds you are taking the behavioral question's time. Sixty is the default even for EM loops.