CS-01 / Project dossier

Modernizing an Insurance Customer Portal with Micro-Frontends and 90% Test Coverage

Architectural reengineering of Línea Directa Aseguradora’s customer-facing portal to improve modularity, reuse, testing, and long-term maintainability.

Industry
Insurance
Role
Frontend Developer
Engagement status
Current engagement
Situation
A customer-facing insurance portal needed a more modular frontend architecture that could support independent teams and long-term product growth.
Contribution
Micro-frontend and hexagonal architecture practices, reusable modules, Storybook, testing conventions, technical refinements, reviews, and developer guidance.
Outcome
Approximately 90% frontend unit-test coverage at a documented stage, stronger reuse and consistency, reduced coupling, and a more maintainable delivery foundation.

CS-02 / Product context

Overview

I contribute to the architectural reengineering of the customer-facing web portal for Línea Directa Aseguradora, one of Spain’s leading direct insurance groups.

The work focuses on improving scalability, reducing technical debt, and creating a frontend platform that is more modular and maintainable over time.

CS-03 / Delivery challenge

The challenge

  1. Evolve the existing frontend into a more modular architecture.

  2. Support independent teams without creating unnecessary coupling.

  3. Make reusable functionality and shared standards easier to apply.

  4. Improve long-term maintainability while product delivery continues.

  5. Help less-experienced developers work within the architecture more confidently.

CS-04 / Public evidence boundary

Public evidence boundary

The project is a current engagement. The client name, my responsibilities, the technical practices listed here, and the approximately 90% frontend unit-test coverage result are approved for publication.

No claim is made about revenue, release speed, customer conversion, or guaranteed outcomes. Sensitive business, security, source-code, and internal architecture details remain outside this case study.

CS-05 / Contribution

My contribution

  1. Frontend architecture modernization

    I helped transition the portal toward a micro-frontend architecture and applied hexagonal architecture principles to separate business logic from UI and infrastructure concerns.

  2. Reusable implementation patterns

    I designed and developed reusable frontend modules and shared UI components, and helped establish common development patterns intended to reduce duplication across teams.

  3. Component documentation and review

    I integrated Storybook to support component development, documentation, and stakeholder review outside complete application flows.

  4. Testing practice

    I introduced and promoted stronger frontend testing practices using Jest and React Testing Library.

  5. Delivery and team support

    I participated in sprint planning, technical refinements, architecture discussions, and cross-team collaboration. I also supported less-experienced developers through reviews, technical guidance, and shared implementation patterns.

CS-06 / Technologies

Technologies

  1. React

  2. TypeScript

  3. Micro-frontends

  4. Hexagonal Architecture

  5. Jest

  6. React Testing Library

  7. Storybook

  8. REST APIs

  9. Agile

CS-07 / Result

Results

  • Frontend unit-test coverage reached approximately 90% at a documented stage.
  • Component reuse and consistency improved across the application.
  • Coupling between frontend modules was reduced.
  • Frontend features became easier to develop, test, document, and maintain.
  • The work created a stronger foundation for independent module delivery.

The coverage figure describes one documented stage of this engagement. It is not presented as a guarantee of overall product quality or a result that can be reproduced automatically elsewhere.

CS-08 / What the work demonstrates

What this demonstrates

Frontend modernization can improve the product foundation and the team’s working model at the same time. Architecture direction, representative implementation, shared components, Storybook, testing practice, reviews, and technical guidance become more valuable when they are integrated into active delivery.

Discuss a similar insurance portal modernizationSee agency delivery support