View training options →

Short answer: Yes — Claude writes UK job descriptions well. Give it the role title, 5-10 bullet points on what the person will do, and the company context, and it produces a job description in minutes. It handles UK conventions properly: inclusive language (Equality Act 2010-compliant), realistic requirements vs nice-to-haves, and a clear structure that candidates can scan.

Short version: Claude is one of the fastest ways to produce a good UK job description. The output is cleanly structured, uses inclusive language by default, and separates must-haves from nice-to-haves — a basic requirement that surprisingly few human-written JDs get right.

This guide covers the right prompt, three JD types, and the Equality Act 2010 pitfalls Claude handles automatically.

The base prompt

Prompt: "Write a UK job description for a [role title] at [company name/type]. The person will: [5-10 bullet points covering key responsibilities]. Must-have requirements: [list — be realistic, not aspirational]. Nice-to-haves: [list]. Reports to: [role]. Team size: [number]. Location: [in office / hybrid / remote]. Salary range: [range]. The company is [one-sentence description]. Tone: professional but human. Inclusive language throughout. UK English. Structure the JD with: role overview, what you'll do, who you are (must-haves + nice-to-haves), benefits, how to apply."

Three job description situations

1. The role you’ve hired before

You've written this JD a dozen times. Save the base prompt as a template in Claude Projects. Each time you hire again, just update the specifics. Takes 5 minutes vs re-writing from scratch.

2. The role you’ve never hired before

Different approach — let Claude help you figure out what the role should look like:

Prompt: "I'm hiring a [role] for the first time. The business is [description]. I need the role to deliver [outcomes]. Help me think through: what are the realistic must-haves vs nice-to-haves for this role at this stage? What salary range is market-rate in the UK for this role? What should I prioritise in the JD to attract the right candidates vs the wrong ones? Then draft the JD."

3. Rewriting an inherited JD that isn’t working

Prompt: "Here's a job description we're currently using: [paste]. We're not getting the right candidates — specifically, [problem — e.g. 'too senior', 'wrong background', 'not diverse enough']. Rewrite the JD to fix this. Flag anything in the original that might be putting candidates off (unnecessary degree requirements, aspirational must-haves that should be nice-to-haves, non-inclusive language)."

What Claude handles automatically that humans often miss

Inclusive language (Equality Act 2010)

Claude defaults to language that avoids discriminating by:

If you want extra assurance, add: "Review the JD for any language that might inadvertently discriminate under the Equality Act 2010 and flag it."

Realistic must-haves

Most human-written JDs are stuffed with 15 must-haves and 3 nice-to-haves. Claude's default is to flip this: 3-5 genuine must-haves, longer nice-to-haves list. This widens your candidate pool without lowering standards.

Scannable structure

Candidates spend ~30 seconds deciding whether to apply. Claude structures JDs to be scannable — bullet points, clear section headers, benefits visible without scrolling.

What to double-check

Related