Career

This is the first post in a series where I’ll translate the world of AI into the language that infrastructure engineers already speak. If you’re the kind of professional who configures VMs, builds CI/CD pipelines, and gets woken up at 2 AM when Nagios fires, this content is for you. The series is based on my open-source book AI for Infrastructure Professionals, adapted and expanded here on the blog. tl;dr AI is another workload with different performance, cost, and data patterns. Infrastructure engineers already own the hard parts: compute, networking, security, observability, and cost control. If you can run production infrastructure well, you already have the foundation to support AI systems. The Monday morning message It’s 8:47 AM on a Monday. You’re halfway through your coffee, reviewing a Terraform plan for a network redesign, when a Slack message lights up your screen. It’s from the data science team lead: ...

Had a 1:1 last week. Nothing unusual, just a regular conversation, catching up on things. But there was one moment that stayed with me after the call ended. At some point he said he usually thinks about people in four different ways. Not as an official framework or anything like that, just how he personally sees it. And I don’t know, the way he explained it felt simple, but it kind of stuck. ...

Over the past year, I’ve been working closely with some of the bigger and more visible AI customers in Microsoft’s ecosystem. Large platforms. Fast-moving teams. High expectations. High stakes. On paper, that kind of visibility sounds exciting. In reality, it comes with a weight that’s hard to explain unless you’ve been there. Because being close to impact also means being close to consequence. Visibility changes everything When you work with smaller teams or early-stage projects, mistakes are usually contained. You can recover. You can explain. You can iterate. ...

Throughout my career, I’ve had countless conversations about career paths with colleagues, mentees, and professionals in transition. In those talks, I often share practices that have helped me personally along the way. But this article is different. It’s transparent and honest. Although I’ve spoken about parts of my story with people close to me, this is the first time I’m sharing it so openly, including my mistakes, lessons, and reflections in a public space. ...

It’s easy, even comforting, to blend in with your badge. We introduce ourselves with our name followed by the company. We join meetings carrying that title. We post with the credibility it gives. But at the end of the day, the company is just where you are, not who you are. You are what you’ve built. What you’ve learned, and taught. You are the reputation that stands when your name shows up alone. You are the value that stays when the badge is gone. ...