Systems Design @ SeatGeek

Project: Internship | Duration: 3 months | Team: UXD, ENG, PM

<aside> <img src="/icons/stars_purple.svg" alt="/icons/stars_purple.svg" width="40px" />

As a product design intern, I contributed to SeatGeek’s design system by evolving foundational components, writing component documentation, and kickstarting the bottom sheet pattern for mobile.

</aside>

TL;DR: At SeatGeek, I identified major gaps in the design system—11 fragmented libraries, duplicative work, and no clear documentation. I helped move the team toward a unified system (Fanatic) by improving components, leading bottom sheet research and exploration, and contributing to clearer guidelines to align design and engineering.

Want a deeper dive? Keep scrolling ;)

A System in Pieces

SeatGeek’s design system was fragmented — 11 library files (3 deprecated, 8 outdated), no clear documentation, and no components built in a dev-friendly way. Designers pulled from inconsistent sources, engineers rebuilt the same components, and there was no shared understanding of what was reliable.

Lack of a centralized library

No clear documentation

Siloed and duplicative work

Without a single source of truth, scaling consistent design across platforms was nearly impossible.