Career journal for

Software Engineers

By performance review season the engineer who shipped six months of work cannot recall the specific PRs, the specific incident saves, or the cross-team unblocks that made the year matter.

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

A captured day for a Software Engineer

1. 01

   8am: pushed final review on the rate-limit PR. Diana caught a race condition I had missed.

2. 02

   11am: paired with Marcus on his first incident; we found the root cause in 12 minutes flat.

3. 03

   3pm: wrote the post-mortem; runbook entry I added has already been used twice this week.

4. 04

   5pm: scoped next week's migration with Priya over Slack; her question about back-pressure changed the design.

What a Software Engineer captures

• Shipped features with measurable outcomes
• Code-review feedback that changed designs
• On-call saves and post-mortems
• Refactors that compounded across the team
• Cross-team dependencies you unblocked

Reduced p99 latency 45% on POST /transaction. Mentored 1 junior. Authored on-call runbook adopted across 3 services.

Promotion rubric, mapped to capture

• Technical impactCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Code quality and reliabilityCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Cross-team collaborationCaptured 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.