About
I started out as a graphic designer — but I quickly realised I was only working on one piece. I wanted the whole picture.
So I kept learning the next layer. From graphics to web design, where my visual background carried over. Then frontend development — because I saw that good design only matters when it can actually be built and handed off cleanly. After three years of writing code, I started to understand products — not just screens, but the full experience and the decisions behind it.
That's when I became a product designer. And as I went deeper, the business lens came in too — KPIs, metrics, and the tradeoffs behind every product decision.
Today, when I make a design decision, I can see it from four sides: what to build, how it's built, what's right for the user, and what the business needs. That's why I can make data-heavy, high-stakes decisions clear and trustworthy — because I spent 13 years learning every angle that makes a decision whole.
Design + build
I prototype in code — HTML, CSS, JavaScript. So what I hand off is developer-ready, and my design decisions account for what's actually buildable.
AI in my workflow
Claude for UX specs, Figma Make for rapid prototyping, Figma MCP for token automation — AI as a design multiplier, not a buzzword.
Also fluent in Figma, ProtoPie, Adobe CS, Jira, Notion, Miro — the everyday toolkit.
Outside work, I like exploring new places and digging into their history — probably the same curiosity I bring to my work. Meditation and workshops keep me grounded and learning.
