I work where frontend meets production systems.

The shape of my career

I've worked through Accenture, at Ford, and for most of the last decade on a regulated, high-scale dispute platform, the last few years there as a direct hire rather than a contractor. The honest read on that history is that it's heavier on big, recognizable names than on a tidy portfolio of side projects, because a lot of the best work happened inside places where the code stays behind the firewall. This site is partly my answer to that: the writeups in Work are how I show the engineering judgment that a résumé bullet flattens into nothing.

How I actually think about frontend

Components are the easy part. On a platform handling disputes at scale across regions, the things that kept me up were runtime contracts between independently deployed surfaces, a testing posture deep enough that a green build meant something, and delivery you could reverse when it went sideways. I care more about whether a system is safe to change than whether it was clever to build.

On AI, honestly

I use AI tooling heavily and every day, and I think pretending otherwise in 2026 is silly. I also think the real skill now is knowing where it helps and where it'll confidently hand you something wrong. Leaning on it for years did soften my unaided instincts, which I noticed and didn't love, and which is part of why I run my own infrastructure: operating real systems is how I keep the layer under the framework from going fuzzy.

What I'm after

A senior frontend or frontend-platform role, ideally at a smaller company or startup, in the Philadelphia area or remote. The work I want is the architecture-quality-delivery kind, not the churn-out-screens kind. Outside work I do improv every week and perform monthly, which turns out to be unreasonably good practice for thinking on your feet in a technical conversation.