Frontend engineer and technical leader building React + TypeScript products, design systems, and developer workflows.
I turn complex product and data problems into fast, maintainable frontend systems. Most recently, I led frontend architecture strategy for a 65-person business unit at Bushel, partnering across design, DevOps, infrastructure, product, and support to help 4-10 engineers ship with less drag.
I care a lot about the places where product quality and engineering leverage meet: performance, design systems, state modeling, release safety, observability, and tooling that gives teams time back.
- Production React + TypeScript apps with careful state handling, resilient API surfaces, and mobile-first UX.
- Design systems that actually get used, mapped closely to Figma components and team workflows.
- Performance-critical interfaces for users on rural 2G/3G networks and lower-powered devices.
- Operational control planes for internal teams managing tenants, releases, access, reporting, and integrations.
- Developer experience systems using AI-assisted workflows, semantic changelogs, Jira/Confluence automation, and sharper release practices.
| Area | Result |
|---|---|
| Frontend performance | Cut a major app bundle from 2MB to 500KB, dropping rural 2G/3G load times from 16s to 6s and improving p75 Core Web Vitals 2x |
| Payments platform | Frontend architect for scheduled transfers, ACH processing, and lien/tranche handling on a platform that peaked at $500M+ transferred |
| Design systems | Drove adoption of a shared React design system across Fulfillment, Payments, and Agribusiness, reducing duplicate component maintenance by about 50% |
| Reliability | Authored release cadence, feature-flag isolation, risk-scoring, and DataDog SLA budget alerting practices supporting a 99.9% platform SLA |
| Mentorship | Mentored 25 NDSU capstone students over 5 years building full-stack agricultural software through sprint planning, code review, and stakeholder demos |
Core frontend
Data, state, and quality
Platform and backend
Workflow
Some of my public repos are small infrastructure experiments, but they show the kind of problems I like: making setup, deployment, and repeatable workflows easier.
| Project | What it is |
|---|---|
| next-docker | Template for Docker and Next.js |
| pnpm-docker | Base Docker image for using pnpm |
| pnpm-next-docker | Next.js + pnpm Docker setup focused on fast build times |
- I like architecture that makes the next feature easier, not just the current one possible.
- I try to model the unhappy paths early: partial data, slow networks, weird permissions, missed releases, and half-finished integrations.
- I enjoy turning team friction into tooling, docs, or reusable primitives.
- I mentor through pairing, code review, and asking engineers to explain the tradeoff, not just the implementation.
Home automation, animation, and DIY/maker projects are where a lot of my curiosity goes after work. I like systems I can touch: code, tools, furniture, wiring, dashboards, and the occasional thing that started as "this should only take an hour."