On-call responsibility rotates weekly among engineers on each team. Being on-call means you’re the first responder for production alerts during your shift.Documentation Index
Fetch the complete documentation index at: https://docs.yupvid.com/llms.txt
Use this file to discover all available pages before exploring further.
Rotation schedule
Check your team’s on-call schedule in NightWatch. Schedules are set four weeks in advance. If you need to swap a shift, arrange it directly with a teammate and update the schedule — don’t just not show up. New engineers join the rotation after 60 days. Your first few on-call weeks are shadowed — you respond, but a senior engineer is on secondary in case you need backup.Before your shift
- Confirm your phone number is correct in the alerting tool.
- Check
#deploysfor any recent changes that might be fragile. - Review any open SEV-3 issues that could escalate.
During your shift
Availability: Respond to pages within 5 minutes during business hours, within 15 minutes outside business hours. If you can’t respond within that window, escalate to secondary immediately. For each alert:- Acknowledge the alert to stop re-paging.
- Triage: is this a real issue or noise? If noise, resolve and file a ticket to fix the alert.
- If real, follow the incident response process.
#incidents even for small issues. It creates a record and helps the next on-call engineer understand what happened.
Escalation path
If you’ve been investigating for 15 minutes and are stuck:- Page the secondary on-call engineer.
- If still stuck after another 15 minutes, escalate to your engineering manager.
After your shift
Hand off any open issues to the next on-call engineer in#incidents. Include: what happened, current status, and what to watch for.