–
Stack Overflow
First designer on the Enterprise and Teams products, created several enterprise features atop Stack's core product, built Stack Overflow's email design system.
I joined Stack Overflow because I was excited about the power of knowledge-sharing at scale. Their consumer product had already become the go-to resource for developers, and I wanted to help bring that same value to companies building their own internal communities.
As the first designer on Stack Overflow’s enterprise product, I wore a lot of hats: conducting user research, designing interfaces, and even writing production code. I focused heavily on admin tools that gave companies the ability to manage their communities and measure ROI, while also contributing to Stack’s design system.
I helped grow the enterprise product from a single customer to over 30, adapting a loved community product for enterprise use cases. I also built one of the first email design systems in the industry, which became a core part of how Stack Overflow communicated with users at scale.
Likes and page views don't tell you if a community is actually working. Stack Overflow had spent years learning what makes a community healthy. I helped bring those insights to Enterprise clients through a custom analytics experience focused on signals that matter, not numbers that just look good.
HTML email is notoriously painful to build. At Stack I turned my open source framework into an email design system that scaled to millions of emails a year.
The code was only part of it. I documented typography and the other components, designed the email section of Stack Overflow’s design system, and shipped interactive docs so people could see components in use, plus dark mode and responsiveness. That visibility helped outside Stack too, through talks and podcasts. Inside, the impact I cared about most was for developers who did not know or like HTML email: they could get further without a designer sitting next to them, which freed design time for the problems that actually needed it.
The system shipped templates for product emails like Stack Overflow for Teams and marketing campaigns like our 10th anniversary. Same components, different contexts.
Stack Overflow is most useful when it fits into how your team already works. I designed a set of integrations that connected our platform to tools like Jira and GitHub, turning separate systems into one seamless workflow.
I've always believed in making space to explore. Alongside my regular work, I sketched out ideas for improving the Stack Overflow experience, including ways to make the platform friendlier for people just getting started. Some made it into the product. Some didn't. All of them were worth doing.
