Communication is probably the most important skill I have as a product designer.

I coded a questionable (but functional) Desperate Housewives website when I was 12, entered BlackBerry and iPhone competitions, and designed my first iOS app at 17. Android came later.

I wasn't thinking about UX frameworks or design systems then. I was simply fascinated by products: how they worked, why some interactions felt intuitive, and how technology could create completely new behaviors. Eventually, that obsession became my profession.

I built on that legacy through youth radio, journalism at Canal Capital, and audience research at Dynamo Producciones. There I analysed HBO pilots, evaluated documentaries for The Guardian, and wrote script coverage for future Netflix series.

That analytical foundation evolved into visual storytelling. I have since worked with product marketing teams on digital campaigns and product design for Samsung, MINI Cooper, Longines, and Olive Young, with editorial features in Vogue, Harper's Bazaar, and ELLE. My personal photography has earned a Canon Latin America award and a placement in a national museum.

The greatest tool media gave me was not a list of accolades. It taught me how to listen, read a room, and translate complex stories into simple, impactful narratives.

Today, my work spans mobile experience, product design, UX research, growth, experimentation, and design systems. I've designed for consumer and B2B products, moving smoothly between mobile interfaces, analytics dashboards, and AI tools.

Research became a natural extension of that curiosity: understanding not only what people tell us, but what they actually do. (Work I contributed to won a Red Dot Design Award for innovation design).

Quantitative and qualitative, not one or the other. Amplitude, BigQuery and GA4 on one side. Interviews, usability testing and diary studies on the other. I've owned analytics end to end: instrumentation, event taxonomy, reporting, experimentation, and personalization roadmaps.

I also build the plumbing research runs on. At GoodData I set up the participant recruitment flow and the research panel behind it, so studies ran with the right people rather than whoever replied first. I run the sessions too: discovery and alignment workshops that turn scattered opinions into a decision the team can act on.

For me, shipping isn't the finish line. I want to know whether people understood it. Where they dropped off. What changed. What didn't. And whether the thing we designed actually solved the problem we started with.

Years after that first childhood website, I joined 42 specifically because I wanted to understand computer vision development. I spent a year and a half working in C, learning exactly what happens below the user interface.

I didn't do it to become an engineer. I did it because I wanted fewer black boxes.