To write a job description that attracts the right candidates, lead with what the person will actually do, separate must-have requirements from nice-to-haves, publish a salary range, and describe how you hire. Specific, honest job descriptions draw fewer but better-matched applicants and save your team hours of screening time.
Most job descriptions fail for the same reason: they are written for the hiring team, not the candidate. They list internal titles, every tool anyone has ever used, and a requirements section that reads like a wish list. Strong candidates, who usually have options, skim past them. This guide shows you how to fix that.
What should a job description include?
A complete job description answers the questions a qualified candidate asks before deciding to apply. Use this structure:
| Section | What it answers | Length |
|---|---|---|
| Job title | Is this my kind of role? | 2-5 words |
| Summary | Why does this role exist? | 2-3 sentences |
| What you'll do | What does a normal week look like? | 5-7 bullets |
| What you'll need | Am I qualified? | 4-6 bullets |
| Nice to have | What would make me stand out? | 2-4 bullets |
| Pay and benefits | Is it worth my time? | Range plus key benefits |
| Location and schedule | Can I actually do this job? | 1-2 lines |
| Hiring process | What happens after I apply? | 3-5 steps |
Every section earns its place. If you cut one, cut the generic "About us" paragraph before you cut pay or the hiring process.
Use a job title people actually search for
Candidates find jobs by searching familiar titles. "Customer Success Manager" will be found; "Client Happiness Champion" will not. Keep internal levels and team names out of the title unless they are standard in your industry, such as "Senior" or "Staff."
A quick test: if you would not type the title into a job search yourself, rewrite it. You can browse live listings on Hire & Job to see which titles other employers use for similar work.
Start with the outcome, not the org chart
The summary should explain why the role exists and what success looks like after six to twelve months. This is what separates a job description that attracts people from one that merely describes a vacancy.
Before:
The Marketing Coordinator will report to the Director of Marketing and support various marketing initiatives across the organization.
After:
You'll run our email program end to end, from the weekly customer newsletter to product launch campaigns. In your first six months, you'll rebuild our onboarding email sequence and own the reporting that shows what's working.
The "after" version tells a candidate what they will build, which helps the right people opt in and the wrong people opt out.
How long should a job description be?
Aim for roughly 300 to 700 words. Shorter than that and you are probably missing pay, location or the hiring process. Longer than that and the important details get buried.
Length matters less than scannability. Use bullets for duties and requirements, keep paragraphs to two or three sentences, and put pay and location where a skimming reader will see them.
Separate must-haves from nice-to-haves
The requirements section is where most job descriptions lose good applicants. Every item you list as required is a reason for a capable person to decide they are not qualified.
For each requirement, ask: "Would we reject an otherwise excellent candidate who lacked this?" If the answer is no, move it to "Nice to have" or delete it.
Replace years with capabilities
Years of experience are a weak proxy for skill. Describe what the person needs to be able to do instead.
| Instead of | Try |
|---|---|
| 5+ years of sales experience | You've closed mid-market deals with multiple decision makers |
| Bachelor's degree required | Degree or equivalent practical experience |
| Expert in Excel | Comfortable building pivot tables and lookups to answer business questions |
| Fast-paced environment | You'll handle 30-40 support tickets on a typical day |
Be specific about the hard requirements
Some requirements are genuinely non-negotiable: a professional license, the ability to lift a certain weight, a security clearance or availability for weekend shifts. State these clearly so nobody wastes time applying.
Write in plain language
Write the way you would explain the job to a friend. Cut jargon, acronyms and clichés like "rockstar," "ninja," "work hard, play hard" and "self-starter." They say nothing concrete and can signal a culture some candidates want to avoid.
Use "you" and "we." "You'll own the quarterly forecast" is clearer and more inviting than "The successful candidate will be responsible for forecasting activities."
Include pay, location and the hiring process
Pay
A salary range is the single most useful piece of information you can give a candidate, and several US states require it in job postings. Set a range you would genuinely pay, based on market data. You can benchmark against published ranges on the Hire & Job salary pages, for example software engineer salaries, and check demand trends in the job market report.
Location and schedule
Say exactly what you mean: fully remote (and in which states or time zones), hybrid (and how many days in the office), or on-site. Include shift patterns for hourly roles. Vague phrases like "flexible" without detail create mismatched expectations.
Hiring process
List the steps and rough timing, for example: "Application review within a week, a 30-minute phone call, a 90-minute team interview, then an offer." Candidates are more likely to stay in a process they understand.
Check for exclusionary language
Federal law prohibits discrimination in job advertisements, including ads that discourage applicants based on race, color, religion, sex, national origin, age, disability or genetic information. The EEOC explains this in its guidance on prohibited employment policies and practices.
In practice, avoid:
- Age-coded phrases such as "digital native," "recent graduate" or "young team"
- Gendered terms such as "salesman" or "he will"
- Physical requirements that are not essential to the job
- Requirements that screen out people unnecessarily, such as a driver's license for a desk role
Add a short equal opportunity statement and explain how candidates can request accommodations during the hiring process. For a neutral description of duties and typical requirements for an occupation, the Bureau of Labor Statistics Occupational Outlook Handbook is a useful reference.
A job description template you can copy
[Job title] - [Location / Remote (states or time zones)]
[Pay range] per [year/hour] + [key benefits]
Why this role exists
[2-3 sentences on the problem this person solves and what success looks like in 6-12 months.]
What you'll do
- [Core responsibility, written as an outcome]
- [Core responsibility]
- [Core responsibility]
- [Who you'll work with day to day]
- [A project you'll own in the first six months]
What you'll need
- [Must-have capability]
- [Must-have capability]
- [Must-have capability]
- [Any genuine hard requirement: license, schedule, travel]
Nice to have
- [Bonus skill]
- [Bonus skill]
How we hire
1. Application review (within [X] days)
2. [Length] call with [role]
3. [Interview or work sample]
4. Offer
[Equal opportunity statement and how to request accommodations.]
When you post on Hire & Job for employers, the AI writing assistant can produce a first draft from a few notes, which you can then edit against this checklist. Your first job post is free.
Frequently asked questions
What is the difference between a job description and a job posting?
A job description is an internal document that defines a role's duties, requirements and reporting line. A job posting is the external advert built from it, written to persuade the right people to apply. Many small employers use one document for both, which works if it is written for the candidate.
Should I include salary in a job description?
Yes, where you can. Several US states require a pay range in job postings, and candidates consistently use pay to decide whether to apply. Check the rules in each state where you hire and publish a range you would genuinely pay.
How many requirements should a job description list?
Keep must-have requirements to around four to six items. Anything beyond that is usually a preference, so move it to a nice-to-have section or remove it. A shorter, honest list encourages qualified candidates who do not tick every box.
How often should I update job descriptions?
Review a job description every time you reopen the role. Teams, tools and pay change, and an outdated description attracts the wrong applicants. A short conversation with the hiring manager before posting is usually enough.


