My role is Product Engineer · I focus on Design & front-end
My best work lives at the interface. I build the stack behind it, too.
I'm a design- and front-end-focused product engineer with 20 years in production UI. The interface is where I bring the most value, and I'm full-stack capable enough to own what's behind it.
- Design-grade front-end
- React · TypeScript · 20 yrs
- Accessibility built in
- Full-stack capable
- Travelers
- Berkshire Hathaway
- America's Test Kitchen
- NASCAR
- NFL
Why my products feel finished.
Most engineers treat design and accessibility as someone else's job, or the first thing cut when a deadline closes in. I build them in. That's why the things I ship work for everyone, not just the average user on a fast laptop, and why they hold up after launch.
The UI is where I bring the most value
Twenty years in design systems taught me where interfaces break: type, spacing, motion, the empty and error states most engineers leave blank. I build it myself, design-grade, instead of handing a spec to someone who will approximate it.
Accessible by construction
Keyboard paths, focus management, and screen-reader behavior built in from the start. Accessibility is the mechanism that makes a product work for everyone, not a checkbox.
I sweat the last 10%
Empty states, recoverable forms, the screen that shows when there is nothing to show yet. Those are the parts that decide whether a product feels finished, and whether it holds up after launch.
Full-stack enough to own it
A capable full-stack developer in Rails and TypeScript: auth, tenancy, data, API. Not because the backend is the point, but so the UI never stalls waiting on someone else to wire it up.
Selected work
Products I owned end to end.
75%
fewer support calls
IVFCRYO: clearer, recoverable flows
55%
fewer shipping errors
IVFCRYO: accessible forms at the source
3 → 1
brands, one library
America's Test Kitchen: one system, three brands
- Design system America's Test Kitchen When a product needs a real design system, I build that too: one library serving three editorial brands, one accessibility floor.
- Design system Berxi A design system for a growing insurance platform, from stakeholder alignment through component library, documentation, and cross-team adoption.
- Accessible flows IVFCRYO Recoverable specimen-shipping flows for a fertility logistics product. Accessibility was the mechanism that moved the numbers.
- Rails platform VMSpark A multi-tenant Rails admin platform rebuilt and shipped in four phases, with no feature flags and zero pipeline regressions.
And the tooling that enforces the quality: a design-system drift auditor that measures UI debt in counts and hours, plus a decision guide for accessible interface patterns.
Designer by origin. Engineer by practice.
I started in design and moved into engineering because I wanted to build the things I drew, not hand them off. Twenty years later, the front end is where I do my best work: design-grade, accessible UI with the judgment most engineering teams have to hire a separate designer to get. I'm also a capable full-stack developer in Rails and TypeScript, so I can carry a product the rest of the way.
I build by feel, fast, and I sweat the finish. Away from the screen, I play bass and gig regularly, which is its own lesson in getting the details right in real time.
Looking for a team that cares about the finish.
I want to build complete, accessible products on a team that treats the last 10% as the point, not the afterthought. If that's the work, let's talk.
Latest writing
Notes on building complete products.
Accessible interfaces, the details that make software feel finished, AI-assisted development, and the changing shape of the front-end engineer.