I studied Computer Science - UFSCar (2015), started as a developer, and moved early into the Salesforce ecosystem - first as an administrator, then developer, consultant, and now architect.

That progression wasn't just a sequence of certifications. Each stage changed how I think about systems: administration taught me the real cost of poorly thought-out decisions; development taught me how to implement; consulting taught me to listen to the business problem before proposing the technical solution. Architecture is where those three things meet.

Today I work as an independent consultant, providing Salesforce architecture, integrations, and delivery engineering services across multiple clients and projects - not as an employee of a single company. I prefer working this way because it forces technical decisions to stay justifiable across different contexts, not just within one team.

In recent years, that has come to include AI applied to software engineering - not as a trend, but as another architecture tool: where it solves a real problem reliably, and where it only adds complexity. That's also the central subject of Force Tricks, where I write about Salesforce, architecture, and applied AI based on what actually worked in production.

I learn best when I need to explain something - that's why documenting architecture decisions, not just making them, is part of how I work.