Case Studies
Selected projects from 10+ years of frontend engineering.
Each case study covers the problem, the approach, and what held.
- one component API that TypeScript can check
- Plain props
- with two other developers from the start
- Team-built
My work building shared components, reviewing APIs, and supporting contributions to a design system used across multiple applications.
The Challenge
Teams worked around shared components when product needs and component behavior diverged. I used working groups and API review to discuss that friction.
The Impact
I built components, chose the API shape, reviewed contributions, coached contributors, and worked closely with design. Since becoming Lead Frontend Engineer, I lead the system.
- Next.js
- TypeScript
- Accessibility
- Tailwind CSS
- React Testing Library
- Design and implementation
- WCAG 2.1
- design approach
- Mobile-first
- co-led frontend from scratch
- Greenfield
I co-led a greenfield portal frontend, introduced a WCAG 2.1-guided accessibility specification, and checked keyboard navigation myself.
The Challenge
The portal's audience made accessibility a product concern. I introduced the requirements and wrote a specification that the team agreed to include.
The Impact
I followed WCAG 2.1 guidance in the specification and implementation, checked keyboard navigation myself, and encouraged QA to include keyboard-based test cases.
- CSS
- DOM APIs
- JavaScript
- Chrome DevTools
- group selection - team benchmark
- 733 → 429 ms
- nested-input selection - team benchmark
- 864 → 586 ms
I optimized HTML and CSS and helped with the React UI in a team rebuild of the Layers panel, with selection results published by UXPin.
The Challenge
A large tree of layers needed to support drag-and-drop, scrolling, and updates from collaborators. The work crossed JavaScript, DOM structure, and CSS rendering.
The Impact
UXPin reported canvas selection times falling from 733 to 429 ms for a group and from 864 to 586 ms for a nested input in the team's rebuild.