Career journal for

Frontend Engineers

Frontend wins compound in numbers nobody screenshots at the time. The LCP move, the bundle reduction, the accessibility fix that quietly opened the product to thousands of users all evaporate by review time.

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

A captured day for a Frontend Engineer

1. 01

   9am: shipped the homepage LCP work. PageSpeed score moved 62 to 91 on mobile.

2. 02

   1pm: design review with Lena on the new modal pattern; her question about focus-trap changed my implementation.

3. 03

   3pm: closed 4 outstanding WCAG violations in the checkout flow.

4. 04

   5pm: paired with Marcus on his first React Suspense boundary.

What a Frontend Engineer captures

• Production features users see
• Core Web Vitals and bundle-size improvements
• WCAG and accessibility audits closed
• Design-system components other teams adopted
• Designer partnerships that scaled

Shipped 7 user-facing features. Moved homepage LCP P75 3.1s to 1.4s. Authored data-table component adopted by 6 product areas.

Promotion rubric, mapped to capture

• User-facing shipped workCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Performance and accessibility winsCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Design-system contributionsCaptured 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.