InterviewStack.io LogoInterviewStack.io

On Call and Production Readiness Questions

Comprehensive operational topic covering the responsibilities, processes, and practices involved in supporting production systems and managing incidents. Candidates should be able to describe on call scheduling models and burden distribution across teams, expected incident volume and typical severity levels, incident triage steps and severity assessment to prioritize and escalate appropriately, and criteria for involving security teams or external vendors. It includes monitoring and alerting strategy, alert thresholds and noise reduction, service level objectives and service level indicators, and tooling for incident management. Candidates should also be able to explain runbooks and playbooks for common incident types, hands on troubleshooting during live incidents, root cause analysis approaches, deployment and rollback practices, and measures to reduce mean time to detection and mean time to recovery. The topic also covers incident communication practices, escalation procedures, post incident activities such as blameless postmortems and follow up actions for continuous improvement, and considerations about allocation of time between maintenance and feature work to preserve production readiness.

MediumTechnical
79 practiced
Your organization averages 3 high-severity incidents per month with an average MTTR of 90 minutes. Design a 6-month program (technical and process) to reduce MTTR to 30 minutes. Include immediate quick wins, instrumentation changes, runbook updates, automation, training, and measurement plans to verify improvement.
EasyTechnical
99 practiced
Explain the pros and cons of 'follow-the-sun' versus regional rotational on-call models for a company with engineering teams in NA, EU, and APAC. Consider response latency, handoffs, staffing cost, continuity, knowledge transfer, and legal/employment differences.
EasyTechnical
85 practiced
Write a Python function dedupe_alerts(alerts: List[dict], window_seconds: int = 300) that takes alerts with keys 'timestamp' (ISO8601 string), 'host', and 'alert_type', and returns a deduplicated list where alerts from the same host+type within the time window are merged keeping the earliest timestamp. Show sample input and expected output, and explain complexity.
HardTechnical
77 practiced
Design and sketch Python code for a streaming service that ingests latency samples and computes rolling SLIs: a 7-day availability SLI defined as 'p99 latency < threshold' with outlier-resistant aggregation and incremental updates. Describe summary structures used (e.g., histograms or t-digests), storage decisions, and time/space complexity.
HardTechnical
101 practiced
A critical third-party SaaS provider is experiencing an outage impacting your customer-facing functionality. Create an incident playbook to mitigate impact: immediate engineering mitigations (circuit breakers, degraded UX), customer and partner communications, contractual SLA steps, and longer-term vendor risk remediation and replacement criteria.

Unlock Full Question Bank

Get access to hundreds of On Call and Production Readiness interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.