Site Reliability Engineering Career Track
This page stitches together three lenses we revisit in every intensive: where you are headed, what evidence you ship, and how you sequence external credentials without drowning in noise.
Roadmap — from signals to ownership
Month one emphasises legible telemetry; month two pairs progressive delivery with honest rollback drills; month three moves into facilitation skills that hiring panels can observe in writing.
┌─────────────┐ ┌──────────────┐ ┌─────────────┐
│ Signals │───▶│ Delivery │───▶│ Facilitation│
│ literacy │ │ guardrails │ │ narrative │
└─────────────┘ └──────────────┘ └─────────────┘
│ │ │
▼ ▼ ▼
dashboard pack pipeline memo exec one-pager Employer-ready project studio
You ship three artefacts: a telemetry pack, a progressive delivery memo with named owners, and a facilitation script used in a recorded mock bridge (redacted). Mentors score each using the same rubric hiring partners helped us calibrate.
Certification planning guide
Vendor exams can help, but only after your artefacts exist. We map common cloud and Kubernetes credentials to the skills each cohort week already practices so you do not study twice or pay for exams you do not need yet.
- Align exam windows with drill weeks so muscle memory overlaps.
- Pair each practice test with a written reflection — panels read prose, not scantrons.
- Skip credentials that duplicate what your portfolio already proves.