The Pager Never Sleeps: Why On-Call Compensation Has Become IT's Fiercest Negotiation

Somewhere in Ohio right now, a systems administrator is eating dinner with a phone face-up on the table. Somewhere in Arizona, a network engineer is waking at 3 a.m. to a PagerDuty alert that will turn out to be a false positive. Multiply that across every enterprise data center and SaaS operations floor in the country, and you have one of the most significant — and least formalized — labor questions in American technology: what is on-call actually worth?

The traditional answer, at many organizations, has been 'nothing.' On-call was bundled into the job description, mentioned in a sentence during onboarding, and compensated with the vague currency of 'experience.' That arrangement is increasingly under strain, and 2025's tightening conversation around workload, retention, and burnout has pushed it into the open.

The Structural Problem With Always-On

On-call differs from overtime in a way that matters. Overtime is work; on-call is readiness — the inability to fully leave the job, the second glass of wine declined, the camping trip planned around a rotation. Research on cognitive load has long shown that anticipation of interruption degrades rest even when no interruption occurs. A weekend 'on standby' is not a weekend off in any psychologically meaningful sense.

Yet compensation structures rarely reflect this. In organizations without explicit on-call pay, the burden tends to fall disproportionately on junior and mid-level staff — the employees with the least negotiating power and the least context to resolve complex incidents quickly, which paradoxically makes incidents last longer.

What Fair Looks Like in 2025

Practices vary widely, but a rough consensus is emerging among operations-mature organizations:

• A stipend for being available, typically ranging from a few hundred dollars per week for primary rotation to a smaller amount for secondary, paid regardless of whether pages occur.
• Hourly compensation for time actually worked, including time-to-respond windows. If the policy demands a 15-minute response, the clock arguably starts at the page, not at login.
• Comp time or premium pay for overnight incident resolution, particularly for non-exempt staff, where FLSA obligations may already apply.
• Hard caps on rotation frequency. Google's well-documented SRE practice of limiting on-call to roughly one week in six, with enforced follow-up time after major incidents, has become a reference point across the industry.

Organizations that have adopted these structures report a quieter benefit: better incident outcomes. Rested, fairly compensated responders triage faster and escalate more appropriately than exhausted ones.

What to Negotiate Before You Accept the Pager

For IT professionals evaluating a role — or renegotiating an existing one — on-call terms deserve the same scrutiny as salary. Before signing:

1. Ask for the rotation schedule in writing. How many weeks per quarter? Primary and secondary split? What happens when colleagues leave and the rotation thins?
2. Clarify response-time expectations. A 'best effort within an hour' policy and a 'phone answered in five minutes' policy are different jobs.
3. Ask whether on-call is compensated, and how. Stipend, hourly, comp time, or nothing — get the answer explicitly.
4. Ask about follow-up time after incidents. A 2 a.m. outage followed by a 9 a.m. standup is a burnout factory.
5. Confirm tooling. A rotation with a functional alerting stack, runbooks, and a genuine escalation path is a fundamentally different experience from one where the pager means 'figure it out alone.'

A Sample Policy Worth Bringing to Your Manager

Teams without a written on-call policy often accept one silently. Proposing your own gives you a seat at the table. A reasonable starting template:

On-call rotates weekly among qualified team members, with no individual serving more than one week in five. Primary responders receive a weekly stipend; incident time is compensated at 1.5x hourly rate or accrued as comp time. Post-incident, responders receive a minimum of four hours of rest time before their next shift. The rotation pauses during scheduled PTO, and staffing shortfalls trigger backfill hiring rather than doubled rotations.

Managers frequently respond better to this framing than expected — a documented policy protects them from burnout-driven attrition, too.

The Bottom Line

On-call is not going away; uptime obligations are structural to modern enterprise IT. But the terms of the arrangement are genuinely negotiable, and the professionals who treat them as part of total compensation — rather than an unexamined footnote — will land on the right side of the shift. The pager may never sleep. That does not mean the person carrying it should never be paid for staying awake.