About
I build systems, solve problems, and look for ways to make things better.
I'm an engineer with nearly five years of experience across DevOps, DevSecOps, and Platform Engineering. My work revolves around building cloud infrastructure, automating processes, strengthening security, and helping teams deliver and operate software more efficiently.
My professional journey has taken me through Inchcape Digital Delivery Center Philippines and Essilor Shared Services Philippines, where I've collaborated with engineering teams across the Americas, Europe, and Asia.
Along the way, I've designed infrastructure and implemented DevOps workflows for a greenfield product now serving customers in China, improved secrets management across enterprise Kubernetes environments, and built automation that helped reduce annual Azure subscription costs by approximately 25%.
But what I enjoy most about engineering isn't necessarily the technology itself. It's understanding how systems work, recognizing where things could be better, and figuring out how to improve them.
How I Approach Engineering
I don't believe a good engineer is defined by how many tools or technologies they know.
Tools change. New technologies emerge. What works today might not be the best approach tomorrow.
What matters is the ability to understand a problem, adapt to unfamiliar environments, evaluate different solutions, and make informed technical decisions.
For me, engineering goes beyond making something work. It's about asking whether there's a simpler, more secure, more reliable, or more maintainable way to build it.
I also believe that good engineering is a team effort.
Technical skills matter, but so do communication, transparency, and the willingness to share knowledge. I value working with people who challenge ideas, ask questions, and aren't afraid to admit when there's something they don't know.
I try to bring that mindset into every project: understand the problem, question assumptions, stay open to better approaches, and help the people around me succeed.
Building Beyond Work
My interest in technology extends beyond my professional responsibilities.
I run a personal Kubernetes homelab where I build, experiment with, and operate infrastructure for applications I use in my daily life.
The environment includes self-hosted applications with public and VPN-restricted access, monitoring with Prometheus and Grafana, ingress routing through Traefik, automated TLS certificate management with cert-manager, and a container registry for my Docker images.
I manage the infrastructure using GitOps, with configurations available in a public repository.
For me, maintaining a homelab is about more than self-hosting applications.
It's an environment where I can experiment freely, troubleshoot problems, understand technologies beyond their documentation, and turn ideas into working systems.
It's also a constant reminder that there's a difference between knowing how a technology works and being responsible for operating it.
→ Explore My GitOps Repository
Engineering in the Age of AI
I've been integrating AI into my engineering workflow since 2023.
What began as using AI for research, troubleshooting, and improving scripts has evolved into working with coding agents like Claude Code and Codex, alongside context management, reusable agent skills, and structured prompting.
I'm particularly interested in how AI can change the way engineers approach everyday work, from accelerating development to reducing repetitive tasks and exploring solutions more efficiently.
But I also believe that writing code faster doesn't automatically mean building better software.
AI-generated solutions still require engineering judgment. We need to understand what we're building, validate its behavior, recognize its limitations, and take responsibility for the outcome.
I see AI as an evolving part of my engineering toolkit, not a replacement for the fundamentals.
What Drives Me
One of the things I appreciate most about engineering is that there's always something new to learn.
I don't want to define myself entirely by a job title, technology stack, or particular area of expertise.
I've spent much of my career working with cloud infrastructure, Kubernetes, automation, and security. But I'm equally interested in understanding the software, systems, and tools that connect everything together.
I want to keep becoming the kind of engineer who can step into an unfamiliar environment, understand how things work, collaborate with the people involved, and contribute something meaningful.
My philosophy is simple:
Understand the problem. Build thoughtfully. Stay adaptable. Keep improving.
Whether I'm working on production infrastructure, experimenting in my homelab, or exploring new engineering workflows, that's the mindset I try to bring to everything I do.