Career journal for

Engineering Directors

Director work is leverage that compounds slowly and disappears from individual memory quickly. The bets you funded, the bets you killed, the engineers you grew all blur together by the next planning cycle.

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

A captured day for a Engineering Director

1. 01

   9am: shipped the H2 platform-consolidation memo to the VP.

2. 02

   12pm: 1:1 with Sarah (eng manager) on her first hiring loop.

3. 03

   3pm: architectural review with the platform team; my redirect saved them a quarter of work.

4. 04

   5pm: built Marcus's L5-to-L6 case with the CTO over a 30-min call.

What a Engineering Director captures

• Org-wide engineering outcomes
• Manager and senior IC development
• Architectural bets funded or killed
• Operating-discipline rituals shipped
• Cross-functional partnership at leadership level

Org of 22 shipped 18 user-visible releases. Hit committee uptime target (99.98%). 3 managers leveled with my contribution.

Promotion rubric, mapped to capture

• Org-level outcomesCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Hiring and team-buildingCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Technical-strategy contributionCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Operating cadenceCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.