On-call is the requirement most often hidden in plain sight. JDs almost never list it as a requirement — but for senior backend, infra, platform, and reliability roles, it’s expected ~60% of the time.
If your resume has no on-call signal and the role expects on-call, the application trips a tacit filter the JD never named.
The on-call cues to read for
A JD doesn’t have to say “on-call” to imply it. The cues:
Direct cues (40% of cases)
Some JDs are honest:
- “Participate in the on-call rotation.”
- “Support 24/7 reliability of [service].”
- “Use PagerDuty / Opsgenie / [tool] for incident response.”
If any of these appear, on-call is required. No ambiguity.
Strong indirect cues (30% of cases)
The JD doesn’t say on-call but implies it strongly:
- “We run a 24/7 platform.”
- “Customer-facing reliability is critical.”
- “Production-critical systems.”
- “99.9% (or 99.99%) SLA.”
- “Incident response and root-cause analysis.”
- “Postmortems and follow-up actions.”
Two or more of these = on-call expected.
Weak indirect cues (15% of cases)
Suggestive but not definitive:
- “Backend / infra / platform / SRE / DevOps role.”
- “High-traffic systems.”
- “Real-time / low-latency systems.”
- “Distributed systems.”
- “Microservices architecture.”
These often imply on-call but not always — depends on company maturity and team structure.
No cues (15% of cases)
Front-end roles, internal tools, batch processing, ML training, design — typically no on-call. If you don’t see any of the above cues and the role isn’t backend-coded, on-call is unlikely.
Why this matters for your resume
If the role implies on-call and your resume has no on-call mention, the hiring manager’s read is:
- “Have they ever been on-call? Will they push back when I tell them about the rotation?”
- “If they’re senior and never on-called, they probably don’t know what production-critical actually means.”
The fix is one bullet on your resume mentioning on-call:
Owned the on-call rotation for [system]; cut incident MTTR from 4h to 38min through better runbooks and alerting.
Even if it’s not in your most recent role, surface it from a previous role. A senior backend resume without on-call signal is suspicious.
Reading the JD for on-call rotation shape
If the JD does mention on-call, it sometimes encodes the rotation shape:
- “Weekly on-call rotation across the team” → standard, often weekly with a backup.
- “Follow-the-sun rotation” → multi-region team; you cover business hours.
- “Primary and secondary rotation” → tiered, the primary handles first response.
- “Weekend / overnight rotation” → bad sign; team is overstretched.
- “On-call expected but not paid extra” → some companies; ask if compensation is included.
If the JD is specific about rotation shape, take it at face value. The reality usually matches.
When on-call is a hard no for you
Some candidates have life circumstances (caregiving, health) that make on-call impractical. The right move is to ask in the screening, not after signing. Some teams will negotiate (no overnight, only weekday hours). Some won’t.
If the JD implies on-call and your hard no is firm, don’t apply expecting to negotiate it away. The role was built around the assumption.
Run the on-call signal check
The diagnostic reads the JD for tacit signals — including on-call — and surfaces whether your resume signal matches. If the role implies on-call and your resume has no mention, it shows up as a tacit-disqualifier flag.
Related reading
- Tacit disqualifiers in job postings — the broader category.
- Find seniority signals in a JD — adjacent altitude signals.
- How to read a JD like a hiring manager — the seven implicit signals pillar.
- Reporting structure clues in job postings — adjacent implicit signal.