On-Call and Junior Engineers: Setting Them Up to Win

Junior engineers can run on-call well with structured support. Without it, they struggle and learn the wrong lessons.

Junior-specific challenges

Junior engineers can run on-call well with structured support. Without it, they struggle and learn the wrong lessons; the trust costs of a bad first incident compound.

• No mental models. Juniors lack the pattern library senior engineers built over years of incidents.
• Low confidence. Autonomous decisions feel risky; the engineer waits for permission instead of acting.
• Weak escalation judgement. Cannot tell when to escalate vs when to push through; both extremes go wrong.
• Cold-start cost. Throwing a junior in cold produces panic and bad calls; the team and the customer pay.

Four supports

• 1. Pre-shift training (covered separately).
• 2. Buddy on standby for first N shifts.
• 3. Explicit escalation permission, better to escalate than guess.
• 4. Post-incident review with mentor.

Buddy system

The buddy system makes junior on-call sustainable. A senior engineer reachable during shifts, contacted only when needed, transforms the experience.

• Senior reachable. Named buddy on standby during the junior's shift; not actively on-call but available.
• Page on confusion. Junior pages buddy only when stuck; most shifts no buddy contact happens.
• Sustainable. Light load on the buddy; safety net matters when needed; not a full second on-call.
• Trust signal. The buddy's existence reduces the junior's stress even when no contact happens.

Autonomy gradient

Autonomy ramps up over the first months. The gradient is explicit; the junior knows where they are on the curve and what comes next.

• Shifts 1-3. Heavy buddy reliance; check in before any non-trivial action; learning by mediated decision.
• Shifts 4-10. Independence with safety net; act first, debrief after; buddy stays available.
• Shifts 10+. Full autonomy; standard senior on-call expectations; buddy steps back.
• Explicit, not implicit. The gradient is documented; not vibes; juniors and buddies know where they are.

Antipatterns

• Junior on-call without support. Bad incident; lost confidence.
• Junior never gets on-call. Never learns; senior burden grows.
• One-shift onboarding. Insufficient.

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.