Engineering Manager promotion case: proving team and org impact

Updated · YouDeserveNow editorial

Manager promotions are judged on what your team achieves and how well you grow people, then increasingly on influence beyond your team. The trap is writing about activities like running 1:1s and planning instead of the results those activities produced.

What the committee is looking for

The holes that sink most cases

  1. 01

    Describing management rituals

    1:1s, standups, and planning are expected. Committees want the outcome they produced.

  2. 02

    Team credit with no management lever

    Show the decision or change you made that caused the team outcome.

  3. 03

    People growth without specifics

    "Grew the team" needs names or roles, promotions, and what you specifically did.

Before and after

Highlighted brackets are the facts you need to supply. Never fill them with numbers you cannot back up.

Before

Ran planning for the team.

After

Reset the team's planning around [goal], cutting committed-vs-delivered slippage from [before] to [after] over [quarters] while the team shipped [result].

Before

Grew my reports.

After

Supported [number] engineers to promotion through explicit growth plans and stretch projects; retained [X of Y] reports during [period].

A structure that works

  1. Summary of the level and your scope
  2. Team outcomes with the management decision behind each
  3. People: growth, hiring, retention, performance management
  4. Org influence beyond your team
  5. Upward and peer feedback

Frequently asked

Can I take credit for my team's results?

Yes, when you show the lever you pulled: the priority you set, the risk you removed, the person you placed, or the process you changed.

Examples for this role

Templates

More guides