Incident Response On-Call Onboarding Curriculum Prompt

You are a staff SRE who has built the on-call ramp program for a 40-engineer org and cut "new on-call engineer paged a wrong escalation" incidents to near zero.

I will provide:
- Our service catalog and which services this team owns
- Current on-call rotation structure (primary/secondary, follow-the-sun?)
- Existing runbooks, dashboards, and the incident tooling (PagerDuty/Opsgenie, Slack, status page)
- The new engineer's background and prior on-call experience

Your job: produce a multi-week onboarding curriculum that ends with a confident, signed-off primary on-call.

1. **Readiness model** — define the 4 competencies a new on-call must demonstrate: navigate (find dashboards/logs/runbooks fast), triage (assess severity correctly), act (execute common runbooks safely), and escalate (know when and to whom). Map every activity below to one of these.

2. **Week-by-week plan** — Week 1 environment + access + tooling drills; Week 2 service deep-dives with the owning engineers; Week 3 shadow on-call (observe, no action); Week 4 reverse-shadow (act, with mentor watching). Give concrete daily activities, not vague goals.

3. **Shadowing milestones** — what the trainee must observe at least once before going primary: a real SEV2+, an escalation, a status-page update, a clean handoff. If they don't hit these organically, propose synthetic equivalents.

4. **Reading list & drills** — top 10 runbooks ranked by page frequency, the 5 dashboards they'll open most, and 3 hands-on drills (e.g., "find the p99 latency for service X over the last 24h in under 60 seconds").

5. **Knowledge checks** — a short quiz per week and one tabletop scenario where the trainee narrates what they'd do.

6. **Go-live sign-off checklist** — explicit, checkbox criteria the mentor signs before adding the trainee to the primary rotation, plus a "first two shifts are buddy shifts" rule.

7. **Failure modes** — what to do if the trainee isn't ready by week 4, and how to avoid throwing them in solo too early.

Output as: a printable curriculum table (week, day, activity, competency, owner), the sign-off checklist, and the week-1 quiz. Bias toward hands-on drills over reading, and make every milestone observable and binary.