I'm an engineering leader with 19+ years in technology, with a career that started close to the code and evolved into building teams, products, platforms, and engineering organizations.

My sweet spot is the intersection of engineering, product, people, and business — especially in environments where technology needs to scale without losing clarity, ownership, or customer impact.

I have worked across fintech, payments, credit, marketplaces, and digital products, including chapters at Stone, Pagar.me, Mundipagg, and OLX.

I still care deeply about code. I just spend more of my time today designing the systems — technical and human — that help great engineers do their best work.

I don't define myself by a stack — and today my role is much more about technical leadership, architecture, and the decisions around these technologies than being hands-on with all of them every day. Across different products and stages of my career, these are some of the ecosystems I've worked with or led teams around:

engineering = people × product × technology × context

leadership:
  - autonomy with context
  - candid feedback
  - strong engineering managers
  - high-performing, humane teams

engineering:
  - simple systems before clever systems
  - explicit trade-offs
  - observability before guesswork
  - reliability as a product feature

product:
  - customer problems before solution theater
  - measurable outcomes
  - technology as a business capability

I've been on GitHub since 2012. A lot of what you'll find here reflects different chapters of my career: front-end experiments, JavaScript, Angular, tooling, open-source forks, learning repositories, and the occasional rabbit hole.

Today, I'm gradually turning this profile into a more intentional record of what I study, build, and think about as an engineering leader.

So yes — there is some archaeology here. 🦖

• System Design — capacity, reliability, distributed systems, trade-offs
• Software architecture — keeping complexity proportional to the problem
• AI + Engineering — tools, workflows, productivity, and organizational impact
• Modern backend engineering — Node.js, TypeScript, testing, APIs, async workflows
• Leadership systems — organizations that can move fast without depending on heroes

When I'm not thinking about software organizations, there's a good chance I'm somewhere around:

cinema · guitars · history · comics

Some systems are distributed. Others are just the X-Men continuity.

Let's connect

I'm always interested in conversations about engineering leadership, product, fintech, architecture, and the future of software development.