About me.

I was naturally drawn to design in college, but I also had a computer science degree I wanted to actually use. That pulled me toward the place where design and code overlap: no-code tools, starting with Webflow and later Framer.

Webflow is how my career actually started. I was hired to maintain the Omnify website, but the role kept growing from there: I ended up helping with marketing strategy, designing landing pages, and eventually designing parts of the actual Omnify product itself. I was also building frontend UI directly in Webflow, not just using it as a page builder.

The product thinking I picked up at Omnify is what got me into Womp as a product designer, building the 3D printing flow and Spark from the ground up.

Now, with AI, that same intersection of design and code keeps getting wider. I'm not writing production code, but I can go from an idea to an actual working prototype, or even a small real project, using AI tools and agents. That's changed what I'm actually capable of shipping on my own, not just designing and handing off.

I care more about solving the actual problem than about which medium I end up working in. Whether that's a shipped screen, a rough prototype, or a flow nobody's figured out yet doesn't matter to me: I just want to be in the room while it gets built.

I learn by shipping, not by studying.

I don't walk into a project with a fixed process or a tidy set of rules. I build early prototypes and functional flows because putting something in front of real people is the fastest way to find out what actually breaks: static mocks don't tell you that. I don't usually start with a solution already worked out in my head; I start exploring, and the right answer tends to show up somewhere in that process. Being comfortable with ambiguity is part of how I work, not something I fight through.