Promotion Packet Template

    Senior → Staff Engineer Promotion Packet

    A Senior → Staff promo packet is fundamentally a scope case: did your work change the trajectory of multiple teams, not just yours? Committees expect organizational impact, durable technical leadership, and influence that operates without authority. This template structures the case around those three.

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

    What to include

    Staff promotion bars are unforgiving on scope — sustained multi-team influence is the price of entry. Self-assessment should lead with org-level impact. Manager letter should corroborate scope. Peer feedback should come from outside your immediate team. Scope evidence should include artifacts that ship across teams.

    Personalize

    Optional · Appears in download

    The template

    01

    Self-assessment narrative

    Your case for Staff — 5-7 paragraphs leading with org-level impact, technical leadership, and the trajectory you've set.

    • ·Lead with the org-level outcome — what shipped that wouldn't have shipped, or shipped worse, without your influence.
    • ·Cite 2-3 specific cross-team or org-wide initiatives you drove.
    • ·Reference your technical leadership — RFCs, design reviews, technical strategy docs you authored.
    • ·Close with where you'd take the technical direction in the next year if promoted.
    02

    Manager letter prompts

    What your manager should specifically corroborate to make the strongest case.

    • ·Scope-of-influence examples — initiatives where your input changed the direction of work in another team.
    • ·Specific RFCs or design docs you authored or substantially shaped that the org adopted.
    • ·Cases where leadership relied on your judgment for a decision they could have made alone.
    • ·Your effect on senior engineers' growth — not juniors, peers.
    03

    Cross-team peer feedback

    Peers to request feedback from. For Staff, the weight is on cross-team — your own team's praise carries less.

    • ·Staff+ engineers in adjacent teams who've seen your work.
    • ·Engineering managers outside your team who've worked with you.
    • ·Senior PMs or design leads who've been in your meetings.
    • ·Prompts to send: 'where have you seen Alex operate at Staff scope, and what's one situation that pushed your thinking forward?'
    04

    Scope and trajectory evidence

    Artifacts that prove sustained, multi-team influence.

    • ·RFCs you authored that affected multiple teams.
    • ·Technical strategy memos cited by leadership.
    • ·Talks, internal posts, or open-source contributions with reach beyond your team.
    • ·Quantified business outcomes tied to work where you were a key contributor.
    05

    Committee anticipation notes

    Prep for the calibration conversation — Staff cases are scrutinized heavily on scope and durability.

    • ·Is your scope concentrated in one big project, or distributed? Distributed is stronger.
    • ·Have you shown sustained impact (multiple cycles), or one strong cycle?
    • ·Any case where you reached past your remit and stepped on a peer's toes?
    • ·The most likely 'not yet' from this committee — what's the counter-evidence?

    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 made significant impact across multiple teams.

    Strong

    Over the last 18 months I've shaped 3 cross-team initiatives: the auth-service consolidation (eng-wide, $1.2M infra savings), the observability stack migration (4 teams, cut MTTR 38%), and the on-call rotation redesign (8 teams, 60% drop in pages). For each I authored the RFC, ran the cross-team alignment, and stayed on as the technical reference through delivery.

    Weak

    My peers value my contributions.

    Strong

    Of 6 peer reviewers (4 from outside my team), 5 cite the auth-service work; 3 cite specific moments where my pushback or proposal changed the direction of their team's quarter. The Director of Infrastructure called my technical-strategy memo the most useful planning input of Q3.

    Weak

    I want to do more strategic work as a Staff Engineer.

    Strong

    If promoted, my 6-month focus would be the platform-team-split RFC — engineering leadership has flagged the current monolithic ownership as a scaling risk, and I'm the consensus pick to author the proposal. Success: RFC published Q1, decision Q2, transition plan 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 Senior → Staff 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

    Mid → Senior Engineer

    Brag Doc

    IC → Engineering Manager

    Brag Doc

    Manager → Director

    Brag Doc