DevOps & Platform Engineering
Pipelines and clusters we owned from design through on-call
A pipeline is where every decision about isolation and access either holds or quietly stops holding, and it is usually the thing nobody owns end to end. We migrated about 300 business-critical services from Docker Swarm to Kubernetes with zero downtime. That platform ran on AWS, with Terraform standing the infrastructure up and Vault holding the secrets.
Elsewhere:
- CI/CD for 100+ microservices on Jenkins, GitHub Actions, and Bitbucket, at an AWS Premier Partner serving 200+ high-growth startups
- Kubernetes on bare metal, EKS, GKE, and AKS
- 100+ Terraform templates at a top-5 US bank
- A GitOps workflow on ArgoCD across 8+ teams, 50+ safe deployments a day
All four were ours from the design review through the on-call rotation afterward. What a build engagement leaves behind is a platform your own engineers deploy to without asking us, plus the runbooks and the Terraform standing under it. Max is carrying infrastructure strategy across 5 parallel projects right now, from financial services to healthcare.
The person who holds the pager is the person who makes the design calls, and no one hands a pager to a contractor who is billing hours into someone else’s backlog.