The work behind
the work.

My path to front-end leadership

Most organizations don't struggle because of a lack of talent. They struggle because their front-end systems evolve without structure. Different teams build different patterns, components drift, and over time the user experience becomes inconsistent and harder to maintain. That's where I focus.

Over the years, I've found that my impact grows when I shift from building individual features to building systems that enable teams. This means creating component libraries that make good design cheap and accessible. It means establishing patterns that prevent technical debt from accumulating. It means helping teams understand not just what to build, but how and why.

What drives me

I believe that great user experiences are built on solid foundations. That foundation is the design system, the component architecture, the accessibility standards, the observability tooling, and the shared practices that teams rely on.

I'm motivated by problems that span products and teams. How do we make it easy for any engineer to build an accessible form? How do we ensure brand consistency across six applications without creating bottlenecks? How do we modernize legacy code while still shipping features? These are the problems I work on - they require technical depth, cross-functional collaboration, and the ability to balance pragmatism with long-term thinking.

How I lead

I'd rather grow a team than be its bottleneck. I set clear norms, expect engineers to talk to each other instead of through me, and treat code review as teaching. I hire for craft and curiosity, and I bring strong front-end engineers into interviews so candidates meet the people they'd work with.

Most of leading is unglamorous: coaching, honest feedback, helping someone find a team that fits them better, and occasionally making the hard call when something isn't working. I try to do all of it the same way, directly and with respect.

Still building

I still write production code, usually the parts that are risky or shared. Recently that's meant restructuring the global layout of live applications so navigation stays put while content scrolls, and building a DataTable that has grown to handle custom sorting, nested rows, and embedded visualizations without splitting into five different components.

Current focus

Right now I'm leading the Customer Experience team at Milliman IntelliScript, growing Sable, and turning our front-end architecture decisions into blueprints that new projects start from. The latest is a micro-frontend blueprint.

I'm also building out my team's AI development toolkit. Next up are tools that estimate a pull request's blast radius, flag performance regressions before they reach production, and draft missing unit tests.