Univé
One of the largest insurers in the Netherlands, a cooperative serving millions of customers.
Led front-end across 16+ insurance funnels in one large Nx monorepo, owning the architecture, performance, and the patterns a whole team builds in every day.
// WHAT I DID
16+ funnels, one architecture
Shared libraries with enforced boundaries, so one fix improves every funnel instead of leaving sixteen copies to maintain.
Performance drives conversion
Bundle discipline, render performance and predictable NgRx state, because a faster funnel is a funnel that converts.
Owned the direction
Set the technical direction, reviewed across teams, and made the abstract-vs-duplicate calls that keep a big codebase shippable.
The scale
Sixteen-plus funnels, one ecosystem
Every insurance product Univé sells online runs through a funnel, and there were more than sixteen of them. Sixteen chances for the code to drift apart. The answer was one large Nx monorepo: shared libraries, enforced module boundaries, single-version dependencies, and tooling that makes the right way the easy way.
How I worked
Lead front-end across teams
As lead I set the technical direction and reviewed across teams. A lot of the job was judgement: when to abstract, when to duplicate, when to migrate, and when to leave well enough alone. The measure of success was a funnel ecosystem that kept shipping features years into its life, without the slowdown big codebases usually grow into.
What I worked with
Angular, Nx, NgRx
Angular and TypeScript, organised in an Nx monorepo, with NgRx for state that stays predictable as flows get more complex. Performance treated as a first-class concern throughout, because in insurance funnels speed is conversion and conversion is the whole point.
16+
Production funnels
// MORE WORK