Google Cloud Delivery Architect
Description
Google Cloud Delivery Architect (Project Owner) for the company Google Cloud Delivery team — Google Cloud Partner of the Year 2024–2026. Takes an approved, scoped, fixed-budget engagement and delivers it end to end: Low-Level Design, implementation, validation, and clean handover. Runs several engagements in parallel, facing each customer directly in a weekly meeting. Presale is owned by Customer Engineers; this role owns execution.
Seniority: Senior / Architect — 5+ years hands-on cloud infrastructure, with deep production experience on Google Cloud specifically.
What You Will Deliver:
-
AWS / Azure → GCP migrations — production platforms moved in waves with controlled cutovers (EKS→GKE, RDS→Cloud SQL, S3→Cloud Storage).
-
Cloud Foundations (Landing Zones) — resource hierarchy, IAM, Organization Policies, network topology, security controls — all codified in Terraform.
-
Kubernetes platforms — GKE design and deployment: private clusters, Workload Identity, Helm add-ons, ingress, Cloud Armor.
-
DevOps / IaC enablement — import hand-built environments into Terraform, reusable modules, GitHub Actions with Workload Identity Federation, Argo CD.
-
Engagement ownership — weekly customer meeting, board and hours current, scope protected via change management, budget deviations flagged early, handover with docs/runbooks/knowledge transfer.
Requirements
Must-Have:
-
Google Cloud, hands-on and deep (20%) — production architecture experience on GCP; not learning it on the job.
-
Terraform expertise (15%) — modular reusable code, remote state, importing hand-built environments.
-
Customer-facing English (15%) — runs workshops, weeklies and handovers with customer engineers and CTOs.
-
Kubernetes / GKE in production (12%) — private clusters, node pools, autoscaling, RBAC, Workload Identity, Helm, ingress.
-
Networking & security (12%) — VPC design, Cloud NAT/DNS/VPN, Private Service Connect, firewall policies, IAM, Org Policies, Secret Manager.
-
CI/CD (10%) — GitHub Actions (or equivalent) with keyless auth to GCP, container workflows, GitOps with Argo CD or similar.
-
Source-cloud fluency (8%) — working knowledge of AWS or Azure; must read the source environment being migrated.
-
AI-driven working (8%) — proficient daily use of AI tools with judgment: what to accept, what to reject, and why.
Originally posted on Himalayas