Design Engineer.
I design it,
I build it.

I started writing Java in middle school and designing on the side. Small games, broken websites, logos for no one. Just the kind of kid who couldn't stop making things. When I landed my first design internship, I had no idea what I was getting into. But something clicked, and I stayed.

The real shift happened when I met a lead who lived in both worlds. Designer and engineer. Someone who understood why an interface felt right, and could build the architecture to make it hold. That's when I knew what I wanted to become. So I started bridging the gap myself, learning to code what I designed, designing what I could ship.

Five years across studios and enterprises taught me the rest. Fintech, banking, biotech, gaming. Products and design systems shipped in every one—interfaces designed, coded, and put in front of real users. What kept pulling me deeper was a frustration I saw everywhere: design and engineering treated as separate jobs, handed off across a gap. Specs that nobody reads, intent lost in translation, products that look right in Figma and feel wrong in production. I wanted to close that gap. Not with process—with craft. One person who owns both sides.

At some point I needed to push the ideas I had in my head as far as they could go. Put myself in conditions where I had to learn, try, and build things I'd never done before. So I did. An open‑source library to share the patterns I kept rebuilding. AI tooling to kill the manual work nobody should be doing. And Lyse, an agent I co‑founded to handle the project management that buries tech teams today. Everything I ship runs in production. That's the only metric I care about.