Nice to meet you!
I'm Fabricio.

Growth Engineer. I build the experiments, own the platform, and ship the measurement.

Resume

Senior

Software Engineer

... years

of experience

Brazil

Based

About me

Journey

I care about the experiment and the outcome. nine years in React and TypeScript, building products that measure what matters and ship based on data, not opinion.

What matters

Building the program, not just running experiments. Owning the platform, the tooling, and the cadence. Growth that compounds because the system behind it is solid.

Right now

Setting up event tracking at a US crypto exchange. Instrumented experiments, feature adoption signals, retention data. Making the invisible visible so the team can ship with confidence.

Technology

JavaScript

TypeScript

React

Next.js

Node.js

GraphQL

Vercel

Azure

Playwright

TailwindCSS

Figma

CMS

Where it all started

From web scrapers to design systems, then to growth engineering. Each role added a layer: performance at scale, the full stack, then what moves a conversion needle.

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.

Mentored developers while on-call for the Django backend. Knowing the full stack is what lets me make better front-end decisions.

Growing into growth

Built the first A/B experimentation program at an online grocery startup. Owned the platform, the experiments, and the measurement.

Building the experimentation program

Ran 2 to 4 live experiments per month while building the platform they ran on. The company had no prior experimentation program.

Removed hard-coded locale configurations. Finland and Germany launched without engineering changes to the core platform.

Experiments that taught us something

Ran a homepage restructure: removed the hero section to surface products above the fold. High confidence it would lift conversion. It dropped. Kept the original based on data, not intuition.

Shipped an immersive onboarding flow, stripped to a stepper form and logo only. Added lead capture for out-of-coverage users. Conversion increased.

Current work

Setting up event tracking and experimentation tooling at a US crypto exchange. Making the data layer visible so the team can ship with confidence.

Tracking, testing, and design systems

Set up Segment event tracking for the Support Center portal across web and 3 React Native apps. Instrumented experiment touchpoints and new UI elements to measure adoption and retention.

Built a visual testing system that cut test execution from 12 minutes to under 1 minute and tripled coverage.

Automated design tokens across 11 core components. Designers now push themes to production without opening a ticket.

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.