Caio Alfonso

Career

I started as an intern at an accounting firm, writing jQuery against a Python backend, and talked my way into introducing Vue to the team because it was obviously better than what we had. That's stayed the pattern since: notice what's broken, fix it, own the fix.

From there I refactored a 10 year old PHP legacy system while shipping a new product alongside it, then rebuilt an internal tool into a SaaS product solo, backend included, built in NestJS. For the past couple years I've led frontend architecture on a fintech platform moving millions in monthly transactions, where design system consistency, accessibility and LGPD compliant data handling are simply part of the job. I also run a side initiative there: an internal automation tool wired into WhatsApp and generative AI, where I own the stack decisions and the contracts with backend and infra.

How I work

The parts of an interface most engineers gloss over are where seniority actually shows: keeping optimistic UI in sync with what the server eventually confirms, catching a hydration mismatch before it causes a layout jump, invalidating cached state everywhere it's read after a mutation. That's where trust in an interface gets won or lost.

I'd rather set a standard once than fix the same bug five times across a codebase. Vue and Nuxt are where most of these eight years went. React and Next are next, and this site runs both side by side, on purpose.

Off the clock

Most of my free time goes to my wife and friends, just hanging out and talking, no real agenda beyond that. I grew up on FPS games, Counter-Strike mainly, and still boot it up when friends are around, even though I've long stopped taking it seriously. Music is rock, grunge and nu metal specifically, though I'll listen to most of the genre. Lately I've been teaching myself Japanese on my own, with manga as the excuse to keep showing up to it.

Based in Goiânia, Brazil. Open to new opportunities.