I build the things engineers build with – and the engineers who build them.

I've spent 14 years on the part of software people actually touch and see.

The work I like best is the translation layer — taking a design file and producing something fast on a mid-range Android, navigable by keyboard, legible to a screen reader, and still exactly what the designer drew. Getting all four at once is harder than it sounds. It's the part of the job I've never gotten bored of.

I've done it at national scale. Campaign sites for PepsiCo and Arby's, where traffic arrives in a spike and nothing is allowed to buckle. Capital One and Adobe, where accessibility isn't a nice-to-have but a legal and institutional requirement. Campbell's and its brand portfolio — V8, Swanson — where one system has to serve many labels without flattening any of them. And The Little Chapel in Las Vegas, which got the same standard as all of it, because the standard isn't a function of budget.

Building one good interface is craft. Building the system that makes fifty good interfaces inevitable is leverage. So I moved into component library and design system work — headless primitives, documented contracts, accessibility solved once instead of twelve times — and into the other half of leverage, which is people. I'm a certified Scrum Master. I break work into tasks precise enough that nobody comes back to ask what I meant, and I estimate timelines accurately enough that other teams plan around mine.

What I'm building next: the server side. Not to change careers — to stop handing off the hard half. When a dropdown takes 900ms to populate, that isn't a spinner problem. It's a query, a cache policy, a schema decision made a year ago. I'm working through [backend stack] so the next system I architect is one I can own end to end.