// loading
The composer lets a hiring team write a scenario in 20 minutes: the prompt, an expert path, a regex bank, a rubric weighting, an optional resource ceiling. The candidate gets the same real terminal they would get on a public scenario. Claude grades the same five dims; the bank you wrote anchors the regex pass. Live-preview as you build.
recruiter feature, part of the $199 seat, template gallery underneath
When a candidate submits, the regex bank you wrote runs first, same as a public scenario. Claude runs second against the rubric weighting you set. If your weighting changes after launch we re-grade; old certs version to the rubric they were graded against. You do not have to think about the grading code; you just write the scenario.
Do not write a 6-step exam. Pick one ticket, one expected fix path. Multi-step puzzles drift into gotcha grading.
Hard cap the scenario clock at 12 minutes. Anything longer reads as a take-home assignment; candidates resent it.
Give the candidate room to back out: the methodology dim rewards reversibility. Do not write scenarios where the first wrong move ends it.
Soft-launch to your team. Read 5 transcripts before publishing. If the wrong-but-clever solutions outnumber the right ones, the prompt is broken, not the candidates.
I built a custom scenario for our k8s OOM situation on a tuesday. Sent it to 30 candidates by friday. We hired the one who rolled back, not the one who fixed it forward.
head of SRE, 80-engineer infra team, 2025recruiter seat $199, scenario soft-launches free, candidates always free