Career journal for

DevOps Engineers

DevOps wins are inverse work. The deploy nobody noticed because it did not break is the work that should be celebrated and never is.

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

A captured day for a DevOps Engineer

1. 01

   8am: shipped the deploy-time fix; team Slack reaction was immediate.

2. 02

   11am: incident review for yesterday's cache event; my proposed cooldown logic was accepted.

3. 03

   2pm: paired with Marcus on his first Terraform module.

4. 04

   4pm: closed the SOC 2 access-review automation; auditor cited it as 'strongest control improvement of the period.'

What a DevOps Engineer captures

• Infrastructure migrations and upgrades
• Uptime and MTTR improvements
• CI/CD pipeline work
• Cost-optimization wins
• Tooling and platform improvements other engineers use

Cut deploy time 63%. Moved uptime 99.94% to 99.98%. Reduced cloud spend $640K annualized through right-sizing across 12 services.

Promotion rubric, mapped to capture

• Reliability and uptimeCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Deployment velocityCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Cost and efficiency winsCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Developer-experience improvementsCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.