Most proud projectTechnical leadershipCross-functionalDeveloper experienceAccessibility (Radix UI)Migration at scaleSales impact
S — Situation
Joined to find no design system. Engineers made UI decisions independently — buttons with inconsistent hover states, spacing values of 14, 16, 18px used interchangeably, no shared visual language. It was slowing down every engineer and designer on every new feature.
T — Task
Proposed and owned this project from scratch, while keeping the product stable and shippable throughout. Had to coordinate with the designer, write the components, migrate the whole product, and document everything — no dedicated team.
A — Action
Started with foundations — worked with the designer to define color, typography, and spacing based on actual product needs. Built 30+ reusable components on Radix UI for native accessibility (dropdowns, buttons, dialogs, etc.), each with documentation and usage examples. Set up milestones in Linear, broke it into tickets across the team, and worked through every part of the app systematically while keeping it shippable.
R — Result
Designer went from ~1 week to produce new designs down to hours. Engineers ~50% faster on UI work. Product went from scrappy to polished — directly helped the sales team demoing to enterprise customers.
30+ components shipped~50% engineer productivity gaindesigner: week → hoursenterprise sales impact
90-second version — ready to say out loud
"When I joined, we had no design system at all. Engineers were making UI decisions independently — buttons with inconsistent hover states, spacing values like 14, 16, and 18px used interchangeably across the product, no shared visual language. It wasn't just a polish problem — it was slowing down every engineer and every designer on every single feature.
I proposed and drove this project from scratch. I started by working with our designer to define the foundations — color, typography, spacing — based on what the product actually needed. Then I built out 30+ reusable components on top of Radix UI, which gave us native accessibility out of the box. Each component shipped with documentation and usage examples so the rest of the team could follow consistent patterns without guessing.
The hardest part was migrating the entire product to the new system while keeping it stable and shippable throughout. I set up milestones in Linear, broke it into tickets across the team, and we worked through the product systematically until every part of the app was on the new system.
The impact was real: our designer went from about a week to produce new designs down to hours. Engineers got roughly 50% faster on UI work. And the product went from feeling scrappy to polished and professional — which directly helped our sales team when demoing to enterprise customers.
What I'm most proud of isn't any single component I built. It's that I created the foundation the whole team builds on top of."
"Most proud / most impactful project"
Lead with: the foundation the whole team builds on
End on the closing line verbatim — it's already perfect
"Led a large technical initiative"
Lead with: proposed it, owned it, coordinated the migration
Emphasize Linear milestones + team coordination
"Improving team productivity"
Lead with: the before state — everyone reinventing the wheel
The 50% productivity number is the anchor — use it early
"Identified a problem and owned it"
Lead with: noticed inconsistency, proposed the fix, nobody asked you to
Shows proactivity + long-term thinking over shipping quick features
The closing line is already perfect — use it verbatim: "I didn't build a single feature — I built what everyone else builds features with." Memorable, humble, and shows systems thinking all at once.