B4 · Pathway B — Cloud & DevOps

Site Reliability Engineering

Build systems that stay up. Learn observability, incident response, SLOs, and reliability practices. Future squad role: Site Reliability Engineer.

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

Site Reliability Engineer

Infrastructure squad · Observability & uptime

Team seat: Infrastructure Lead seat (Observability & uptime)

Own reliability after launch — SLOs, observability, and incident response.

In the venture, you will

  • Instrument logs, metrics, and traces the squad trusts
  • Define SLOs and error budgets with Product Lead
  • Run incident response so launch is not a one-week miracle
  • Compete for Infrastructure Lead with reliability evidence — distinct from DevOps pipelines

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 Site Reliability 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.