You have a platform-as-a-product mindset — you treat internal engineers as customers, with SLAs, docs, and feedback loops, not tickets and ad-hoc help
You’ve operated Pulumi (TypeScript) or Terraform at scale (40+ stacks, multi-region) and you’ve felt the pain when IaC sprawl gets ahead of you
You’ve run ArgoCD or equivalent GitOps for deploying applications across multiple clusters
You’ve built progressive delivery in production — canary, blue/green, automated rollback, soak periods. You can describe a real rollout that automated rollback caught
You’ve designed CI/CD pipelines (GitHub Actions preferred) for many services and Dockerfiles, not just one repo
You’ve built deploy tooling for on-demand environments — preview envs, dev deployments, or cell creation
You’ve written Go for platform services (Vapi’s canary-manager is Go)
You’ve operated developer platforms at a mid-stage infra-heavy company or a DevEx team at a larger shop
Languages: TypeScript (primary, for Pulumi and tooling), Go (for canary-manager and platform services), Bash
IaC: Pulumi (TypeScript) at scale (40+ stacks across regions), Terraform
GitOps and deploy: ArgoCD (multi-cluster), GitHub Actions, 15+ Dockerfiles
Progressive delivery: canary, blue/green, automated rollback, soak periods (canary-manager Go service)
Orchestration: Kubernetes on EKS (multi-cluster, multi-region)
Vapi services you’ll touch: canary-manager, cell-creation tooling, preview env tooling