Recruiting in 2026 means your ATS is full, your inbox has 300 applications for a mid-level role, and your hiring managers are sending you bullet points at 4pm asking for a job description by end of day. You're writing the same outreach message for the twelfth time this week, slightly adjusting names and companies, and somehow you're also supposed to give a rejected candidate a warm, personalized note so they don't leave a Glassdoor review. The writing load alone is a second job.
That's the daily reality for in-house recruiters, talent acquisition managers, agency recruiters, and HR business partners who carry a req load. Claude doesn't change what recruiting requires — judgment, relationships, pattern recognition built over years. What it changes is the time tax: the hours spent writing JDs from scratch, drafting outreach messages that still sound templated, and turning interview notes into structured guides that never get finished before the next phone screen. Claude AI for recruiters handles the writing so you can focus on the conversations.
This post covers six use cases with copy-paste-ready prompts. Use them today — no setup required.
1. Job Description Writing
A hiring manager sends you six bullet points at 3pm. You need a polished JD posted by tomorrow. That gap — between rough notes and a complete job description with a compelling overview, clear responsibilities, and a "why join us" section that actually makes the role sound worth applying for — takes an hour or more to close properly.
Claude closes it in minutes. Paste the hiring manager's notes, give Claude context on your company and the level of the role, and it returns a complete, structured JD you edit and post. You stop spending your writing time on structure and start spending it on accuracy.
For a broader set of prompts that apply across professional writing, see Claude AI prompts that will change how you work.
Write a job description for a [role title] at [company type/size]. Use these notes from the hiring manager as the raw material: [paste notes].
Structure: (1) Role Overview — 2 sentences on what this person owns and why the role exists now; (2) Responsibilities — 6–8 bullet points, starting with the most important; (3) Requirements — must-haves only, no inflated wish lists; (4) Why Join Us — 3–4 sentences specific to this team and company, not generic "great culture" language.
Tone: direct and specific — this should attract someone who actually fits the role. Don't start bullet points with "You will" — use active verbs.
2. Candidate Outreach Messages
Generic sourcing messages get ignored. Candidates on LinkedIn receive dozens of InMails a week that all follow the same formula: "Hi [Name], I came across your profile and I'm impressed by your background in X. I have a great opportunity at Y…" They know it's a template. You know it's a template. The response rates reflect that.
Claude writes outreach that doesn't sound templated — because it isn't. Give it the candidate's actual profile details and a specific description of the role, and it generates a first message that references something real. That specificity is what gets replies.
For more on how Claude handles professional correspondence with precision, see Claude AI for executive assistants.
Write a personalized sourcing message for a candidate I want to reach out to on LinkedIn. Keep it under 100 words. Reference something specific from their background and connect it to why this role is worth a conversation.
Candidate profile: [paste key details — current title, company, notable experience or skills]
Role: [job title] at [company]. Key draw: [2–3 specific things that make this role worth the candidate's time — not generic perks]
Tone: direct and human — this should sound like a recruiter who actually read their profile, not a mass outreach tool.
3. Screening Question Generation
Your standard screening call covers the same questions for every role. For some positions, those questions surface exactly what you need. For others, they miss the real signal entirely — and you end up moving candidates forward who fall apart later in the process.
Claude generates role-specific screening questions from a JD, calibrated to surface the skills that actually matter and the red flags you need to catch early. The output is a working list you refine with the hiring manager — not a blank page.
Generate 8 phone screening questions for a [role title] candidate. Use the following job description as the source: [paste JD].
For each question: include the question itself and a 1-sentence note on what a strong answer typically looks like versus a red flag answer. Focus on: [2–3 specific skills or experiences most critical for this role]. Avoid questions that are answered by the résumé — these should surface what the résumé can't show.
4. Interview Prep Briefs
Pre-interview prep is often rushed. You have a candidate's résumé, a job description, and three minutes before the hiring manager joins the call. A proper interview prep brief — one that identifies focus areas, maps résumé gaps to the requirements, and suggests specific questions — usually lives in someone's head rather than on paper.
Claude builds that brief from the résumé and JD in one pass. Give it both documents and a note on the role level; it returns a structured guide the hiring manager can actually use.
For more on how Claude supports people operations workflows, see Claude AI for HR and people operations.
Create an interview prep brief for a hiring manager. The candidate is interviewing for [role title].
Resume: [paste resume]
Job Description: [paste JD]
Produce: (1) a 3-bullet summary of the candidate's strongest qualifications for this role; (2) 2–3 areas to probe — gaps between the JD requirements and what the résumé shows; (3) 5 structured interview questions tailored to this specific candidate and role, not generic questions; (4) one red flag or open question to watch for during the conversation.
5. Rejection Emails
A rejection email is employer brand work. Most candidates who apply for a role will be rejected. How you write that email — whether it's a two-sentence form letter or a warm, specific note — is what they'll remember about your company. A good rejection takes two minutes to write and protects your brand with everyone who doesn't get the job.
Claude writes rejection emails that are warm, professional, and specific enough to feel real — without the time a fully personalized note would require. Give it the role and the rejection reason; it returns a note that leaves a good impression.
Write a rejection email for a candidate who applied for [role title]. Rejection reason: [brief note — e.g., strong candidate but another finalist was a closer fit; role is on hold; missing a specific requirement].
Tone: warm and professional — not cold or form-letter. Acknowledge their time and application. Do not give false hope or invite them to "keep in touch" if we don't mean it. Under 100 words. Sign off from [recruiter name / talent team].
6. Offer Letter Drafts
Offer letters are repetitive to write and costly to get wrong. The structure is always the same — role, compensation, start date, reporting line, conditions of employment — but every draft starts from scratch because no one has a clean template that matches the current terms. Claude generates a complete, professional first draft from key offer details in seconds.
For more on how Claude handles formal business writing, see Claude AI for startup founders.
Write an offer letter for [candidate name] for the role of [job title] at [company name]. Use the following offer terms:
- Compensation: [base salary] per year, paid [bi-weekly / semi-monthly]
- Start date: [date]
- Reports to: [manager name and title]
- Employment type: [full-time / part-time / contract]
- Location: [remote / on-site / hybrid — city, state]
- Benefits: [brief summary — e.g., health/dental/vision, 401k, X days PTO]
- Offer expiration: [date]
Format: professional letter with standard offer language. Include an acceptance signature block. Tone: warm and clear — this is a milestone for the candidate, not a bureaucratic form.
Why Claude Over ChatGPT for Recruiting Work
Both tools can write a job description. For the specific demands of recruiting work, Claude is the more practical choice for five reasons.
Long context window. Claude's context window lets you paste a full résumé, a complete job description, and the hiring manager's briefing notes all in one prompt — and get coherent output based on all of it. For interview prep briefs and candidate analysis, this matters. ChatGPT's shorter effective context means you're often splitting documents or summarizing before you get to the output.
No moralizing on recruiting prompts. ChatGPT sometimes flags recruiting-related prompts — candidate screening questions, sourcing outreach, requirements language — with disclaimers about potential bias or suggestions to consult legal counsel. Claude processes the request and returns the output. You're a professional; you don't need an AI that second-guesses whether you should be writing a job description.
Tone calibration that holds. Offer letters are formal and legally-adjacent. Sourcing messages are casual and direct. Rejection emails thread the line between warm and final. Claude adjusts across all three registers in the same session, following specific tone instructions reliably. ChatGPT tends to drift toward a default corporate register regardless of what you ask for.
Projects feature for recruiting context. Claude's Projects feature lets you set up a recruiting Project once — your company voice, EVP, standard benefits language, and a sample JD as reference — and every output will be on-brand without starting from scratch. No more adding the same company boilerplate to every prompt.
Structured output by default. Interview prep guides, screening question lists, JD sections — Claude produces structured, formatted output you can hand directly to a hiring manager or paste into your ATS without reformatting. You're not cleaning up unformatted AI text for twenty minutes before it's usable.
4 Practical Tips for Recruiters Using Claude
Set up a Claude Project with your EVP, benefits language, and a sample JD. This is the highest-leverage setup step. Spend twenty minutes loading your company's employer value proposition, standard benefits copy, tone preferences, and one polished JD as a reference. Every output you generate from that Project will be on-brand from the first word — no re-briefing required.
Paste the full LinkedIn profile or résumé when generating outreach or interview briefs. More context produces better output. For outreach, copy the candidate's full profile summary and work history. For interview briefs, paste the full résumé. Claude handles long input well, and the specificity of the output improves significantly when it has the full picture.
Use Claude to draft, not finalize. Claude closes the gap from blank page to solid first draft. The review step is yours: check that job requirements are accurate, outreach messages match the candidate's actual background, and offer letters reflect the real terms. The leverage is in the drafting time Claude saves — not in bypassing the final read.
Batch your JD writing. Instead of writing job descriptions one at a time across three days, collect all your open req notes and run them in one Claude session. Drop all the hiring manager bullet points at once and ask Claude to produce all JDs back-to-back. Batching cuts total time and keeps output consistent across roles.
Go Further With The Complete Claude Playbook
The prompts above cover the core recruiting workflows. If you want the full system — 100+ prompts built for professional use across hiring, communications, HR, and operations, with step-by-step guidance on building these workflows from scratch — The Complete Claude Playbook is the fastest path there. It's $27, instant PDF download, and written for practitioners who want Claude as a real part of how they work — not something they try once and leave in a tab.