Leonardo Ribeiro
Prepared for Rafael Quiroz De Lucia · Everforth Apex
Email me
UX Engineer · São Paulo, Brazil · Remote

I work on the seam between Figma and production.

Hi Rafael, thanks for the conversation. This page is a quick view of how I work as a UX Engineer, built so you can skim it or pass it on to the hiring team.

HighALERT · INV-07

Inverter 07 underperforming

6 related alarms · since 09:12
O&MO&M team · NorthAssign
AlertCard / severity=high
24
gap 16
radius 12
FigmaReact
Same component, two sources of truthDrag to compare
01 · Role fit

What a UX Engineer role asks for, and where I've done it.

Each line points to real work. Happy to go deeper on any of them.

Figma

My daily tool for five years. Component libraries with variants and variables, dev-ready specs, and public, organized files linked from my portfolio.

Daily

Storybook

Built a live documentation site on top of a React Storybook with ~180 components, showing every variant and the real JSX to copy.

Shipped

Documenting designs

Multi-screen specs with states and edge cases, client-facing and internal audit documents, and a Design Field Guide for onboarding.

Shipped

Jira

Ran PM validation of Jira tickets before release, across multiple clients, as the bridge between design, product and QA.

Daily

Usability on web apps

In-context research with port terminal operators, and redesigns with measured results: +23% session time, +18% conversion.

Shipped

AI design tools

Claude Code, Lovable and HTML prototyping to test ideas in real code. I also wrote an llms.txt so AI agents can build with the design system.

Daily

Complex operational apps

Ops-critical web apps in energy monitoring and port logistics: alarms, schedules, live status and decisions under time pressure.

Shipped
02 · Proof

A design system that lives in the code.

At Delfos I was the only designer on D4, a renewable energy monitoring platform for asset managers and O&M teams. Instead of handing off static screens, I built a documentation site inside the product's React repository. It reads the Storybook build, renders each component in the real theme, and shows developers the JSX to copy. When the code changes, the docs change with it.

It lived in an isolated folder, so developers' code was never touched until review.

Fg
Figmasource designs
{ }
Theme tokensone source
</>
React componentsAnt Design first
Sb
Storybookstories, states
Docs
Live docs sitewhat I built
Devs and AI agentscopy, build, ship
~180components documented live
552design tokens from the real theme
2theme modes, light and dark
1llms.txt so AI agents can use the library
Ant Design firstTheme tokens before custom CSSReact code in every exampleStatus: stable · in transition · experimental
03 · Proof

Prototypes people can click, not imagine.

When interaction matters, I prototype in the real medium, so product, sales and clients react to something that behaves like the product.

Delfos · Data Studio

Analytics module in HTML

An interactive prototype of the core analytics module: five user-flow prototypes and a master prototype built on Highcharts, iterated with the PM.

Delfos · Maintenance Planning

A sales request, prototyped in days

A maintenance timeline with multi-month tasks, requested by sales and built on the same design system as the rest of the product.

<div class="card">
Workflow

Figma to HTML, repeatable

A migration workflow that moves Figma screens into HTML with the product's tokens, plus a 12-point UX audit of a PM-built AI prototype.

04 · How I work

Four habits the team will notice.

Specs you can build from

States, edge cases and tokens in every handoff, so developers don't have to guess.

Prototype in the real medium

HTML or React when interaction matters. Figma when layout is the question.

Validate before release

I check tickets against the design before they ship, and flag gaps early.

Remote by default

Years on international teams across Europe, the US and LatAm, working in English.

Based inSão Paulo, BrazilRemote, international teams
Time zoneUTC-3Overlaps US Eastern business hours
LanguagesEnglish, PortugueseFluent English, native Portuguese
BackgroundInformation SystemsComfortable inside front-end codebases

Thanks again, Rafael. Let's keep in touch.

If the hiring team wants to see anything in more detail, a Figma file, a prototype or a specific case, I'm happy to send it.