Gabriel
Rigon

Where I add the most value

Three problem shapes that keep coming back, whatever the industry.

Owning the technology function

Architecture, delivery, infrastructure and the calls that carry real risk, held end to end. I've seen which decisions compound and which ones quietly cost you a year.

AI where the stakes are real

This means production, not pilots, and the hard part is getting a team to trust it, use it the same way twice, and stay inside the lines when nobody's watching.

Leading engineering at any scale

From a single squad to a whole technology organization, the standards a team refuses to drop are what scale with it.

Track record

I started in 2010 building websites and Rails apps, then moved through developer, tech lead and architect roles. Today I'm CTO at Appolus Tecnologia.

That path made me a full-range engineer, from native mobile apps to back ends and the infrastructure under them. I've built consumer iOS apps, SAP integrations, APIs for Brazil's national health data network, search over large medical datasets, and systems that tens of thousands of people use every day.

I've always worked inside the problem, not next to it, through audits, outages, migrations and public deadlines that don't move. Building something that many people actually use never stopped being a good reason to get up.

On my own time I build small apps at gbrlrg.com.br and a free civic education app, Saber Importa.

Away from all that, I'm into good food, the beach, trekking, travel and sun.

What I'm working on

Most of my time goes into R&D, the part of the job I'd keep if I had to drop everything else: finding and rolling out what makes teams faster, and not only the technology ones.

Right now that means AI in critical delivery. Every gain is measured before I call it a gain, and so far the numbers have held up.

How I work

Simple solutions to complex problems. The architecture is whatever serves the outcome best, and I care about the result, the quality, and not wasting the team's time.

I lead teams of every size with the same technical depth, and I'm still close to the code, because you can't hold a technical conversation you can't have yourself. I understand the problem, cut it to its essentials, ship it and measure what happened.

I also build for handover from day one, writing decisions down, naming owners, and setting standards a team can hold without me in the room. If the work only works with me in it, it isn't finished.

Toolbox

Ordered by where I carry the most weight today, not by where I started, and it keeps growing from here.

Contact

The best way to reach me is email. My résumé is one click away.