I design products by understanding structure first. Architecture taught me that good systems are invisible — when the underlying logic is right, everything else follows.

When I moved into frontend development, I learned that strong design decisions depend on understanding how things get built. It’s not about limiting creativity — it’s about having the right information. That approach helps me separate ideas that look good from solutions that actually ship.

That combination shapes how I evaluate ideas. I focus on the system behind a solution before worrying about how something looks on screen.

Throughout my career, I've worked closely with founders, product leads and engineering teams on high-impact decisions—aligning on what is possible, what is necessary, and where trade-offs matter. These conversations are where the best decisions happen.