Career journal for

QA Engineers

QA prevents outcomes. The bugs you caught do not get a parade, and the incidents that did not happen are invisible to calibration.

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

A captured day for a QA Engineer

1. 01

   9am: caught a payments-flow regression in the staging build before release.

2. 02

   12pm: shipped the new visual-regression test framework; the team has already caught 3 layout bugs.

3. 03

   3pm: paired with Marcus on his first E2E test for the search flow.

4. 04

   5pm: wrote the post-mortem for the prior-week incident that the team's testing should have caught.

What a QA Engineer captures

• Bugs caught before production
• Test framework and tooling work
• Automation coverage growth
• Release-quality metrics
• Engineer-coaching on quality patterns

Caught 23 pre-production regressions worth ~$340K in prevented incidents. Moved E2E automation coverage 41% to 68%.

Promotion rubric, mapped to capture

• Quality outcomesCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Test infrastructureCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Bug-prevention workCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Cross-team partnershipCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.