Writing an inclusive, skills-based job description
Job descriptions are the single most common AI use in recruiting (66% in SHRM's 2025 data), and the reason is simple: the boilerplate ones repel good people. Inflated "requirements," an endless wish list, and quietly gendered language shrink and skew the applicant pool before anyone applies. AI is good at a fast first draft you then tighten around what the role actually needs.
You are helping an experienced recruiter draft an inclusive, skills-based job description. You write the first draft; I edit it to match the real role. Role and level: {{role_title}} What the person actually needs to do the job (skills and outcomes, not credentials): {{must_have_skills}} Team, mission, and who they report to: {{team_context}} Location, work model, and anything I can state about pay: {{comp_and_location}} Write a job description with: a two-sentence hook, a "What you'll do" list of 5-6 outcomes, a "What you'll need" list split into must-haves and nice-to-haves, and a short "How we work" paragraph. Rules: - Base every requirement on the skills and outcomes I gave you. Do NOT invent responsibilities, technologies, years-of-experience bars, or benefits I did not state — insert [VERIFY] where a detail is missing. - Keep must-haves short; move anything not truly required to nice-to-haves. Long requirement lists narrow and skew the pool. - Flag any wording that could read as gendered, ageist, or exclusionary ("rockstar," "young and energetic," "native English speaker") and suggest a neutral alternative. - Plain language, active voice, no superlatives. Aim for under 500 words.
Fill in your details and the prompt updates live — then copy.
Senior Customer Success Manager You'll own the renewal relationships for our mid-market accounts and be the person customers call before they call anyone else. This is a role for someone who reads a usage dashboard and sees a conversation waiting to happen. What you'll do - Own renewals and expansion for a book of ~40 mid-market accounts - Run quarterly business reviews that customers actually find useful - Spot churn risk early and rally the team around it What you'll need Must-haves: experience owning B2B renewals; comfort with usage data. Nice-to-haves: SaaS background; [VERIFY: specific tools].
The full workflow
- Feed the prompt only the skills and outcomes the role truly needs — not a copy of the last posting.
- Cut every must-have that is a preference, not a requirement, before you post.
- Resolve every [VERIFY] tag and confirm the posted pay range meets your state's pay-transparency rules.
- Read the final draft once for tone and coded language, then publish.
Watch out for
Unnecessary requirements create legal exposure: a degree or years-of-experience bar the job does not need can produce disparate impact under Title VII. Keep must-haves job-related and defensible.
AI will happily invent perks, salary, or benefits to make the post sing — strike anything you did not state, and verify pay-transparency wording against your jurisdiction manually.
Where this comes from
Every use case on this site is grounded in real reports from working recruiters — not invented by us.