Kandra B.

I didn't start out wanting to be a DevOps engineer — I started out wanting to understand how things actually work under the hood. That curiosity is what pulled me from computer science fundamentals into the world of infrastructure, observability, and distributed systems, and it's what keeps me going today. In just under a year at UnifyApps, I've had the opportunity to work across a breadth of challenges that most engineers don't see until much later in their careers. I've set up Kubernetes clusters from scratch — bare metal in data centres, on-prem environments, and managed services like EKS, GKE, and AKS — which gave me a deep appreciation for what managed cloud services abstract away, and more importantly, what they don't. Running workloads across AWS, GCP, Azure, and Moro Cloud simultaneously taught me that "cloud-agnostic" is easy to say and hard to actually deliver. One of my proudest contributions has been building out a full observability stack — Prometheus, Grafana, Graylog, OpenSearch, and Fluent Bit — from the ground up. Observability isn't just about dashboards; it's about giving teams the confidence to ship fast and sleep at night. Getting alerting rules tuned well, log pipelines structured correctly, and dashboards that actually tell a story — that's where I find real satisfaction. What makes me a little different is that I don't just operate infrastructure — I build on top of it. I wrote a Kubernetes dashboard application in Go that lets developers update deployment image metadata without ever needing cluster access. It's a small tool, but it removed a real bottleneck and gave developers autonomy without sacrificing security. That intersection of DevOps and development is where I want to grow. I'm passionate about cost efficiency too — implementing Karpenter and KEDA to right-size compute resources showed me that smart infrastructure design isn't just a technical win, it's a business one. If you're looking for someone who can set up your clusters, own your observability, collaborate with your backend teams on Kafka and MongoDB, and still write production Go code — I'm your person.