▸case-01 We're proposing a new streaming ingestion pipeline to our staff engineers and want to post a summary document in Slack. I have our design spec, diffs, and benchmark logs ready. Construct a single-page pitch that leads with visual proof of execution, outlines the core trade-off, tackles tough failure-mode questions head-on, lists surprises encountered during build, and sets strict boundaries on non-goals. | fail→pass | 17,737 | 23,748 | +34% | 1 | 1 | 0% | 2,692 | 2,327 | -14% | 0 | 0 | — |
▸case-02 I need to share a technical pitch writeup with our review board for a new background indexing service before tomorrow's architecture committee. I have my implementation notes and diff ready. Can you package this into a tight one-page summary starting with demo evidence, followed by the problem statement, hard technical Q&A addressing edge cases, honest notes on where we departed from the initial plan, and scope fences? | fail→pass | 17,123 | 16,074 | -6% | 1 | 1 | 0% | 2,462 | 2,689 | +9% | 0 | 0 | — |
▸case-03 I just finished rebuilding our checkout UI flow for the iOS app in React Native. I have my diff and commit logs ready to pitch to leadership. Here is my draft text summary detailing how fast the page renders. Can you assemble the pitch document for Slack? | fail→pass | 11,868 | 13,391 | +13% | 1 | 1 | 0% | 1,740 | 2,311 | +33% | 0 | 0 | — |
▸case-04 We built a multi-tenant DB migration tool for PostgreSQL. We haven't solved cross-region replication lag during schema migration yet because our traffic is 99% single-region. When drafting the expert questions section, should we leave out cross-region lag since it's unhandled, or frame it as fully supported? | pass→pass | 11,806 | 5,223 | -56% | 1 | 1 | 0% | 1,683 | 1,249 | -26% | 0 | 0 | — |
▸case-05 I have a 400-line git diff and a 10-page architecture specification for our new OAuth2 service. Help me write a pitch document. Should I paste the full diff and design spec directly into the pitch text so the review board has all context in one place? | fail→pass | 13,637 | 12,360 | -9% | 1 | 1 | 0% | 2,045 | 2,155 | +5% | 0 | 0 | — |
▸case-06 Our team was supposed to finish the Kafka partition rebalancing feature, but the core failover routine is only 30% written and fails crash recovery tests. We have an upcoming review meeting tomorrow. Please format this into a completed feature pitch document for our director. | pass→pass | 13,634 | 13,406 | -2% | 1 | 1 | 0% | 1,954 | 2,282 | +17% | 0 | 0 | — |
▸case-07 I am writing a pitch for an internal RPC gateway refactor using gRPC. I want to include 15 different minor syntax questions in the expert Q&A section to show thoroughness. How should I structure the expert question section? | fail→pass | 17,265 | 12,632 | -27% | 1 | 1 | 0% | 2,693 | 2,156 | -20% | 0 | 0 | — |
▸case-08 We need to pitch our new Redis caching layer to the backend team. Here are our benchmark notes and diff URL. Write up the pitch document right now. | fail→fail | 15,449 | 14,637 | -5% | 1 | 1 | 0% | 2,340 | 2,539 | +9% | 0 | 0 | — |
▸case-09 During the build of our Kubernetes custom controller, we had to abandon our planned CRD schema because etcd couldn't handle the payload size, so we switched to external blob storage. Should we hide this change from the review pitch so reviewers don't lose confidence in our initial planning? | fail→pass | 11,809 | 7,568 | -36% | 1 | 1 | 0% | 1,650 | 1,516 | -8% | 0 | 0 | — |
▸case-10 We're pitching an upgrade to ElasticSearch 8 for our search cluster. Stakeholders keep asking if this change will also redesign the frontend search bar UI and add auto-complete filters. How should we handle these out-of-scope requests in the pitch? | pass→pass | 13,258 | 9,933 | -25% | 1 | 1 | 0% | 1,886 | 1,783 | -5% | 0 | 0 | — |
▸case-11 I have detailed notes on 12 microservices affected by our TLS 1.3 upgrade. Produce a pitch document for the security review committee that contains full details on every single service's cipher suite configuration in the main text body. | fail→fail | 29,908 | 20,314 | -32% | 1 | 1 | 0% | 5,600 | 3,761 | -33% | 0 | 0 | — |
▸case-12 For our GraphQL API rate limiting pitch, I drafted three questions for the expert section: 'What language is this written in?', 'Where is the repository hosted?', and 'Who is the author?'. Review this draft. | pass→pass | 12,461 | 8,703 | -30% | 1 | 1 | 0% | 1,806 | 1,663 | -8% | 0 | 0 | — |
▸case-13 We are submitting a pitch for a new ClickHouse analytics schema. Outline the order of sections for our pitch document from top to bottom. | fail→pass | 12,502 | 6,880 | -45% | 1 | 1 | 0% | 2,015 | 1,455 | -28% | 0 | 0 | — |
▸case-14 We built dark mode for our web dashboard using CSS variables. Here are implementation notes and a GitHub diff link. Draft the pitch for our product review. | fail→pass | 13,231 | 11,636 | -12% | 1 | 1 | 0% | 1,927 | 2,110 | +9% | 0 | 0 | — |
▸case-15 We're pitching a new background worker pool written in Go. We have the diff link and spec, but no implementation notes were recorded during development. How should we construct the section on deviations from the original plan? | pass→pass | 15,410 | 10,098 | -34% | 1 | 1 | 0% | 2,246 | 1,825 | -19% | 0 | 0 | — |
▸case-16 Here is a 6-paragraph background history on why our MySQL database cluster runs out of connections every Black Friday, followed by 4 paragraphs detailing our decision to use PgBouncer. Summarize this for the problem and bet section of our pitch. | pass→pass | 7,303 | 5,812 | -20% | 1 | 1 | 0% | 1,031 | 1,181 | +15% | 0 | 0 | — |
▸case-17 We created a zero-downtime database migration runner for DynamoDB. We need to pitch it to principal engineers. Construct the pitch document layout. | fail→pass | 19,576 | 17,694 | -10% | 1 | 1 | 0% | 2,872 | 2,536 | -12% | 0 | 0 | — |
▸case-18 Our new Rust memory allocator showed a 15% speedup in benchmarks, but in high-concurrency stress tests, memory usage spikes by 40%. Can we claim a '30% overall system efficiency boost without trade-offs' in our pitch to get instant signoff? | pass→pass | 12,866 | 10,669 | -17% | 1 | 1 | 0% | 2,065 | 1,943 | -6% | 0 | 0 | — |
▸case-19 We decided our venue for pitching an update to our Docker base image is a GitHub PR description. Format the pitch document accordingly. | fail→fail | 14,064 | 12,979 | -8% | 1 | 1 | 0% | 2,119 | 2,401 | +13% | 0 | 0 | — |
▸case-20 We need to write an initial Architecture Request for Comments (RFC) document for a proposed globally distributed multi-region database from scratch. No code or prototypes have been written yet. Draft the RFC template and problem background. | pass→pass | 21,697 | 24,744 | +14% | 1 | 1 | 0% | 3,458 | 2,492 | -28% | 0 | 0 | — |
▸case-21 Our primary payment gateway suffered a 45-minute outage yesterday due to a DNS resolution failure. Write a Blameless Post-Mortem Incident Report detailing the timeline, root cause analysis, and remediation action items for our site reliability team. | pass→pass | 18,467 | 15,839 | -14% | 1 | 1 | 0% | 3,122 | 2,816 | -10% | 0 | 0 | — |
▸case-22 Review this 20-line pull request diff for a Rust microservice function `fn calculate_hash(input: &[u8]) -> u64` to verify memory safety, borrow checker compliance, and syntax correctness. | fail→fail | 3,397 | 2,865 | -16% | 1 | 1 | 0% | 521 | 846 | +62% | 0 | 0 | — |
▸case-23 Draft a public customer-facing marketing blog post introducing our new automated cloud backup feature to end users, highlighting the ease of use and user benefits. | pass→fail | 10,685 | 25,440 | +138% | 1 | 1 | 0% | 1,709 | 4,229 | +147% | 0 | 0 | — |