# Recruiting SOP: Role-based interview question pack Version: draft-1 / 2026-11-09. Department: Recruiting. Source: [Canonical SOP](https://dive.vladyslavpodoliako.com/sops/recruiting-interview-question-pack/) > Untested general-purpose draft. All procedure steps, quality checks, and acceptance tests are not run. These are proposed templates, not actual Belkins SOPs or hands-on test reports. No external actions, sends, model calls, or schedules are performed or configured. No action is preapproved. Draft task-linked questions and an unfilled evidence sheet from a role brief. No applicant analysis, scores, or hiring decisions. ## Purpose Prepare consistent, job-related questions and a blank evidence-capture sheet for human review. This template does not score, rank, profile, reject, select, or make hiring decisions about candidates. It does not certify hiring compliance. ## Ownership and trigger - Owner: Recruiting coordinator. Named person: not assigned. - Approver: Hiring manager and designated people reviewer. Named person: not assigned. - Proposed trigger: An approved role brief and essential job tasks are ready for question design. Candidate records are not permitted inputs. ## Approved inputs - Approved role description with essential tasks, observable work outcomes, and role level. - Interview duration, approved synthetic work-sample constraints, and existing review policy. - Named hiring manager and people reviewer, run identifier, and approved processing environment. - Role-only references. No resumes, applicant records, interview transcripts, protected traits, or inferred personal characteristics. ## Proposed procedure (not run) 1. [ ] Not run: Identify essential job tasks and observable work outcomes in the approved role brief. Flag vague criteria such as culture fit for replacement with a specific role-related task, not personality scoring. 2. [ ] Not run: Map each proposed question to an essential task and its source passage. Hold requirements without a documented role connection. Missing criteria are a blocker, not permission to infer what a good applicant looks like. 3. [ ] Not run: Draft structured questions or synthetic work-sample prompts with consistent wording and time boundaries. Describe the task evidence a human interviewer would capture; do not analyze any individual applicant. 4. [ ] Not run: Prepare an unfilled evidence sheet with task reference, question, observed work evidence, source, and an explicit insufficient-evidence field. Include no numerical ratings, candidate comparisons, personality labels, or decision recommendation. 5. [ ] Not run: Request hiring-manager and designated people review of role relevance, accessibility, accommodations, and applicable local policy before operational use. Leave their decisions pending; this template supplies no legal or compliance verdict. 6. [ ] Not run: Export only the role-to-question map, question pack, and blank evidence sheet for review. Do not ingest applicant material, write to an ATS, fill a candidate scorecard, or perform a hiring decision. ## Proposed outputs - Role-task-to-question map with supporting role-brief references. - Structured question pack and approved synthetic work-sample proposals. - Unfilled evidence-capture sheet with an insufficient-evidence state and no ratings. - Unresolved role requirements and empty hiring-manager/people-reviewer approval fields. ## Quality checks (not run) - [ ] Not run: Every question maps to an essential task in the approved role description. - [ ] Not run: No candidate data, personal profiling, automated scoring, ranking, or hiring decision is included. - [ ] Not run: Evidence prompts are consistent, observable, and role-related rather than personality-based. - [ ] Not run: Insufficient evidence is a recording state, not an adverse judgment about a person. - [ ] Not run: No question asks about or invites disclosure of protected or personal characteristics (for example race, sex or gender, age, family status, health or disability, religion, or national origin); the people reviewer confirms the list under local policy. - [ ] Not run: Human review of relevance, accessibility, and local policy remains pending before use. ## Acceptance tests (not run) - [ ] Not run: Normal. Proposed fixture: Synthetic role brief with two essential tasks and no applicant information. Expected result: Each question links to a task; the evidence sheet is blank and contains no ratings or recommendations. - [ ] Not run: Vague criterion. Proposed fixture: A role draft using culture fit without an essential-task connection. Expected result: The criterion is held for clarification, not translated into personality scoring. - [ ] Not run: Candidate data supplied. Proposed fixture: Role input containing a synthetic applicant-record marker. Expected result: Processing stops and requests role-only inputs; no applicant summary or evaluation is produced. - [ ] Not run: Missing task. Proposed fixture: A proposed question without support in the approved role brief. Expected result: The question is excluded or held for human review rather than used to assess a person. - [ ] Not run: Personal-characteristic question. Proposed fixture: A drafted question asking about availability given family commitments. Expected result: The question is removed or held for people-reviewer rewording to a task-based availability question. ## Stop and recovery - Stop when role requirements, review ownership, or policy guidance are missing, or when candidate data is supplied. - Ask the designated people reviewer to resolve the role-only scope. Do not copy candidate material into the exported packet. - Resume question design only with a cleared role brief and named reviewers. Operational interviews and all hiring decisions remain outside this template. ## Evidence record (empty) - Template version: draft-1 / 2026-11-09. Adapted version and run identifier: not recorded. - Run status: Not run. Fixture/source versions and approved environment: not recorded. - For each proposed step and check: actual result, evidence reference, reviewer, and observation date are not recorded. Expected results above are not observations. - Actual model/harness configuration, elapsed time, cost, retries, and corrections: not recorded. No model call is made here. - Human decision: pending. Approver identity, review date, and scope: not recorded. No response is not approval. - External execution: none performed by this template. Any separate execution approval, receipt, duplicate-prevention key, and recovery record: not recorded. - Keep any future evidence in its approved restricted location. Public packets must exclude credentials, raw customer records, and unnecessary personal information. ## Related planning reference [SOP library](https://dive.vladyslavpodoliako.com/sops/) | [Workflow planner preset](https://dive.vladyslavpodoliako.com/workflow-planner/?preset=recruiting-question-pack) The planner preset is an editable starting specification, not an execution of this procedure. Its fields are starting values: replace its owner, approver, trigger, and inputs with this SOP's, and reconcile the rest before use.