B1 · Pathway B — Cloud & DevOps

Cloud Engineering

Provision, configure, and manage cloud infrastructure on AWS, GCP, or Azure. Future squad role: Cloud Engineer.

B1Closed — opens later

This specialization is listed for planning. It’s closed for Cohort 1 and opens in a later cohort — you can still apply to the pathway on an open track.

Future squad role

Cloud Engineer

Infrastructure squad · Cloud platforms & environments

Team seat: Infrastructure Lead seat (Cloud platforms & environments)

Own the cloud home the squad deploys into — compute, storage, networking, access.

In the venture, you will

  • Provision and run cloud infrastructure for the venture
  • Keep cost and access sane for a lean Nigerian Ltd
  • Give the squad a real production environment, not a laptop demo
  • Compete for Infrastructure Lead with cloud-platform evidence (distinct from DevOps or SRE)

Team placement is based on evidence and venture need — this is the job this track prepares you for, not an automatic title. Several specializations may compete for the same team seat; each keeps its own craft identity.

In a Phase B squad

Infrastructure & reliability

In Phase B, Cloud & DevOps specializations are different jobs: Cloud Engineer, DevOps Engineer, Infrastructure as Code Engineer, and Site Reliability Engineer. One of them fills Infrastructure Lead after team placement — usually the builder whose evidence matches the venture’s delivery needs (often DevOps).

Typical seats: Infrastructure Lead

Inside this track

  • Deep craft work in Cloud Engineering across a six-month Phase A rhythm.
  • Shared UTP Core and Venture Thread for every builder — specialization is your edge, not your only curriculum.
  • Weekly projects, feedback, and portfolio evidence that inform Phase B team placement.
How the Learning System works →

Ready to choose a track?

Browse every specialization, then apply — or create an account and pick during onboarding when enrollment opens for you.