Component Library Insurance Platform

Tasked with building a complete component library for a major insurance company, I started from zero: setting up Webpack configuration, solving integration challenges with a legacy stack running Node 10 and class-based React components, and designing a component API that could work across old and new codebases. Despite being nominally supported by a 15-person team across other products, I worked entirely alone. I had to self-define tasks, write my own specs, run refinements, estimate effort and make UX decisions independently after the UX Lead went on extended leave mid-project. I delivered the library with full Storybook documentation and a migration of one existing product flow. I left the engagement shortly after due to poor engineering practices and team ethics.

Key outcomes

• Delivered a full component library from Webpack setup to Storybook documentation
• Solved complex integration challenges with a legacy stack: Node 10, old React, class components
• Self-managed the entire project lifecycle: task definition, refinement, estimation and delivery
• Migrated one existing product flow to the new component system
• Made UX decisions independently after the UX Lead went on extended leave mid-project