Prompt Engineering for HR and Recruiting: 10 Templates That Save Hours

Recruiters spend hours writing job descriptions, screening resumes, drafting outreach emails, and preparing interview questions. AI can do most of this in minutes — if you give it the right instructions.

The problem? Most HR professionals type something like "write a job description for a software engineer" and get back a generic, bland posting that sounds like every other one on LinkedIn. The fix isn't a better AI model — it's a better prompt.

This guide gives you 10 structured templates for the tasks HR teams do every day — from job descriptions to performance reviews. Each template produces output you can use immediately, not just a starting point you have to rewrite.

Why HR Prompts Need More Structure

HR content is high-stakes. A poorly worded job description attracts the wrong candidates. A bad rejection email damages your employer brand. An incomplete interview question set misses critical skills.

Vague prompt:

Write a job description for a product manager.

Result: A generic JD with every cliché in the book. "Fast-paced environment." "Wear many hats." "Rockstar candidate." Nobody applies because it looks like every other posting.

Structured prompt:

Write a job description for a Senior Product Manager at a B2B SaaS company
(50 employees, Series B, project management tool).

Include:
- Role summary (3 sentences max — what makes this role unique)
- Key responsibilities (6-8 bullet points, specific to our product stage)
- Requirements: must-have vs nice-to-have (separate clearly)
- What we offer (beyond generic benefits — what's genuinely different)
- Salary range: $150K-$180K base + equity

Tone: professional but human. Avoid corporate jargon and buzzwords.
Use inclusive language (no "rockstar", "ninja", "guru").
Optimize for job board SEO: include the title "Senior Product Manager"
in the first 2 sentences.

Result: A specific, compelling JD that attracts qualified candidates and ranks well on job boards.

The Templates

1. Job Description Writing

The most common HR writing task. Good JDs attract better candidates and rank higher on job boards.

Template:

Write a job description for [job title] at [company type/size/stage].

Company context:
- Industry: [industry]
- Size: [employee count]
- Stage: [startup/growth/enterprise]
- Product: [what we build, in one sentence]
- Culture: [2-3 words describing work culture]

Role details:
- Reports to: [title]
- Team size: [direct reports or team members]
- Location: [remote/hybrid/onsite, city if relevant]
- Salary range: [range, or "competitive" if not disclosing]

Structure:
1. **Opening hook** (2-3 sentences — what's exciting about this role specifically)
2. **What you'll do** (6-8 specific responsibilities, ordered by importance)
3. **What you bring** (split into Required and Nice-to-Have)
4. **What we offer** (specific benefits, not generic lists)
5. **How to apply** (clear next step)

Requirements:
- Use inclusive language (avoid gendered terms, "rockstar", "ninja")
- Avoid corporate jargon ("synergy", "leverage", "fast-paced environment")
- Include the job title naturally in the first 2 sentences (SEO)
- Keep under 600 words (longer JDs get fewer applications)
- Each responsibility should start with an action verb

Why it works: The structure forces specificity. "Manage product roadmap for our enterprise collaboration features" is infinitely more compelling than "Own the product roadmap."

2. Resume Screening Criteria

Stop reading every resume line by line. Create a scoring rubric first.

Template:

Create a resume screening rubric for [job title].

Job requirements (from our JD):
- Required: [list must-have qualifications]
- Nice-to-have: [list preferred qualifications]

Create a scoring matrix with:

1. **Knockout criteria** (auto-reject if missing):
   - [e.g., minimum years of experience]
   - [e.g., required certifications or skills]

2. **Scoring categories** (rate 1-5 each):
   - Relevant experience (weight: [high/medium/low])
   - Technical skills match (weight: [high/medium/low])
   - Industry experience (weight: [high/medium/low])
   - Education/certifications (weight: [high/medium/low])
   - Career progression (weight: [high/medium/low])

3. **Green flags** (bonus points):
   - [specific achievements or experiences that indicate strong fit]

4. **Yellow flags** (investigate further):
   - [patterns that might indicate issues but aren't dealbreakers]

5. **Threshold**: Advance candidates scoring [X] or above out of [total]

Make the rubric objective and consistent — two screeners should reach
the same conclusion on the same resume.

Why it works: A rubric eliminates inconsistency between screeners and reduces unconscious bias. It also speeds up screening by 60-70%.

3. Interview Question Generation

Structured interviews are 2x more predictive than unstructured ones. Build the structure upfront.

Template:

Generate interview questions for [job title] role.

Competencies to assess:
1. [Technical skill or domain knowledge]
2. [Behavioral competency, e.g., leadership, collaboration]
3. [Problem-solving or analytical thinking]
4. [Culture fit / values alignment]
5. [Role-specific competency]

For each competency, provide:
- **Behavioral question** (STAR format: "Tell me about a time when...")
- **Situational question** ("How would you handle...")
- **Follow-up probes** (2-3 follow-ups to dig deeper)
- **What good looks like** (key elements of a strong answer)
- **Red flags** (answers that indicate poor fit)

Interview format:
- Duration: [30/45/60 minutes]
- Stage: [phone screen / technical / hiring manager / final]
- Interviewer: [role of the person asking]

Additional requirements:
- Include at least one question that reveals how the candidate handles
  [specific challenge relevant to your team]
- Avoid illegal or inappropriate questions (age, family status, religion, etc.)
- End with a compelling "sell" question that lets us pitch the role

Why it works: Pre-built question sets with evaluation criteria make interviews consistent across candidates and interviewers. The "what good looks like" section aligns the team on what you're actually looking for. Adding a few example answers to the prompt produces even better evaluation rubrics.

4. Candidate Outreach Personalization

Cold outreach that sounds personal gets 3x higher response rates.

Template:

Write a personalized recruiting outreach message for a passive candidate.

Candidate info:
- Name: [name]
- Current role: [title at company]
- Notable experience: [specific achievement, project, or skill from their profile]
- Connection point: [mutual connection, shared background, or relevant interest]

Our opportunity:
- Role: [job title]
- Company: [name, one sentence about what we do]
- Why this role is compelling: [specific reason this person would be interested]
- Unique selling point: [one thing that sets us apart — compensation, mission,
  technology, growth opportunity]

Message requirements:
- Platform: [LinkedIn InMail / email / other]
- Length: [under 150 words for LinkedIn, under 200 for email]
- Tone: [casual professional / formal / enthusiastic]
- Open with something specific about THEM (not about us)
- Mention their [specific achievement] to show you did your research
- End with a low-pressure CTA ("Would you be open to a quick chat?" not
  "Apply now!")
- Do NOT use: "exciting opportunity", "perfect fit", "I came across your profile"

Why it works: Generic "I came across your profile and was impressed" messages get ignored. Referencing a specific project or achievement shows genuine interest and dramatically increases response rates.

5. Rejection Email Drafting

Rejections are your employer brand in action. Bad rejections burn bridges; good ones build them.

Template:

Write a rejection email for a candidate who [stage reached].

Context:
- Candidate name: [name]
- Role applied for: [title]
- Stage reached: [application / phone screen / interview / final round]
- Reason for rejection: [skills gap / experience level / culture fit / stronger candidate]
- Anything positive: [genuine strength or positive impression, if any]
- Future potential: [would we consider them for other roles? yes/no]

Email requirements:
- Thank them specifically for [what they invested — time, project, presentation]
- Be honest but kind — don't give false hope, but don't be cold
- If applicable, provide ONE piece of constructive feedback they can act on
- If we'd consider them for future roles, say so specifically
- If not, wish them well without implying future contact
- Keep under 150 words (respect their time)
- Subject line should not be misleading ("Update on your application at [Company]")

Tone: warm, professional, human. This person spent hours of their life
on our process — acknowledge that.

Why it works: Most rejection emails are either coldly automated or awkwardly vague. This template produces emails that leave candidates with a positive impression — many will refer other candidates or reapply later.

6. Offer Letter Drafting

Offer letters need to be legally accurate and compelling. Get the structure right.

Template:

Draft an offer letter for [candidate name] for the [job title] position.

Offer details:
- Start date: [date]
- Salary: $[amount] [annually/hourly]
- Bonus: [structure, if applicable]
- Equity: [shares/options, vesting schedule, if applicable]
- Benefits: [health, 401k match, PTO days, other specifics]
- Sign-on bonus: [amount, if applicable]
- Reporting to: [manager name and title]
- Location: [office/remote/hybrid, details]

Terms:
- Employment type: [full-time/part-time/contract]
- At-will: [yes/no, if applicable in jurisdiction]
- Contingencies: [background check, references, etc.]
- Response deadline: [date — give them reasonable time]

Tone: excited and welcoming — this is a celebration, not a legal filing.
Include a brief personal note about why we're excited to have them join.

Note: This is a DRAFT. Advise that it should be reviewed by legal/HR
before sending. Flag any sections that may need jurisdiction-specific
legal language.

Why it works: Offer letters that feel celebratory (not just contractual) increase acceptance rates. The template balances warmth with the legal details candidates need.

7. Onboarding Checklist Creation

Good onboarding reduces early turnover by 50%. Bad onboarding is the top reason new hires leave in the first 90 days.

Template:

Create an onboarding checklist for a new [job title] starting [date].

Company context:
- Company size: [employees]
- Work setup: [remote/hybrid/onsite]
- Team they're joining: [team name, team size]
- Manager: [name]
- Buddy/mentor: [name, if applicable]

Create a checklist organized by timeline:

**Before Day 1** (HR/IT prep):
- Equipment, accounts, access needed
- Welcome package or materials to send
- Team notifications and introductions to schedule

**Day 1**:
- Welcome activities
- Essential setup tasks
- Key meetings (manager 1:1, team intro, HR orientation)
- End-of-day check-in

**Week 1**:
- Systems and tools training
- Key stakeholder introductions
- First tasks or projects to start
- Daily check-ins schedule

**Days 8-30**:
- Deeper training and ramp-up milestones
- First deliverable or contribution target
- Feedback checkpoints (2-week check-in)

**Days 31-90**:
- Independent work expectations
- 30-day review meeting
- 60-day review meeting
- 90-day milestone goals

For each item, specify: task, owner (HR/manager/IT/buddy), and due date.

Role-specific requirements:
[List any tools, certifications, or domain knowledge they need to learn]

Why it works: Onboarding fails when it's ad-hoc. A structured checklist with owners and deadlines ensures nothing falls through the cracks — especially critical for remote hires.

8. Performance Review Drafting

Help managers write reviews that are useful, not just annual paperwork.

Template:

Help me draft a performance review for [employee name], [job title].

Review period: [date range]
Review type: [annual / semi-annual / quarterly / probation end]

Performance data:
- Key achievements this period:
  1. [Achievement with specific outcome/metric if possible]
  2. [Achievement]
  3. [Achievement]

- Areas where they met expectations:
  [List responsibilities they handled well]

- Areas for improvement:
  1. [Specific behavior or skill gap — not personality]
  2. [Specific area]

- Goals from last review:
  [List previous goals and whether they were met/partially met/not met]

Overall rating: [Exceeds / Meets / Below expectations]

Write the review with:
1. **Summary** (2-3 sentences — overall performance narrative)
2. **Strengths** (specific examples, not vague praise)
3. **Achievements** (tied to business impact where possible)
4. **Development areas** (constructive, specific, actionable)
5. **Goals for next period** (3-5 SMART goals)
6. **Career development** (growth trajectory, skills to develop, potential next role)

Tone: honest, specific, growth-oriented. Every piece of feedback should be
backed by an example. Avoid: "good team player" (vague), "needs to improve
communication" (not actionable). Instead: specific situations with specific
behaviors.

Why it works: Managers hate writing reviews because they're hard to make specific and actionable. The template forces concrete examples and SMART goals, which makes the review actually useful for the employee.

9. Employee Feedback Summarization

Turn survey responses and feedback into actionable themes.

Template:

Summarize the following employee feedback into actionable themes.

Feedback source: [engagement survey / exit interviews / 360 reviews /
pulse survey / skip-level meetings]
Number of responses: [N]
Department/team: [scope]

Raw feedback:
[Paste all feedback responses — anonymous is fine]

Analysis structure:
1. **Top themes** (ranked by frequency):
   - Theme name
   - Number of mentions (approximate)
   - Representative quotes (2-3 per theme)
   - Sentiment: positive / negative / mixed

2. **Quick wins** — Issues that could be addressed within 30 days:
   - What to change
   - Expected impact
   - Owner suggestion

3. **Strategic issues** — Deeper problems requiring longer-term action:
   - Root cause analysis
   - Recommended approach
   - Timeline

4. **Positive reinforcement** — What's working well that we should
   keep doing or expand

5. **Contradictions** — Where feedback conflicts (some love X,
   others hate X) and what to do about it

Important: Maintain employee anonymity. Do not include details that
could identify specific respondents. If a quote is too specific to
be anonymous, paraphrase it.

Why it works: Raw feedback is overwhelming. This template produces a structured report that HR and leadership can act on immediately.

10. Policy Document Writing

Internal policies need to be clear, comprehensive, and readable. Most are none of these.

Template:

Write an internal policy document for [policy topic].

Company context:
- Company size: [employees]
- Industry: [industry]
- Locations: [countries/states, for compliance context]
- Work model: [remote/hybrid/onsite]

Policy document structure:
1. **Purpose** — Why this policy exists (2-3 sentences)
2. **Scope** — Who this applies to (all employees, specific departments, etc.)
3. **Policy statement** — The actual rules, clearly numbered
4. **Definitions** — Key terms defined (avoid ambiguity)
5. **Procedures** — Step-by-step process for compliance
6. **Exceptions** — How to request an exception and who approves
7. **Consequences** — What happens if the policy is violated
8. **FAQs** — 5-8 common questions employees would ask
9. **Contact** — Who to reach out to with questions
10. **Effective date and review schedule**

Requirements:
- Write at a 10th-grade reading level (clear, not legalistic)
- Use numbered sections for easy reference
- Include specific examples where rules might be ambiguous
- Flag any areas where local laws may require customization
  (mark as [LEGAL REVIEW NEEDED])
- Keep under [1000/2000] words

Note: This is a draft. Recommend legal review before publication,
especially for policies touching employment law, data privacy,
or workplace safety.

Why it works: Most internal policies are either too vague to enforce or too legalistic to read. The template balances clarity with completeness and flags areas needing legal review.

Tips for Better HR Prompts

Include Your Company Context

HR content is meaningless without context. "Write a job description" produces generic output. "Write a job description for a Series B fintech startup with 50 employees" produces relevant output.

Always include:

• Company size and stage
• Industry
• Work model (remote/hybrid/onsite)
• Team structure

Specify Inclusive Language

Modern HR content needs to be inclusive by default. Add this to any template:

Use inclusive language throughout:
- Avoid gendered pronouns (use "they" or "you")
- No ability-biased language ("must be able to stand for 8 hours"
  unless genuinely required)
- No age-biased language ("digital native", "5+ years experience"
  when 3 would suffice)
- No cultural assumptions

Always Flag Legal Review

AI doesn't know your jurisdiction's employment laws. Add to any legally sensitive document:

Flag any statements that may have legal implications in [jurisdiction].
Mark these as [LEGAL REVIEW NEEDED]. Do not provide legal advice —
provide a draft that a legal team can refine.

Keep Tone Human

HR communication shapes how employees and candidates feel about your company:

Tone: professional but warm. Write like a thoughtful colleague,
not a corporate handbook. Every communication represents our brand.

How Promplify Helps HR Teams

Writing structured prompts for every JD, interview guide, and policy document is effective but time-consuming. Promplify optimizes your HR prompts automatically:

• Adds missing context using techniques like the STOKE framework to produce role-specific, not generic content
• Structures output so the model covers all required sections consistently
• Flags quality issues in your prompt that would lead to vague or incomplete output
• Works across models — optimize once, use with ChatGPT, Claude, or Gemini

Paste your rough HR request into the optimizer and get back a prompt that produces professional, inclusive, ready-to-use output.

Key Takeaways

• Generic HR prompts produce generic content that hurts your employer brand
• Always include company context: size, stage, industry, work model
• Specify inclusive language requirements explicitly
• Flag legally sensitive content for human review — AI doesn't know employment law
• Template-based prompts are reusable — build a library your HR team shares
• The highest-impact templates are JDs, interview questions, and onboarding checklists

---

HR teams don't have time to engineer prompts all day. Try Promplify free — paste your rough request and get back a structured prompt that produces professional, inclusive HR content on the first try.