Career journal for

Data Engineers

Data engineering wins compound when nobody notices the pipeline broke. The SLA you held is invisible until the day it slips.

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

A captured day for a Data Engineer

1. 01

   9am: shipped the dbt-test framework; 3 analysts have already added tests to their models.

2. 02

   12pm: incident review on yesterday's pipeline failure; root caused the schema-drift issue.

3. 03

   3pm: paired with Sarah (analyst) on her first incremental model.

4. 04

   5pm: optimized the slowest mart query (cut runtime 18 min to 4 min).

What a Data Engineer captures

• Pipelines and warehouses owned
• Data-quality and SLA outcomes
• Internal tooling other teams adopted
• Migrations and modernizations
• Analyst and DS partnerships

Migrated event-tracking pipeline (84% faster). Built dbt-test framework adopted across 6 marts. Hit 99.97% pipeline SLA.

Promotion rubric, mapped to capture

• Pipeline reliabilityCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Data-platform contributionsCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Cross-team supportCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Performance and cost winsCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.