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

Juniors lack mental models for incidents; lack confidence for autonomous decisions; lack escalation judgement.

Throwing them in cold produces panic and bad calls.

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

Buddy: a senior engineer reachable during junior’s shifts. Pages out only on actual confusion.

Sustainable: most shifts no buddy contact; the safety net matters when needed.

Autonomy gradient

Shifts 1-3: heavy buddy reliance.

Shifts 4-10: independence with safety net.

Shifts 10+: full autonomy.

The gradient is explicit; not implicit.

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.