Reliable by design.
Boring on purpose.

I spent seven years in desktop support and hardware engineering before retraining as a developer in 2022, then working up through DevOps roles (junior, associate, and now senior) over the years since. That path means I've genuinely sat on both sides of an incident: the person fixing the machine, and the person whose pipeline broke it.

Most of what I actually enjoy about the job is the second-order stuff. Fixing a flaky pipeline is one thing; making the fix reusable enough that other teams copy it without being asked is the part that actually sticks. A CI/CD pattern built for one project usually ends up as the default for the rest. The monitoring pack built for one Kubernetes service is what every new service gets wired up with now. And a run of test failures that traced back to AWS spot instance evictions turned into pre-stop hooks, then into how the team debugs infrastructure flakiness generally, not just that one incident. Pairing with junior engineers until DevOps work stops feeling like someone else's job comes from the same place.

Day to day that's Kubernetes, Terraform, CI/CD pipelines and infrastructure-as-code for services that need to stay up. Outside work I run a similar kind of platform at home, because the fastest way to actually learn a tool is to be on call for it yourself.