Career journal for

Senior Software Engineers

The senior engineer's actual contribution is half decisions and half organizational gravity. None of it shows up in PR titles, and by review time the calibration committee has only the visible artifacts.

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

A captured day for a Senior Software Engineer

1. 01

   9am: wrote the buy-vs-build memo for the auth direction. 2 pages, 3 alternatives weighed.

2. 02

   1pm: senior reviewer on Marcus's L4 promotion case; gave specific examples from his rate-limit work.

3. 03

   3pm: design-doc review for the platform team; my comment about back-pressure pattern changed their approach.

4. 04

   5pm: pairing with Diana on her first staff-level architecture decision.

What a Senior Software Engineer captures

• Multi-month projects owned end-to-end
• Architecture decisions you held the call on
• Engineers leveled with your contribution
• Design docs and RFCs you authored
• Strategic technical bets that compounded

Owned the event-bus consolidation across 3 teams. Authored buy-vs-build memo that saved 1.5 staff-engineer-quarters of work.

Promotion rubric, mapped to capture

• Scope and autonomyCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Technical judgment markersCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Cross-team influenceCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Growth trajectoryCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.