Promotion Packet Template

    Mid → Senior Engineer Promotion Packet

    A Mid → Senior promo packet is the case that you've been operating at Senior for a sustained period — not aspiring to, performing as. The committee looks for independence, technical depth, and the multiplier effect on junior engineers. This template structures all five common sections.

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

    What to include

    Mid → Senior is the most common promo case and the most pattern-matched by committees. They look for: independent ownership of a meaningful surface, technical depth shown in design decisions, code-review quality, mentorship of newer engineers, and consistent delivery. Each section here matches a committee tab.

    Personalize

    Optional · Appears in download

    The template

    01

    Self-assessment narrative

    Your case for the promotion in your own voice — 4-6 paragraphs covering scope of work, technical contribution, leadership moments, and growth.

    • ·Lead with the strongest evidence — a project where you operated independently at Senior scope.
    • ·Cite 2-3 specific shipped projects with metrics and your role on each.
    • ·Reference your mentorship or onboarding work with names.
    • ·Close with what you'd build next if promoted — show you're thinking past the bar.
    02

    Manager letter prompts

    Notes for your manager's recommendation letter. Send these alongside your self-assessment to make their writing easier.

    • ·Top 3 projects you shipped this cycle, with the specific decision points your manager observed.
    • ·Examples of your judgment under ambiguity — moments when you decided rather than escalated.
    • ·Evidence of multiplier effect — engineers whose code/decisions improved because of your reviews.
    • ·Areas of growth from last cycle and the receipts that you closed them.
    03

    Peer feedback structure

    Suggested peers to request feedback from, and the prompts to send them. Pick 3-5 across teams.

    • ·Cross-team partners who saw your collaboration (PMs, designers, adjacent engineers).
    • ·Junior engineers you mentored — their growth is the strongest peer signal.
    • ·A skip-level or staff+ engineer whose review you've contributed to.
    • ·Send each peer: 'name 2 moments where I worked at Senior scope and 1 area you'd want to see grow.'
    04

    Scope evidence

    Artifacts that document your work — design docs, RFCs, post-mortems, talk recordings.

    • ·Links to 2-3 design docs you authored that shipped.
    • ·Any RFC where you ran the discussion and the team adopted your recommendation.
    • ·Post-mortems you wrote or led.
    • ·Internal talks, lunch-and-learns, or docs others now reference.
    05

    Committee anticipation notes

    Prep for the calibration conversation — likely concerns the committee will raise, and the receipts that address each.

    • ·What's the weakest part of your case, and what's the strongest counter-evidence?
    • ·Any rating you got last cycle below Meets — what changed?
    • ·Any project that slipped this period — what did you do about it?
    • ·If the committee says 'not yet,' what's their most likely reason and how would you address it next cycle?

    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've been operating at the Senior level for some time and would like to be promoted.

    Strong

    Over the last 12 months I've owned the search service end-to-end (3 launches, 2 incidents handled, full design ownership). Two months ago I was the team's first choice when the staff engineer rotated off — I held the surface for 6 weeks without escalation. The committee will see this as Senior scope; my manager and the staff engineer corroborate it in their letters.

    Weak

    My peers think I'm doing great work.

    Strong

    Of the 5 peer reviewers, 4 cite the same example: the migration RFC where I pushed back on the original direction in week 2 and shipped a smaller-scope alternative that closed in 6 weeks instead of 14. Two cite mentorship moments with new hires by name.

    Weak

    I plan to take on more responsibility as a Senior.

    Strong

    If promoted, the next 6 months I want to own the rate-limiting platform spinoff — the work is sitting between two teams without a clear owner, and I've already drafted the design memo with engineering management's go-ahead. Success: design doc Q1, beta Q2, two teams onboard by Q3.

    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 Mid → Senior Engineer 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

    Senior → Staff Engineer

    Brag Doc

    IC → Engineering Manager

    Brag Doc

    Manager → Director

    Brag Doc