Career journal for

Backend Engineers

Backend work is half what shipped and half what did not break because of you. The 2am page that saved $40K in lost transactions is gone from memory by Friday.

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

A captured day for a Backend Engineer

1. 01

   9am: ran the second cutover phase of the Postgres migration. Took 23 minutes, no customer-side errors.

2. 02

   12pm: on-call paged at 11am; root-caused a cache stampede in 18 minutes.

3. 03

   3pm: reviewed Marcus's first PR on the new event-bus pattern; gave detailed feedback on retry logic.

4. 04

   5pm: wrote the runbook entry for the cache-stampede recovery pattern.

What a Backend Engineer captures

• Services and APIs you owned
• Latency, throughput, error-rate moves
• Database and queue work
• Internal libraries other teams adopted
• Incident response and post-mortems

Migrated primary user database (11 weeks, zero downtime). Cut p99 latency 45%. Authored feature-flags library now used by 11 services.

Promotion rubric, mapped to capture

• Systems shippedCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Performance and reliability winsCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Data-layer workCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Platform contributionsCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.