Skip to content
Open to board advisory and board seats — 2H 2026, then CY 2027–2028.
See details →
Cloud · DevOps · SRE

Cloud, DevOps & infrastructure

How I think about cloud architecture, platform teams, and DevOps in regulated, high-growth environments.

Pillars

Multi-cloud landing zones

Account/subscription structure, SCPs, paved roads, and the boring guardrails that pass audits cheaply.

CI/CD & GitOps

Pipelines as product, signed builds, progressive delivery, and rollback you can trust at 2am.

Platform engineering

Internal platforms run like real products — roadmap, NPS, paved roads, tiered support.

DevSecOps

Shift-left controls that don't slow shipping: SAST, SBOMs, secret scanning, policy-as-code.

Reliability & SRE

SLOs that match revenue, error budgets engineers actually respect, on-call you can sustain.

FinOps & cost

Tagging that holds up, unit economics per workload, rightsizing as a recurring practice.

Reference stack

Compute
  • AWS (primary)
  • Azure
  • EKS / Kubernetes
  • ECS Fargate
  • Lambda
Delivery
  • GitHub Actions
  • ArgoCD
  • Terraform
  • Helm
  • OpenTofu
Observability
  • Datadog
  • OpenTelemetry
  • Grafana
  • PagerDuty
  • Sentry
Security
  • Wiz
  • Snyk
  • OPA / Gatekeeper
  • Vault
  • AWS Security Hub

Building or rebuilding a cloud platform?

I advise fintech and regulated SaaS teams on cloud architecture, DevOps maturity, and platform engineering.