How to Write a Job Description That Attracts Applicants
Five real tasks, honest requirements, and a pay range. Here is the structure that brings in fewer applicants and better ones, plus the phrases to cut.
In this report 7 sections
A good job description names the five real tasks the person will do, the outcomes they own, three to five genuine requirements, and an honest pay range, in that order. Skip the culture boilerplate and wish-list qualifications entirely. A posting written this way draws fewer applicants, but a noticeably higher share of them are actually qualified for the role.
Open any job board and you will find a posting for a coordinator role requiring seven years of experience, a bachelor's degree, and a "passion for excellence." Nobody wrote that. It accumulated, one copied paragraph at a time.
This guide is for hiring managers and recruiters who want a job description that attracts qualified applicants and holds up in the rest of the process. It covers the structure, the requirements trap, pay range rules, and the specific phrases to delete.
How to Structure a Job Description
Five blocks, in this order. The order matters because candidates read the first 150 words and skim the rest.
- What the job does. Two sentences. "You will run payroll for 400 employees across three states and own the monthly close for people costs."
- The five main tasks. Actual recurring work, with rough proportions if they are lopsided.
- What success looks like at 6 and 12 months. This is the block most postings skip and the one strong candidates look for.
- Requirements, split into must-have and helpful. Three to five must-haves, maximum.
- Pay range, location rules, and how to apply. No mystery, no "competitive salary."
Write the success criteria before the requirements. Once you know what the person has to accomplish in the first year, the genuine requirements fall out of it, and the aspirational ones become obviously unnecessary.
Company description goes last, and two sentences is plenty. A candidate deciding whether to apply cares about the work first and the mission statement fourth.
For task language, O*NET OnLine, the occupational database sponsored by the U.S. Department of Labor, lists the actual tasks and work activities associated with each occupation. Pulling from it beats copying a competitor's posting, which is how bad requirements spread across an entire industry.
The Requirements Trap
Every unnecessary requirement is a filter on your own pipeline, and it filters hardest on the people who read the list literally.
Degree requirements are the clearest example. Many postings still require a bachelor's degree for roles where nothing in the daily work depends on one. Occupational entry requirements published in the Occupational Outlook Handbook from the U.S. Bureau of Labor Statistics (BLS) are a useful reality check: for a large share of jobs, the typical entry path is a credential or on-the-job training rather than a four-year degree.
Years of experience deserve the same scrutiny. Five years of doing a job badly is not better than two years of doing it well, and the number is mostly a proxy for confidence rather than capability.
There is a compliance angle too. Job descriptions are used to establish the essential functions of a position, which matters for accommodation decisions under federal law. The U.S. Equal Employment Opportunity Commission (EEOC) guidance on reasonable accommodation and undue hardship under the Americans with Disabilities Act (ADA) is worth reading before you list a physical or scheduling requirement that is not truly essential.
| Common requirement | What it usually means | Better version |
|---|---|---|
| Bachelor's degree required | Nobody revisited this since 2014 | Remove, or state the specific knowledge needed |
| 7+ years experience | We want someone senior | Name the scope: "has owned a $2M budget" |
| Excellent communication skills | Unmeasured | "Writes weekly updates read by executives" |
| Fast-paced environment | We are understaffed | Say what changes week to week, honestly |
Does a Job Posting Have to Include a Pay Range?
Include the range even where no law requires it. Candidates who would decline the offer screen themselves out early, which saves four interviews that were never going to close.
In much of the country this is no longer optional. As of 2026, 18 states plus Washington, D.C. have some form of disclosure requirement, and roughly a dozen require a good-faith range in the posting itself. Remote roles generally trigger the rules of any covered state where the work can be performed, which our guide to pay transparency laws in 2026 breaks down state by state.
One caution for multi-state employers. If the role is remote, assume the strictest applicable state rule governs the posting rather than the rule where your headquarters sits. Excluding covered states from the posting is legal in most cases and costs you a large share of the candidate pool.
Make the band real. A range of $60,000 to $140,000 for one role tells candidates you have not defined the job, and in several states it invites a regulator's attention.
Phrases to Delete From Your Job Description Today
These add length and subtract applicants. Each one is followed by what it should say instead.
- "Wear many hats." Say which hats. Candidates assume the worst, and they are often right.
- "Rock star," "ninja," "guru." These narrow your applicant pool with no upside.
- "Work hard, play hard." Reads as long hours with a beer fridge.
- "Other duties as assigned." Legally weightless and vaguely ominous. Name the real scope instead.
- "Competitive salary." Post the number.
- "Family atmosphere." Families do not conduct layoffs. Describe the actual team.
Length matters as well. Postings that run past roughly 700 words lose candidates in the middle, and the middle is usually where the requirements list sits. In the hiring teams The Work Floor has worked with, cutting a posting in half rarely reduced qualified applicants and reliably reduced unqualified ones.
Writing a Description That Survives a Leveling Audit
A job description that only exists to fill an open req tends to fall apart the first time someone runs a pay-equity or leveling review, because nothing in it maps cleanly to a level, a band, or a comparable role. Write the description with that future audit in mind, not just the immediate hire.
Name the level explicitly if your company uses one (Coordinator, Senior Coordinator, Manager) and tie the five core tasks to that level's actual scope, not an aspirational version of it. A "Senior" title attached to entry-level tasks is exactly the kind of mismatch a leveling review flags first, and it's far cheaper to fix before the posting goes live than after someone's already been hired at the wrong band.
We've seen HR teams at The Work Floor get burned by a job description that quietly drifted from the actual leveling framework over a few years of copy-paste reposting. Revisiting the description every time the role reopens, not just editing the last posting, is what keeps that drift from compounding.
Pay-equity reviews look at the same document from a different angle: whether two people doing materially the same job, per their written descriptions, land in noticeably different pay bands. A description that's vague about scope makes that comparison harder to defend, since a reviewer can't tell whether two "Coordinator" roles are actually equivalent work or two different jobs sharing one title. Specific, honest task lists protect the company here as much as they help candidates self-select accurately.
Make the Job Description Do Double Duty
The document should not stop working once the posting goes live.
Write your interview questions directly from the five tasks. One question per task gives you a complete question set and guarantees the interview measures the job rather than the interviewer's instincts, which is the foundation of structured interviews that predict performance.
Use the six- and twelve-month success criteria as the new hire's first review framework. If those criteria felt hard to write, that is useful information about how well the role is defined, and it is better to learn it before someone is doing the job.
Send the description to one person who does the job today. Ask them to mark anything that is not true. That five-minute review catches more problems than a second recruiter's read, because they are the only person with the daily detail.
Revisit the posting after every hire in that role. Ask the person who took the job which part of the description turned out to be wrong. The answer is usually specific and easy to fix.
The Version to Publish
Two sentences on the job, five real tasks, success criteria at six and twelve months, three to five must-haves, and a genuine pay range. Under 700 words, company description last.
Then use the same document to build your interview questions and the new hire's first review. A job description written this way is the cheapest quality improvement available to a hiring team, which is why The Work Floor keeps pointing hiring managers back to it before they change anything else about their process.
The Work Floor covers careers, hiring, management, and the changing shape of work for the people who do it.
