On-Call Onboarding: Surviving the First Shift
Throwing a new engineer onto on-call without preparation is irresponsible. Four weeks of structured onboarding fixes it.
Why onboarding matters
Unprepared engineers do harm: wrong actions, slow response, lost trust.
Prepared engineers do well: confident, calm, fast.
The difference is structured onboarding.
Four-week structure
- Week 1: read runbooks; review past postmortems.
- Week 2: shadow current on-call; observe alerts.
- Week 3: handle alerts under buddy supervision.
- Week 4: first solo shift with buddy on standby.
Shadow shifts
Shadow: new engineer paired with on-call; sees real alerts; reviews real responses.
No production access; just observation; learns the patterns.
First solo
First solo shift: scheduled in a low-volume window; buddy reachable for backup.
Debrief after first shift; document gaps; iterate.
Antipatterns
- No onboarding. First shift is trial by fire.
- Onboarding without shadow. Theory only.
- Solo first shift in peak window. Sets up for failure.
What to do this week
Three moves. (1) Apply this practice to your next on-call rotation. (2) Survey the team after one cycle. (3) Iterate based on feedback; the discipline is the cadence.