About me
At State Farm, I’m a Senior Software Engineer and Digital Experience Platform Lead. My official title is Senior Technology Engineer. I lead frontend engineering and software delivery strategy across 100+ repositories supporting customer-facing, insurance-agent-facing, and internal applications. My direct statefarm.com assignment covers 8 product teams and 50+ engineers within that broader enterprise mandate. I retain responsibility for SFDS, which serves 1,000+ engineers and designers.
I’m leading the buildout of a frontend engineering platform across AEM and custom web applications. Approved starters, shared integrations, journey telemetry, and broader CI validation are work underway. I define machine-readable component contracts and policies for coding agents and recommend architecture patterns, including monorepos and microfrontends, directly to engineering leadership. XD and backend partners help connect customer-experience strategy, data, and the GraphQL migration.
The Figma-to-code workflow combines Figma MCP, sf-ui agent skills, and deterministic validation with human review. I’m the primary engineer for the skills, Figma integrations, and design-system validator CLI, maintained alongside platform engineering. These tools guide coding agents to supported components and check generated code against component APIs, attributes, and styles. Configured Codex and Claude Code agent hooks block on findings; CI deliberately reports warnings without stopping deployment, preserving teams’ ability to release urgently.
I’m happiest when a problem is technically deep and organizationally messy. I trace it far enough to find the real constraint, whether it lives in a system contract, a data invariant, missing repository context, a delivery model, or the economics of a service at scale. The implementation matters, as do the migration path, governance, observability, and explanation. A platform earns trust when an engineer can integrate it, an agent can follow its boundaries, and a leader can understand how it is operated.
Section One keeps me accountable for a live product I operate part-time, with shared agent workflows and publication checks across 20 college-football programs. In dibble, I publish portable skills and deterministic checks for Claude Code, Codex, and CI. Both projects make the implementation and operating choices available to inspect.
What I Care About
Engineering Taste
I like boring force multipliers: clear boundaries, APIs that are hard to misuse, context close to the work, invariants enforced in the layer that can guarantee them, and delivery models that make the correct path the easiest one.
Working Style
I tend to start with evidence and the people closest to the problem. Then I make the tradeoffs explicit, choose the smallest architecture that preserves the important guarantees, and leave behind enough context, tooling, and feedback loops for the system to outgrow my direct involvement.
Outside the Editor
I’m 6′8″, so basketball found me early, but I’ll play or watch nearly any sport. I’m training for my first half marathon and still enjoy losing an evening to a PC build. An earlier chapter was Fukuoka, Japan, where I led volunteer trainings in Japanese and taught English to 100+ students. Family is the anchor.