---
title: How to Write a Job Description with AI in 10 Minutes
url: "https://goremy.ai/blog/articles/how-to-write-a-job-description-with-ai-in-10-minutes"
author: Luis Chavez-Mattos
editor: Luis Chavez-Mattos
editor_title: Director, Product
published: "2026-11-18T19:40:15.414Z"
updated: "2026-11-18T19:40:15.414Z"
topic: Recruiting and Hiring
description: A step-by-step way to write a clear job description with AI in about 10 minutes, with a copy-paste prompt, a worked example, and what to check before posting.
---

# How to Write a Job Description with AI in 10 Minutes

> A step-by-step way to write a clear job description with AI in about 10 minutes, with a copy-paste prompt, a worked example, and what to check before posting.

Edited by Luis Chavez-Mattos, Director, Product · Published 2026-11-18

## How do you write a job description?

To write a job description, state the job's purpose in one or two sentences, list the main outcomes the person will own, separate the true must-haves from the nice-to-haves, describe the team and working conditions, and include pay and how to apply. AI can produce a solid first draft in about a minute if you give it real notes about the role. Your job is to supply the facts and check the result.

## TL;DR

- **Start with notes, not a blank page.** Five minutes of honest answers about the role beats any template, and those answers are what you feed the AI.
- **A good job description describes outcomes,** what the person will have done after 90 days and a year, not a list of every task someone once did in the seat.
- **Keep must-haves to five or fewer.** Long requirement lists shrink your applicant pool and tend to filter out qualified people who read them literally.
- **AI writes the draft; you supply the facts.** Tell it not to invent anything, and have it list what it still needs from you.
- **Check pay, legal language and claims yourself.** AI will happily write a benefit your company does not offer.
- **The whole process fits in 10 minutes** if you split it: 3 for notes, 1 for the prompt, 4 for review, 2 for sign-off.

## What goes into a good job description?

Candidates read a job description to answer three questions: what would I do, can I do it, and is it worth it. Everything in the document should serve one of those. Here is the structure that works for almost any role, in any department.

| Section | What it answers | Length |
|---|---|---|
| Job title | What is this role, in words people search for? | 2 to 6 words |
| Summary | Why does this role exist? | 2 to 3 sentences |
| What you'll do | What outcomes will I own? | 5 to 7 bullets |
| What you'll bring (must-have) | Can I do this? | 3 to 5 bullets |
| Nice to have | What would make me stand out? | 2 to 3 bullets |
| About the team | Who will I work with, and where? | 2 to 4 sentences |
| Pay and benefits | Is it worth it? | Range plus 3 to 5 specifics |
| How to apply | What happens next? | 1 to 3 sentences |

A few notes on titles, since people search them. Use the title the market uses, not your internal grade or level code. "Senior Accountant" gets found. "Finance Associate III" does not. If your company needs an internal level, put it at the bottom of the posting or in your applicant system.

## How do you write a job description with AI in 10 minutes?

The trick is to treat AI as a fast drafter that knows nothing about your team. It knows how job descriptions are structured. It does not know why you need this person. You supply that, and it handles the structure and the wording.

### Step 1: Write your intake notes (3 minutes)

Answer these questions in rough bullets. Do not polish. This is the most valuable part of the process, and it is the part AI cannot do for you.

```
ROLE INTAKE NOTES

Job title (as the market would search it):
Team and who it reports to:
Why this role exists now (new headcount, backfill, new project):
What success looks like at 90 days:
What success looks like at 12 months:
The 5 to 7 main things this person will do:
Must-have skills or experience (5 max), and why each is truly required:
Nice-to-have skills (3 max):
Tools or systems they will use daily:
Location and work arrangement (onsite, hybrid, remote, travel):
Pay range and benefits worth naming:
Interview process (number of steps, rough timeline):
Anything candidates often get wrong about this job:
```

If you are a recruiter, send this list to the hiring manager and ask them to fill in the first three lines before you talk. If you are the hiring manager, do it yourself. The last question is the useful one. "People assume this is a support job, but it's mostly analysis" is the sentence that attracts the right applicants and discourages the wrong ones.

### Step 2: Paste the prompt (1 minute)

Use the prompt in the next section. Paste your notes at the bottom. Use whichever AI assistant your company approves.

### Step 3: Review the draft (4 minutes)

Read it once as the candidate and once as the hiring manager. The checklist further down tells you what to look for.

### Step 4: Fill the gaps (1 minute)

The prompt asks the AI to list what is missing instead of guessing. Answer those questions, or delete the lines that depend on them.

### Step 5: Get sign-off (1 minute to send)

Send the draft to the hiring manager and compensation or HR contact for the pay range and legal check. Send it with a specific ask: "Reply with changes to the must-haves and confirm the pay range."

## What prompt should you paste?

Copy this whole block. Replace the bracketed part at the end with your notes.

```
You are an experienced recruiter writing a job description for a large company. Write a clear, honest job description using ONLY the information in my notes below.

Rules:
- Do not invent responsibilities, requirements, benefits, pay, team details, or company facts. If something is missing, list it at the end under "Questions for the hiring manager."
- Plain, direct language. No buzzwords or phrases like "rockstar," "ninja," "fast-paced environment," or "passionate self-starter."
- Describe outcomes, not just tasks. Start each "What you'll do" bullet with a verb.
- No more than 5 must-have requirements. Keep nice-to-haves separate and label them clearly.
- Only include a years-of-experience requirement if my notes give a reason for it. Otherwise describe the skill instead.
- Use inclusive, gender-neutral wording.
- Length: 450 to 650 words.

Use this structure:
1. Job title
2. Summary (2 to 3 sentences on why the role exists)
3. What you'll do (5 to 7 bullets)
4. What you'll bring (must-haves)
5. Nice to have
6. About the team and how we work
7. Pay and benefits (use the range from my notes; if none is given, write [PAY RANGE NEEDED])
8. How to apply and what the interview process looks like

After the job description, add:
- "Questions for the hiring manager": anything missing or unclear
- "Requirements to challenge": any must-have that might be excluding good candidates, and why

MY NOTES:
[paste your intake notes here]
```

The two sections at the end do real work. "Requirements to challenge" gives you a ready-made conversation with a hiring manager who wants eleven must-haves.

## What does this look like with a real example?

Here are filled-in notes for a role that could sit in almost any company: a customer operations manager.

```
Job title: Customer Operations Manager
Team: Customer Support, reports to Director of Customer Experience
Why now: Team grew from 8 to 15 in a year, no one owns process and quality
90 days: Has reviewed all support workflows, picked the top 3 causes of repeat contacts, started fixing the first
12 months: Repeat contacts down, new-hire ramp time shorter, monthly quality report the leadership team reads
Main things: Run weekly team metrics review; own the help-center content process; work with Product on recurring bugs; train and coach 2 team leads; manage the support tooling budget; build the monthly quality report
Must-haves: Has managed or led a support or operations team; comfortable with ticket and metrics data (spreadsheets, a BI tool); has improved a process end to end; clear writer
Nice-to-have: Experience with Zendesk or similar; has onboarded new hires at scale
Tools: Zendesk, Looker, Google Sheets, Slack
Location: Hybrid, Chicago, 2 days in office
Pay: [from compensation team: $X to $Y], bonus, standard benefits
Process: Recruiter screen, manager interview, case exercise, team panel; about 3 weeks
Common misconception: People think it's a people-management role. It's about half process and analysis.
```

A good result from the prompt opens something like this:

> **Summary:** Our support team has doubled in a year, and we need someone to own how it runs. As Customer Operations Manager, you'll find why customers contact us twice, fix the causes, and build the habits that keep the team's quality high as it grows.
>
> **What you'll do**
> - Run the weekly metrics review and turn what you find into decisions
> - Identify the top causes of repeat contacts and lead the fixes with Product and Support
> - Own the help-center content process so articles stay accurate
> - Coach two team leads and help them develop their teams
> - Publish a monthly quality report for the leadership team

Notice what the AI did well: it turned notes into outcomes and kept the "half process and analysis" point. What you still need to do is the next section.

## What should you check in the AI's answer?

Go through this list every time. It takes about four minutes.

1. **Facts.** Does every responsibility, tool, location and benefit appear in your notes? Delete anything that doesn't. AI fills gaps with plausible filler, such as "competitive benefits," "opportunities for growth," or a tool your team doesn't use.
2. **The must-have list.** Would you reject a candidate who lacked each item? If not, move it to nice-to-have. Ask whether any item is a proxy, like "bachelor's degree" standing in for "can analyze data."
3. **Years of experience.** Numbers like "7+ years" are often arbitrary. Replace them with the skill: "has led a team through a process change."
4. **Title and level.** Does the seniority in the writing match the title and pay? A "Manager" role described as all execution, or an "Associate" role asking for strategy, will confuse candidates.
5. **Tone.** Read the summary aloud. If it sounds like a brochure, rewrite it in your own words. Candidates notice generic copy.
6. **Length.** Aim for a posting someone can read in two to three minutes. Cut anything that doesn't help a candidate decide whether to apply.
7. **Biased or exclusionary wording.** Watch for phrases like "digital native," "young and energetic," or "must be able to lift" when lifting isn't essential. Phrases that imply an age, a gender, or physical ability that the job doesn't require should come out.

## Where should you not trust AI?

AI is good at structure and phrasing. It is unreliable on several things that matter in a hiring document.

- **Pay.** Never let it supply a number. Use the range from your compensation team. A growing number of US states and cities require pay ranges in postings, and other countries have their own rules, so ask HR or legal which apply to the locations you are hiring in.
- **Legal and compliance language.** Equal opportunity statements, accommodation language and work-authorization wording should come from your company's standard text, not from a model's best guess.
- **Company facts.** Headcount, growth, mission statements, awards and benefits. If it isn't in your notes or on an approved company page, it doesn't go in.
- **Role level.** The model can't know that your "senior" means something specific in your company. You can.
- **Confidential details.** Follow your company's AI policy. Don't paste in internal strategy, candidate names or anything your IT or security team has told you to keep out of AI tools. Role notes like the ones above are usually fine, but check.

## What mistakes make job descriptions fail?

Most weak job descriptions share the same problems, with or without AI.

- **A copy of the last posting.** The role has changed since someone wrote it. Start from today's notes.
- **A wish list.** Twelve required skills describe a person who doesn't exist. Hiring managers write these, and recruiters inherit them. Use the "Requirements to challenge" output to push back with something concrete.
- **Company-centered openings.** Three paragraphs about the company before any mention of the job. Lead with the role.
- **Hidden pay.** Candidates skip postings with no range, and in many places leaving it out is not allowed.
- **Vague outcomes.** "Support the team" says nothing. "Cut repeat contacts by finding and fixing their causes" says something.
- **Unclear process.** Say how many interviews and roughly how long. It reduces drop-off and anxious emails.

## How is this different for recruiters and hiring managers?

The steps are the same. The starting point is different.

**Hiring managers** know the work but not always how to describe it for outsiders. Your notes will be rich in detail and heavy on internal jargon. Ask the AI to "rewrite any internal acronyms or team names so an outside candidate understands them," and read the draft as someone who has never heard of your project names.

**Recruiters** know the market but not the daily work. Your risk is writing something polished and generic. Spend your three minutes on the intake conversation: ask the manager the "what do people get wrong about this job" question and the "what would make you regret this hire in six months" question. Put those answers into the notes.

**Engineering and design roles** deserve extra care. Name the actual problems the person will work on, not a list of every technology in the stack. Separate "we use this daily" from "familiarity helps." Candidates in these fields read postings closely and skip the ones that look like keyword lists.

## Is there a way to stop rewriting job descriptions from scratch?

If your team opens roles often, the repeated work is collecting the same intake notes from different managers and sending drafts back and forth. A small internal tool can handle that: a request form where a manager fills in the role details, a draft generated from the answers, and a place for the recruiter and compensation contact to review and approve it. You can describe that app in plain English to [Remy](https://goremy.ai), which builds and deploys full-stack apps with sign-in, a database and role-based access, so managers, recruiters and approvers each see what they should. Check with your IT and security team before putting hiring data into any new tool, and remember that the AI usage is billed at cost on top of the platform's flat monthly fee.

## Frequently Asked Questions

### How long should a job description be?

Roughly 450 to 650 words is enough for most roles. Candidates should be able to read it in two to three minutes and understand the job, the requirements and the pay. Longer postings tend to bury the useful parts, so cut anything that does not help someone decide whether to apply.

### Should a job description include the salary?

Yes, where you can. Candidates use pay to decide whether to apply, and a growing number of US states, cities and other countries require a range in postings. Get the range from your compensation team, and ask HR or legal which rules apply where you are hiring. Don't ask AI to estimate it.

### What is the difference between a job description and a job posting?

A job description is the internal document that defines the role: duties, level, requirements and reporting line. A job posting is the public version written to attract candidates. They overlap, but the posting is shorter, speaks directly to the reader, and adds pay, process and how to apply. The method in this post produces a document you can use for both.

### Can AI write a job description that doesn't discriminate?

AI can help you spot exclusionary wording, and the prompt above asks for inclusive language and for requirements to be challenged. It can also introduce bias from patterns in its training, so review the result yourself and have HR check anything that touches legal requirements. The real protection is a short, accurate list of what the job truly requires.

### Can I reuse the same prompt for every role?

Yes. The prompt stays the same, and only the intake notes change. Save the prompt and the notes template together, and adjust the rules if your company has house style, such as required legal text or a standard benefits paragraph.
