About
Solving business problems with platform engineering
I build engineering platforms that let software teams move faster with confidence. Based in Montevideo, Uruguay, the work sits where software engineering, cloud architecture, infrastructure, and production operations intersect — modernizing complex systems, simplifying engineering workflows, and improving operational reliability.
That has meant architecting a multi-tenant AWS EKS platform running 500+ Kubernetes deployments across 3 availability zones, building a device-management layer for 50,000+ IoT devices monitoring public infrastructure, and leading through architecture and hands-on execution rather than people management — staying close to code, infrastructure, and production systems while guiding the engineers around me.
Ambiguity, technical debt, and architectural complexity are usually where the most useful work is — they're opportunities to simplify a system rather than problems to route around. The goal is a platform developers trust, operators enjoy running, and a business can grow on with confidence.
Engineering Philosophy
How the work gets approached
I build platforms that make engineering teams more productive, not just applications that work. A cloud migration or a CI/CD pipeline is only successful if it reduces the cognitive load on the people who operate it every day.
Good architecture is a balance between simplicity, scalability, and operational excellence. The best systems I have shipped were not the most sophisticated — they were the ones that stayed boring, observable, and easy to change under real production pressure.
Architecture Principles
What guides the decisions
Infrastructure as Code over manual operations
If a change to production cannot be expressed in version control, it is not a repeatable process.
Observability is a feature, not an afterthought
Metrics, logs, and traces are designed alongside the system, not bolted on after the first incident.
Simplicity scales better than cleverness
A boring solution that the whole team understands outlives a clever one that only its author can operate.
Automate first, optimize later
Remove manual steps before tuning performance — most reliability problems are process problems in disguise.
Measure before changing architecture
Architectural decisions are justified by data — throughput, latency, cost, incident history — not by trend.
Security by design
Identity, encryption, and least-privilege access are part of the initial design, not a hardening pass before launch.
Technical Leadership
Beyond architecture
Leading platform teams and setting the standards they operate by.
Architecture-Led, Not People Management
Leads through architecture and hands-on execution — staying close to code, infrastructure, and production systems while guiding the engineers on the team.
Mentoring & Team Leadership
Provides technical leadership and mentorship for a team of 3 DevOps engineers at TicketSocket/Halo Media, and led 2 engineers on IoT solutions at Globant.
Production Incident Leadership
Leads technical investigation and resolution of complex production incidents across distributed systems, databases, networking, and cloud infrastructure — driving long-term architectural fixes instead of temporary patches.
AI-Assisted Engineering
Uses AI-assisted engineering (GitHub Copilot, ChatGPT) to accelerate troubleshooting and documentation, while keeping engineering judgment and final review in-house.