15 years of cloud and DevOps experience, most of it leading cloud migrations and running the DevOps teams that keep production honest at 3am.

I've built and led a DevOps team directly, and mentored engineers through an online cloud-engineering program. Teaching that skill matters to me as much as writing the code itself.

I've run infrastructure from the inside and advised on it from the outside. I bring that directly to every engagement, as your single point of contact from the first call to the last deploy.

What I Actually Work In

The domains I work in day to day, grouped by what breaks together.

$ tree ~/skills
cloud-infrastructure/
├── aws
├── gcp
├── kubernetes (gke/eks)
├── terraform
└── docker

reliability-cicd/
├── gitlab-ci
├── github-actions
├── prometheus-grafana
└── disaster-recovery

data-systems/
├── postgresql-tuning
├── linux-administration
├── python
└── go-automation

How I Think About Infrastructure

• Cost tracks usage, not habit. Most cloud waste isn't a bad decision. It's a decision nobody revisited after the traffic pattern changed.
• An untested failover is a guess. Backups and rollbacks only count once someone has actually pulled the trigger on them outside of an incident. I'd rather find the gap in a drill on a Tuesday than during the real thing.
• Developer enablement. The best infrastructure is the kind engineers stop thinking about: guardrails and self-service that make the safe path also the fast one.

How I Work With Teams

• I work inside your repos, next to your engineers. Changes ship as PRs in your CI/CD, alongside your team, throughout the engagement.
• Every fix ships with the why. Documentation and a pairing session go out with every change, so your team can maintain and extend it without me on call.
• I'm reachable mid-engagement. Questions get answered in your Slack or standup that week, not saved up for a final report nobody reads.

Outside of client work, I'm still the person who notices when something's off and wants it fixed. If we end up working together, that's the same attention you're getting.