I design products.
I think in systems.

My title has always been in design, but my thinking has never stayed there. I work at the intersection of design, engineering, and product, comfortable in every conversation and always asking how one decision ripples across the whole.

View My Work ↓Connect ↗

How I Approach Work

Good design isn't just how something looks. It's how well you understood the problem before you touched a tool.

I break things down until they're clear

When a problem feels overwhelming, that's usually a signal the framing is wrong. I slow down, map the system, and find the one thing that actually matters. That clarity tends to unblock everyone around me too.

I stay in the room with engineers

I've spent enough time in codebases and sprint reviews to understand how engineers think. I write specs they can actually use, and I ask questions that don't waste their time. That trust makes a real difference in what ships.

Every detail has a downstream effect

A small UX decision can create a data modeling problem. A component choice can constrain a product decision six months later. I try to hold that context while still moving fast — and speak up when something feels off.

I think at the product level

Even when I'm deep in a flow or a component, I'm thinking about the broader experience and the business behind it. Design is where I work. Product is how I think.

Selected Work