Skip to my story

Nice to meet you!
I'm Fabricio.

Senior Software Engineer. I build full-stack products across web and mobile, from frontend architecture to backend integrations.

Resume

Senior

Software Engineer

... years

of experience

Brazil

Based

About me

Journey

I care about the product and the engineering underneath it. React and Next.js, nine years building full-stack features across web and mobile.

What matters

Foundational systems that make teams faster: component libraries, testing infrastructure, design token pipelines, and APIs that hold up under load.

Right now

Building React Native apps, backend integrations, visual testing infrastructure, and design systems across web and mobile.

Technology

JavaScript

TypeScript

React

Next.js

Node.js

GraphQL

Vercel

Azure

Playwright

TailwindCSS

Figma

CMS

Where it all started

From web scrapers to full-stack software engineering. Each role added a layer: performance at scale, the full stack, then leading teams and systems that ship.

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 architecture and performance

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 depth: knowing the cloud, the stack, the system end to end. That is what makes the front-end layer more durable.

Current work

Building foundational systems across web and mobile: design systems, visual testing, backend integrations, and software that teams can ship with confidence.

Full-stack systems and 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.

Things I've actually built

Selected work. What it was, what went sideways, and what shipped.

Tech Lead

Visual Testing System

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

PlaywrightTypeScriptCI/CD
What went wrong

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.

Solo build

Design Token Automation

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

FigmaTypeScriptTailwind CSS
Tech Lead

Live Chat Unification

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

ReactReact NativeGraphQL
What went wrong

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.

Solo build

CMS Architecture Overhaul

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

SanityNext.jsTypeScript
3D Lego portrait of the shop's author, Fabricio Pirini

Still here? Let's talk.