What’s the expected response when you’re on call but away from your laptop?

Being on call means planning your activities around being able to respond. You do not necessarily have to sit at home, but you should stay reachable, remain fit to handle an incident, and have the tools needed for critical issues. Missing one page can happen, but repeated missed alerts usually lead to a management discussion because the escalation process is intended as a safety net, not a substitute for responding.

The exact expectations depend on the organization and the severity of the system, but they should be agreed on ahead of time. A phone is usually enough to acknowledge a page and begin basic triage. For anything more involved, on-call engineers generally keep a laptop nearby and have a backup connection, such as phone tethering. Some teams set rules like being able to reach a laptop within 15 minutes.

A common setup is a five-to-20-minute acknowledgment window, followed by an escalation if the primary engineer does not respond. The alert may go to a secondary engineer and then to a team lead or manager. Resolution time is much harder to standardize: a simple restart might take minutes, while diagnosing a complex production failure could take hours. The important thing is to acknowledge the alert, communicate clearly, and keep working toward mitigation.