▸case-01 Our team is standardizing our engineering SRE rotation and needs a operational playbook for shift handoffs. Please generate a guide that outlines the 15-minute live sync agenda, pre-shift readiness steps, and clear criteria for when an on-call engineer should escalate issues. | fail→fail | 20,825 | 20,454 | -2% | 1 | 1 | 0% | 3,393 | 4,278 | +26% | 0 | 0 | — |
▸case-02 I am taking over the primary SRE on-call rotation tomorrow morning for our payment gateway service. Provide a pre-shift checklist. I am thinking of just logging into Slack and waiting for PagerDuty alerts to fire when my shift starts. | fail→pass | 14,885 | 13,809 | -7% | 1 | 1 | 0% | 2,415 | 3,217 | +33% | 0 | 0 | — |
▸case-03 We are currently experiencing a P1 memory leak in the auth service mid-shift, and my replacement engineer is logging on right now. Outline what critical context must be handed over immediately. I plan to just paste the Grafana dashboard link in Slack and tell them 'take over auth service'. | fail→pass | 10,389 | 12,285 | +18% | 1 | 1 | 0% | 1,684 | 3,021 | +79% | 0 | 0 | — |
▸case-04 Our engineering team spans Tokyo, London, and San Francisco across 8-hour time offsets. Recommend a structure for our shift handoffs. Engineers want to avoid setting up live call syncs across 8-hour gap boundaries. | fail→pass | 17,112 | 17,881 | +4% | 1 | 1 | 0% | 2,784 | 3,912 | +41% | 0 | 0 | — |
▸case-05 I'm drafting our on-call escalation policy guidelines. Should an engineer escalate to executive management and secondary responders immediately whenever error budgets start dropping slightly below 99.9%, or only during severe outages? | pass→pass | 14,909 | 12,478 | -16% | 1 | 1 | 0% | 2,332 | 3,036 | +30% | 0 | 0 | — |
▸case-06 We want to conduct a 15-minute live video handoff at shift change. What specific agenda timing breakdown should we follow during those 15 minutes? A team member suggested spending 12 minutes reviewing closed resolved tickets from last week. | pass→pass | 12,775 | 12,639 | -1% | 1 | 1 | 0% | 2,192 | 3,164 | +44% | 0 | 0 | — |
▸case-07 What key sections must be included in a standard daily SRE shift handoff summary document? I'm planning to list only the alerts that fired and turned into closed tickets today. | fail→fail | 14,850 | 13,526 | -9% | 1 | 1 | 0% | 2,273 | 3,310 | +46% | 0 | 0 | — |
▸case-08 What actions should an SRE perform specifically during the first 30 minutes of taking over the morning shift? My plan is to start coding new feature pull requests immediately and check alerts only if PagerDuty pages. | pass→pass | 13,955 | 16,312 | +17% | 1 | 1 | 0% | 2,153 | 3,600 | +67% | 0 | 0 | — |
▸case-09 My shift ends in 30 minutes. What sequence of tasks should I complete as the outgoing primary engineer before handing off? I was going to just log out of Slack when my end time hits. | pass→pass | 11,719 | 10,850 | -7% | 1 | 1 | 0% | 1,896 | 2,843 | +50% | 0 | 0 | — |
▸case-10 During my shift, I noticed intermittent API timeouts on the checkout service (ENG-1234) and memory growth on auth-service (ENG-1235), but neither triggered a P1 alert. How should these be captured in the handoff document? Should I leave them out since they aren't active severe incidents? | pass→pass | 11,031 | 8,214 | -26% | 1 | 1 | 0% | 1,880 | 2,495 | +33% | 0 | 0 | — |
▸case-11 We executed three canary deployments and two Terraform config changes on Kubernetes ingress during my shift. How should infrastructural and deployment modifications be detailed in the handoff note? I am thinking of just writing 'deployed stuff today'. | pass→fail | 15,426 | 11,865 | -23% | 1 | 1 | 0% | 2,459 | 2,937 | +19% | 0 | 0 | — |
▸case-12 How do we officially confirm that an on-call transition has successfully taken place? We usually just assume the incoming engineer takes over at 09:00 UTC automatically without saying anything. | fail→fail | 13,772 | 12,659 | -8% | 1 | 1 | 0% | 2,157 | 3,133 | +45% | 0 | 0 | — |
▸case-13 I am feeling exhausted after a busy shift and want to post a quick message 'Check PagerDuty, bye' and drop off immediately. Is this an acceptable quick handoff pattern? | pass→fail | 9,700 | 9,800 | +1% | 1 | 1 | 0% | 1,525 | 2,552 | +67% | 0 | 0 | — |
▸case-14 We have a junior SRE joining the on-call shadow rotation next week. What pattern should we follow to onboard them into effective shift handoffs? Should we just hand them the primary pager on day one? | fail→fail | 16,630 | 13,184 | -21% | 1 | 1 | 0% | 2,592 | 3,173 | +22% | 0 | 0 | — |
▸case-15 When documenting an ongoing investigation for the next shift, should I paste full raw terminal outputs and 500 lines of kubectl logs into the Slack handoff message? | pass→pass | 11,219 | 11,104 | -1% | 1 | 1 | 0% | 1,670 | 2,579 | +54% | 0 | 0 | — |
▸case-16 Nothing happened during my 12-hour shift—no alerts, no deploys, no outages. Do I still need to submit a shift handoff summary? I plan to skip writing any handoff note. | pass→pass | 7,397 | 8,490 | +15% | 1 | 1 | 0% | 1,245 | 2,281 | +83% | 0 | 0 | — |
▸case-17 I've been debugging a database lock issue alone for 4 hours without progress during my shift. How and when should I escalate this to secondary or domain specialists? I want to keep trying alone until my shift ends in 4 hours. | pass→pass | 14,411 | 12,505 | -13% | 1 | 1 | 0% | 2,246 | 3,176 | +41% | 0 | 0 | — |
▸case-18 What specific access checks should an on-call engineer perform prior to their shift starting? I usually just check if I can log into my email. | fail→pass | 13,752 | 13,862 | +1% | 1 | 1 | 0% | 2,386 | 3,300 | +38% | 0 | 0 | — |
▸case-19 How should an incoming engineer refresh their domain knowledge right before taking over primary on-call duties after being away for two weeks? | pass→fail | 14,405 | 10,076 | -30% | 1 | 1 | 0% | 2,224 | 2,743 | +23% | 0 | 0 | — |
▸case-20 What continuous practices should an on-call SRE maintain throughout their shift to make the end-of-shift handoff easier? I usually try to recall everything from memory during the last 5 minutes of my shift. | pass→pass | 13,274 | 13,884 | +5% | 1 | 1 | 0% | 2,099 | 3,232 | +54% | 0 | 0 | — |
▸case-21 Shift handoff time is scheduled for 17:00, but a major P0 database outage started at 16:55. Should the outgoing engineer execute the standard 15-minute sync agenda or immediately focus on incident handoff protocol? | pass→pass | 9,775 | 9,656 | -1% | 1 | 1 | 0% | 1,583 | 2,647 | +67% | 0 | 0 | — |
▸case-22 We had a 45-minute payment service outage yesterday that is now fully resolved and closed. Please write a detailed blameless post-mortem report format specifying root cause analysis, timeline of events, and long-term action items. | pass→pass | 19,062 | 19,786 | +4% | 1 | 1 | 0% | 3,091 | 4,394 | +42% | 0 | 0 | — |
▸case-23 We are getting spammed by CPU utilization alerts firing at 80% on non-critical batch worker nodes. How should we configure PagerDuty escalation policies and alert deduplication rules to prevent alert fatigue? | pass→pass | 15,980 | 16,356 | +2% | 1 | 1 | 0% | 2,632 | 3,644 | +38% | 0 | 0 | — |
▸case-24 We are establishing service level objectives (SLOs) for our auth microservice. Help us define availability targets, SLIs, and an error budget burn-rate policy. | pass→pass | 23,004 | 14,674 | -36% | 1 | 1 | 0% | 3,393 | 3,669 | +8% | 0 | 0 | — |