A job description records one particular role: the work it covers, the reason it exists, what the worker must bring, and the conditions of the job. Employers use that record for recruiting, onboarding, performance conversations, and keeping the role current.
It names the work. It doesn't sell a fantasy candidate.
Why do so many descriptions still sound like filler? Writing one properly forces decisions about purpose, scope, requirements, and working conditions. Many drafts skip those decisions and become task lists.
A job description isn't the same thing as a job advertisement. The description documents the job. The posting presents the opportunity and tells applicants how to respond. They may share wording, but they serve different readers.
Turns out, the weakest descriptions usually have the same problem. They list activities without explaining the role's purpose or drawing its boundaries. Stronger versions connect work to outcomes and keep genuine requirements separate from useful preferences.
The definition in plain English
Think of a job description as the operating brief for one position. It covers the role itself, not the personality of an ideal candidate and not the marketing message meant to attract applicants.
Here's a practical test. Remove the company logo and application button. Does the document still make sense?
It should show a manager what the employee owns. It should show a candidate what the work involves. It should also give an ATS or job board accurate information to display.
| Question | Where the answer belongs |
|---|---|
| What is the role called? | Job title and department |
| Why does the role exist? | Purpose or summary |
| What will the employee do? | Responsibilities and expected outcomes |
| What must the employee know or do already? | Required qualifications |
| What would be helpful but is not essential? | Preferred qualifications |
| Where and under what conditions is the work performed? | Location, schedule, travel, tools, and physical requirements |
| How will success be judged? | Goals, deliverables, or performance measures |
No single federal format applies to every employer. The right structure depends on the role, the organization, and whether the document is internal, public, or both.
The parts of a useful job description
You don't need to document every tiny detail. You do need enough information to remove avoidable uncertainty.
Most useful descriptions include these elements:
- Job title and work context: Choose a title candidates will recognize and search for. Add the department, manager, location, employment type, and work arrangement.
- Purpose statement: Use one or two plain-language sentences to explain the role's main contribution.
- Responsibilities: Cover recurring work, decisions, relationships, and deliverables. Group related tasks instead of listing every minor activity.
- Scope and authority: Clarify what the employee owns, what they influence, and where approval is required. A manager, coordinator, and director shouldn't sound interchangeable.
- Required qualifications: List the minimum education, experience, technical ability, license, certification, or other condition needed to perform the job.
- Preferred qualifications: Keep useful extras in their own section. A preferred item shouldn't quietly become an absolute requirement.
- Working conditions: State the schedule, location, travel, physical demands, equipment, environment, and regular on-call expectations.
- Success measures: Identify the outcomes or standards that will guide performance conversations between the employee and manager.
The familiar advice to list four to seven duties isn't a universal rule. Represent the actual job through a few meaningful responsibility groups, then remove repeated ideas. Time percentages may help with some internal classification systems. Elsewhere, invented precision can make the document less believable.
Qualifications need the same scrutiny. If a degree is required, explain why the work needs it or provide an equivalent path where appropriate. A long credential list can narrow the applicant pool without improving the hiring decision.
A practical job description template
Start with the structure below. Don't fill it with generic language just because every field is present.
Job title: [Recognizable title]
Department and manager: [Team] | Reports to [role]
Purpose: [Explain why the role exists and the result it supports.]
Primary responsibilities: [Describe the main work areas, decisions, partners, and deliverables.]
Required qualifications: [List only the minimum education, experience, skills, licenses, or certifications needed.]
Preferred qualifications: [List helpful but nonessential background.]
Work context: [Location, schedule, work arrangement, travel, tools, physical demands, and environment.]
Success measures: [Describe the outcomes, service standards, milestones, or measures used to evaluate the role.]
Hiring details: [Employment type, pay information where appropriate, benefits summary, and application instructions.]
Readers understand responsibilities faster when each one shows an action and its scope. These examples illustrate the difference:
| Vague wording | Clearer wording |
|---|---|
| Responsible for social media | Plan and publish the monthly social calendar across approved channels, then report engagement trends to the marketing manager |
| Helps customers | Resolve customer questions through email and chat, document recurring issues, and escalate account risks |
| Manages projects | Coordinate project timelines, owners, risks, and status updates from kickoff through delivery |
| Good communication skills | Explain product changes to customers and internal teams in clear written updates and live meetings |
The clearer versions aren't more impressive because of jargon. They simply tell the reader what the employee will do.
Job description, job specification, and job posting
HR teams often blur these terms. Some employers combine all three into one file. The distinction still helps people use the document correctly.
| Document | Main question | Typical audience | Main use |
|---|---|---|---|
| Job description | What does this role do? | Managers, HR teams, employees, and candidates | Define work, scope, expectations, and conditions |
| Job specification | What must the person bring? | Recruiters and hiring managers | Screen for education, experience, skills, and credentials |
| Job posting or job ad | Why should someone apply, and how do they apply? | External candidates | Present the opportunity and collect applications |
A job specification often appears as one section inside a job description. It doesn't always need its own file.
The public posting changes the emphasis. A description might say that the role owns quarterly planning and vendor coordination. The posting may instead lead with the mission, team, schedule, pay information, benefits, and application process.
That change is useful. The internal record defines the work. The public version helps a candidate decide whether to apply.
How a job description works with an ATS or job board
Employers often keep the approved description as the source record in an applicant tracking system. From there, the ATS may send selected fields to job boards, a careers page, or a recruiting campaign.
Keep that source record accurate first. Adapt the public copy for scanning afterward, but don't change the substance of the role.
Thing is, candidates shouldn't have to decode the system. They need a searchable title, a clear location, a visible work arrangement, readable headings, and an application process that says what happens next. Put important facts in text fields. Don't hide them in an image or an attached file.
The workflow is easier to trust when the same information appears everywhere:
| Field | What to verify |
|---|---|
| Title | The internal and public titles describe the same level and work |
| Location | City, state, remote limits, and travel expectations are accurate |
| Employment type | Full-time, part-time, temporary, contract, or internship status is clear |
| Responsibilities | The public duties match the approved role |
| Requirements | Required and preferred qualifications are not mixed together |
| Pay and benefits | Any published information is current and follows applicable rules |
| Application route | The link, instructions, and contact details work |
Keywords need restraint. Use terms that candidates and recruiting platforms would reasonably recognize, then write normal sentences around them. An ATS organizes applications. It can't fix an inaccurate role definition.
A step-by-step writing workflow
Begin with the work, not the wording. The following sequence keeps the draft connected to the actual role.
- Start with the actual work. Speak with the hiring manager and, when possible, an experienced employee who performs similar work. Review current deliverables, decisions, tools, and recurring problems.
- Set the role's boundaries. Confirm the manager, team, level, location, schedule, travel, and authority. This keeps a coordinator role from sounding like a department head role.
- Write the purpose before the task list. Describe the contribution the role makes and the business or customer result it supports. Keep the language concrete.
- Group responsibilities by outcome. Combine related tasks into a few meaningful areas. Active verbs such as analyze, coordinate, build, resolve, maintain, and advise usually produce clearer descriptions.
- Separate minimums from preferences. Ask whether each requirement is genuinely necessary on the first day, legally required, or merely familiar to the current team. Move useful extras into the preferred section.
- Add the work context. Explain where the work happens, how the schedule operates, whether travel is routine, and which physical or environmental demands are essential.
- Review it in the tools candidates will use. Check the ATS record, job board preview, careers page, and application link. Ask someone outside the hiring team to describe the role after reading it.
- Set a review date. Update the description when the manager, systems, reporting lines, location, or major responsibilities change. An old version can mislead candidates and employees.
The last review is easy to skip. It is also where mismatches tend to show up.
Legal and accessibility checks in the United States
A job description doesn't create a legal safe harbor. It documents the role, but it doesn't excuse biased recruiting, inconsistent screening, or an application process people can't use.
Federal anti-discrimination rules affect both job wording and hiring practices. Title VII covers discrimination based on race, color, religion, sex, and national origin. The Americans with Disabilities Act protects qualified individuals with disabilities from employment discrimination. The EEOC's employer guidance on the ADA explains employer responsibilities.
Test each requirement against the work itself. Describe an essential physical demand accurately, including the task and condition involved. If someone could perform a task with a reasonable accommodation, vague or exaggerated wording shouldn't screen that qualified person out. The EEOC's reasonable accommodation guidance provides more detail.
| Review area | Question to ask |
|---|---|
| Essential functions | Which duties are fundamental to the role, and which are occasional or incidental? |
| Qualifications | Can the team explain why each required credential or experience level is necessary? |
| Language | Does the description avoid gender-coded, age-coded, or otherwise exclusionary wording? |
| Physical demands | Are the demands specific, accurate, and connected to actual work? |
| Work location | Does the location and schedule match what the employer will require? |
| Pay information | Have the employer and platform checked applicable state and local posting rules? |
| Application access | Can candidates find, read, and complete the application without unnecessary barriers? |
State and local requirements may differ. Before publishing compensation, location, notice, or application details, check the rules for the job's location.
Using O*NET without copying it blindly
The U.S. Department of Labor's O*NET system provides information about occupational characteristics and worker requirements across occupations. Employers can use it to compare related roles, identify useful skill terms, and spot duties that deserve a closer look.
O*NET gives you a reference point. It doesn't replace job analysis.
A customer support role at a software company may share an occupation with another role while using different systems, serving different customers, following different schedules, and carrying different decision rights. Those details belong in the employer's own description.
Use outside occupational data to test the draft. Use interviews and current work records to finish it.
AI-assisted drafting
AI can turn notes into a first draft. That can save time when an employer has many roles to document.
It can't decide whether a qualification is essential, whether a title reflects the level, or whether a responsibility belongs with another team. Those decisions still require someone who understands the work.
To be honest, polished wording can conceal bad assumptions. Give the tool verified role notes, then check every duty, requirement, location detail, and statement about flexibility. Don't paste confidential employee information into a tool unless the organization has approved that use.
A human role owner should approve the final version. Before applications open, that person should compare the approved text with the ATS record and the public job board posting.
How job seekers can read a job description
Candidates can use the description as a screening tool. It can show whether the role deserves an application and whether the posting makes sense internally.
Start with the purpose and primary responsibilities. Those sections usually say more about day-to-day work than a string of personality traits. Then distinguish required qualifications from preferred ones. Missing a preferred item isn't automatically a reason to stop.
Practical details come next. Check the location, schedule, travel, work arrangement, employment type, pay information if provided, and application instructions. An appealing title may still lead to work you don't want.
Compare the job board listing with the employer's official careers page when one exists. The title, duties, location, and application details should match. If the platform lets you, save a copy of the posting. That matters more when the employer may update the listing later.
The description can sharpen your application, too. Use the employer's own accurate terms when describing relevant experience, but don't claim a skill you don't have. Clear wording helps the candidate and the hiring team.
A final prepublish check
Run this check before the description goes live:
| Check | Pass condition |
|---|---|
| Role identity | A reader can tell the level, team, manager, location, and work arrangement |
| Purpose | The first section explains why the role exists |
| Responsibilities | The duties describe real work and meaningful outcomes |
| Requirements | Minimum qualifications are distinct from preferences |
| Conditions | Schedule, travel, physical demands, and environment are accurate |
| Candidate experience | The posting is readable and the application path works |
| Compliance | The language has been reviewed for job-related, accessible, and nondiscriminatory wording |
| Maintenance | Someone owns the record and knows when it will be reviewed |
Frequently asked questions
Is a job description the same as a job posting?
No. A description defines the role. A posting presents that role to potential applicants.
An employer may use the description as the posting's source. The public version should still include candidate-facing information and a clear application route.
Does every job description need a salary range?
No nationwide rule requires one in every case. Pay disclosure requirements vary by state and locality, and an employer may choose to publish compensation voluntarily. Check the rules for the job location, and keep any published range current.
How long should a job description be?
It needs enough detail to explain the work without hiding the main facts. Short roles may need only a few focused sections. Complex roles may need more detail about scope, systems, travel, or compliance.
There isn't a useful fixed word count. Accuracy matters more.
Should required and preferred qualifications be separate?
Yes, in most cases. Separate sections show candidates the real screening standard and help recruiters apply that standard consistently.
Can an employer change a job description after hiring?
An employer can revise a role as the work changes. Major changes should be discussed with the employee and reviewed for effects on pay, level, reporting, classification, and accommodation needs.
Keep the version history in the HR or ATS system.
Begin with one open role. Pull the manager-approved duties, write the purpose in plain language, separate minimums from preferences, and compare the final copy everywhere the job appears. Fix the first mismatch you find.