Liberty Mutual

Role

Front-End Engineer

Timeline

2010 - 2013

Team

  • Mobile Product
  • Design
  • Engineering
  • QA

Skills

  • Front-End Engineer
  • Design Engineer
  • JavaScript, HTML, CSS
  • UI/UX Implementation

Outcomes

  • Founding mobile team for Liberty Mutual’s first consumer app (since evolved)
  • Claims FNOL / submission flows and reusable wayfinder (stepper) UI
  • Helped the app reach a 4.8/5 App Store rating with tens of thousands of reviews
  • Front-end implementation from design comps in HTML, CSS, and JavaScript

I was on the founding mobile development teamthat shipped Liberty Mutual's first consumer mobile app—the one that introduced millions of policyholders to self-service on iOS and Android. The product has since been redesigned and rebuilt many times over, but that original release is where I cut my teeth shipping production UI alongside designers and PMs.

Day to day I translated Photoshop comps into interfaces with HTML, CSS, and JavaScript, pairing with design and product to keep interactions clear and fast on early hardware.

Early Liberty Mutual mobile app home screen on an iPhone
Early app-era home screen mockup—Manage Policy, Billing, ID cards, and claims entry in one vertical hub.

First notice of loss & claims submission

One of the projects I'm most proud of is the claims submission workflow—also known as first notice of loss (FNOL)—inside the mobile app. Policyholders were often stressed; the flow had to orient them quickly, capture the right photos and details, and show unmistakable progress. The composite below shows Safeco Express Estimate (a Liberty Mutual company) flows that reflect the same FNOL patterns we were pushing on at the time.

Sequential mobile screens for Express Estimate FNOL: intro, damage photo guidance with step thumbnails, camera capture, and summary with estimate
FNOL / photo capture sequence: guided damage photos, thumbnail "wayfinding" across steps, and estimate handoff.

Wayfinder (stepper) in CSS and JavaScript

I built the horizontal stepper—we also called it the wayfinder—that anchored the Report a Claim experience: linked segments for Intro, Scene, Vehicles, and beyond, with a clear active state as customers moved through FNOL. It was implemented with CSS and JavaScript (no component libraries on those builds). Below is a Tailwind recreation—a flat segmented control you can tap to explore states; the reference screenshot above shows the original chevron styling in the shipped app.

Interactive recreation — tap a step

Active step: Vehicles · 3 of 5

Liberty Mutual Report a Claim header with chevron wayfinder showing Vehicles as the active step
Reference capture from the live-style Report a Claim header—the wayfinder across Intro, Scene, Vehicles, More Info, and Final.

That mix of systems thinking, visual craft, and plain old DOM scripting is where I realized I wanted to keep living at the intersection of design and engineering.

Download on the App StoreGet it on Google Play