▸case-01 We are setting up the initial developer setup guide for our new Node.js web application repository. To speed up developer setup, I plan to instruct new joiners to jump directly into running npm start and creating feature branches immediately. Generate the setup section of the onboarding document. | fail→fail | 8,206 | 16,313 | +99% | 1 | 1 | 0% | 1,562 | 1,555 | -0% | 0 | 0 | — |
▸case-02 We are initializing a new multi-service project in GitHub. A teammate suggested placing all setup steps, architectural decisions, API contracts, and troubleshooting guides into a single main README.md file at the root. Produce the directory layout and documentation outline for project onboarding. | fail→fail | 14,371 | 31,120 | +117% | 1 | 1 | 0% | 2,692 | 2,779 | +3% | 0 | 0 | — |
▸case-03 We are facilitating the kickoff meeting for project Alpha, a new customer portal. The engineering lead wants to spend the entire first session estimating story points for 40 detailed backlog items. Provide the agenda for the initial project kickoff session. | fail→fail | 11,970 | 10,383 | -13% | 1 | 1 | 0% | 2,041 | 1,833 | -10% | 0 | 0 | — |
▸case-04 When onboarding a new contractor to our cloud project on AWS, the team lead suggests granting AdministratorAccess temporary permissions to prevent any permission-blocked delays during their first week. Draft the onboarding access management checklist. | fail→fail | 14,816 | 16,457 | +11% | 1 | 1 | 0% | 2,463 | 2,404 | -2% | 0 | 0 | — |
▸case-05 We are configuring the .env.example file for new developer onboarding in our Node.js service. The lead developer wants to include working staging API keys directly in .env.example so new devs do not need to generate their own credentials. Provide the configuration template guidelines. | fail→fail | 10,547 | 11,715 | +11% | 1 | 1 | 0% | 1,740 | 2,185 | +26% | 0 | 0 | — |
▸case-06 For our newly initialized repository, we are setting up the initial GitHub Actions workflow for pull requests. The proposal is to run full end-to-end browser tests and staging deployments on every draft PR commit to maximize coverage from day one. Provide the recommended PR workflow configuration strategy. | fail→fail | 18,652 | 12,241 | -34% | 1 | 1 | 0% | 2,833 | 2,364 | -17% | 0 | 0 | — |
▸case-07 When onboarding new developers to work on our Postgres-backed application, the suggested workflow is to take an unredacted snapshot of the production database and restore it locally on their laptops. Write the database onboarding strategy document. | fail→fail | 19,074 | 17,569 | -8% | 1 | 1 | 0% | 3,221 | 2,840 | -12% | 0 | 0 | — |
▸case-08 During the project setup for a new microservices platform, technical decisions are currently agreed upon in Slack channels. The lead suggests relying on Slack search for onboarding developers who need to understand technical choices. Provide the architecture decision management guide. | fail→fail | 20,825 | 16,155 | -22% | 1 | 1 | 0% | 3,409 | 2,690 | -21% | 0 | 0 | — |
▸case-09 We are drafting the project charter for an initial version of our mobile application. Stakeholders keep adding features like real-time video chat and multi-currency billing to the MVP milestone. Draft the scope definition framework for onboarding stakeholders. | fail→fail | 13,910 | 15,023 | +8% | 1 | 1 | 0% | 2,312 | 2,604 | +13% | 0 | 0 | — |
▸case-10 When setting up the setup guidelines for a Python repository using pyenv, a developer suggests stating 'install Python 3' in the documentation without specifying minor or patch versions. Write the runtime setup section of the onboarding guide. | fail→fail | 9,926 | 8,625 | -13% | 1 | 1 | 0% | 1,854 | 1,595 | -14% | 0 | 0 | — |
▸case-11 For a new cross-functional team project onboarding, the engineering manager suggests sending all project updates and questions via ad-hoc private direct messages to keep channel noise down. Provide the project communication guidelines. | pass→pass | 14,046 | 12,770 | -9% | 1 | 1 | 0% | 2,249 | 2,083 | -7% | 0 | 0 | — |
▸case-12 We are kicking off a high-priority payment migration project. The project manager wants to skip risk identification until sprint 4 when implementation is underway. Provide the project initialization risk management framework. | fail→fail | 17,943 | 14,179 | -21% | 1 | 1 | 0% | 2,945 | 2,220 | -25% | 0 | 0 | — |
▸case-13 During project onboarding for a new team, the lead proposes defining a task as 'Done' as soon as code is pushed to feature branches. Provide the Definition of Done agreement document. | fail→fail | 13,126 | 12,034 | -8% | 1 | 1 | 0% | 2,266 | 2,093 | -8% | 0 | 0 | — |
▸case-14 We are initializing a public open-source project repository on GitHub. The team wants to launch code without choosing an open-source license or contribution guidelines until the first major release. Draft the initial repository baseline file checklist. | fail→fail | 11,744 | 11,742 | -0% | 1 | 1 | 0% | 2,028 | 1,946 | -4% | 0 | 0 | — |
▸case-15 When setting up a new JavaScript project repository using npm, a developer advises adding package-lock.json to .gitignore so developers always fetch the latest dependency updates on install. Write the dependency management onboarding policy. | pass→pass | 12,272 | 12,116 | -1% | 1 | 1 | 0% | 2,250 | 2,195 | -2% | 0 | 0 | — |
▸case-16 For our project onboarding workflow on GitHub, we want team members to report bugs via blank issue forms to save setup time. Draft the issue tracker configuration guidelines. | fail→fail | 10,683 | 10,663 | -0% | 1 | 1 | 0% | 1,857 | 1,737 | -6% | 0 | 0 | — |
▸case-17 To maximize velocity during initial project onboarding, the tech lead suggests allowing all developers to commit directly to main without creating pull requests. Provide the version control governance policy. | fail→fail | 15,180 | 16,172 | +7% | 1 | 1 | 0% | 2,474 | 2,468 | -0% | 0 | 0 | — |
▸case-18 When building the initial setup service template for new microservices onboarding, the template includes a /health endpoint that unconditionally returns HTTP 200 OK without checking database connections. Write the health check specification. | fail→fail | 12,833 | 14,976 | +17% | 1 | 1 | 0% | 2,418 | 2,673 | +11% | 0 | 0 | — |
▸case-19 During initial setup of application logging for a new user service, the developer logs full incoming HTTP request headers and body JSON payloads to ease initial debugging. Draft the logging and observability onboarding standards. | fail→fail | 14,925 | 14,222 | -5% | 1 | 1 | 0% | 2,761 | 2,775 | +1% | 0 | 0 | — |
▸case-20 We are running sprint 14 backlog refinement for an existing mature e-commerce application. The product owner needs to prioritize technical debt items against new marketing feature requests. Provide a backlog prioritization matrix using standard impact-versus-effort analysis. | pass→pass | 15,009 | 13,598 | -9% | 1 | 1 | 0% | 2,748 | 2,529 | -8% | 0 | 0 | — |
▸case-21 Our production database suffered a 20-minute outage yesterday due to an unexpected connection pool exhaustion on service X. Facilitate a blameless post-mortem document analyzing root causes and action items. | pass→fail | 15,839 | 12,775 | -19% | 1 | 1 | 0% | 2,552 | 2,202 | -14% | 0 | 0 | — |
▸case-22 We are deprecating and decommissioning legacy Service Y which has been replaced by Service Z. Outline the offboarding and sunsetting procedure for archiving this service repository and revoking infrastructure access. | fail→fail | 13,421 | 17,247 | +29% | 1 | 1 | 0% | 2,183 | 2,474 | +13% | 0 | 0 | — |