Promotion Packet Template

    Software Engineer (entry to mid) Promotion Packet

    The entry-to-mid software engineer promo is about demonstrating you can own work end-to-end. The committee is looking for evidence that you have moved past needing prescribed task descriptions, that you can scope and execute features with judgment, and that the work you produce is starting to multiply other engineers' time rather than consuming it. The template below structures that evidence.

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

    What to include

    The four things calibration committees weigh at this transition are: scope and autonomy (can you own a multi-week feature without a senior holding your hand?), technical judgment (do you make architecture choices that hold up?), cross-team influence (do other engineers reach out to you?), and growth trajectory (are you on a curve that justifies the title bump?). Concrete artifacts beat narrative; numbers beat adjectives.

    Personalize

    Optional · Appears in download

    The template

    01

    Scope and Autonomy Evidence

    Multi-week or multi-month work you owned without senior babysitting.

    • ·Pick the largest project you owned end-to-end. What was its scope? Who else was involved?
    • ·What decisions did you make without escalating to a senior? Which would you defend in committee?
    • ·What surprised you about the execution that required judgment, not just code?
    02

    Technical Judgment Markers

    Architecture or design choices that held up.

    • ·What design doc did you author or substantially shape this period?
    • ·What technical choice did you make where the easy path was wrong and you took the harder one?
    • ·What technical debt did you avoid creating that a less-senior version of you might have shipped?
    03

    Cross-Team Influence

    Evidence other teams or senior engineers seek you out.

    • ·Who outside your team has consulted you for code review, design feedback, or debugging help?
    • ·What cross-team meeting did you contribute substantively to (not just attend)?
    • ·What internal docs or RFCs did you author that other teams reference?
    04

    Growth Trajectory and Peer Comparison

    Evidence the curve justifies the title.

    • ·What were you not able to do six months ago that you do routinely now?
    • ·Which senior engineer on your team would say you operate at their early-mid level today?
    • ·What feedback have you received that suggests the next title fits?

    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

    Owned a project.

    Strong

    Owned the multi-region rate-limiter rollout end-to-end across 11 weeks. Authored the design doc (3 architectural alternatives weighed), shipped it in 4 PR-stages without breaking any consumer service, and resolved 2 production incidents without escalation. Senior reviewer Diana said the design doc was 'staff-quality reasoning at L4.'

    Weak

    Helped other teams.

    Strong

    Was consulted 7 times over the period by engineers on Identity, Billing, and Catalog teams for cache-invalidation patterns (came out of the rate-limiter work). Two of those consultations turned into RFCs they shipped against, both of which referenced my original design doc.

    Weak

    Got better at code review.

    Strong

    Switched from 'lgtm with one nit' to multi-pass technical review six months ago. Of my last 40 review comments, 31 resulted in design changes the author thanked me for. Manager flagged the shift specifically as L4-ready behavior.

    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 Software Engineer (entry to mid) 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

    IC → Engineering Manager

    Brag Doc