Role, HR

Claude for
people work

Policies, job descriptions, interview guides, sensitive communications, and the places where tone matters as much as content.

HR is one of the places where Claude's help is most valuable and also the place where you have to be most careful about what goes in. The enterprise account protects your data from training, but names, compensation, performance details, personal circumstances, all of that deserves real thought before it becomes a Claude prompt. This page assumes you're going to use judgement on that. The workflows below are the ones where Claude genuinely earns its keep.

Three places to start

Three workflows where Claude does a real share of the drafting without getting in the way of the human judgement that matters most.

1. Refining a job description

Most JDs are written once and then copy-pasted forever. Claude is excellent at tightening them: sharpening the first two sentences so the right candidate wants to read on, cutting generic filler, and trimming the requirements to the three or four that actually matter. Give it the current draft and a JD you were happy with as a voice reference.

JD refinement prompt, annotated

Four elements applied to the "make this JD better" ask.

YouHere is the current draft JD for a Senior Product Analyst role on my team, pasted below. 1 Here is a JD we were happy with last year for a similar role, as a voice reference. The voice is deliberately specific and a bit opinionated, and I want to keep that. 2 Rewrite my draft to match the reference voice. Cut generic filler. Tighten requirements to the three or four that actually matter. Make sure the first two sentences would make the right candidate want to read on. 3 Do not invent benefits or responsibilities that are not in my draft. Preserve any opinionated phrasing rather than softening it to corporate speak. 4
1
Context. The role, the team, the document.
2
Example. Voice reference, plus an explicit note on what makes the voice worth preserving.
3
The ask. Sharpen, cut, hook. No vague "make it better".
4
Escape hatch. "Preserve opinionated phrasing" is the line that stops Claude flattening the personality.

Where this falls over

Claude will tone down anything that sounds edgy or opinionated, which is often the thing that would attract the right person. If your reference JD has personality, tell it explicitly to preserve the voice.

2. Building a structured interview guide

Paste the JD and ask for a 45-minute interview guide: intro, behavioural questions with follow-ups, a small practical task, wrap. For each behavioural question, ask Claude to explain what it's trying to learn. The extra explanation is what lets you tell which questions are actually useful and which are generic.

Interview questions, weak vs useful

Same role, two prompts. The second gives you questions you can actually defend.

Yougive me some interview questions for a senior product analyst
What Claude sends back

"Tell me about yourself." "Describe a challenging project." "What is your greatest weakness?" "Where do you see yourself in five years?" Generic questions that tell you nothing about whether this person can actually do the job.

YouI need an interview guide for a Senior Product Analyst role. The JD is pasted below. The three things I most care about learning in the interview are: - can they work with messy, incomplete data and make a defensible call - can they push back on a product manager who wants a specific answer without sounding combative - can they turn a ten-slide data story into three slides without losing the point Produce a 45-minute guide: intro and rapport (5 min), three behavioural questions with follow-ups (25 min), a small practical task (10 min), wrap (5 min). For each behavioural question, explain in one line what you are trying to learn about the candidate.
What Claude sends back

A 45-minute structured guide. Three behavioural questions, each with a one-line "what this is testing" annotation:

  • Tell me about a time you had to make a call with incomplete data. Testing: can they tolerate ambiguity and still commit to a defensible position.
  • Walk me through a disagreement with a product manager where you were right and they were wrong. Testing: do they push back constructively, or avoid conflict, or get combative.
  • Show me a chart or report you made recently that you would now simplify. Walk me through what you would cut and why. Testing: do they have editorial judgement, or do they treat every finding as equally important.

Plus a 10-minute practical task: a messy CSV of quarterly metrics and a two-sentence brief from a fictional PM asking for "insights". See what they do with it.

Where this falls over

Without the "explain what each question is trying to learn" instruction, the output is generic interview questions you could have got from a template. That instruction is what makes it worth doing.

3. Drafting sensitive employee communications

Layoffs, policy changes, sensitive announcements, difficult emails. These are the messages where tone and content both matter, and Claude is genuinely good at both. Give it the key points, the constraints on what can and cannot be said, and the audience. The output is a first draft, not a final version, but a first draft saves more than half the work.

Drafting a tricky message, as a conversation

Notice that Claude asks the clarifying questions before it writes anything.

YouI need to write a message to the team about a change to our flexible working policy. The new policy is slightly more restrictive than the old one. I don't want to sugarcoat it but I also don't want to lead with the bad news in a way that makes everyone panic.
ClaudeBefore I draft anything, four questions so I get the tone right. (1) What is the actual change, specifically? (2) Who decided this, and what would the team see as the reason if they heard it from someone else first? (3) What is the timeline, is this effective immediately or is there a transition period? (4) What is staying the same that people might fear is also changing?
YouChange: mandatory in-office on Tuesdays and Thursdays from next month, was previously flexible. Decision: leadership team, wanting better collaboration on the core delivery days. Timeline: four weeks' notice. Unchanged: work-from-home on the other three days, including the fully-remote option for anyone with a formal arrangement.
ClaudeThanks. Here is a two-paragraph draft. It leads with "here is what is changing, here is why, here is what is staying the same". The "why" is in paragraph one, not buried at the bottom, because you asked me to be honest about it. I have kept the existing formal arrangement language as a clear "this does not affect you" line so people with those arrangements see it immediately. Tell me if the tone is right before I tighten anything.

Where this falls over

Claude's default is warm but slightly bland. The fix is to give it explicit instructions on tone ("warm but clear, no corporate hedging, no false cheer") and to push back on anything that sounds like canned corporate language.

Worked examples

Before and after, on tasks from HR work.

Prompts to steal

Copy any of these, fill in the square brackets, run.

Try this week

Pick one. All of these are under an hour.

The boundary for HR is sharper than for most roles: no personal data, no performance specifics, no compensation numbers tied to named people. Everything above that line is fair game, and the upside is significant.

If you want to go broader, the Beginner guide covers the habits that apply everywhere. The prompt library has the full set of role-tagged prompts in one place.