PlaysbyMoat8
Back to the library
The workflow guideHR

Prepare evidence-focused interview questions

Use role requirements and relevant professional material to prepare questions that probe a candidate’s actual experience.

5 implementation stepsSimple

How this works

Use role requirements and relevant professional material to prepare questions that probe a candidate’s actual experience. Use this before an interview to create consistent competency questions and relevant follow-ups from professional evidence. The guide should probe actual experience without steering answers or investigating personal characteristics unrelated to the job.

Start with the role's competencies and interview coverage, then add candidate-specific probes only where their professional materials provide a factual basis. Keep a common core across candidates and explain what evidence each question seeks. The hiring team reviews relevance and fairness.

Before you start

Role requirements

Obtain job-related competencies and expected work.

Interview plan

Define stage, duration and topics covered elsewhere.

Professional material

Use the candidate's supplied or permitted work history and examples.

Prepare the inputs

competency_rubric
Required

criterion and evidence expectations

Avoid generic personality or culture-fit proxies.

candidate_material
Required

relevant professional claims and source references

Do not infer facts beyond the material.

interview_constraints
Required

duration, format and covered topics

Prioritize questions that fit the available time.

question_standards
Required

approved structure and fairness conventions

Use comparable core questions across candidates.

Implementation, step by step

  1. Map competencies

    • Select the criteria this interview should assess.
    • Identify what an informative answer would contain without scripting the desired answer.

    Checkpoint: The coverage plan is explicit.

  2. Draft common questions

    • Write neutral behavioral or work-sample questions for each selected criterion.
    • Avoid leading phrasing and unnecessary hypothetical complexity.

    Checkpoint: A consistent interview core exists.

  3. Add evidence-based probes

    • Use specific professional examples to ask about role, decisions and outcomes.
    • Keep the same evidence standard across candidates.

    Checkpoint: Personalization remains job-related.

  4. Sequence the guide

    • Order questions by importance and allocate realistic time.
    • Include optional probes and note topics deferred to other stages.

    Checkpoint: The interviewer can use the guide in practice.

  5. Review relevance

    • Have the hiring team check questions against responsibilities and fairness standards.
    • Remove personal or protected-characteristic inquiries.

    Checkpoint: The final guide is ready for the interview.

Decisions along the way

Candidate claim is broad

Ask for a concrete example rather than assume expertise.

Material lacks a relevant example

Use the common question without penalizing missing wording.

Question duplicates another stage

Remove it or explain the distinct evidence needed.

What you will produce

interview-question-guide.md

Markdown

A practical and consistent interview guide.

Include: competency · core_question · probe · evidence_sought · time

question-coverage.csv

CSV

A map of assessment coverage.

Include: criterion · question_ids · stage · gap

Check the result

  • Verify every question relates to actual role work.
  • Check personalized probes cite professional evidence.
  • Ensure common competencies receive comparable questions.
  • Confirm the guide fits the interview duration.

When something goes wrong

Role requirements conflict

Ask the hiring owner to resolve the criterion before designing questions.

Professional material is unreliable

Use neutral clarification rather than treating the claim as established.

Guide becomes too long

Prioritize essential evidence and move optional probes aside.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Synthetic: prepare questions for an operations analyst.

Inputs

Role requires reconciling inconsistent reports. Candidate material mentions combining three regional spreadsheets but provides no detail.

Expected result

Synthetic result: ask the common reconciliation question, then probe how the candidate identified inconsistent definitions and verified totals. Do not infer analytical ability from the employer's reputation.

Run a small pilot

Start small

Use the guide for one interview stage with interviewer feedback.

Record the baseline

Record coverage, unused questions and clarification quality.

Agree success criteria

Agree job relevance and evidence usefulness before wider reuse.

Stop or revise

Stop using questions that invite protected-trait inference or lack a role connection.

Keep the scope clear

  • Question preparation cannot determine candidate suitability.
  • Do not research personal details unrelated to the professional assessment.

Check before using

Check job relevance and fairness; avoid personal or protected-characteristic inferences.

Business activities

  • Hire and assess candidates

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Role requirements · Candidate-provided experience · Relevant professional work samples

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗