⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Linux & SRE Interview Questions Scenario 135 of 135 in Linux & SRE
Senior DevOps / SRE Linux/SRE On-Call Operations & Incident Management Operations & Support Loop

Q: Are you comfortable working in a rotational on-call support model? How do you distinguish responsibilities between an Operations team and a Backend Engineering team?

How to operate effectively in a 24/7 rotational on-call support model, establish clear boundaries between Operations and Backend teams, and prevent alert fatigue.

#SRE #On-Call #Production Support #PagerDuty #Incident Management #Operations
🎙️ Candidate Opening & Architectural Context
"I am fully comfortable and experienced in 24/7 rotational on-call models (e.g. 1 week primary on-call every 5 weeks with follow-the-sun or secondary escalation). A healthy on-call culture requires a clear division of operational responsibility: the Operations/Platform team owns infrastructure availability, network transit, cluster health, and CI/CD pipelines, while Backend Engineering teams own application business logic, data modeling, and code bugs."
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: I am fully comfortable and experienced in 24/7 rotational on-call models (e.g. 1 week primary on-call every 5 weeks with follow-the-sun or secondary escalation). A healthy on-call culture requires a clear division of operational responsibility: the Operations/Platform team owns infrastructure availability, network transit, cluster health, and CI/CD pipelines, while Backend Engineering teams own application business logic, data modeling, and code bugs.

1

Rotational On-Call Cadence & Handover Protocols

On-call shifts run on scheduled rotations using PagerDuty / Opsgenie with primary and secondary responders. Shift handovers include a formal 15-minute sync reviewing unresolved non-critical alerts, ongoing maintenance windows, and planned releases.

Shift Handover Sync→Primary Incident Triage (P1/P2)→Paging Backend SME If Needed→Service Restoration→Blameless Post-Mortem
2

Clear Boundary: Operations Team Responsibilities

- Core cloud infrastructure (AWS/Azure networking, VPCs, Transit Gateways, IAM). - Kubernetes cluster control plane, worker node pools, CNI, CSI, and ingress controllers. - CI/CD runner infrastructure, artifact registries, and GitOps engines. - Disaster recovery, regional failover orchestration, and telemetry platforms (Prometheus, Loki, Datadog).

Advertisement
3

Clear Boundary: Backend Engineering Responsibilities

- Application code, API endpoints, business logic algorithms, and data serialization. - Relational database schema designs, SQL query optimization, and ORM migrations. - Application-level error handling, retry policies, and domain service dependencies.

Pro Tip: Shared Responsibility Model: Operations delivers the resilient platform runway; Backend teams write the application logic that flies on it. Both share on-call responsibilities via 'You build it, you run it'.
4

Triage & Escalation Workflow During P1 Incidents

When a P1 fires, Operations acts as Incident Commander: triaging whether the failure is platform-wide (node down, network partition) or application-specific (null pointer, broken SQL query). If application-specific, the on-call engineer pages the designated Backend service SME.

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Embrace 24/7 on-call with disciplined handoffs and clear boundaries: Operations owns infrastructure, networking, and cluster platforms; Backend owns code logic and queries. Both collaborate under shared incident command."
⚡ 60-Second Elevator Pitch Talking Points
  • Comfortable in 24/7 rotational on-call with primary/secondary escalation and formal shift handoffs.
  • Operations owns platform infrastructure, cluster health, networking, and CI/CD availability.
  • Backend owns application business logic, API implementations, and database query performance.
  • Operations acts as Incident Commander on P1s, pulling in backend SMEs when application code is the root cause.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring Navigating 24/7 Rotational SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
  2. Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring Navigating 24/7 Rotational Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (df -h) shows ample free space.
  3. Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring Navigating 24/7 Rotational Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
  4. Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring Navigating 24/7 Rotational Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (pid_max).
Advertisement
Want more Linux & SRE scenarios?
Explore our complete collection of scenario-based Linux & SRE interview runbooks.
Browse All Linux & SRE Questions →