The Design-Code Bridge
I comfortably discuss React Architecture and Design Tokens in the same sentence. I translate design needs into component structures that engineers actually enjoy maintaining.
Across 7+ years—from fast-paced startups in Dublin to architecting massive e-commerce ecosystems in Amsterdam—I’ve seen a recurring pattern: products break when design and engineering don’t speak the same language.
I operate in the hybrid space to fix this. I don’t just close tickets. I align technical reality with design intent, removing friction to deliver software that is robust, not just functional.
I comfortably discuss React Architecture and Design Tokens in the same sentence. I translate design needs into component structures that engineers actually enjoy maintaining.
Clean code is useless if it solves the wrong problem. I question the 'why' before the 'how', prioritizing business value and user experience over just writing code.
I don’t believe in reinventing the wheel. I build systems that function as true infrastructure, allowing the team to ship faster without accumulating technical debt.
Visual sensitivity doesn't mean lowering the engineering bar. I focus on strict TypeScript and stability, writing solid code that others can read, extend, and trust.
I’m driven by a genuine curiosity for how things work—whether that’s a complex software architecture or a permaculture garden. To keep my mind sharp and balanced, I rely on meditation and stepping away from the screen.
That same curiosity pushed me to backpack solo through Asia and the Americas for 18 months. Navigating the unknown with just a backpack taught me more about problem-solving than any job could. It made me comfortable with uncertainty and highly autonomous.



