I'm Aditya, a DevSecOps Engineer who enjoys understanding what happens behind the scenes.
I work at the intersection of infrastructure, security, and software, building the systems that allow applications to run reliably and securely. My day-to-day work involves things like Kubernetes, cloud infrastructure, CI/CD, automation, observability, and security, but what interests me most isn't any particular tool. It's understanding how all these pieces fit together.
I like taking something that works, but is manual, fragile, or difficult to maintain, and asking:
“Can this be automated? Can this be made simpler? Can it be made safer? What happens when it breaks?”
That mindset has shaped how I approach engineering.
From writing code to running systems
I started out on the software side, building applications and experimenting with different technologies. Over time, I became increasingly interested in everything happening outside the application itself: how it gets deployed, how infrastructure is provisioned, how services communicate, how failures are handled, and how we keep the whole thing secure.
That eventually led me toward DevOps and, naturally, toward DevSecOps.
Today, I spend most of my time working with cloud platforms, containers, Kubernetes, infrastructure-as-code, CI/CD pipelines, monitoring, and security. I enjoy the kind of problems where there isn't always a single correct answer and you have to understand the system before you can fix it.
What I enjoy building
I'm particularly drawn to systems that are automated, observable, reproducible, and boring in the best possible way.
A good infrastructure setup shouldn't require someone to remember a sequence of commands. A deployment shouldn't depend on one person's machine. Security shouldn't be something added at the very end. And when something inevitably breaks, the system should give you enough information to understand why.
That's the kind of engineering I try to practice.
Beyond the terminal
Technology is a big part of my life, but it isn't all of it.
I like travelling, exploring new places, discovering new technology, and occasionally going down completely unnecessary rabbit holes just because I want to understand how something works.
I'm also interested in the bigger picture: not just becoming better at the tools I use today, but continuously figuring out what I should learn next.
There is a lot left to explore.
And that's probably what I enjoy most about engineering: there is always another layer underneath.