Active project
Riel
I’m building Riel to make everyday company management easier to understand, for small businesses in Argentina.
Product definition, development, and operation
Engineering leadership,
from code to organizations.
I’m Head of Engineering at Make, leading engineering across its projects and the adoption of AI in software delivery. My career began in teaching and software development, and grew into leading teams, managers, and engineering organizations.
Career
From software engineer to engineering leader.
The timeline begins with teaching and early software work, then follows a ten-year progression from engineer to Head of Engineering and my current role at Make.
-
2024 — present
Head of Engineering
I lead engineering across all of Make's projects and the company-wide adoption of AI in software delivery. My work combines research, practical playbooks, internal tooling, and direct support for teams.
-
2014 — 2024
Software Engineer → Head of Engineering
Citrusbyte · Theorem · TheoremOne · Formula.Monks · Monks
This was one ten-year chapter at the same company, through several name changes and the 2022 integration with Monks. I moved from hands-on engineering to leading engineering organizations: roughly 90 engineers before the integration and approximately 350 people afterward.
How I lead
Simple systems, shared decisions, high standards.
-
01
Remove unnecessary complexity
I make the mission, priorities, constraints, and quality bar explicit, then keep only the processes and abstractions that help people decide or do the work.
-
02
Develop leaders and share decisions
I delegate decisions with real consequences and coach leaders at every level so the organization can make sound decisions throughout.
-
03
Combine high standards with respect
I pair direct conversations about quality and accountability with honesty, respect, and care for the person doing the work.
Projects
Products and tools.
Writing & conversations
Ideas in practice.
-
Building MCP servers in the real world — The Pragmatic Engineer
Quoted on using current external documentation in coding-agent and MCP workflows.
-
The Captain’s Cabin — Remote engineering teams
A conversation about remote engineering, communication, consulting, hiring, client expectations, advice for founders scaling a company, and product-minded engineers.
-
Best practices for taking advantage of Airbrake
Patterns for turning error reports into useful engineering feedback that teams can act on.
Influences
Books that shaped my career.
A personal, unranked collection of books that changed how I build software, lead people, and design organizations.
-
The Manager’s Path
One of the first books I read when I began leading people. It gave me a map for the transition from engineer to leader: how the role changes as its scope grows, and how trust, feedback, delegation, and thoughtful 1:1s help people develop. I still recommend it to engineers considering the leadership path.
-
The Coaching Habit
It reshaped how I approach 1:1s: stay curious longer, make room for silence, and ask questions that help people find their own way forward instead of reaching too quickly for advice.
-
Code Simplicity
This book made simplicity central to how I think about software. Systems inevitably grow and change, so I try to keep their individual parts understandable, reduce maintenance effort, and favor designs that make future change easier even when I cannot know exactly what that future holds.