Career journal for

Principal Engineers

At Principal, your IC craft is one of many inputs and your real contribution is the memo and the meeting. Without a private capture habit, the whole year disappears into invisible influence.

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

A captured day for a Principal Engineer

1. 01

   10am: posted the data-store consolidation memo for final exec review.

2. 02

   1pm: technical-strategy review with the CTO on the H1 2027 platform direction.

3. 03

   3pm: senior+ promotion review board; gave the deciding feedback on James's principal case.

4. 04

   5pm: design review on the multi-region replication pattern; my comment changed the approach for 4 teams.

What a Principal Engineer captures

• Architectural decisions spanning multiple orgs
• Technical-strategy memos that shaped how engineering thinks
• Senior engineers whose growth you shaped
• Patterns and conventions used company-wide
• Bets killed at the architectural level

Company committed to data-store consolidation (3 orgs aligned). Killed 2 build-it-yourself bets saving $4M in opportunity cost. 3 engineers promoted at senior+ band.

Promotion rubric, mapped to capture

• Company-scale technical betsCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Multi-org leverageCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Engineers leveled at scaleCaptured 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.