I joined when Open Insurance was still being added to the codebase. With the Tech Lead I decided on a layered Clean Architecture honoring the dependency rule from day one. Coverage went from 0 to ~90% under a TDD culture I built. About a year in I saw the cross-product cost of reinventing primitives and started the multi-framework Design System. Later, in a PI Planning, the superintendent (Bruno Venceslau) brought up the company's app - Cordova + WebView, basically delegating to the website. I volunteered to lead the rewrite to React Native and added 2FA, FaceID/TouchID and Android biometrics in the process.
Open Insurance from scratch
I joined when the Open Insurance regulated module was just being added. The Tech Lead and I shaped a Layered Clean Architecture honoring the dependency rule - domain pure, infrastructure on the outside. The decision held; the team's onboarding and bug containment both got cheaper as the codebase grew.
TDD from 0 to 90%
There was no testing culture when I arrived. I made automated tests a PR prerequisite, paired through the early sprints to calibrate the bar, then pushed full-time TDD. Coverage climbed from 0 to ~90% over months; the team stopped fearing refactors and started hunting them.
Birth of the Design System
About a year in I could see the cost: every product team rebuilding the same buttons, modals and accessibility patterns in their own framework (Angular, React, React Native, Vue). I proposed the multi-framework DS, got executive sponsorship, and led the team that built it: Figma Tokens Studio as source of truth, bidirectional Figma↔Git sync via Azure Pipelines, monorepo + Storybook as living documentation.
PI Planning + Brasilprev app migration
In a company-wide PI Planning the superintendent (Bruno Venceslau) raised the Brasilprev app - Cordova + WebView, delegating most of its responsibility to the website. I volunteered on the spot. The migration to React Native was mine: I rewrote the app, added 2FA, FaceID/TouchID and Android biometrics, and shipped a foundation that survived the Tech Lead handoff.
Outcome
Two years later: an Open Insurance team running on a clean layered architecture, 90%+ tested codebase, a multi-framework DS adopted across products, and a Brasilprev's app rebuilt on React Native with biometrics and 2FA. The previous Tech Lead recommended me for his seat on his way out.
- Why Layered + Clean Architecture (dependency rule first)?Layered Clean ArchitectureOpen Insurance is a regulated, contract-driven domain. Keeping the domain pure and pushing integrations to the outside meant we could test the regulated logic without spinning up the regulator's environment, and swap integration libraries without touching business rules.
- Why TDD as a hard PR gate (going from 0 to 90%)?Tests required to mergeCoverage targets without a gate decay. The PR gate forced design-for-test from commit one and removed the 'I'll add tests later' debt - particularly important when the regulator can change a contract and break your release window without warning.
- Why tokens-first instead of framework wrappers in the DS?Token-first across all 4 frameworksA token change (color, spacing, radius) propagates instantly across Angular, React, React Native and Vue. A wrapped component would have required library updates per framework - at the speed our brand and regulatory requirements moved, that approach would never catch up.
- Why volunteer for the app rewrite at PI Planning?I raised my handCordova + WebView meant every fix had to ride through the website team. By offering to lead the React Native migration I unlocked a front the company couldn't move on its own - and got to define the foundation (TypeScript, biometrics, 2FA, DS-aligned components) before anyone else owned it.
Open Insurance team running on a clean architecture and a 90%+ tested codebase, the multi-framework DS adopted across products, and app rebuilt on React Native with biometrics and 2FA. The previous Tech Lead recommended me for his seat.