New repo, new problems, same obsession: building things people can trust.

Tomorrow I start a new job at Rivio.

I’ve been sitting with that sentence for a while. It feels exciting, but it also feels like closing a chapter that mattered to me.

I’m leaving Banco John Deere, a joint venture between John Deere and Banco Bradesco. And before I jump into what’s next, I want to write down why I made this decision, not as a goodbye letter, and definitely not as a list of complaints, but as an honest checkpoint in my career.

What I’m leaving behind

I’m grateful for my time at Banco John Deere.

It was a place where I grew a lot as an engineer, worked with smart people, and got to build things that weren’t “toy problems”. I learned what it means to operate in real constraints: timelines, stakeholders, compliance, reliability, and production consequences.

I’m leaving with respect, and with a lot of lessons I’ll carry forward.

Why I decided to leave

The short version: it was time to change the kind of trade-offs I was making.

The longer version has two main pieces.

1. Hybrid work wasn’t the problem, the commute was

My work situation changed from remote to hybrid. On paper, that sounds normal.

But my reality was: I’m moving back to São Paulo, and the office is in Indaiatuba. With the hybrid model (3 days a week), the commute would take almost 5-6 hours per day.

And at some point you have to call things by their name: that’s not “a small inconvenience”. That’s a lifestyle.

I don’t have a problem working in an office. I have a problem spending a huge part of my week inside a bus/car, arriving tired, leaving tired, and losing time that could go to health, learning, and life.

2. I wanted a stronger data engineering environment

Another reason is more personal.

I realized I was craving an environment that pushes me more: stronger technical references, deeper engineering discussions, and a culture that naturally makes me study, sharpen me tools, and level up.

Not because my previous team was bad, but because I’m at a point where I want a new slope of learning.

Why I said yes to Rivio

I’m joining Rivio as a Senior Data Engineer.

What made me say yes is the combination of challenge + growth:

• The chance to build data infrastructure from zero, with real ownership.
• The opportunity to shape a lakehouse direction from the beginning.
• The chance to dive into a new cloud for me: GCP (until now, I’ve mostly worked with AWS).
• And the chance to work again in a startup environment.

I like problems where the question isn’t “how do we patch this?”, but “how do we design this so it can scale and stay sane?”

That’s what Rivio feels like.

What I’m carrying with me

From Banco John Deere, I’m taking principles I don’t want to compromise anymore:

• correctness over hype
• boring systems over fragile cleverness
• standards that reduce ambiguity
• and the mindset that reliability is part of the product

What I want this next chapter to look like

Tomorrow isn’t a finish line. It’s a starting point.

My goal for the first weeks at Rivio is simple:

• listen a lot
• understand the system
• earn trust through small wins
• build momentum

If I do that well, the rest will come with time.

---

I’m nervous, but it’s the right kind of nervous.

The kind that comes from choosing growth, and choosing my time back.

On to the next commit, I’ll share what I learn.