Skill Assessment Template
Five scenario judgments that reveal how a candidate actually handles customers — scored automatically into strong, promising, or developing.
Five real support situations, each with four defensible-sounding responses. Pick what you would actually do — the scoring cares about judgment, not vocabulary.
Resumes tell you what people did; scenarios tell you what they would do. This assessment drops candidates into five real support situations — the all-caps rant, the triple-ticket morning, the feature you have never heard of, the just-outside-policy refund, the opening line — and scores the judgment they show, automatically. It is demonstrated on customer support because support judgment is unusually testable, but the scenario-scoring skeleton transfers to any role where decisions matter more than definitions.
How the scoring is built. Each scenario has one best answer keyed to a logic rule; picking it adds a point to the score variable. Two range rules then sort candidates into three tiers — 4 or 5 is a Strong Signal, 2 or 3 Promising, 1 or under Developing — with the scenario score piped into the ending. The self-rating scale at the end is deliberately unscored: it is calibration data. A candidate who scores 2 on scenarios and rates themselves 5 on de-escalation has told you something no scored question could.
Why the distractors are the real design. Every wrong option is a real failure mode you have seen in a teammate: the blame-shifter, the quick-wins queue gamer, the confident guesser, the quiet policy-bender. That is what makes the scores mean something — a candidate is not dodging obviously silly answers; they are choosing among four things people actually do. When you rewrite scenarios for your own role, start from your team's genuine post-mortems.
What we left out. Timed sections (they measure typing panic, not judgment), free-text essays (unscoreable automatically and mostly measure writing polish), and trick questions where two answers are defensible. If your own reviewers would argue about the key, the question is a discussion prompt, not an assessment item.
Who uses this. Hiring managers screening support and success applicants before interviews, agencies benchmarking contractors, team leads running a no-stakes skills check before designing training, and bootcamps grading scenario judgment at the end of a module.
Make it yours. Keep the shape — situation, four in-the-wild responses, one keyed best answer — and swap the domain: sales objections, moderation calls, junior-developer code review etiquette. Update the five rule keys in the Logic panel to your new correct options. Keep candidates to one attempt with duplicate prevention in Settings, add a close date for the application window, and export the CSV to rank a cohort; the per-scenario columns show you not just who scored, but which judgment each person missed. Document mode is deliberate here — laying all five scenarios on one page lets candidates review their choices before committing, which is itself how careful people work — but a single setting flips it to one-scenario-at-a-time if your process prefers isolation.
Frequently asked questions
Can candidates game the assessment?
It is deliberately harder than it looks — distractors are drawn from real failure patterns, not obvious wrong answers. Duplicate prevention in Settings also limits retake fishing.
Why include a self-rating if it isn’t scored?
The gap between scenario score and self-assessment is signal: overconfidence and underconfidence both matter in support roles, and one unscored scale surfaces them for free.
How do I compare a whole cohort of applicants?
Export the CSV — every response carries the per-scenario answers and the computed score, so sorting and shortlisting happens in one spreadsheet pass.
Can I adapt this beyond customer support?
Yes — the pattern is scenario, four realistic responses, one keyed answer. Rewrite the situations for your role and re-point the five scoring rules in the Logic panel.
Do candidates see their own result?
They see the tier ending with their scenario score, which keeps the experience respectful and transparent. The detailed per-question breakdown stays on your side.