A bit about me.

I’m a backend and platform engineer. I like the unglamorous middle of a system: the content API, the event bus, the CDN rules, the release pipeline. When those work, editors publish in seconds and nobody thinks about them.

I spent more than ten years at Turner, WarnerMedia, and Warner Bros. Discovery, the same company under three names. I started on the front end of NBA.com and the NBA League Pass storefront, moved to the site and API for Turner Classic Movies, and then to the shared publishing platform behind HBO.com, TCM.com, DC.com, and other brand sites.

On that platform my work shifted from writing features to designing how the pieces fit. I co-designed its Kafka event bus, led the backend side of moving TCM.com onto it, and designed a publishing path that replaces a whole-site rebuild with a single JSON manifest. Along the way I wrote ten architecture decision records and reviewed more than 1,700 pull requests.

I write things down. Runbooks, migration plans, and developer guides are part of how I ship, because a system that only one person understands is a liability. I also take incidents seriously: I’ve written the post-incident reports and then filed and driven the hardening work that follows.

Lately I’ve been working with AI coding tools every day, and I built a proof-of-concept agent pipeline that triages and drafts fixes for vulnerability tickets while leaving the merge decision to a person.

I’m looking for a backend or platform engineering role where the problems are architectural and the team cares about operating what it builds.

The fastest way to reach me is hello@example.com.