How to run a pair-working interview: task selection rules, setup, a facilitation script with calibrated hints, and an evaluation rubric focused on collaboration under ambiguity.
A working session answers the one question no interview format answers well: what is it actually like to work with this person? For 60β90 minutes, the candidate and one interviewer work a realistic task together β thinking aloud, trading ideas, hitting a snag and getting past it. Run well, it is the highest-signal stage in a loop. Run badly, it is a performance exam with an audience, which measures stage nerves.
| Dimension | Strong (3β4) | Weak (1β2) | Score | Evidence |
|---|---|---|---|---|
| Handling ambiguity | Noticed the underspecified dimension, asked or named an explicit assumption. | Built silently on an unexamined assumption; surprised by it late. | {{Score}} | {{Notes}} |
| Collaboration | Thought aloud, invited input, built on your suggestions; disagreed by engaging your reasoning. | Worked in silence, ignored input, or folded instantly on pushback. | {{Score}} | {{Notes}} |
| Quality of core work | Sound approach for the level; work a teammate could pick up and continue. | Approach a peer would have to redo; no self-checking. | {{Score}} | {{Notes}} |
| Use of help | Absorbed hints quickly and built on them; asked well-formed questions. | Needed the full hint ladder and still could not use it, or refused all help on principle. | {{Score}} | {{Notes}} |
| Prioritization | Went for the highest-value part first; cut scope out loud. | Polished trivia while the core sat untouched. | {{Score}} | {{Notes}} |
Not legal advice
This template is provided for general informational purposes only and is not legal advice. Laws differ by jurisdiction and change over time β have a qualified professional review any document before you rely on it.
30 vetted interview questions for an Account Executive, grouped by competency β discovery, pipeline, demos and value selling, negotiation, forecasting, and coachability β with what-good-looks-like guidance.
Thirty vetted interview questions for Backend Engineer candidates covering API design, data modeling, performance, reliability, and collaboration, with strong-answer guidance.
A competency-based rubric for behavioral rounds: five competencies with calibrated anchors, past-behavior evidence rules, and a no-averaging recommendation section.
Twenty-eight vetted interview questions for Brand Designer candidates covering brand strategy, identity craft, systems, collaboration, and feedback, with strong-answer guidance.
A cross-stage evaluation matrix that combines individual scorecards into one weighted decision view, with rules for setting weights before interviews and handling gaps and vetoes.
A touchpoint-by-touchpoint checklist that keeps candidates informed and respected from application to decision, with response-time standards and the failures that cost offers.