Google Cloud Architect: Service-by-Service
A provider-deep tour of Google Cloud Platform for solutions and cloud architects. Walks the full service landscape - compute, storage, databases, networking, identity (IAM), data and analytics (BigQuery) - then layers on infrastructure-as-code, containers (GKE), operations, security and the Architecture Framework, and finishes with the architecture deep-dives and behavioral themes GCP architect loops grade against.
The Google Cloud service landscape
Build a working map of the core families: compute (Compute Engine, Cloud Run, Cloud Functions, GKE, App Engine), storage (Cloud Storage, Persistent Disk, Filestore), databases (Cloud SQL, Spanner, Bigtable, Firestore, Memorystore), analytics (BigQuery, Dataflow, Dataproc, Pub/Sub), and the glue (Pub/Sub, Workflows, Eventarc). This category is the spine of the path.
Networking and content delivery
Anchor the GCP networking model: VPC (global by default), subnets, firewall rules, Cloud NAT, Shared VPC, VPC peering, Cloud Interconnect, Cloud DNS, and Cloud CDN / global load balancing before the design rounds.
Data stores and analytics
Work through relational (Cloud SQL) vs globally-consistent (Spanner) vs wide-column (Bigtable) vs document (Firestore) trade-offs, then the analytics path that GCP is known for - BigQuery, Dataflow, Pub/Sub - and Memorystore caching.
Infrastructure as Code and containers
Build fluency in declarative provisioning (Terraform is the GCP standard; also Config Connector / Deployment Manager) and the container stack (GKE, Cloud Run) that runs most modern GCP workloads.
Operations, observability and DevOps
Cover Cloud Monitoring and Cloud Logging (the Operations Suite, formerly Stackdriver), Cloud Build / Cloud Deploy pipelines, and the deployment-safety patterns architects bake in.
Security, governance and the Architecture Framework
The pillars architects are graded on: IAM least privilege, Cloud KMS, the resource hierarchy (Organization / Folders / Projects) and Organization Policy for governance, plus the Google Cloud Architecture Framework (operational excellence, security, reliability, cost, performance).
Architect deep-dives (system design)
Bounded designs that exercise the conversations GCP architects lead - decoupling with Pub/Sub, consistency across services, throttling, and payment-grade reliability.
- 01DesignDesign a Distributed Message Queue (Kafka deep-dive)System Design · Hard
- 02DesignDesign Distributed Transactions (2PC, Saga, TCC)System Design · Hard
- 03DesignDesign a Rate Limiter (API Throttling)System Design · Medium
- 04DesignDesign a Payments / Checkout System (Stripe-style)System Design · Hard
Behavioral: influence and judgment
Architect rounds screen for driving decisions across teams you don't manage and making pragmatic cost/resilience trade-offs. Have a story per theme with concrete business impact.
- 01BehavioralLeadership Without AuthorityBehavioral · General
- 02BehavioralDealing with AmbiguityBehavioral · General
- 03BehavioralFrugality (Amazon Leadership Principle)Behavioral · Amazon LP
- 04BehavioralDive Deep (Amazon Leadership Principle)Behavioral · Amazon LP
- 05BehavioralLearn and Be Curious (Amazon Leadership Principle)Behavioral · Amazon LP
Browse other learning paths
Three role-targeted paths are live: Backend, SRE / DevOps, and ML Engineer. More are on the way - if you have a role you want covered, let us know.
View all paths →