Candidate: Oobayemi
Goal: Top 1% Software Engineer | AI Systems Architect
This phase focuses on mastering the "Raw Materials" of the Google Cloud ecosystem: Compute, Networking, and Security.
Date: March 10, 2026
Status: ✅ Completed (Score: 100/100)
In this foundational lab, I transitioned from a "User" mindset to an "Architect" mindset. I explored the Google Cloud Console—the central nervous system for global resource management—and established the security and billing boundaries required for enterprise-grade AI solutions.
- Resource Encapsulation: I managed Google Cloud Projects, learning how they act as isolation boundaries for billing and security. I distinguished between Temporary Lab Projects (Full Access) and Shared Resources (Read-Only).
- Identity & Access Management (IAM): I implemented the Principle of Least Privilege by assigning a "Viewer" role to a secondary principal. I mastered the power hierarchy of Viewer vs. Editor vs. Owner.
- Service Orchestration (APIs): I practiced Service Enablement by activating the Dialogflow API. I learned that Google Cloud is a modular system where advanced AI capabilities must be explicitly "plugged in" via APIs.
"A Top 1% Architect doesn't just 'click buttons.' They manage the Blast Radius. By isolating the Dialogflow API within a specific Project and restricting permissions to 'Viewer' for non-essential staff, I protected the system from unauthorized changes and cost overruns."
Started the Architecting with Google Compute Engine series. I am learning the Solution Continuum: balancing between IaaS (Maximum Control) and PaaS (Maximum Agility). I now understand that Infrastructure is the 'Underlying Framework' (Networking, Compute, Storage) that allows Applications to serve global users.
When you update your GitHub for the Introduction to Google Cloud module, use this:
"I mastered the hierarchy of Regions and Zones. I learned that a Region is a geographic boundary (like a city) and a Zone is a failure boundary (like a neighborhood). As an Architect, I design for Fault Tolerance by distributing resources across multiple zones to ensure that a single point of failure (like a local power outage) does not result in a global service disruption
When you update your GitHub for this section, use this:
"I deconstructed the two pillars of Network Performance: Bandwidth (Capacity) and Latency (Delay). I learned that as an Architect, I must balance both. For 'Global Solutions' like AI agents or Gaming, Low Latency is the priority to ensure real-time responsiveness, while High Bandwidth is essential for data-heavy tasks like model training or video streaming."
Strategic Insights: Interaction Modalities
"I analyzed the four vectors of interacting with Google Cloud. While the Cloud Console provides vital visibility, I recognize that Cloud Shell / CLI (gcloud) and Admin APIs are the primary tools of an Architect. To build scalable AI platforms, infrastructure must be treated as code. I also noted the utility of the Cloud Mobile App for mobile incident management and critical SSH access during outages."