Design Engineer. I build interfaces that look exactly as intended and feel better than expected.
Senior
Software Engineer
... years
of experience
Brazil
Based
I care about the pixel and the pipeline. React and Next.js, nine years building interfaces that work exactly as designed, and hold up under the hood. Not corporate theater. Just craft.
Component craft that scales. Design systems that bridge Figma and production. Every animation, every spacing decision, every hover state is a deliberate choice, not an accident.
Automating the gap between design and engineering. Design tokens that let designers push to production. Visual testing that ships with confidence. The details that make interfaces feel right.
Where it all started
From web scrapers to design systems. Each role added a layer — performance at scale, the full stack, then what it means to make something feel right for the person using it.
Scaling data collection
Rebuilt web crawlers and scrapers from the ground up — 10x faster, half the resource cost. First exposure to shipping at scale and learning that performance is a feature, not an afterthought.
Learned how teams actually work together: Agile in practice, not on a slide deck.
Scaling the platform
Migrated a legacy codebase to React — not just a rewrite, but a chance to rethink every interaction from the user's perspective. Worked with the design team to close the gap between what was designed and what actually shipped.
Mentored developers while on-call for the Django backend. Knowing the full stack is what lets me make better front-end decisions.
Growing into leadership
When I took on leadership, I realized it wasn't about me anymore. It was about making my team and company better.
Frontend performance & design systems
Led frontend architecture for an e-commerce platform. Made things 40% faster by treating performance as a design problem, not a backend problem.
Worked directly with designers to close the gap between intent and implementation. The UI shipped looking exactly like the Figma file. That became the standard.
Defining the front-end standard
Set the component architecture, design token strategy, and front-end practices that gave all teams a shared language between design and code.
The engineering breadth — knowing the cloud, the infra, the stack — informed those standards. Knowing how the system works end to end is what makes the front-end layer more durable.
Current work
Bridging design and engineering. Design systems that scale, visual testing that ships with confidence, tokens that let designers work directly in production.
Design systems & engineering craft
Automated design tokens across 11 core components. Designers now push themes to production without opening a ticket.
Built a visual testing system that cut test execution from 12 minutes to under 1 minute and tripled coverage.
Led live chat unification across web and mobile. One integration, two platforms, consistent experience.
Rebuilt the Sanity content setup. Content teams now deploy articles independently, without engineering involvement.
Selected work. What it was, what went sideways, and what shipped.
Rebuilt the visual regression suite from scratch. Replaced a 12-minute CI job with a sub-60-second Playwright pipeline and tripled coverage in the process.
12 min → <1 min, 3× coverage
First version tried to diff every pixel. Screenshot noise from antialiasing killed the signal-to-noise ratio. Switched to element-level snapshots and the false-positive rate dropped to near zero.
Automated design token propagation across 11 core components. Designers now push theme changes to production without opening a PR or filing a ticket.
11 components, zero engineering overhead per theme release
Led the consolidation of web and mobile chat into a single platform integration, centralizing support tooling for the entire product.
Unified support across 2 apps, one integration to maintain
The web and mobile SDKs had diverged significantly. We had to write an adapter layer to normalize event shapes before we could share any business logic. Added two weeks but saved months of future drift.
Redesigned the Sanity content setup to support multi-product publishing. Content teams can now manage and deploy articles across all products without engineering involvement.
Content deploys decoupled from engineering releases
Still here? Let's talk.
