Skip to my story

Nice to meet you!
I'm Fabricio.

Product Engineer. Ship. Measure. Follow up. Define what moves the needle before writing the first line.

Resume

Senior

Software Engineer

... years

of experience

Brazil

Based

About me

Journey

I care about the user and the metrics. nine years in React and TypeScript. I build the thing, measure whether it solved the problem, and iterate based on data.

What matters

Writing success metrics before writing code. Following up after deployment to see if it worked. Shipping quickly, then iterating. I open PRs early and document decisions because context that stays in your head helps nobody.

Right now

Building a Figma-to-code design token pipeline that powers 3 brand lines. Setting up Segment tracking for a React Native support portal. In both cases the work started with a success metric and a problem statement, not a ticket.

Technology

JavaScript

TypeScript

React

Next.js

Node.js

GraphQL

Vercel

Azure

Playwright

TailwindCSS

Figma

CMS

Where it all started

From web scrapers to product engineering. Each role added a layer: performance at scale, the full stack, then learning that shipping is the easier part. The hard part is whether it worked.

Scaling data collection

Refactored web crawlers and scrapers into 5 independent microservices. 120x faster, 10x less resource usage. Measured the improvement to justify the migration.

Migrated CI/CD from Jenkins to GitLab. 85% reduction in deploy failures. Tracked deployment frequency and failure rate as metrics.

Learning full stack

Worked across Django backend and React frontend. Built A/B experimentation infrastructure from scratch.

The full-stack perspective helps me make better product decisions. I know what's possible, what's hard, and what's expensive.

Building the experimentation program

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

From 0 to 1 experimentation

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

Analyzed results and made go/no-go decisions based on data. Killed features that looked good on paper but failed in the wild.

Measured international expansion

Removed hard-coded locale configurations blocking Finland and Germany. Monitored adoption via product analytics after launch.

The work was done. The measurement proved it worked. Parsed, not guessed.

Current work

Building foundational systems at Kraken. Design tokens that eliminated manual theme work, shared components adopted by 3 teams, and the tracking setup that finally tells us which features users touch.

Figma-to-code design pipeline

Built design token pipeline powering 3 brand lines (6 light/dark variants). Replaced days of manual work per brand change.

Measured reduction in handoff time. Faster time-to-market for brand initiatives.

Component library for internal products

Built a shared component library adopted by 3 product teams. Measured ~25% reduction in feature cycle time.

Tracked component usage patterns to prioritize investment vs deprecation.

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.