Experience

An event invitation and RSVP platform where multilingual support is a first-class concern, not a later translation pass.

There are two of us, so on top of owning the client I set the technical direction across the entire stack. A lot of my work has also gone into the tooling we develop with, both for the two of us now and for whoever joins later.

• Own

  The client surface

  Architecture, design system, state management, and routing are all mine. Multilingual support runs through each of those decisions rather than sitting on top of them, which is what makes it the constraint that shapes the most code.

• Designed

  Our AI development pipeline

  Schema-validated skill workflows with a human in the loop by design, plus automated CI failure analysis that posts to pull requests with remediation guidance. A contributor can ship safely without being an expert on every system they touch.

• Built

  Migration and schema testing on PGlite

  Migrations and schema changes are validated against a real Postgres engine rather than a mock, and without touching a live database. An engineer can trust a migration before it reaches an environment where being wrong is expensive.

Foundations work for the TV client, where my customers were the hundred-plus engineers building the interface you know and love.

Developer experience was the product here, which meant my customers were internal. The measure of a framework was never how clever it was, but how quickly an engineer could pick it up and ship with it.

• Built

  Frameworks and tooling for the TV client

  More than a hundred Netflix engineers shipped TV interfaces on the frameworks and tooling we built. The goal was for them to move quickly and stay confident in what they shipped. That came both from the tools being intuitive and powerful, and from us being there when gaps surfaced.

• Designed

  The standard styling library and animation framework

  Built in close collaboration with design, so that a Figma file and the code implementing it used the same vocabulary. That shared language is what let designs reach production quickly and come out consistent.

• Wrote

  A custom React reconciler

  The TV platform was proprietary, and the existing reconcilers simply could not target it. React DOM talks to browser APIs and React Native to a native bridge, and neither one knows a renderer like this exists. Writing our own meant engineers kept the ergonomics and testability they expect from React while rendering at native performance.

Technical lead on the frontend for InsightIDR, Rapid7’s incident detection and response product, through the rewrite that created it.

Moving a Backbone product to React meant betting on something that had not settled yet. Most of my work went into the decisions that would be expensive to change later, which is also why they held long enough to be adopted across the org.

• Owned

  Frontend architecture for InsightIDR

  Component model, state management, testing strategy, code style, and the build and deploy pipelines. All of it started as decisions for a single product, and all of it ended up adopted across the organization.

• Led

  The rewrite of UserInsight into InsightIDR

  A full migration from BackboneJS to React and Redux, with a feature-based architecture underneath it so that versioning, testing, scale, and productization were structural rather than afterthoughts.

• Built

  A shared component library

  Built and maintained with the designers directly, then distributed to other product teams through a private npm registry so that every product shared one visual and interaction foundation.