Most of my recent work sits at the intersection of cloud engineering and operations: infrastructure, automation, and keeping systems running. Security was always part of that picture, but I want it to be the center of how I design and evaluate systems—not an afterthought bolted on at the end.
What pulled me in
Identity and access problems are infrastructure problems. So are logging, segmentation, and safe deployment pipelines. Once I started treating those as first-class design constraints—not ticket-queue noise—the work became more interesting and more impactful.
How I'm approaching the shift
Deliberate practice: labs, policy-as-code experiments, and writing down what I learn. I am not chasing certification bingo; I am building depth in areas that show up in real environments—Entra ID, Zero Trust patterns, secure CI/CD, and cloud-native detective controls.
What I hope to contribute
Teams need people who can build and defend. I want to be useful on both sides: shipping reliable platforms while making abuse paths narrower and incidents easier to understand. This blog is part of that—short, honest notes as the transition unfolds.