About

I'm a design engineer with 9 years of experience building at the intersection of design and code, for a global clientele ranging from pre-seed startups to multinational enterprises. I've architected and built scalable component systems for clients like Dubai Holding, replatformed blogs with hundreds of posts and hundreds of thousands of monthly visitors for clients like Emplifi, and helped a whole lot of startups extend their brands into their web presence. I'm CPACC-certified, I've recently started making accessibility-focused open source contributions, and I've had PRs merged on name dropping projects like Angular.

I've been self-employed most of my career, so I'm fluent at working with non-technical people: hearing a business problem, translating it into a technical solution, and delivering it. I'm also a bit of a solopreneur — I've built and sold digital products ranging from website templates to WordPress plugins.

The short version: I design brand systems and the digital surfaces they live across, and then I build them. Most designers hand off and hope it ships clean. I implement the systems myself, so nothing gets lost between intent and the live product.

Design wasn't a direct career path for me. I started in architecture school, which taught me two things that still shape everything I make: I love designing and building things, and I think in systems. Then I found what felt like a restricted section in the library. It wasn't actually restricted, but I was reading the marketing and branding books so intently it felt like I shouldn't be there.

Almost a decade later, I've moved countries more than once, written the briefs, managed the relationships, made the calls when things went sideways, and shipped the final product. The upside is understanding the whole picture: design, business, and the actual mechanics of how good work gets made. These days I bring that range to product work in-house, alongside select projects of my own.

When I'm not designing, I'm probably walking by the lake with a coffee, playing with my daughter, or falling deeper into a book.

I think in systems. Whether it's a brand identity, a website, or a design component, I'm always asking how the pieces fit together and how they'll hold up over time.

Good design isn't just how something looks on launch day — it's how it scales, how it adapts, and whether the team inheriting it can actually work with it.

I work closely with the people I build for. I ask a lot of questions upfront, I explain my thinking, and I push back when I think there's a better direction. It's how you end up with work that's actually worth shipping.