Connor Dibble
Design systems / platform engineering / AI tooling
I set the technical direction for SFDS, the enterprise design system serving 1000+ engineers and designers, and the statefarm.com Digital Experience platform across 8 product teams. My work spans component architecture, design-token pipelines, Figma tooling, cross-framework integration, release governance, and the AI-assisted workflows that carry design intent into production code.
Selected work
Enterprise platform scale, executive-backed AI product delivery, and open-source readiness tooling for agent workflows.
SFDS
State Farm, closed source
State Farm's canonical enterprise design system and migration target for statefarm.com. I led sf-ui, a framework-agnostic Lit/Web Components library with 70+ primitives, plus the Figma Variables → W3C token pipeline and npm/CDN release governance for 1000+ engineers and designers.
- Web Components
- TypeScript
- Design Tokens
- npm + CDN
DesignRail
Open source
Human review gate for design-to-code workflows. It turns component intent into schema-backed proposals, surfaces compliance risk, and requires a recorded decision before export.
- Developer Tools
- React
- TypeScript
Insurance Agent Feedback Platform
State Farm, closed source
Full-stack AI feedback platform commissioned by State Farm's EVP of enterprise technology. Went from concept to production in two months for its debut at agency convention, and the pilot earned backing to become the official support and feedback channel for all 10,000+ State Farm agents.
- Angular
- TypeScript
- Node.js
Systems that hold together
At State Farm, I set the technical direction for SFDS, the enterprise design system serving 1000+ engineers and designers, and lead the statefarm.com Digital Experience platform across 8 product teams and 40-50 engineers.
The useful work sits between design intent, system contracts, and the teams that inherit both. I like problems that cross design tooling, frontend architecture, delivery infrastructure, and the operating model required to make a platform last.
More about meMy path here runs through React and Angular applications, Java and Node.js services, event-driven systems, release governance, and applied AI tooling. Through Proceris and open source, I stay close to the full product loop: customer conversations, technical discovery, implementation, and the checks that keep software understandable after launch.
Field notes
Longer-form notes on the decisions, tradeoffs, and costs behind the work above.
All writingAgentic Software Needs a Design System
July 2026 · 9 min read
Why an AI agent should be treated as another contributor to a governed platform, and how design-system mechanisms map one for one onto agentic equivalents.
Success Was the Incident
June 2026 · 10 min read
Adoption turned a five-minute browser cache into a budget problem. Splitting it into three caches with three owners, hashing dependencies behind stable component files, and a finops partnership cut request volume to a third of its peak.
From Snippets to Shadow DOM
June 2026 · 13 min read
Why a jQuery-era design system splintered into forks and customized local versions, how Shadow DOM moved governance into the component boundary, and what it took to earn adoption from a thousand engineers.
Teaching AI Agents to Use a Design System
May 2026 · 9 min read
A practical look at constraining AI-generated frontend code with design-system primitives, agent instructions, and repeatable validation.
Experience
Senior Technology Engineer, Digital Experience
State Farm / Mar 2026 – Present
Set technical direction across the statefarm.com Digital Experience suite: 8 product teams, 40–50 engineers, and an executive-backed migration toward 100% SFDS adoption. Shape GraphQL contracts, service-integration patterns, and AI tooling for customer-, agent-, and internal-facing workflows, including a Figma MCP pipeline that translates fully designed pages into sf-ui Web Component implementations. Validation tooling wired into local hooks and PR workflows has reviewed 50+ merge requests for design-system alignment and accessibility risk.
Lead Software Engineer, State Farm Design System (SFDS)
State Farm / May 2023 – Mar 2026
Led engineering for SFDS, State Farm's canonical enterprise design system. Architected sf-ui, a framework-agnostic Lit/Web Components library of 70+ primitives, and a Figma Variables → W3C design token plugin in TypeScript. Owned npm + CDN release governance for 1000+ engineers and designers.
Software Engineer, Drive Safe & Save Telematics
State Farm / May 2020 – May 2023
Built Node.js Lambda APIs and Java Spring backend services for the Drive Safe & Save telematics enrollment experience on statefarm.com. Owned frontend direction for the product suite across React apps and micro-frontends.
Tools I reach for
- Design Tooling
- Figma Plugin/API · Figma MCP · W3C Design Tokens · Design-to-Code Automation · Component Governance · Accessibility · Documentation Systems
- Frontend / Platform
- React · TypeScript · JavaScript · Lit / Web Components · Angular · SPA Architecture · State Management · Cross-Framework Integration
- Backend / Cloud
- Node.js · Java · AWS Lambda · GraphQL · REST · API Contract Design · Service Integration · DB Schema Design · Event-Driven Systems · Serverless · npm / CDN Delivery · GitLab CI/CD
- AI + Reliability
- Application-Level GenAI · Agent Workflows · MCP Servers · Agent Skills · Structured AI Outputs · GitLab Webhook Agents · SLOs & Observability · Dynatrace RUM · AWS CloudWatch · Incident Response