Regulated complexity,
translated into flow

I work where the rules are non-negotiable and users would rather not deal with them: tax invoicing, insurance purchase, credit analysis, branch opening. In these products, the hard part is rarely the screen. It's understanding the real process, with the actors and exceptions nobody documented, and deciding what users need to see and what the design has to absorb.

6 years, two companies

01
Mercado Livre
Sr. UX Designer · 2023 to 2026
Tax and invoicing flows for sellers across several Latin American markets. I designed the re-invoicing self-service in Mexico, which cut support requests by 70%, reusing a global form so the solution could scale to other countries with minimal engineering effort. Then I took on branch opening for Full sellers: a process with 14 touchpoints, three external actors and no internal management tool. I mystery-shopped the real process, mapped the service end to end and delivered the seller flow, the tax team backoffice and the email sequence. Throughout, I brought Amplitude and data-informed decisions into the team.
02
Neon
Product Designer · 2022 to 2023
Zero-to-one products, in partnership with Growth. Fatura Protegida, a card credit-protection insurance built with BNP Paribas Cardif: 100% in-app acquisition, no landing page, three entry points. The flow, the offer screen and the coverage bottom sheet were designed to be reused for other insurance products in the app, and the product became the global conversion benchmark for Cardif in this insurance category. Before that, the debit cashback program, created to retain customers who had been denied credit: nine flows, a dedicated component library adopted by other squads, and 4x more sign-ups at launch.
03
Neon
Junior Product Designer · 2019 to 2021
Credit card lifecycle and a redesign of the credit denial flow. The finding I carry most from that period: increasing the perceived analysis time reduced support contacts, because with an instant answer customers assumed nobody had actually reviewed their application. It was the first time I saw that perception and system are not the same thing.

Three habits that decide the outcome

01
I start with the process, not the screen.
A brief asking for a form is usually hiding a service problem. I'd rather spend a week mapping than a quarter redesigning the wrong part.
02
I design for the second country.
Componentizing, reusing what already exists and planning for the exception state costs little up front and decides whether the solution scales. I built and maintained component libraries at Neon and Mercado Livre.
03
I phase out loud.
Saying "this goes in phase 2" with a blueprint in hand is different from saying it on instinct. I have argued for the less ambitious version because it fit the team's real capacity, and documented the other one as roadmap.

A workshop across cultures

At Mercado Livre, I ran my first workshop with designers from other Latin American countries, in a language that wasn't my own. It was a team-building session: bringing together people who design for the same products without sharing an office or a first language.

Read the post on LinkedIn

What the team says

Anonymous 360 feedback, product teams at Neon and Mercado Livre.

Where I come from

Bachelor of Design, UFCG (2013 to 2018), and UX/UI bootcamp at Ironhack (2019). Design Patterns for Human-Centered AI Experiences (HAX) certification, 2025. Portuguese native, English C1, professional Spanish.

Let's
talk