About

I bridge design and code, so good ideas survive the handoff.

Senior Product Designer and frontend engineer with 10+ years across enterprise platforms, luxury retail concepts, and 0-to-1 builds. I care about the fundamentals (typography, interaction, information architecture) and about the systems underneath them holding up at scale.

I started as a graphic designer in Brazil, which is where I first learned to balance aesthetics, storytelling, and function, long before I had words like "design system" or "information architecture" for what I was actually doing.

That early instinct evolved into product design and frontend development, across SaaS, e-commerce, beauty and wellness, and enterprise software. What hasn't changed is the throughline: taking something complicated (a workflow, a dataset, a category nobody's designed for yet) and making it feel simple without making it shallow.

My background lets me move between visual design, systems thinking, and enough technical fluency to know what I'm asking engineering for. I've architected token systems and governance processes adopted across 15+ teams, and I've also been the only designer on a team, taking a product from a blank page to launch. Both modes matter to me; I don't think of "scrappy" and "rigorous" as opposites.

Outside of work, I play volleyball and weight train, both for the discipline of showing up consistently, not for any title. I also volunteer my time keeping the website and tech running for a local dog shelter, work no one assigned me, for an organization that couldn't otherwise afford it.

How I work

Craft

I hold a relentless bar on the fundamentals (typography, spacing, interaction detail) because small inconsistencies compound fast, especially in systems used by many teams.

Systems thinking

I design for what happens after launch: governance, versioning, migration. A system that drifts within a year isn't a system, it's a snapshot.

Ownership

I'm comfortable owning a problem end to end, including the parts that aren't strictly "design": research, scoping, and writing the spec that gets a team aligned.

AI-native workflow

AI is the first tool I open, not the last. I use it for research and problem framing before a design tool, and for coded prototypes when a question needs a fast, real answer.