Career journal for

CTOs

CTO work is the company's technical bets and the bench you built. Neither shows up in any single artifact and both disappear from board memory quickly.

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

A captured day for a CTO

1. 01

   8am: shipped the technical pre-read for next week's board meeting.

2. 02

   10am: 1:1 with VP Eng on the H2 hiring plan; agreed on the staff-engineer bench priority.

3. 03

   2pm: board prep call with the CFO and CEO; my section drove the strategic-investment conversation.

4. 04

   4pm: drafted the H1 2027 platform-direction memo for the December all-hands.

What a CTO captures

• Multi-year technical bets owned
• Engineering-org outcomes (reliability, velocity, hiring)
• Board pre-reads and exec memos authored
• VP-level bench developed
• Technical-direction memos that became company plan of record

Authored H2 technical strategy (board adopted). Engineering hit all 4 committee-target reliability metrics. Closed VP Platform hire (14 weeks).

Promotion rubric, mapped to capture

• Company technical strategyCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Engineering org performanceCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Board and exec partnershipCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Director and VP developmentCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.