Even though I’m a deep technical guy, I’m also an extrovert. I’ve been in the game for 23 years now, and honestly, I’m still in love with what I do. Started from the bottom, installing cables, and worked my way up through traditional companies like IBM, then to FAANGs, and so on. Along the way, I’ve learned what works best depending on the size and expertise of each kind of company.That being said, my profile might appear a bit confusing (at least it does for me), but I consider myself a Developer at heart. I love coding, but I’m oriented towards infrastructure, distributed systems, operating systems, complex network stuff, and automation as a whole. Business logic isn’t my top choice, though I’ve been there many times. What I'm not? Frontend guy. But I’m a problem solver: I like things reliable, I like them fast, and I like performance. Always trying to keep things as simple as possible.Over the years, I’ve picked up over 10 programming languages by heart, countless frameworks, and a range of databases (SQL, NoSQL, time-based, vectorized—you name it). I’ve worked extensively with systems like Hadoop, Kafka, and Spark, plus the newer ones. Basically, I’m a bit of a “technical handyman” who learns fast—and loves to learn.Most of my experience has been in infrastructure and architecture roles, mainly in DevOps and SRE (now leaning to Platform Engineering - IdP). But once I’m working with you, I can cover all bases. I’m a big believer in automation, and years of experience taught me a few core truths: write clean code, document well, always plan for updates (the next guy will love you), and avoid repeating mistakes. Some problems can be fixed with tech, some with better processes.I’m an easygoing person and a positive player who really values people (you might notice that, even with a CS background, I did a postgrad in psychology). When I’m leading a team, I represent them fully—I own that responsibility, and I do my best so they can do their best as well.One last topic: Clouds 🌤 — I go way back. In the early 2000s, I built a cloud from scratch at Globo.com with CloudStack and KVM, developed an orchestrator and the ISaaS's, a DNS-as-a-Service (basically an early Route 53) using Ruby on Rails over Bind. I could’ve used PowerDNS? No! My manager vetoed that! I also set up Database-as-a-Service with Linux kernel cgroups, creating bare-metal slices that some might call early containers. Nowadays, I’m fluent in AWS, GCP, Azure, OCI, and Tencent (yes, I can handle a Chinese dashboard!).* I am an infrastructure specialist first *