Career journal for

VPs of Engineering

VP work is the org you built and the bets you placed. Both are real and both are hard to make legible at the moment they happened.

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

A captured day for a VP of Engineering

1. 01

   8am: shipped the H2 strategy memo to the board after 14 weeks of synthesis.

2. 02

   11am: 1:1 with Maria (director) on her first VP-track call.

3. 03

   2pm: board prep call with the CEO; the technical pre-read I authored became the canonical board doc.

4. 04

   4pm: closed the VP Platform hire after 14 weeks of search.

What a VP of Engineering captures

• Org-wide reliability and velocity outcomes
• Directors hired and developed
• Engineering operating-system work (review, planning, on-call)
• Exec and board partnerships
• Hiring-bar and culture decisions

Org of 80 hit uptime target (99.98%). 2 directors developed. Re-introduced senior on-call, moved MTTR 47min to 21min.

Promotion rubric, mapped to capture

• Company-scale technical outcomesCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Director-level benchCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Engineering operating systemCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Exec partnershipCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.