Beyond components: architecture, performance, product.

Before code, I closed accounting ledgers. I started out in accounting at Itaú, and moved into development when I realized solving problems with logic hooked me a lot more than solving them with a spreadsheet. Since then, it's been 8+ years of raising the bar: I started with landing pages and e-commerce, worked through Angular, and now I own architecture decisions on products with heavy data and concurrent-user load, mostly in React and TypeScript.

In recent years I've led frontend architecture for products like Auren's real-time energy analytics platform (MVVM, 1M+ records processed daily) and INEO's digital notary platform (a hybrid Next.js + Vite architecture that cut infrastructure cost without sacrificing performance). I also owned the architecture for Familhão, a benefits platform that hit 300K concurrent users on sweepstake days, built on micro-frontends and hexagonal architecture.

I like being close to whoever's making the business call, understanding the why before the how. And I like getting junior devs off the ground even more: mentoring, internal talks, and code reviews that helped whole teams level up, not just ship.

Front-end is still where I live (React, TypeScript, application architecture), but studying AI these last few months pushed me out of my comfort zone of only looking at our own layer. I've been getting back into Node, databases, and the architecture patterns underneath the front-end, because understanding the whole system is what separates implementing a screen from owning the technical decision.