DevOps On-Call Pay in 2026: $6K–$24K/Year Extra — What to Expect and Negotiate
On-call duty is the most under-discussed component of DevOps compensation. Nearly 80% of DevOps engineers participate in on-call rotations, yet compensation for this work varies wildly from $0 (at many startups) to $24,000+ per year (at well-run enterprise SRE organisations). This page provides the data you need to evaluate and negotiate on-call compensation.
On-call is not free work. It constrains your personal time, disrupts your sleep, affects your health, and creates ongoing stress. Companies that do not compensate on-call are externalising a real cost onto their employees. Understanding market rates for on-call pay gives you the leverage to negotiate fair compensation or choose employers who value your time.
On-Call Compensation Models
Flat Monthly Stipend
Fixed payment per on-call week regardless of incident volume. The most predictable model for both employer and employee. Common at mid-market and enterprise companies.
Per-Incident Pay
Payment triggered by each page or incident response. Can be lucrative during incident-heavy weeks but unpredictable. Sometimes combined with a base stipend.
Comp-Time
Day off after each on-call rotation instead of cash. Valued at $300-$600/day depending on salary. Some engineers prefer this for work-life balance, especially at companies with unlimited PTO policies.
Combined Model
Base stipend plus per-incident bonus. The most comprehensive model. Common at well-run SRE organisations and top-tier tech companies.
No Compensation
On-call is considered 'part of the job' with no additional pay. Most common at startups and companies with poor engineering culture. This is below market and a red flag for work-life balance.
On-Call Pay by Company Type
| Company Type | On-Call Structure | Annual Comp | Notes |
|---|---|---|---|
| Startup (1-50) | Often unstructured | $0-$3K/year | On-call may be 'everyone is always on-call' with no formal rotation or compensation. Negotiate explicit expectations before accepting. |
| Growth (50-200) | Informal rotation | $3K-$8K/year | Rotating schedule exists but may not be well-defined. Stipends common but modest. Incident management often ad-hoc. |
| Mid-Market (200-1K) | Formal rotation | $8K-$15K/year | Well-defined rotation with PagerDuty or Opsgenie. Monthly stipend standard. Incident post-mortems and escalation paths established. |
| Enterprise (1K+) | Structured program | $12K-$24K/year | Formal on-call policy with stipend, per-incident pay, and comp-time. Multiple escalation tiers. SLA-driven incident management. |
| FAANG | Rigorous SRE model | $15K-$30K+ (included in TC) | On-call compensation often folded into equity and bonus. Google SRE on-call stipend plus comp-time. Amazon notoriously heavy on-call with compensation built into the overall package. |
On-Call Burden by Specialisation
| Specialisation | Burden Level | Typical Frequency | Annual Comp | Notes |
|---|---|---|---|---|
| SRE | Heavy (1-in-4 to 1-in-6) | 3-8 pages/week | $12K-$24K | Heaviest on-call burden in DevOps. Primary responder for production incidents. 95% of SREs participate. |
| General DevOps | Moderate (1-in-4 to 1-in-8) | 1-4 pages/week | $6K-$15K | Varies by company. Some DevOps teams share on-call with SWE teams. 78% participation rate. |
| DevSecOps | Incident-driven | Varies (security events) | $8K-$18K | Not rotation-based but must respond to security incidents. Burden is unpredictable and can involve extended response during breaches. |
| Platform Engineering | Light (1-in-6 to 1-in-10) | 0-2 pages/week | $3K-$10K | Platform teams are typically not primary on-call for application issues. On-call covers platform infrastructure only. 55% participation. |
| MLOps | Moderate | 1-3 pages/week | $6K-$15K | Model serving and training pipeline issues. On-call often shared with ML engineering team. Growing as AI systems become production-critical. |
Negotiating On-Call Compensation
Many companies do not proactively offer on-call compensation. You often have to ask for it, and knowing the market rate gives you leverage. Here are strategies that work:
Quantify the Burden
"A 1-in-4 rotation means 25% of my weeks are on-call. Each on-call week constrains 168 hours of my personal time. At my hourly rate of $65/hr, even 10% of that time being actively disrupted represents $1,100/week of value. A $1,000/month stipend is a fair starting point."
Reference Market Data
"Industry data shows mid-market companies compensate DevOps on-call at $8,000-$15,000 per year. I would expect a similar range here given a [1-in-4/1-in-6] rotation frequency."
Propose Alternatives
If the company cannot pay a stipend, negotiate comp-time (one day off per on-call week), a higher base salary to compensate, or reduced on-call frequency. Some companies are more flexible on structure than on budget.
On-Call and Burnout
On-call burnout is a real risk with measurable consequences. Research from the DevOps Research and Assessment (DORA) team and industry surveys reveals the scope of the problem:
Engineers with on-call duties report 40% higher burnout rates than peers without on-call. Sleep disruption from night pages is the primary driver, with each page causing an average of 45 minutes of lost sleep and 90 minutes to return to sleep. Over a year of 1-in-4 rotation, this accumulates to 50-80 hours of lost sleep.
Companies with uncompensated on-call experience 2x higher turnover among on-call engineers. The cost of replacing a DevOps engineer ($30K-$60K in recruiting and onboarding) far exceeds the cost of fair on-call compensation. This is the business case to present to leadership when advocating for on-call pay.
Best practices for sustainable on-call include: rotation frequency no higher than 1-in-4, mandatory comp-time after on-call weeks, incident budgets that trigger engineering investment when exceeded, and regular review of on-call burden and compensation. For broader negotiation strategies, see our salary negotiation guide.
Frequently Asked Questions
How much extra do DevOps engineers get paid for on-call?
DevOps on-call compensation ranges from $6,000 to $24,000 per year. The most common model is a flat monthly stipend of $500-$2,000 per on-call week. Some companies add per-incident pay of $50-$200 per incident on top of the stipend. Enterprise companies tend to pay more ($12K-$24K) while startups often provide $0-$6K or no on-call compensation at all.
What is a fair on-call stipend for DevOps?
A fair on-call stipend depends on the rotation frequency and incident volume. For a 1-in-4 rotation with moderate incident volume (2-4 pages per week): $1,000-$1,500/month is fair. For a 1-in-6 rotation with low volume: $500-$800/month. For heavy rotations (1-in-3 with frequent pages): $1,500-$2,000/month plus comp-time. Any rotation without compensation is below market.
Do all DevOps engineers have to be on-call?
Not all, but most. About 78% of DevOps engineers participate in some form of on-call rotation. SREs have the heaviest on-call burden (95% participate), while platform engineers have the lightest (55%). Release engineers and CI/CD-focused roles may not have on-call duties at all. On-call expectations should be discussed during the interview process, not discovered after accepting the offer.
How do I negotiate on-call compensation?
Three approaches: 1) Quantify the burden: 'One week in four of 24/7 availability is 25% of my time with sleep disruption. A $1,500/month stipend values this at $72/week, well below my hourly rate.' 2) Reference market data: 'Industry standard for a 1-in-4 rotation at a mid-market company is $12K-$18K/year.' 3) Propose alternatives: if the company will not pay a stipend, negotiate comp-time (day off after each on-call week) or a higher base salary to compensate.
Does on-call affect burnout in DevOps?
Yes, significantly. Research shows on-call engineers experience 40% higher burnout rates than non-on-call peers. Sleep disruption from night pages is the primary driver. Companies with fair compensation, reasonable rotation frequencies (no more than 1-in-4), and strong incident management practices have markedly lower burnout. Uncompensated on-call correlates with 2x higher turnover rates.