Career journal for

Staff Engineers

Staff engineers' work is mostly other people's work plus the architectural calls that prevented bad directions. Both vanish into invisibility by the time the next review cycle starts.

Bloom is the career journal built for the moments the work actually happens, not the night before the review.

A captured day for a Staff Engineer

1. 01

   9am: shipped the v3 of the event-bus contract memo after 4 rounds of feedback from senior engineers.

2. 02

   12pm: 1:1 with Marcus on his L5 case; specifically the migration he just shipped.

3. 03

   3pm: cross-team architecture review; my framing of back-pressure became the team's canonical answer.

4. 04

   5pm: killed the proposed ML-infra rebuild in a memo; reallocated 4 engineers.

What a Staff Engineer captures

• Architectural bets that compounded
• Memos and strategy docs the org committed to
• Engineers whose growth you shaped at scale
• Cross-team patterns you authored
• Decisions that outlived the project

Authored event-bus strategy memo; org committed. Mentored 3 engineers through L5/L6 promotions. Killed 2 build-it-yourself bets that saved $3M.

Promotion rubric, mapped to capture

• Technical strategy and architectureCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Cross-team multiplier effectCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Mentorship and judgment loaningCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Durable technical influenceCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.