work

Where I tend to contribute the most on a team:

Design systems teams actually adopt

I build and consume internal component libraries, and handle the unglamorous parts that decide whether anyone actually uses them: spacing tokens, registry setup, and wiring libraries into product apps.

Client-side integrations built with quality and instrumentation

Stripe, Rokt, Amplitude, Flagsmith, BriteVerify, Turnstile. Payments, analytics, feature flags, A/B testing, and plenty more.

An observability mindset on the frontend

I instrument what I ship: Datadog browser logs and production dashboards, frontend and backend connected end to end, and errors ranked by severity from real data instead of argued about in a meeting.

Frontend depth, without stopping at the API

React, Next.js, TypeScript and Tailwind are my comfort zone, but I also develop the Node services and REST APIs behind them, integrated Ruby on Rails, wired up Angular micro-frontends, and put LLM APIs into real production products used by millions of people.

Modernizing code that still has to ship

I've modernized React and Rails apps that had been in production for years and pulled them into modern patterns, TypeScript, and real test coverage, as a series of safe steps backed by risk and constraint analysis, not a rewrite that stops the roadmap.

Closing the loop, not just the pull request

I follow a change through review, merge, deploy and monitoring, and write the RFC when a structural decision needs clarity before it turns into chaos. Most of my work happens as the bridge between design, backend, DevOps and product.