Promotion Packet Template

    IC → Engineering Manager Promotion Packet

    The IC → Manager case is different from level promotions: it's a *track transition*, and the committee wants evidence you'll be a competent manager, not just a competent senior IC. Readiness signals matter more than technical achievement. This template captures the five categories of evidence committees look for.

    Fill it in below. Saves to your browser automatically. Download when you're done.

    What to include

    Manager-track committees evaluate readiness, not just performance. They look for: hiring loop participation, mentorship outcomes with measurable improvement, conflict-mediation moments, comfort with ambiguous people decisions, and a credible answer to 'why management?' Each section maps to one signal category.

    Personalize

    Optional · Appears in download

    The template

    01

    Self-assessment & 'why management' narrative

    Your case for the transition — why you want it, why now, and what evidence shows you're ready.

    • ·Lead with your honest answer to 'why management?' (not 'I want to lead' — what specifically draws you in?).
    • ·Cite the 2-3 specific moments that built your conviction — hiring loop, mentorship, conflict mediation.
    • ·Reference engineers whose growth you've directly influenced, by name.
    • ·Acknowledge what you'll give up (technical depth, hands-on code) — committees trust candidates who name the tradeoff.
    02

    Manager letter prompts

    What your current manager should corroborate to show your readiness.

    • ·Cases where you've made management-shaped decisions (e.g., navigating a peer conflict, raising a performance concern).
    • ·Examples of you operating as 'shadow tech lead' — coordinating, unblocking, sequencing.
    • ·Feedback you've delivered to peers that was hard but landed well.
    • ·Your manager's honest read on what gap remains and how you'd close it.
    03

    Peer & mentee feedback

    Junior engineers you've mentored are the highest-signal feedback source. Their trajectory is the strongest evidence.

    • ·Engineers you've onboarded — their ramp time and current trajectory.
    • ·Peers who've worked with you in cross-team contexts where coordination mattered.
    • ·Send mentees: 'what's one thing you do differently because of how Alex coached you, and what would you have wanted more of?'
    • ·Send peers: 'where have you seen Alex operate beyond IC scope, and any case where you wished they'd shown more management readiness?'
    04

    Trial-management artifacts

    Concrete evidence you've already been doing some of the work — hiring, planning, performance conversations.

    • ·Hiring loops you've participated in. Number of interviews conducted, hires you championed.
    • ·Planning or roadmap meetings you've facilitated.
    • ·Any 1:1s or career conversations you've held with reports of your manager.
    • ·On-call leadership or incident-command experience.
    05

    Committee anticipation notes

    IC → Manager transitions are scrutinized heavily — and rejected for a single weak signal in any of three areas.

    • ·Have you had a difficult performance conversation? What was the outcome?
    • ·Have you delivered hard feedback that wasn't well-received initially?
    • ·Have you actively recruited (sourcing, not just interviewing)?
    • ·Most likely committee concern: are you running toward management for the right reason? Have a specific, non-prestige answer.

    Your entries save automatically in your browser. Nothing is sent anywhere.

    Opens your browser's print dialog · Choose "Save as PDF"

    Weak vs. strong bullets

    The format does the easy part. The bullets carry the weight. A few examples to set the bar.

    Weak

    I'm interested in management because I want to have more impact.

    Strong

    I've sat with the 'why management' question for 18 months. The honest answer: the part of my IC work I've enjoyed most lately is the cross-team coordination on the auth migration — the unblocking, the sequencing, the difficult conversation with the security team. The technical decisions felt easier than usual. I'm not running toward management for prestige; I'm running toward the work I've found I'm pulled to.

    Weak

    I've mentored junior engineers.

    Strong

    Onboarded 4 engineers in the last 18 months. Priya joined Q1 last year — I paired daily for 3 weeks, weekly after. She shipped her first production change in week 4 (team median 7), led her own RFC in Q3, and is now mentoring Marcus. Her growth review last cycle cited me by name.

    Weak

    I'm ready for management responsibility.

    Strong

    Trial-management evidence: ran the team's hiring loop for 6 months (8 candidates interviewed, 3 hired, 2 retained at 1 year); facilitated the Q3 planning meeting after my manager was out sick; held weekly 1:1s with two new hires during onboarding by manager request. None of this was assigned — I asked for it.

    Manual template vs. Bloom generated report

    Manual promotion packet

    • Works when you already remember the right examples.
    • Requires manual sorting, rewriting, and evidence cleanup.
    • Best for a one-time draft or printable structure.

    Bloom promotion evidence

    • Starts from the work you captured when it happened.
    • Organizes entries by goals, skills, impact, and review period.
    • Turns daily evidence into shareable summaries and PDF reports.

    The promotion case writes itself, if the daily work is captured.

    Promo packets are won on evidence — the daily moves nobody remembers six months later. Bloom captures them as they happen. By the time you sit down to submit, the scope evidence, peer-feedback prompts, and impact bullets are already in your share sheet. Ready to copy in.

    Get Bloom for iPhone

    Free to start · iPhone · iOS 17+

    Build the evidence before you need the template

    Templates help with format. A career journal helps with memory. Use these pages together: learn the structure, generate a quick outline, then keep the source material current in Bloom.

    Brag document guide

    What to include and how to write stronger bullets.

    Brag doc generator

    Turn role, goals, and wins into an outline.

    Bloom career journal

    Capture the evidence that feeds your promotion packet.

    Frequently asked questions

    Can I use this IC → Engineering Manager template for a promotion packet?▾

    Yes. Use it to organize scope, impact, feedback, and next-level evidence. Promotion packets work best when the claims are supported by dated examples.

    Is Bloom a brag doc app?▾

    Yes. Bloom is a career journal and brag doc app that captures daily wins and turns them into promotion evidence, reports, and review summaries.

    What is the difference between a brag doc and a promotion packet?▾

    A brag doc is the running evidence bank. A promotion packet is the formal case. The brag doc feeds the packet.

    More engineering templates

    Mid → Senior Engineer

    Brag Doc

    Senior → Staff Engineer

    Brag Doc

    Manager → Director

    Brag Doc