Business Operations
How to Write Job Descriptions with AI - Get Better Applicants and Save Hours of Drafting
How to write job descriptions with AI: the inputs that produce a useful draft, how to remove the language that repels good candidates, and the Role Clarity Test for checking a description before you post it.

AI Educator, AI Tools and Training Club · September 10, 2026 · 8 min read

The short version
- AI can draft a job description in minutes, but the quality of the draft depends entirely on what you tell it about the role. A vague input produces a vague output that attracts the wrong applicants.
- The most common mistake is listing requirements that sound rigorous but actually filter out strong candidates - things like degree requirements for roles where skill and results matter more.
- The Role Clarity Test: before you post, confirm that someone who has never spoken to you could read the description and know exactly what they would do on day one, what success looks like in 90 days, and why this role exists in the business.
How to write job descriptions with AI
You write a job description with AI by giving it a clear brief about the role and asking it to turn that brief into a structured, plain-English description that a real candidate would want to read. The AI handles the formatting, removes filler language, and produces a draft in minutes. Your job is to write the brief accurately and edit the output for tone and specifics before you post it anywhere.
The brief matters more than the prompt. If you tell the AI what the role is called, what the person will actually do in a typical week, what a good hire looks like at 90 days, and what the working arrangement is, you will get a description that attracts the right candidates. If you give it a job title and nothing else, you will get a generic template that attracts no one in particular.
What to include in your brief before you prompt the AI
The brief is four things: the role's real function, the specific outputs the person owns, the conditions of the work, and the profile of the person who has done this kind of job well before. You do not need to write this formally. You can describe it the way you would to a friend: 'I need someone who will handle all our inbound leads, qualify them, and hand off the warm ones to me. They need to be comfortable on the phone and good at keeping a CRM updated without being chased. We are fully remote, about 20 hours a week to start.'
- What the person will do in a typical week - specific tasks, not department-level labels.
- What success looks like in the first 90 days - one or two concrete outcomes, not a personality wish list.
- What they own versus what they support - where is the line between their responsibility and someone else's?
- Working arrangement - remote, in-person, hours, contractor or employee.
- The one or two things that will make or break the hire - the non-negotiables that are not obvious from the title.
The prompt structure that produces a useful draft
A prompt that works: 'I am hiring for [role]. Here is what this person will actually do: [your brief in plain English]. Write a job description that includes a short summary of the role, a list of what the person will own and be responsible for, what we are looking for in terms of experience and skills, what the working arrangement is, and why someone who is good at this kind of work would want this role. Keep the language plain and direct. Avoid corporate filler and do not require a degree unless the job genuinely requires one.'
That last instruction matters. Most AI-generated job descriptions default to credential requirements because they are trained on existing descriptions that carry them. If your role rewards results and does not require formal qualifications, say so explicitly or you will get a draft that filters out experienced candidates who did not follow a traditional path.
| Include in the prompt | Avoid in the prompt |
|---|---|
| Plain English brief about actual duties | Just the job title |
| 90-day success outcome | Vague phrases like 'driven self-starter' |
| Explicit instruction to skip unnecessary degree requirements | Letting AI default to standard credential lists |
| Note on working arrangement (remote, hours, pay range if you have one) | Leaving compensation out entirely |
| Why someone good at this work would want this role | Generic 'competitive salary and benefits' filler |
What to ask for versus what to avoid in a job description prompt
The language patterns that repel good candidates
AI will default to several language patterns that make a description less effective, not more. The most common one is the requirements list that sounds specific but is actually a filter against candidates who could do the job well. A 10-point list of requirements where six are nice-to-haves signals to experienced candidates that the hiring manager does not know what they actually need. Strong applicants have options and they pass on roles that look confused.
- Degree requirements where skills and outcomes matter more - remove unless genuinely necessary.
- Years-of-experience minimums that rule out capable people who moved faster than average.
- Long lists of 'must have' tools where you actually only need the underlying skill.
- Phrases like 'wear many hats', 'fast-paced environment', and 'self-starter' - they signal disorganisation rather than opportunity.
- Generic culture statements ('we are a team that cares') without specific evidence of what that looks like in practice.
After the AI produces a draft, read it from the perspective of the candidate you actually want. Does it tell them what they will do, what success looks like, and why this role is worth their time? If you find yourself reading credential requirements and culture sentences instead of answers to those three questions, edit it before you post.
The Role Clarity Test before you post
The Role Clarity Test is a three-question check you run on a description before it goes live. If a candidate who has never spoken to you can answer all three from the description alone, it is ready. If they cannot, it needs more work.
- What would I actually do on day one? If the description only lists the category of work rather than the specific tasks, it fails this question.
- What does success look like in 90 days? If the description does not name an outcome - a number, a deliverable, a situation improved - it fails this question.
- Why does this role exist in the business? If a candidate cannot tell from the description what problem they are solving or what gap they are filling, it fails this question.
A description that passes all three attracts applicants who have read it properly and self-selected in. A description that fails any of them attracts volume but not fit, which means you spend more time reviewing applicants and more time explaining the role in early interviews. The test takes two minutes and it is the fastest editing pass you can make.
How to adapt the AI draft for the platform you are posting on
Job boards have different audiences and different norms, and the same description lands differently depending on where you post it. A LinkedIn post for a senior role can be longer and more detailed because the audience expects it. A posting on a platform where contractors browse needs to be shorter, lead with the scope and pay range, and get to the point faster. After you have the base draft from AI, ask it to reformat for the specific platform: 'Reformat this as a LinkedIn job post, keeping it under 400 words and leading with what the person will own.'
For contractor or freelance roles, you also need to be specific about the engagement terms - hours per week, project scope, pay range or rate, and how you prefer to work together - because contractors evaluate fit differently than full-time applicants. [How to automate hiring with AI](/blog/how-to-automate-hiring-with-ai) covers the next stage: once your description is live, how to use AI to screen applicants and manage the early communication without drowning in messages.
Frequently asked questions
Can AI really write a good job description?
Yes, if you give it a good brief. A one-line prompt produces a generic template. A brief that describes what the person will actually do, what success looks like in 90 days, and what the working arrangement is produces a description that reads like it was written for a real role. The quality of the output tracks the quality of the input.
What should I always include in a job description?
What the person will do in a typical week, what success looks like in the first 90 days, who they report to and what they own versus what they support, the working arrangement and hours, and why someone who is good at this kind of work would want this role. Those five things separate a useful description from a credential list that attracts the wrong applicants.
How do I stop AI from adding unnecessary requirements to a job description?
Tell it explicitly not to. Include an instruction in your prompt: 'Do not require a degree unless the job genuinely requires one. Do not include years-of-experience minimums unless I specify them. Focus on outcomes and skills rather than credentials.' AI defaults to the patterns it has seen in existing job descriptions, which are full of credential requirements. An explicit instruction overrides the default.
Should I include salary in an AI-written job description?
Yes, if you know it. A salary range in the description increases the quality of applicants because it lets candidates self-select based on whether the role fits their situation. Leaving it out tends to produce more volume and less fit, because candidates apply speculatively rather than with informed interest. Ask the AI to include a pay range placeholder if you do not have a firm number yet.
What is the Role Clarity Test for a job description?
A three-question check: can a candidate who has never spoken to you tell what they would do on day one, what success looks like in 90 days, and why this role exists in the business? If all three questions have clear answers in the description, it is ready to post. If any of them cannot be answered from the text alone, the description needs more work before it goes live.