Owning the platform for an AI-security product team
Since late 2025 I have worked as an independent platform engineer, and this is my primary engagement. I joined the product team of an AI-security company with a hand-built cloud and a product that could not afford downtime. The first decision was to make the whole GCP estate code: 316 Terraform-managed resources in 12 modules across 9 environments, including 48 build triggers, imported live behind zero-diff gates so nothing changed by accident while the team kept shipping.
Then we made it multi-cloud without storing a single key. Four partner AWS accounts receive our images through identity federation, with the same digest promoted from dev to prod, and one Helm chart now deploys 6 services to 7 GKE and EKS environments.
Security became a system instead of a report: a weekly sweep over every running image, an owner for every finding, and tickets that close themselves when the fix lands. The first run surfaced 12 critical and 388 high findings. And the cloud bill dropped by about seventy percent, through GPU capacity that scales to zero and environments that switch themselves off when nobody is using them.
Terraform · GKE · Cloud Run · Cloud Build · Helm · Argo CD · AWS EKS · OIDC / Workload Identity · Trivy · Grype · BigQuery · Python