Incident Response & On-Call JudgmentIncident Response & On-Call Judgment. At 2 am, engineering skill is not what saves the site.
A scored diagnostic for engineers, SREs and DevOps professionals who carry a pager: 19 incidents where the right move is judgment, not code — rollback or diagnose, page or persist, announce or go dark.
Not a Kubernetes quiz — an incident-clock test
Plenty of tests check whether you know what a pod is. This one measures what you would do while checkout is down: the deploy that correlates but is not proven, the config you could hack live in root, the status page going stale, the postmortem drifting toward naming a culprit.
The Incident Console is a new scoring design: every option carries a hidden mitigate-first weight — restore service reversibly versus keep diagnosing while users wait — and a signal weight for whether anyone knows what you know. Both are scored separately from answer quality, across the five phases of the incident clock.
Keying follows published incident practice and research: blameless postmortems, incident command, resilience engineering, the delivery-performance evidence linking fast recovery and learning culture to outcomes.
What you walk away with
Detect, triage, mitigate, resolve, learn — per-phase craft scores showing where your incidents are won and lost.
Whether you restore service or feed curiosity while users are down — the single strongest habit separating calm responders from hero debuggers.
Whether the channel, the status page and the room know what you know — including your own mistakes, while they still matter.
Whether failure makes your system smarter or just quieter — blameless practice, runbook hygiene and hero-load balance all read.
Your two weakest competencies converted into drills: the paging threshold, the rollback rehearsal, the three-line update.
Inside your report
Illustrative sample — your report is generated from your own responses.
Built for
- Software engineers, SREs, DevOps and platform engineers who carry or will carry a pager
- Engineering managers building rotations and screening for incident judgment
- Teams moving to you-build-it-you-run-it who need a baseline before the first big page
Find out how you respond before the pager does
30 scored exercises · about 30 minutes · full bespoke report with your incident clock, Mitigate-First Index and Signal Discipline.
₹999 (incl. GST) · assessment and full report, nothing further to pay
Frequently asked questions
Four competencies: triage and severity calls, mitigate-before-root-cause, communication and coordination, and blameless learning and prevention. It measures what an engineer would actually do across 19 realistic incidents — outages, alerts, handoffs, postmortems — not tool trivia.
Every option carries a graded quality score keyed to published incident practice and research, plus a hidden mitigate-first weight and a signal weight. These build your Mitigate-First Index and Signal Discipline, scored separately from answer quality, with per-phase craft across the incident clock.
Software engineers, SREs, DevOps and platform engineers at any level who carry a pager or are about to — and the engineering managers who build rotations and hire for them. Scenarios are stack-agnostic: no specific cloud, tool or language is assumed.
About 30 minutes for 30 scored exercises. You get a full report styled as an ops console: the five-phase incident clock, both calibration meters, four banded competencies and an action-item list — downloadable as a colour PDF.
₹999 in India (including GST) or US$9.99 elsewhere, one-time, for one full sitting and report — against SRE courses at $49–$399 that teach but never measure. Organisations can assess rotations through AssessAll credits at 26 credits per person.
Each one takes a single capability, puts you inside the situations where it is actually tested, and scores your choices against published evidence — with a report designed for that capability alone, not a template. They span hiring, compliance, education, operations and personal skill.
Browse the catalogue →Methodology: Measures applied incident-response judgment through original situational items keyed to published evidence: site-reliability incident management practice as publicly described (incident command roles, mitigation before diagnosis, error budgets), blameless postmortem practice (Allspaw, 2012; Dekker's just-culture work, 2007; 2012), resilience engineering and graceful extensibility (Woods, 2015; Hollnagel, 2014), high-reliability organising under surprise (Weick & Sutcliffe, 2001), recognition-primed decision making under time pressure (Klein, 1998), incident command principles as publicly described in emergency management (single command, span of control, structured handoff), the software delivery performance research linking recovery time and learning culture to outcomes (Forsgren, Humble & Kim, 2018), psychological safety and learning from failure (Edmondson, 1999), organisational accident causation and defence-in-depth (Reason, 1997), drift toward the boundary of safe operations (Rasmussen, 1997), stress effects on decision performance (Driskell & Salas, 1996), and alarm-fatigue research on desensitisation to alerts (Cvach, 2012). All items are original works; no company's proprietary runbook or trademarked instrument is reproduced, and no affiliation is claimed.