I started out the way most engineers do — curious, and mildly obsessed with knowing why things work. That curiosity didn't stay academic for long. It turned into building and operating cloud infrastructure that other engineers depend on without ever thinking about it, which is exactly the point.
Most of my working life happens somewhere between Kubernetes operators, distributed backends, and the dashboards that tell you the truth about both. I've spent years around systems that manage thousands of clusters — the kind of scale where a small inefficiency stops being small, and a quiet bug becomes everyone's Tuesday.
I like building things. I like understanding why they break even more.
That's not a tagline — it's roughly how I spend my time. Reliability engineering, at its core, is applied curiosity: you're always asking what happens next, what happens at 3am, what happens when the thing you didn't think about happens. I find that question genuinely interesting, which probably explains the rest of this website.
