Recruiter / HR skill · inclusive-job-description
Inclusive job description
What it does
Writes or rewrites a job description that is clear, skills-based and inclusive: real must-haves separated from nice-to-haves, plain language, no coded or exclusionary wording, and a flag list of phrases changed. Use it whenever you open or refresh a role.
- Time saved
- ~30–45 min per role (estimate)
- Difficulty
- Beginner
- Version
- v1 · 2026-10-01
What you give it
- Role notes or the current JD — e.g. Rockstar backend dev, 10+ yrs, must be a digital native, work hard play hard culture, Java/Spring, AWS.
- About the team/company (what you may say) (optional) — e.g. Team of 8 building order-management software; hybrid, 2 office days.
- Benefits and salary range (if published) (optional) — e.g.
How it works
- Separate true must-haves (needed on day one) from nice-to-haves; challenge years-of-experience requirements and suggest skills instead.
- Replace jargon and coded words ("rockstar", "digital native", "young", "aggressive") with neutral, specific language — see references/inclusive-language.md.
- Describe outcomes and tasks, not personality stereotypes.
- Include salary and benefits only if provided; never invent them.
- Add an encouraging line for candidates who don't meet every nice-to-have.
- List every phrase you changed and why.
Output
Title · About the role · What you'll do (5–7 bullets) · Must-haves (≤ 6) · Nice-to-haves · How we work · Benefits (only provided) · How to apply · Changes made (table: original phrase · issue · replacement).
Quality checklist
- ☑ Must-haves are truly required
- ☑ No coded or age-related wording
- ☑ No invented benefits or pay
Human check: Have the hiring manager and HR confirm requirements and check the JD against local employment and pay-transparency rules.
Example (fictional)
- Role notes or the current JD: Rockstar backend dev, 10+ yrs, must be a digital native, work hard play hard culture, Java/Spring, AWS.
- About the team/company (what you may say): Team of 8 building order-management software; hybrid, 2 office days.
Title: Backend Engineer (Java) Must-haves: building and running Java/Spring services in production; working with AWS services. Changes made
| Original | Issue | Replacement |
|---|---|---|
| rockstar | vague, can read as exclusionary | Backend Engineer |
| 10+ yrs | years ≠ skills | skills listed instead |
| digital native | can imply age | (removed) |
▶ Try it
Guests get 3 runs a day — sign in for more.Don't paste confidential or personal data.
Take it with you
Paste into any chat assistant and replace the {{placeholders}} with your details.
You are helping me with this task: Inclusive job description.
## Instructions
1. Separate true must-haves (needed on day one) from nice-to-haves; challenge years-of-experience requirements and suggest skills instead.
2. Replace jargon and coded words ("rockstar", "digital native", "young", "aggressive") with neutral, specific language — see references/inclusive-language.md.
3. Describe outcomes and tasks, not personality stereotypes.
4. Include salary and benefits only if provided; never invent them.
5. Add an encouraging line for candidates who don't meet every nice-to-have.
6. List every phrase you changed and why.
## Output format
**Title** · **About the role** · **What you'll do** (5–7 bullets) · **Must-haves** (≤ 6) · **Nice-to-haves** · **How we work** · **Benefits** (only provided) · **How to apply** · **Changes made** (table: original phrase · issue · replacement).
## Before you answer, check
- Must-haves are truly required
- No coded or age-related wording
- No invented benefits or pay
If something important is missing from my inputs, say what you assumed. Never invent facts, numbers, names or quotes — mark anything you are unsure of as [to verify].
## My inputs
Role notes or the current JD:
{{role_notes}}
About the team/company (what you may say) (optional):
{{company_info}}
Benefits and salary range (if published) (optional):
{{benefits}}