On-Call Shadow and Mentorship Program Prompt
Design a structured shadow-and-reverse-shadow program that ramps new engineers onto the on-call rotation safely — with milestones, sign-off criteria, and mentor responsibilities — so nobody carries the pager unprepared.
- Target user
- Team leads and on-call program owners onboarding engineers to the rotation
- Difficulty
- Beginner
- Tools
- Claude, ChatGPT
The prompt
You are an SRE lead who has onboarded dozens of engineers to on-call without burning them out or letting them break production on their first page. I will provide: - The team's services, runbooks, and tooling - The current rotation structure and paging policy - The experience level of the incoming engineers - Any prior onboarding pain points (thrown-in-deep-end, no feedback, unclear readiness) Your job: 1. **Phase the ramp** — design a multi-stage path: observe-only shadow, reverse-shadow (newcomer drives, mentor backstops), and supervised solo. Define entry and exit criteria for each phase, not just a duration. 2. **Shadow-phase activities** — what the shadow actually does: attend every page, narrate the mentor's reasoning back, locate the right runbook, and write up what they observed. Make it active, not passive watching. 3. **Reverse-shadow phase** — the newcomer leads response while the mentor stays silent unless safety is at risk. Specify when the mentor must intervene and how to debrief afterward. 4. **Readiness checklist** — a concrete, signable list: can find and follow runbooks, can escalate correctly, knows the severity rubric, can declare and communicate an incident, knows the rollback path, knows who to call for each dependency. 5. **Mentor responsibilities** — what mentors owe the program: availability windows, debrief cadence, written feedback, and a go/no-go recommendation. Make mentoring a recognized, allocated responsibility, not unpaid heroics. 6. **Safety nets** — guarantees for the first few solo shifts: a named backup always reachable, reduced-blast-radius scheduling, and a no-judgment escalation culture. 7. **Measure readiness, not tenure** — define signals that someone is ready (handled N pages, demonstrated escalation, passed a tabletop) rather than "it's been three weeks." Output as: (a) the phased ramp plan with entry/exit gates, (b) shadow and reverse-shadow activity guides, (c) the signable readiness checklist, (d) a mentor responsibilities charter, (e) first-solo-shift safety nets. Bias toward: demonstrated competence over time-served, active practice over passive observation, psychological safety throughout.
Run this prompt with AI
Test it, get an AI-improved version, or compare models — live in the Prompt Workspace. No copy-paste.
Related prompts
-
Incident Response On-Call Onboarding Curriculum Prompt
Design a structured, week-by-week onboarding curriculum that takes a new engineer from zero to confident shadow-to-primary on-call, with shadowing milestones, reading lists, and a sign-off checklist.
-
Swarm vs Escalate Decision Guide Prompt
Give the first responder a fast rule for the early-incident fork: keep working it solo, pull in a swarm of experts, or escalate to a formal incident with a commander — so pages neither languish under one overwhelmed engineer nor over-mobilize the whole org for a blip.
-
Firing Alert Severity & Escalation Decision Prompt
Given a firing alert and current impact signals, decide an appropriate severity level and whether to escalate or page additional responders, with explicit reasoning against your severity rubric — leaving the final call to a human.
-
First-Alert Triage & Hypothesis Ranking Prompt
Take a freshly fired alert plus a snapshot of metrics, logs, and recent changes, and produce a ranked list of failure hypotheses with the cheapest next diagnostic step for each — without taking any action on the system.
More Incident Response prompts & error guides
Browse every Incident Response prompt and troubleshooting guide in one place.
Reading prompts? Get all 500 in one free PDF
500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.
- 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
- Instant PDF download — yours free, forever
- Plus one practical AI-workflow email a week (no spam)
Single opt-in · unsubscribe anytime · no spam.