Full disclosure: my team built a job description tool, so I'm biased. The structure below works in any doc.
TL;DR
A good job description is short, specific and honest about what the job is. Write for the person you want to apply.
- Use a plain title people actually search for.
- Open with a two or three sentence summary of the role and why it exists.
- List real responsibilities, then must-have requirements only.
- Include compensation and logistics where you are able to.
The job post at a glance
| Section | What goes in it | Rule |
|---|---|---|
| Title | The common name for the role | No jargon or invented titles |
| Summary | What the role does and why it exists | 2 to 3 sentences |
| Responsibilities | 5 to 7 bullets | Verb first, real tasks |
| Requirements | Must-haves, then nice-to-haves | Keep must-haves short |
| Compensation and logistics | Pay range, location, hours, process | Share what you can |
Why this goes wrong
- Wish lists. Long requirement lists scare off qualified people.
- Fancy titles. Searchers type the common name, not an internal one.
- Hidden basics. Candidates skip posts without pay, location or process.
- Copy and paste. Reused posts describe a job that no longer exists.
Step 1: Interview the hiring manager
Ask what the person will do in the first three months, what success looks like, and what is truly required on day one.
Step 2: Choose the title
Use the standard name for the role and put level or team in a separate line if needed.
Step 3: Write the summary
Two or three sentences: the team, the problem the role solves, and who it works with.
Step 4: Split must-haves from nice-to-haves
If a skill could be learned in the first months, it is probably a nice-to-have.
Step 5: Add pay and logistics
Check local rules on pay transparency, then add the range, location or remote setup, and the hiring steps. Use [TBD] in your draft for anything you still have to confirm.
A made-up example
This example is invented for illustration.
Title: Customer Support Specialist
Summary: You'll help customers solve problems by email and chat and pass patterns to the product team.
Responsibilities
- Reply to customer tickets within the agreed time.
- Document common issues in the help center.
Requirements
- Clear written communication.
- Experience with a support tool, or willingness to learn.
Compensation:
[range TBD]
What I'd do today
- Ask the hiring manager for the first-three-months list.
- Cut the requirements down to the real must-haves.
- Add the pay range, location and hiring steps, or mark them as TBD.
- Ask a colleague outside the team to read it and say what the job is.
FAQ
How long should a job post be?
Short enough to scan, usually one page.
Should I list salary?
Many places require it or encourage it. Check your local rules and your company's policy.
Do I need years of experience?
Only if it is truly required. Describe skills where you can.
Can AI write job descriptions?
It can draft one from notes, but review it for accuracy and for wording that could exclude people unfairly.
Drafting faster with Job Description Writer
If you'd like a first draft, my team built a chat agent called Job Description Writer. It runs on Capafy, an AI agent marketplace.
What you send: the hiring manager's rough notes.
What you get back, according to the listing:
- a title,
- a summary,
- responsibilities,
- requirements,
- compensation and logistics.
The listing describes it as turning rough notes into a clean, ready-to-post description. It works from your notes, so confirm pay and process details yourself before you publish.
Pricing on the listing is $2.99/week or $6.99/month.
Wrap-up
- Use a plain title and a short summary.
- Keep must-haves short and separate from nice-to-haves.
- Share pay and logistics where you can, or mark them TBD until confirmed.
Disclosure: my team built Job Description Writer and sells it on Capafy.
Top comments (0)