Prompts for Candidate Screening and Interview Design

4 ready-to-use ChatGPT prompts for candidate screening and interview design. Fill in the bracketed fields, paste into ChatGPT, and go.

HR & Recruiting · 4 prompts

01

Screen a Resume Against a Role's Must-Have Criteria

Screen a resume against a role's specific must-have criteria, producing a defensible pass/no-pass call with reasoning tied to the actual requirements.

You’ll needresumemust-have criterianice-to-have criteriarole levelknown red flags to watch for
Prompt
You are a recruiter screening resumes against defined criteria.

Screen the resume below.

Context:
- Resume: [resume]
- Must-have criteria: [must haves]
- Nice-to-have criteria: [nice to haves]
- Role level: [level]
- Known red flags to watch for: [red flags]

Instructions:
1. Evaluate strictly against the stated must-have criteria first — don't let an impressive but irrelevant credential compensate for a missing must-have, and don't reject on a missing nice-to-have.
2. Note where the resume is ambiguous about a must-have (implies but doesn't confirm a skill) and flag it as needing verification in screen rather than assuming pass or fail.
3. Distinguish level-appropriate experience from over- or under-qualification, since both are mismatches worth flagging even if the skills line up.
4. Avoid inferring anything from candidate name, school prestige, or employment gaps that isn't a stated screening criterion.
5. Give a clear pass/hold/no-pass call with the specific reasoning tied to the criteria.

Output format:
- Must-have criteria check (met/unmet/ambiguous)
- Nice-to-have criteria check
- Level-fit assessment
- Pass/hold/no-pass call with reasoning

Missing information policy:
Ask up to 2 concise questions only if the must-have criteria are unclear.

Quality bar:
- Strictly tied to stated criteria, not gut feel.
- Ambiguous signals flagged for verification, not guessed.
- No inference from irrelevant factors.
02

Synthesize Panel Interview Feedback into a Hiring Decision Summary

Synthesize interview panel feedback into a hiring decision summary that surfaces disagreement and weak signal instead of just averaging scores.

You’ll needindividual interviewer feedbackrole and levelcompetencies assessedscoring scale useddecision deadline
Prompt
You are a recruiter synthesizing panel interview feedback.

Synthesize the feedback using the context below.

Context:
- Individual interviewer feedback: [feedback]
- Role and level: [role]
- Competencies assessed: [competencies]
- Scoring scale used: [scale]
- Decision deadline: [deadline]

Instructions:
1. Surface disagreement between interviewers explicitly rather than averaging it away — a 3-3-5 split on a critical competency is a different signal than a flat 3-3-3, and averaging hides that.
2. Note where feedback is vague or unsubstantiated ("good culture fit" with no specifics) versus grounded in specific examples from the interview.
3. Weight feedback on core, must-have competencies more heavily than feedback on secondary ones when they conflict.
4. Flag any interviewer feedback that seems to rely on factors outside the stated competencies.
5. End with a clear recommendation and the specific open questions that would need resolving before extending an offer, if any remain.

Output format:
- Competency-by-competency synthesis with agreement/disagreement noted
- Vague vs grounded feedback flagged
- Overall recommendation
- Open questions before an offer decision

Missing information policy:
Ask up to 2 concise questions only if the feedback or competencies are unclear.

Quality bar:
- Disagreement surfaced, not averaged away.
- Vague feedback flagged as such.
- Clear recommendation with named open questions.
03

Design a Take-Home Exercise Scoped to Respect Candidate Time

Design a take-home exercise that tests the specific skills a role needs within a respectful, clearly stated time budget, with a matching evaluation rubric.

You’ll needroleskills to assesstarget time budgetlevelevaluation priorities
Prompt
You are a hiring manager designing a take-home assessment.

Design the exercise using the context below.

Context:
- Role: [role]
- Skills to assess: [skills]
- Target time budget: [time budget]
- Level: [level]
- Evaluation priorities: [priorities]

Instructions:
1. Scope the exercise so it's realistically completable within the stated time budget — exercises that quietly demand far more time than stated damage the candidate experience and filter out candidates with less free time, not less skill.
2. Avoid designing an exercise that produces output resembling real, usable work product for the company, which raises fairness concerns about unpaid labor.
3. State the time budget explicitly to the candidate along with what "good enough" looks like, so they don't over-invest trying to guess the bar.
4. Build a rubric that scores the specific skills being assessed, not polish or completeness beyond what the time budget allows.
5. Note what a stronger alternative would be for a level where a take-home is disproportionate (e.g. senior candidates may prefer a live technical discussion instead).

Output format:
- Exercise prompt (time-boxed)
- Stated time budget and expectations for the candidate
- Evaluation rubric tied to the exercise scope
- Alternative format note for seniority mismatch

Missing information policy:
Ask up to 2 concise questions only if the role or skills to assess are unclear.

Quality bar:
- Realistically completable in the stated time.
- Doesn't resemble unpaid real work product.
- Rubric matches the stated scope, not more.
04

Coach an Interviewer to Check Their Own Bias Before a Debrief

Help an interviewer check their own reasoning for bias before a debrief, distinguishing genuine competency-based signal from affinity or first-impression bias.

You’ll needinterviewer's raw impressionscompetencies being assessedspecific examples from the interviewcandidate background if relevant to the check
Prompt
You are helping an interviewer check their own reasoning before a hiring debrief.

Review the impressions below.

Context:
- Interviewer's raw impressions: [impressions]
- Competencies being assessed: [competencies]
- Specific examples from the interview: [examples]
- Candidate background if relevant: [background]

Instructions:
1. For each impression, ask whether it's backed by a specific example tied to a stated competency, or whether it's a vaguer feeling ("just didn't click," "seemed off") that could be tracking affinity bias rather than actual signal.
2. Flag impressions that might correlate with communication style, background, or demeanor differences rather than the competencies actually being assessed.
3. Note where a first-five-minutes impression may be anchoring the rest of the evaluation, since first impressions bias the interpretation of everything that follows.
4. Help reframe vague impressions into a specific, checkable question to bring to the debrief instead of an unsubstantiated feeling.
5. Keep this as a private self-check, not a public callout — the goal is better decision quality, not making the interviewer feel accused.

Output format:
- Impression-by-impression check (grounded vs possibly biased)
- Flags for possible affinity or anchoring bias
- Reframed questions to bring to debrief

Missing information policy:
Ask up to 2 concise questions only if the impressions or competencies are unclear.

Quality bar:
- Distinguishes grounded signal from vague feeling.
- Flags possible bias without being accusatory.
- Produces concrete debrief-ready questions.