Consulting & advisory

Platform engineering
for teams running
serious GKE workloads.

Your team is running Kubernetes in production. But nobody truly owns the platform layer. IAM is sprawling, alert fatigue is real, Terraform state is a mess across three projects, and the deploy process relies on institutional knowledge that lives in one engineer's head.

I've spent the last decade building and operating GCP infrastructure and GKE clusters across enterprise environments — from IBM storage to healthcare to financial services. I work with engineering teams that need a senior platform engineer without a full-time headcount.


Is this your situation?

  • You're on GKE and GCP but your cluster setup grew organically — no consistent approach to namespacing, RBAC, node pool sizing, or workload isolation.
  • Your Terraform is working, but barely — monolithic state, manual applies, no clear ownership between teams, and upgrades that nobody wants to touch.
  • Security is a shared assumption — IAM roles broader than they should be, secrets in environment variables, no systematic way to handle rotation or audit.
  • Incidents take too long to diagnose — observability is patched together, runbooks are stale, and post-mortems don't stick.
  • You need a senior infrastructure opinion on an architecture decision, a migration, or an incident — without waiting for a six-week procurement cycle.

How I work


Recent work


I'm a platform engineer and DevOps practitioner based in Philadelphia. I've worked across GCP, AWS, and Azure, with the deepest production depth on GKE and GCP. My background spans enterprise environments at IBM and Equifax, healthcare infrastructure, and early-stage product teams.

I write about what I actually work on — production incidents, infrastructure migrations, security engineering, and platform design — at cloudista.org. The writing is the portfolio.

I'm a polyglot engineer. I default to Python and Go for infrastructure tooling, but I work in whatever the codebase requires. I'm not interested in rewriting your stack — I'm interested in making it operationally sound.


Get in touch

Tell me what you're working with. I'll respond within one business day. If it's not a fit, I'll say so directly and point you somewhere useful if I can.

No sales process. No NDAs to sign before a conversation.