6 ready-to-use ChatGPT prompts for job descriptions and requisitions. Fill in the bracketed fields, paste into ChatGPT, and go.
HR & Recruiting · 6 prompts
01
Turn Rough Role Notes into a Job Description That Attracts the Right Candidates
Write a job description from rough hiring-manager notes, prioritizing candidate self-selection over inflated requirement lists.
You’ll needrole notes from hiring managerteam and reporting linemust-have vs nice-to-have skillscompensation range if shareablecompany context
Prompt
You are a recruiter turning hiring-manager notes into a job description.
Write the job description using the context below.
Context:
- Role notes from hiring manager: [notes]
- Team and reporting line: [team]
- Must-have vs nice-to-have skills: [skills]
- Compensation range if shareable: [comp]
- Company context: [company]
Instructions:
1. Separate true must-haves from nice-to-haves explicitly — inflated requirement lists ("10+ years for a role that needs 3") are a leading cause of strong candidates self-selecting out, especially from underrepresented groups.
2. Write the responsibilities section around what the person will actually do in the first 6 months, not a generic list of duties copied from a similar posting.
3. Avoid gendered or exclusionary language patterns (aggressive competitive language, unnecessary jargon) that research shows suppresses application rates from some candidate groups.
4. Include compensation range if shareable — postings without a range increasingly get filtered out or distrusted by candidates.
5. End with a clear, low-friction application step.
Output format:
- Role summary
- Must-have vs nice-to-have skills (separated)
- What success looks like in 6 months
- Compensation and benefits note
- Application instructions
Missing information policy:
Ask up to 2 concise questions only if the must-have skills or team context is unclear.
Quality bar:
- Must-haves genuinely minimal, not inflated.
- No exclusionary language patterns.
- Grounded in real first-6-months responsibilities.
02
Build a Business Case for a New Headcount Request
Build a business case for a headcount request that quantifies the cost of the current gap, not just the value of filling it.
You’ll needrole being requestedcurrent gap or pain pointteam contextbudget owner concernsalternatives already tried
Prompt
You are a people ops strategist building a headcount business case.
Build the business case using the context below.
Context:
- Role being requested: [role]
- Current gap or pain point: [gap]
- Team context: [team]
- Budget owner's likely concerns: [concerns]
- Alternatives already tried (contractors, redistribution, tooling): [alternatives]
Instructions:
1. Quantify the cost of the current gap (missed deals, delayed launches, team burnout, attrition risk) since budget owners weigh a concrete cost-of-inaction more than an abstract value-of-hiring pitch.
2. Show what's already been tried to solve this without new headcount, so the request doesn't read as reaching for a hire before exhausting cheaper options.
3. Address the budget owner's likely specific concerns directly rather than a generic pitch.
4. Include a realistic ramp-time estimate before the new hire offsets the cost, not an assumption of immediate impact.
5. Propose the request at the right scope — full-time vs contract vs fractional — matched to the actual gap, not defaulted to full-time.
Output format:
- Cost of the current gap (quantified)
- What's already been tried
- Proposed role and scope
- Ramp-time and expected offset timeline
- Response to likely budget owner concerns
Missing information policy:
Ask up to 2 concise questions only if the gap or budget owner concerns are unclear.
Quality bar:
- Cost of inaction quantified, not just value of hiring.
- Shows what was tried before requesting a hire.
- Realistic ramp-time included.
03
Design a Role Leveling Framework for a Job Family
Build a leveling framework for a job family with concrete, distinguishing criteria between levels so leveling decisions are consistent and defensible.
You’ll needjob familynumber of levels neededexisting role examples at each rough levelcompany stagecomparable framework if any
Prompt
You are a compensation and leveling strategist.
Design a leveling framework using the context below.
Context:
- Job family: [job family]
- Number of levels needed: [levels]
- Existing role examples at each rough level: [examples]
- Company stage: [stage]
- Comparable framework if any exists: [comparable]
Instructions:
1. Write each level's criteria in terms of scope, complexity, and impact — concrete enough that two different managers would place the same person at the same level.
2. Avoid vague qualifiers ("strong," "advanced," "expert") without a concrete behavioral anchor attached.
3. Make the distinction between adjacent levels explicit and non-overlapping, since overlapping level descriptions are the most common source of leveling disputes.
4. Note where scope-based criteria (what someone owns) should outweigh tenure-based criteria (years of experience), since tenure alone is a weak signal of level.
5. Keep the number of levels realistic for the company stage — too many levels at an early-stage company creates unnecessary bureaucracy.
Output format:
- Level-by-level criteria (scope, complexity, impact)
- Adjacent-level distinctions made explicit
- Behavioral anchors per level
- Scope-vs-tenure guidance
Missing information policy:
Ask up to 2 concise questions only if the job family or number of levels is unclear.
Quality bar:
- Concrete, non-overlapping level criteria.
- Behavioral anchors, not vague qualifiers.
- Scope weighted over tenure.
04
Build an Interview Question Bank Mapped to Specific Competencies
Build an interview question bank where each question is explicitly mapped to a competency the role requires, with follow-up probes for shallow answers.
You’ll needrolekey competencies to assessinterview stageinterview lengthlevel
Prompt
You are a recruiter designing structured interview questions.
Build an interview question bank using the context below.
Context:
- Role: [role]
- Key competencies to assess: [competencies]
- Interview stage (screen, panel, final): [stage]
- Interview length: [length]
- Level: [level]
Instructions:
1. Map every question explicitly to one of the stated competencies, so the interviewer knows what a strong versus weak answer signals for that specific competency, not just generally.
2. Write a follow-up probe for each question to use when the candidate gives a shallow or rehearsed-sounding answer, since a single question rarely surfaces real signal on its own.
3. Avoid questions that are easy to prep a generic answer for ("tell me about a time you showed leadership") in favor of ones that require specific, checkable detail.
4. Note which questions are appropriate for which interview stage, since a deep technical probe doesn't belong in an initial screen.
5. Keep the total question count realistic for the stated interview length.
Output format:
- Questions grouped by competency
- Follow-up probe per question
- Stage placement guidance
- Time-realistic question count
Missing information policy:
Ask up to 2 concise questions only if the role or competencies are unclear.
Quality bar:
- Every question mapped to a specific competency.
- Includes follow-up probes, not just top-level questions.
- Resistant to rehearsed generic answers.
05
Audit a Job Description for Language That Suppresses Applications
Review a draft job description for language patterns known to suppress applications from qualified candidates, and recommend specific rewrites.
You’ll needdraft job descriptionroletarget candidate poolknown past issues if any
Prompt
You are a recruiter auditing a job posting for inclusive language.
Audit the draft below.
Context:
- Draft job description: [draft]
- Role: [role]
- Target candidate pool: [pool]
- Known past issues if any: [past issues]
Instructions:
1. Flag gendered or coded language patterns (research-documented terms like "ninja," "rockstar," excessive competitive framing) that measurably suppress application rates from some candidate groups.
2. Flag inflated requirement counts (years of experience, degree requirements) that filter out qualified candidates who don't meet every line item, even when the role doesn't strictly need them.
3. Check for unnecessary jargon or internal acronyms that a strong external candidate wouldn't recognize.
4. Distinguish requirements that are genuinely necessary from ones that are aspirational, and recommend moving the latter to a nice-to-have section.
5. Provide specific rewritten language for each flagged issue, not just a list of problems.
Output format:
- Flagged language issues (with reasoning)
- Inflated requirement flags
- Specific rewrite suggestions
- Clean revised version
Missing information policy:
Ask up to 2 concise questions only if the draft or role is unclear.
Quality bar:
- Flags grounded in known suppression patterns, not personal opinion.
- Provides specific rewrites, not just criticism.
- Distinguishes necessary from aspirational requirements.
06
Prioritize Open Requisitions When Recruiting Capacity Is Limited
Build a prioritization approach for open requisitions when recruiting capacity can't cover every role at full speed, so limited effort goes to the roles that matter most.
You’ll needlist of open rolesrecruiting capacitybusiness urgency per rolehiring manager pressure signalsconstraints
Prompt
You are a recruiting operations strategist.
Prioritize open requisitions using the context below.
Context:
- List of open roles: [roles]
- Recruiting capacity available: [capacity]
- Business urgency per role: [urgency]
- Hiring manager pressure signals: [pressure]
- Constraints: [constraints]
Instructions:
1. Rank roles by actual business urgency and cost of vacancy, not by which hiring manager is applying the most pressure — the two aren't always the same thing.
2. Flag roles where a search is likely to be slow (niche skill set, narrow location requirement) so expectations are set early rather than discovered after weeks of low pipeline.
3. Recommend which lower-priority roles should be paused or run at reduced effort rather than spreading capacity thin across everything at once.
4. Note where combining or sequencing searches (similar profile, same team) could save recruiting effort.
5. Set a review cadence to re-prioritize as business needs shift.
Output format:
- Priority ranking with reasoning
- Slow-search risk flags
- Roles to pause or deprioritize
- Sequencing opportunities
- Review cadence
Missing information policy:
Ask up to 2 concise questions only if the role list or urgency signals are unclear.
Quality bar:
- Ranked by real urgency, not just pressure volume.
- Flags likely-slow searches early.
- Includes an explicit review cadence.