How I can help
Platform Audit
A fast, focused review of your cloud and Kubernetes setup to identify what's broken, fragile, or costing too much.
What you get:
- Clear breakdown of what's broken or fragile
- Identification of scaling and reliability risks
- Cost inefficiencies and optimization opportunities
- Gaps in infrastructure as code, CI/CD, and automation
- Prioritized next steps for fixing the platform
Platform Build / Fix
I design, rebuild, or stabilize your platform so it behaves predictably under real-world load and doesn't break when you scale. This includes infrastructure as code, CI/CD pipelines, and deployment workflows that remove manual steps and improve reliability.
- Cloud platform work across AWS and GCP
- Kubernetes — managed (EKS, GKE) or self-hosted
- CI/CD and GitOps improvements
- Infrastructure automation (Terraform, Pulumi, Crossplane)
- Reliability and scaling remediation
Advisory
Ongoing support to help you make the right platform decisions as you scale.
- Architecture and platform guidance
- Review of RFCs, designs, and post-incident follow-ups
- Troubleshooting and technical direction
- Hiring signal for platform, SRE, and infra roles
Not sure which one?
Most engagements start with a Platform Audit. If you already know what needs fixing, we can go straight to build. If you just need a second opinion, advisory.
What I work on
I work directly on production systems:
Platform Health Check
Identify bottlenecks, risk, and unnecessary complexity — with clear next steps to improve.
Kubernetes
Managed or self-hosted. Predictable upgrades, scaling, and day-two operations.
CI/CD & GitOps
Faster, more reliable delivery through pipelines your team can actually maintain.
Infrastructure as Code
Terraform, Pulumi, or Crossplane — standardized so changes are reviewable and safe to ship.
Scaling & cost
Cut waste and attribute spend to teams, services, and resources — not blanket downsizing.
Architecture review
Stress-test big bets before you commit — networking, clusters, and how changes reach production.
How engagements work
1. Short call
What you're running, what's hurting, what good would look like. If it's not a fit, I'll say so.
2. Scope agreed up front
Audit, build, or advisory — time-boxed with a defined outcome. No open-ended hours.
3. Hands-on in your stack
I work in your repos, clusters, and cloud accounts. Async-first, with calls when they move the work forward.
4. A platform your team owns
The goal is a system your team fully understands after I leave — not an ongoing dependency.
Not sure if this is a fit? We can figure that out quickly on a short call.
OpsDevCode