B3 · Pathway B — Cloud & DevOps

Infrastructure as Code

Define and manage infrastructure programmatically using Terraform, Pulumi, and related tools. Future squad role: Infrastructure as Code Engineer.

B3Closed — 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

Infrastructure as Code Engineer

Infrastructure squad · Codified environments

Team seat: Infrastructure Lead seat (Codified environments)

Own environments as code — Terraform and related tools the venture can re-apply.

In the venture, you will

  • Write infrastructure configs the company can recreate from zero
  • Make staging and production reproducible across the squad
  • Reduce “it only works on my laptop” risk for incorporation-ready launches
  • Compete for Infrastructure Lead with IaC evidence — distinct from Cloud ops 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 Infrastructure as Code 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.