Angular Signals migration

As primary frontend contact for four core modules across a CMS, a B2B portal and a public site — order/quote/wishlist listings, product search, brand details and product bundles.

The modules ran on RxJS with Zone-based change detection: every emission risked re-rendering far more of the tree than the change required, and reasoning about update paths was getting harder as the modules grew.

• 01Migrated all four owned modules from RxJS/Zone-based change detection to Angular Signals, module by module, without pausing feature delivery.
• 02Built highly custom shared components — multiselect, nested multiselect, OTP input — and custom pipes reused across all three repos, so the migration also consolidated duplicated UI logic.
• 03Instrumented every module I touched with Amplitude: signup funnel, checkout (step, payment method, quantity) and search-to-purchase flows, with 20+ granular events per module.

Fewer unnecessary re-renders, simpler update reasoning, and a shared component layer three repos now depend on — plus the analytics to prove how each flow actually performs.