Module Federation at scale
Five micro-frontends composed at runtime on a regulated dispute platform, held together by singleton and design-system contracts so five teams could ship without a shared deploy train.
Senior Frontend Platform Engineer
I build frontend systems that hold up in production.
I spent most of the last decade on a regulated, high-scale dispute platform: five federated micro-frontends, multi-region, on the order of 300,000 disputes a day. The problems worth solving there were never just components. They were the runtime contracts, the deploy safety, and the observability that decide whether a frontend is actually safe to change. And when contract work threatened to dull the layer beneath the framework, I started running my own infrastructure to keep it sharp.
Modern React / TypeScript
React 18 and TypeScript on multi-step regulated flows. TanStack Query for server state, React Hook Form and Zod for typed, validated boundaries where one schema does both runtime and compile-time duty.
Production quality engineering
Six testing layers, each catching a different class of bug, wired into staged release gates. Including the two everyone skips, mutation and contract testing, which are the two that actually save you.
Reliability & observability
OpenTelemetry tracing, circuit breakers, blue-green deploys, and rollback treated as a first-class idea rather than a fire drill. Proven on infrastructure I run myself.
Modern CI/CD
Jenkins and Spinnaker delivery with coverage, mutation, contract, security, load, and smoke gates standing between a commit and production.