I don’t design screens in isolation. My first instinct is to map the underlying architecture – how data, people, and operations interlock – to ensure the entire system is structurally sound before thinking about the interface.

I thrive in highly ambiguous environments. By deconstructing complex domains down to their raw variables, I rapidly adapt to any landscape, whether that means modeling financial calculations, balancing glaze chemistry, or architecting software.

I have a high tolerance for technical complexity because I (sometimes) actually build the things I design. I partner seamlessly with engineering because we share the same mental models. I don’t know all the syntax, but I can define the core system logic and data flow that structures the code, bridging the gap between backend and frontend.