From building applications to running them in production.

I started out as a web designer, building responsive interfaces with HTML, CSS, Bootstrap and JavaScript. That was where I learned to care about how something behaves once it is in front of a real user.

From there I moved into full-stack development, working on MERN applications and REST APIs. After the internship I kept building through paid freelance work alongside my BCA, delivering client websites from development through deployment, including AWS/Vercel hosting and production domain configuration. That led into a Software Engineer role at MyPay working on POS and payment-related systems. Payments are unforgiving: you learn quickly that shipping the code is only part of the job, and that most of the interesting problems show up in production.

The move into DevOps wasn't a sudden reset. Within my first months at MyPay, I began managing production servers, automating deployments that had previously relied on manual AWS steps, and introducing Docker-based workflows and CloudFront delivery for files and images — all while continuing to build application features. Moving into the dedicated DevOps Engineer role in July 2026 formalised work I was already doing.

Today that is the whole job. Day to day it means AWS infrastructure and production environments, Docker and Kubernetes on EKS, Terraform for infrastructure as code, and CI/CD pipelines in Jenkins and GitHub Actions. It also means Linux servers, Nginx, deployments, and keeping an eye on things through Grafana, Loki and CloudWatch.

The part I think actually matters is the overlap. When a service degrades, I am not only looking at nodes and pipelines — I can read the application, the API and the database behind it. Knowing what is being deployed, not just where it runs, is the difference between guessing and diagnosing.

I keep building on that with hands-on work in observability and platform reliability, and I'm open to DevOps roles on-site, hybrid or remote, including relocation.