About

Staff-level DevOps / Infrastructure Engineer with 10+ years of hands-on experience. Specialized in Kubernetes, multi-cloud platforms, and production systems at scale. I’ve led infrastructure design at two very different companies — a unicorn identity startup and an enterprise security product — and taken both from “it works” to “it scales, it’s observable, and it doesn’t wake anyone up.”
Started in tech support in 2014. Moved to Linux administration, then hosting infrastructure, then eCommerce platforms, then Docker, then Kubernetes, then owning multi-cloud platforms end-to-end. Each step was a deliberate climb toward harder problems and more ownership.
Engineering principles#
I don’t have a manifesto, but I do have opinions shaped by shipping real systems:
- Everything is code. Infrastructure, configuration, policy, deployment — if it’s manual, it’s broken.
- Monitoring isn’t optional. If you deploy something and can’t tell whether it’s working, you haven’t deployed it.
- Complexity is debt. Every abstraction layer you add is a layer someone has to debug at 3am.
- Automation makes humans faster, not redundant. The goal is to eliminate toil, not judgment.
- Ownership over activity. A platform you own end-to-end is more valuable than ten features you touched.
Core stack#
Orchestration: Kubernetes (EKS, GKE), Helm, Kustomize, ArgoCD IaC: Terraform, Pulumi (TypeScript) Cloud: AWS (deep), GCP CI/CD: GitHub Actions, GitLab CI, Jenkins Observability: Datadog, Prometheus, Grafana, ELK Languages: Python, Bash, TypeScript, Go Data: MySQL, PostgreSQL, Redis, Elasticsearch
Leadership#
Principal DevOps at Palo Alto Networks (mentorship, architecture ownership, cross-org reviews). Comfortable operating with ownership and influence without formal management — driving decisions through technical rigor, not org-chart authority.
This site#
I built this as a weekend project that got out of hand (in a good way). The full architecture is documented in the source repo. It’s intentionally over-engineered — that’s the point.