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

Throwing a new engineer onto on-call without preparation is irresponsible. The difference between unprepared and prepared shows up in the first incident.

• Unprepared harm. Wrong actions, slow response, lost trust; the team and the customer pay the cost.
• Prepared performance. Confident, calm, fast; the engineer ships the right action under stress.
• Structured onboarding. The difference is not talent; it is investment in the first 4 weeks.
• Trust signal. Engineers who get good onboarding stay; ones thrown in cold leave within a year.

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 shifts are the bridge from theory to practice. The new engineer sees real alerts and real responses without owning the outcome.

• Pair with on-call. New engineer rides along; sees the actual alert flow as it happens.
• Observe responses. Watch how the on-call investigates; the unwritten rules become visible.
• No production access. Just observation; no risk of wrong action while learning.
• Pattern recognition. Two weeks of shadow surfaces the recurring incident shapes; theory turns into instinct.

First solo

The first solo shift is the moment of truth. Schedule it carefully; debrief after; iterate the onboarding based on what surfaced.

• Low-volume window. Scheduled in a quiet shift; buddy reachable for backup if needed.
• Buddy on standby. Named buddy reachable; new engineer not alone if a real incident hits.
• Debrief. Conversation after the shift; what was hard, what was unclear, what was missing.
• Iterate. Gaps fed back into the runbook and the next onboarding cycle; the programme improves with use.

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.