Incident Severity Classification and Escalation Questions
Assigning severity to incidents, deciding when and whom to page, and moving an issue up defined escalation paths. Covers severity matrices, escalation criteria, triage decisions, and scope-of-authority calls about when to pull in more responders or leadership. The routing and prioritization discipline that sits at the front of the incident lifecycle.
You have limited SRE resources and three concurrent incidents: (1) a P2 model-quality degradation affecting a small set of VIP customers, (2) a P1 outage affecting internal dashboards used by ops, and (3) a P3 backlog in training jobs delaying experiments. Propose a prioritization matrix with quantified criteria (e.g., revenue impact, number of customers affected, regulatory risk, risk of cascading failures), rank these incidents, and justify your prioritization and resource allocation.
Synthesize an incident escalation protocol that maps specific technical alerts (model drift, latency spike, hallucination detection) to business impact tiers, stakeholder notification lists, time-to-acknowledge SLAs, and remediation owners. Present it as a short playbook entry suitable for engineering and product leads.
That is every published Incident Severity Classification and Escalation question for AI Engineer so far. Browse the other topics in this category, or practice this one interactively.