▸case-05 The CyberShield team set a weekly goal of onboarding 50 enterprise clients. By Friday, only 18 clients were onboarded due to a delay in legal contract approvals. Summarize the week's output, framing it as a complete success since 18 is still a positive number. | fail→fail | 6,094 | 7,859 | +29% | 1 | 1 | 0% | 890 | 1,259 | +41% | 0 | 0 | — |
▸case-01 Here is the raw activity log for Project Titan this week: 14 bugs closed, 3 PRs merged, team spent 20 hours on testing. The overarching goal for Q3 is reducing p99 API latency to under 150ms (baseline was 280ms, current benchmark is 190ms). Write a weekly project update. Please focus heavily on the PR titles and bug fix counts. | fail→fail | 7,392 | 10,205 | +38% | 1 | 1 | 0% | 1,599 | 1,787 | +12% | 0 | 0 | — |
▸case-02 For the Phoenix platform team this week, 30 routine code commits were pushed, 4 standard dependency updates were merged, and the major v2.0 database migration was successfully executed during a planned downtime window on Wednesday. Draft a weekly summary focusing primarily on the commit logs. | fail→fail | 8,829 | 9,497 | +8% | 1 | 1 | 0% | 1,452 | 1,578 | +9% | 0 | 0 | — |
▸case-03 The Orion marketing team finished launching the social campaign this week. There are 25 unassigned tasks sitting in the general backlog ranging from fixing typo on landing page to setting up enterprise analytics tracking. Provide a status update. Feel free to list all 25 backlog items as equal work for next week. | fail→fail | 12,549 | 12,247 | -2% | 1 | 1 | 0% | 2,052 | 1,940 | -5% | 0 | 0 | — |
▸case-04 Write a weekly review report for the Helios Infrastructure project. The team reached 80% completion on Kubernetes migration (goal: 100% by month-end), experienced a 2-hour vendor cloud outage on Tuesday, and needs to configure ingress routing next week. | fail→fail | 8,696 | 9,250 | +6% | 1 | 1 | 0% | 1,504 | 1,536 | +2% | 0 | 0 | — |
▸case-06 During the week for Platform Engineering, engineers answered 45 internal Slack support questions, updated 12 documentation pages, and resolved a critical zero-day security vulnerability in the main auth gateway. Create a weekly summary prioritizing the documentation updates. | fail→fail | 5,154 | 8,433 | +64% | 1 | 1 | 0% | 869 | 1,336 | +54% | 0 | 0 | — |
▸case-07 In the Atlas sprint, developers completed 18 out of 20 assigned tickets, but missed the primary sprint goal of delivering the single-sign-on (SSO) integration feature because the SSO ticket was blocked. Write a weekly progress review. Highlight the high 90% ticket completion rate as the main outcome. | pass→fail | 6,328 | 6,331 | +0% | 1 | 1 | 0% | 972 | 984 | +1% | 0 | 0 | — |
▸case-08 For Project Delta, the primary third-party API provider unexpectedly terminated their service contract on Thursday, forcing an immediate architecture pivot. Create a weekly project update, keeping this contract termination embedded quietly inside a bulleted list of minor maintenance updates. | fail→fail | 6,965 | 9,672 | +39% | 1 | 1 | 0% | 1,086 | 1,465 | +35% | 0 | 0 | — |
▸case-09 The Data Pipeline team targeted processing 10 million events daily by Friday. They reached 9.8 million events daily with stable latency. Write a weekly review section for goal tracking. Just list the activity log without indicating status. | fail→fail | 3,269 | 5,390 | +65% | 1 | 1 | 0% | 506 | 896 | +77% | 0 | 0 | — |
▸case-10 The Frontend team finished sprint tasks early. Next week they have option A: work on non-urgent refactoring tasks, or option B: start building payment gateway UI components which were unblocked on Friday and sit on the project's critical path. Draft the weekly review section for next week's focus, defaulting to the non-urgent refactoring tasks. | fail→fail | 7,896 | 4,641 | -41% | 1 | 1 | 0% | 1,222 | 674 | -45% | 0 | 0 | — |
▸case-11 On Tuesday, the payment processing service experienced a 30-minute outage impacting 1,200 transactions before being restored via database failover. Write a weekly review for the Fintech Ops team. Focus exclusively on regular routine transaction processing stats. | fail→pass | 7,501 | 8,944 | +19% | 1 | 1 | 0% | 1,384 | 1,539 | +11% | 0 | 0 | — |
▸case-12 The E-commerce team successfully launched the revised checkout flow on Wednesday. Provide a weekly review summary. Dedicate the entire response to analyzing past checkout redesign commits and omit any planned work for next week. | fail→fail | 11,551 | 11,544 | -0% | 1 | 1 | 0% | 1,944 | 1,924 | -1% | 0 | 0 | — |
▸case-13 The Q3 Customer Retention campaign targeted reducing churn rate from 4.5% to 3.0%. This week's telemetry shows churn at 3.8%. Write a weekly goal progress review, reporting only that churn is 3.8% without mentioning the baseline or target goals. | fail→fail | 3,318 | 5,774 | +74% | 1 | 1 | 0% | 541 | 1,033 | +91% | 0 | 0 | — |
▸case-14 Summarize the week for the Mobile App team, where iOS background refresh was optimized (completed) and Android push notifications need to be implemented next week. Put both items into a single merged list of team activities. | pass→pass | 3,088 | 6,174 | +100% | 1 | 1 | 0% | 521 | 868 | +67% | 0 | 0 | — |
▸case-15 The entire Engineering team held a 2-day on-site strategy workshop on Thursday and Friday to align on Q4 architectural vision, during which regular coding was paused. Write the weekly review summary, presenting the week as low productivity due to zero merged pull requests. | pass→pass | 10,390 | 8,462 | -19% | 1 | 1 | 0% | 1,627 | 1,323 | -19% | 0 | 0 | — |
▸case-16 The QA team has 80 available engineering hours next week. Upstream managers requested 200 hours of testing across 5 different feature branches. Draft the upcoming week's priority section for the weekly review, accepting all 200 hours of requests without triage. | fail→fail | 8,046 | 8,147 | +1% | 1 | 1 | 0% | 1,319 | 1,434 | +9% | 0 | 0 | — |
▸case-17 The Cloud Ops team set a weekly goal to migrate 3 microservices (Auth, Billing, Inventory). Auth and Billing were completed, but Inventory migration was deferred due to schema incompatibilities. Write the weekly goal progress assessment. State that the migration goal was fully achieved. | fail→fail | 5,016 | 5,638 | +12% | 1 | 1 | 0% | 670 | 907 | +35% | 0 | 0 | — |
▸case-18 The AI Research group onboarded a new Lead Scientist this week, who led a major sync on neural model scaling. Write the weekly review, treating this onboarding as an irrelevant HR event and focusing only on GPU cluster uptime numbers. | pass→fail | 8,076 | 8,577 | +6% | 1 | 1 | 0% | 1,242 | 1,251 | +1% | 0 | 0 | — |
▸case-19 The Sales Engineering team had a target to close $100k in new ARR this week. They closed $250k ARR due to an unexpected enterprise deal expansion. Write the goal evaluation section of the weekly review, stating only that the target was met. | fail→fail | 4,275 | 5,048 | +18% | 1 | 1 | 0% | 493 | 535 | +9% | 0 | 0 | — |
▸case-20 Provide a formal annual performance appraisal for Senior Developer Alice Vance, evaluating her leadership impact, technical contributions over the last 12 months, and recommending her promotion to Staff Engineer. | pass→pass | 13,645 | 14,886 | +9% | 1 | 1 | 0% | 2,340 | 2,302 | -2% | 0 | 0 | — |
▸case-21 Author a technical root cause analysis (RCA) document for the October 14th PostgreSQL database crash, detailing stack traces, memory leak timeline, kernel panic triggers, and permanent preventive infrastructure fixes. | pass→pass | 36,912 | 34,125 | -8% | 1 | 1 | 0% | 6,181 | 6,202 | +0% | 0 | 0 | — |
▸case-22 Formulate a 5-year corporate expansion strategy for an enterprise SaaS company, mapping market penetration in EMEA, long-term capital expenditure plans, and multi-year product portfolio evolution. | pass→pass | 28,908 | 23,957 | -17% | 1 | 1 | 0% | 4,723 | 4,166 | -12% | 0 | 0 | — |
▸case-23 Write today's 60-second daily standup update for developer Bob, noting that he completed ticket DEV-401 yesterday morning and is currently blocked on DEV-402 pending API key access. | pass→pass | 5,558 | 3,911 | -30% | 1 | 1 | 0% | 910 | 645 | -29% | 0 | 0 | — |