A job description isn't a checklist — it's a sales document. The best ones do two things simultaneously: they tell a qualified candidate exactly why this role is worth their time, and they scare off the wrong applicants before they waste anyone's time. Most JDs fail at both.

The stats are stark. Companies that write clear, candidate-centric job descriptions see 30% higher application quality and 22% faster time-to-hire (LinkedIn Talent Trends 2025). Meanwhile, 67% of job seekers say they'd skip a listing without a salary range — and in 2026, you're legally required to include one in over 20 US states. The era of vague, liability-minimizing JDs is over. Candidates demand specifics; the law demands transparency; your hiring pipeline demands efficiency.

This guide covers everything: the 10-step framework for writing a complete JD, the compliance requirements that trip up even experienced HR teams, how to handle remote and hybrid roles, and the exact mistakes that cause great candidates to close the tab. It's the most comprehensive resource available on writing job descriptions in 2026.

Step-by-Step Guide: Write a Job Description That Converts

Before you open a blank document, answer these three questions in writing — even if you're posting internally first. The answers become the spine of your entire JD:

  1. What problem does this hire solve for the organization in their first 90 days?
  2. What does success look like at the 6-month mark?
  3. What's the career path for someone in this role 2–3 years from now?

If you can't answer all three, generate a first draft with JD Generator and use it as a structured thinking tool — the act of filling in the fields forces clarity you wouldn't get otherwise.

The 7-Second Rule: Recruiters spend an average of 7.4 seconds scanning a job description before deciding to read further or move on. Your job title, company overview, and first bullet point need to do the heavy lifting in that window.
1

Define the Role's Purpose and Scope

The single most common mistake in JDs is starting with the job title before understanding the role. Title first leads to generic bullet points. Purpose first leads to specificity.

Your scope definition should answer: Who does this person report to? What's their budget authority? How large is their team? What cross-functional relationships define their day? What's the most consequential decision they make independently? If you can't answer those questions, talk to the hiring manager — that conversation is the most valuable 30 minutes you'll spend on this hire.

2

Choose the Right Job Title

Your job title is a search signal. Candidates search 'Senior Product Manager,' not 'Product Virtuoso.' Internal titles that reflect your org structure (say, 'IC2' or 'Level 3 Engineer') belong in your ATS, not your job posting.

Three title rules:

  1. Match industry norms. If competitors call it 'Marketing Manager,' don't call it 'Growth Storyteller.' The search-intent mismatch costs you applicants.
  2. Don't inflate or deflate. Calling a coordinator role 'Senior Coordinator' to attract experience helps no one. Candidates who see through it will distrust your org. Calling a director role 'Manager' to widen the pool shrinks qualified response.
  3. Include seniority for searchability. 'Accountant' gets generic searches. 'Senior Accountant' gets qualified searches.

The exception: very early-stage startups with strong employer brands can use more creative titles — but only if the role genuinely carries the scope those titles imply.

3

Write a Compelling Company Overview

Your company overview is your first impression with every candidate. Most are terrible — a wall of generic mission-statement language that tells candidates nothing about what it's actually like to work there.

A good company overview has three layers:

  1. What you do and for whom. One sentence: 'We help small businesses manage their payroll.'
  2. What's different about you. 'We've been fully remote since 2018' or 'Our product is used by 3 of the Fortune 10' — specific differentiators, not buzzwords.
  3. One culture signal. 'We value async-first communication and documented decisions' tells a candidate more than 'we have a fast-paced environment.'

Keep it under 100 words. Link to your about page for more detail. JD Generator's company profile feature lets you save your overview and reapply it across all your job postings.

4

Structure Responsibilities with Impact and Specificity

The #1 rule for responsibilities: lead with outcomes, not activities. 'Lead the quarterly pipeline review process' is an activity. 'Increase win rate by 15% through structured pipeline reviews and data-driven coaching' is an outcome. Candidates want to understand impact before they think about execution.

Structure responsibilities in 3–4 clear categories. Example for a Sales Manager:

  • Team Leadership: Coach and develop a team of 6 Account Executives, conducting weekly 1:1s and monthly performance reviews.
  • Pipeline Management: Own quarterly revenue targets; maintain pipeline accuracy within 10% via weekly forecasting cadences.
  • Process Optimization: Implement and iterate on the sales methodology to improve team-wide quota attainment from 65% to 80%.

Notice the specificity: '6 Account Executives,' 'weekly 1:1s,' 'monthly performance reviews,' 'within 10%.' Numbers signal credibility. Vague bullets like 'work cross-functionally' can describe any role at any company.

Bad Example
Good Example
Vague bullet — could describe any job

Responsible for various marketing tasks as assigned

Specific, outcome-driven bullet — signals real scope

Own the content calendar end-to-end: produce 8 long-form articles and 4 case studies per quarter, managing a freelance network of 6 writers

5

Separate Required vs. Preferred Qualifications

This is the highest-leverage structural change you can make. Required = must-haves, without which the hire fails in the role. Preferred = nice-to-haves that would accelerate success. Conflating them is the most common JD mistake.

When you're drafting requirements, ask: 'If a candidate has everything except this, would we still hire them?' If the answer is yes, it's preferred, not required. A candidate who doesn't meet a required skill will almost certainly fail. A candidate who's missing a preferred skill can learn it.

For qualifications, three additional principles:

  1. Skills over credentials. 'Demonstrated proficiency in Salesforce' beats 'Salesforce certification required.' Certification doesn't measure ability; demonstrated work does.
  2. Audit years-of-experience floors. Many roles say '5+ years' when 3 years plus demonstrated growth would work. Research from Harvard Business School found that removing unnecessary degree and experience requirements expanded candidate pools by 25% without reducing quality.
  3. Don't list tools as requirements without context. 'Proficient in SQL' tells a candidate to prepare technically. 'Comfortable writing basic SQL queries to self-serve data from our analytics dashboard' tells them exactly how much SQL they need.

For a full breakdown of bias-free qualification writing, see our Inclusive Job Descriptions guide.

6

Include the Salary Range — It's the Law in 20+ States

Legal Alert (2026): Salary transparency laws now cover the majority of US workers. California, Colorado, Connecticut, Washington, New York, and 18 other states require salary or wage ranges on all job postings. Federal contractors face additional Pay Transparency requirements. Omitting a salary range isn't just a candidate experience failure — it can be a compliance violation.

Even in states without mandates, the business case for salary transparency is overwhelming. Listings with salary ranges receive 30% more applications on average (Hired.com 2025 Compensation Survey). Candidates who see a range and apply are pre-qualified on compensation — you'll spend less time on candidates who would have turned down an offer at the end of a long process.

How to present the range:

  • Use a wide range if flexibility exists: '$90,000 – $140,000' is more honest and less awkward than a single number that rules out a whole tier of candidates.
  • Show the basis: 'The range reflects our budget for a mid-level hire; senior candidates with exceptional experience will be considered above this range.'
  • Separate base from total comp: If there's equity, bonus, or commission, list the base salary clearly and note the additional components.

For a deep-dive on compensation structure and how to benchmark properly, see our Senior-Level Job Descriptions guide — compensation benchmarking is especially important for Director and VP-level roles.

7

Add Benefits and Perks That Actually Move the Needle

'Competitive benefits' is meaningless. Every company says it. To a candidate evaluating three offers, it tells them nothing.

Break benefits into specifics:

  • Health: '100% premium coverage for employee; 80% for dependents'
  • Retirement: '4% 401k match, vests immediately'
  • Time off: 'Unlimited PTO with a 2-week minimum encouraged; 10 company holidays plus the week between Christmas and New Year'
  • Remote/work flexibility: '$1,000 home office stipend on day one; $500 annual upgrade budget'
  • Development: '$2,000 annual learning and development budget; 5 days paid conference leave'

If your benefits are genuinely above market, say so. 'We cover 100% of health premiums' is a recruiter's dream phrase — candidates remember it and it drives offers accepted. If your benefits are standard, say so honestly rather than hedging with 'competitive.'

8

Set the Right Tone and Language

The tone of your job description is a culture signal. A 12-paragraph, highly formal JD signals process-heavy, hierarchical culture. A conversational, direct, 2-page JD signals fast-moving, outcome-driven culture. Neither is wrong — they're different. But the mismatch between JD tone and actual culture is one of the top reasons new hires quit within 6 months.

Tone principles that work in 2026:

  1. Write for the reader, not your ATS. Human-readability matters more than keyword-density for final candidate quality.
  2. Use active voice. 'Lead cross-functional initiatives' beats 'cross-functional initiatives will be led by.'
  3. Avoid corporate-ese. 'Synergy,' 'circle back,' 'deep dive,' 'move the needle' — these phrases have been so overused they signal genericness, not competence.
  4. Name the team and context. 'You'll join a 4-person marketing team and report to the VP of Marketing, who came from HubSpot and runs weekly strategy reviews' — that's a real culture signal, not a generic one.

JD Generator writes in your company's voice — you can set a tone preference (formal, conversational, technical) and it will adjust accordingly. Set up a company profile once and apply it across every JD you generate.

9

Run an Inclusive Language Check

Inclusive language isn't about being politically correct — it's about not accidentally filtering out the best candidate. The research is consistent: gendered language, inflated requirements, and culturally specific idioms all narrow your applicant pool without improving quality.

The three highest-impact checks:

  1. Gender-coded language. 'Competitive' and 'dominate' skew male. 'Nurture,' 'collaborate,' and 'support' skew female. Run your JD through a gender decoder tool before posting.
  2. Experience inflation. As noted above: many '5+ years required' roles are fixable with 3 years of strong performance. The years requirement is often a proxy for judgment that isn't being measured directly.
  3. Cultural assumptions. 'Must be a self-starter' has different meaning across cultures. 'Must be comfortable working autonomously with ambiguous direction' is clearer and less loaded.

The Inclusive Job Descriptions guide has a complete checklist you can use before every posting. JD Generator's bias-check is built in — it flags gendered language, experience inflation, and exclusionary phrasing automatically.

10

Optimize for ATS Scanning and Candidate Experience

Before your job description reaches a recruiter's eyes, it passes through an Applicant Tracking System (ATS). ATSs parse JDs for keywords, rank them against a scoring model, and surface the highest-scoring candidates first. If your JD is formatted chaotically or missing standard section headers, it can score poorly and never reach human eyes.

ATS optimization basics:

  • Use standard section headers: 'About the Role,' 'Responsibilities,' 'Qualifications,' 'Benefits' — not 'What you'll do,' 'What we're looking for,' 'The stuff you know.' ATSs normalize but they don't always parse creative headers correctly.
  • Keyword density without stuffing: Include the actual job title and its common variants. If the role is 'Senior Software Engineer,' include both 'Software Engineer' and 'Senior Software Engineer' — candidates search both, and the ATS reads both.
  • Clean formatting: Simple bullet lists. No tables in the ATS parse field. Plain text in the main body is safer than heavily nested formatting.
  • Mobile readability: 60% of job searches happen on mobile. A JD that renders poorly on a phone loses the candidate before they even read the first word.

The ATS Optimization guide has a full scoring model breakdown and a repair checklist for common ATS scoring failures.

Common Job Description Mistakes (and How to Fix Them)

After reviewing thousands of JDs, these patterns consistently separate filled roles from perpetually open ones:

Common Mistake
The Fix
"Other duties as assigned"

Generic catch-all that tells candidates nothing and signals an underspecified role.

Name the specific scope

"Own the quarterly reporting process, manage vendor relationships for 2 key tools, and lead the weekly all-hands setup"

Common Mistake
The Fix
"Must be able to work in a fast-paced environment"

Every startup says this. It signals nothing and reads as boilerplate.

Quantify the pace and what it means

"We ship product weekly; the engineering team deploys to production 3x per week and handles on-call rotations on a 1-week-per-quarter rotation"

Common Mistake
The Fix
Copy-pasted requirement lists from old JDs

Requirements that haven't been updated since the role was created, many of which are no longer relevant.

Write from scratch for this specific role

Start with the 3 questions in Step 1. Build requirements from the actual problems this hire solves. Run them by your hiring manager and cut anything that doesn't map directly to the role.

Common Mistake
The Fix
No mention of who the role interacts with

Candidates want to know their ecosystem — who do they collaborate with, who do they present to, who do they report to?

Name the cross-functional relationships explicitly

"You'll partner closely with Product, Sales, and Customer Success; you'll present quarterly results to the leadership team; you'll report directly to the VP of Engineering"

Job Description Compliance Guide: EEOC, Salary Transparency, and ADA

Job descriptions are legal documents. They can be used as evidence in discrimination lawsuits, EEOC investigations, and wage disputes. Writing them with compliance in mind isn't optional — it's risk management.

EEOC Requirements

The standard Equal Employment Opportunity statement is required on JDs for employers with 15+ employees. Beyond the legal boilerplate: ensure your requirements are genuinely job-related and consistent with business necessity. The job-relatedness question is the one that matters in litigation, not whether you included the EEOC phrase.

Salary Transparency Laws

As of 2026, 21 states plus multiple cities require salary ranges on job postings. States include CA, CO, CT, WA, NY, RI, MD, NJ, NV, IL, KY, OH, and more. Check your state's requirements — the list expands every year. Even where not required, omitting the range reduces candidate quality and increases offer rejection rates.

ADA Compliance

Job descriptions that include physical requirements (lifting, standing, climbing) must be accurate and must reflect what the role actually requires — not a generic form. If a role is 90% desk work, don't list 'must be able to lift 50 lbs' unless there's a genuine, frequent need. Under ADA, employers must consider accommodations unless the requirement is a genuine business necessity.

Background Checks

If your hiring process includes background checks, you may need to disclose this in the JD depending on state law. Several states (California, Washington, others) have Ban the Box laws that restrict when and how criminal history can be considered. Consult your legal counsel if you operate across multiple states.

For salary transparency specifically, see our Senior-Level Job Descriptions guide which covers compensation benchmarking for senior roles — this is where compliance failures are most expensive because senior-level salary ranges are larger and more scrutinized.

Writing Job Descriptions for Remote and Hybrid Roles

Remote and hybrid roles require five elements most standard JDs omit entirely. Without these, you'll attract candidates who assume location flexibility you don't offer — or miss candidates who assumed you required relocation.

📍

See our complete guide: How to Write Job Descriptions for Remote and Hybrid Roles (2026) — includes location requirement templates, timezone expectation language, equipment policies, and before/after rewrites for remote-specific JDs.

Quick checklist for remote/hybrid JDs:

  • Location statement: Is location unrestricted, restricted to specific states/countries, or hybrid (in-office X days/week)? Be explicit.
  • Timezone expectations: 'Fully async, no set hours' or 'core overlap required 10am–2pm Pacific'? Name it.
  • Equipment policy: What does the company provide? What's the employee's responsibility?
  • Communication tools: Naming Slack, Notion, Asana, or whatever you use signals remote-readiness to candidates who care about async tooling.
  • Remote experience signals: 'We've been fully remote since 2018' or 'Our team spans 12 time zones' tells a candidate this isn't their first remote rodeo.

Salary Transparency Deep-Dive

In 2026, salary transparency is table stakes — not a competitive differentiator. Here's how to do it right:

  1. Start with your compensation band. Not the 'target' or the 'top of the range' — the actual band. What does a junior hire in this role earn vs. a senior hire? The range should encompass that.
  2. Be honest about where you sit in the range. If you're posting a range that tops out below what the market pays for this role, candidates will find out. Better to say 'Budget for this hire is $X, and we're open to above-market for exceptional candidates' than to post a range that undersells.
  3. Separate base from total comp. If there's equity, explain the vesting schedule. If there's a bonus, state the target percentage. Candidates evaluate total comp, not just base.
  4. Note the pay equity policy. If you do regular pay audits and adjust for pay equity gaps, say so. This is increasingly important to younger candidates who research employers.

See our pricing page for more on how JD Generator handles compensation benchmarking for teams managing multiple role levels.

Tools and Resources

The best job description process combines structured thinking, compliance checking, and polished output. Here's what that stack looks like:

JD Generator

Generate bias-checked, ATS-optimized JDs in 60 seconds. Salary transparency built in. Free plan includes 2 JDs/month.

JD Generator Team

Unlimited JDs, shared company profiles, bias-check enforcement across your team. For recruiting teams posting 5+ roles/week.

Inclusive JD Checklist

Complete 22-point checklist for bias-free job descriptions. Used by 400+ recruiting teams.

JD Red Flags Guide

The 12 mistakes that make great candidates skip your listing. Includes a 20-minute fix checklist.

Skip the blank page

Generate a polished, bias-checked, legally compliant job description in 60 seconds. Free plan includes 2 JDs per month — no credit card required.

Create your first JD free →

Frequently Asked Questions

How long should a job description be?
Aim for 600–1,200 words. Under 500 words often lacks the detail candidates need to self-screen. Over 1,500 signals either an underspecified role or requirements inflation. The sweet spot: enough specificity to attract the right person, concise enough to respect their time. JD Generator hits this range automatically while ensuring all critical sections are covered.
Do I legally have to include a salary range on job descriptions?
In 2026, salary transparency laws cover the majority of US workers. California, Colorado, Connecticut, Washington, New York, and 18 other states require salary or wage ranges on all job postings. Federal contractors face additional requirements. Even in states without mandates, omitting the salary range is the #1 reason qualified candidates skip your listing — and it signals a compensation culture problem, not just a compliance gap.
What makes a job description bad?
The five most damaging JD sins: (1) Vague responsibilities like 'handle various tasks' that could describe any job. (2) Inflated requirements — '5+ years required' when 2 years and aptitude would work. (3) No salary range, which filters out both candidates who can't afford to take the risk and quality candidates who know their worth. (4) Generic culture language that tells candidates nothing. (5) 'Fast-paced environment' without specifics — every startup says this. See our full breakdown at the Job Description Red Flags guide.
How do I write a job description for a remote role?
Remote job descriptions need five elements most standard JDs skip: (1) Location requirements or explicit statement that location is unrestricted. (2) Timezone expectations — 'must be available 9am–3pm ET' or 'fully async, no set hours.' (3) Equipment/home-office policy — what does the company provide? (4) Async communication expectations. (5) Remote-readiness signals like 'we've been fully remote since 2019.' See our dedicated guide: How to Write Job Descriptions for Remote and Hybrid Roles.
Should I use a creative or fun job title?
No — unless your company is explicitly anti-corporate and your target candidates are in that culture, creative titles backfire. 'Rockstar Ninja' tells a qualified candidate nothing about what they'd actually do. The search behavior matters: candidates search 'Marketing Manager,' not 'Marketing sorcerer.' Standard titles win on reach; creative titles can work for early-stage startups with strong employer brands.
How do I avoid bias in job descriptions?
Three highest-impact changes: (1) Remove gendered and culturally coded language — 'competitive' and 'dominate' skew male; 'nurture' and 'collaborate' skew female. (2) Replace degree requirements with skills-based alternatives where possible — '4-year degree in CS' can become 'demonstrated proficiency in Python and system design.' (3) Audit years-of-experience requirements — many roles are fixable with 2 years where the listing says 5. Our Inclusive Job Descriptions guide has a complete checklist.
How many bullet points should a job description have?
For responsibilities: 6–10 bullets, no more. For qualifications: 5–7 required, 3–5 preferred. Quality beats quantity — five bullets that describe actual day-to-day work beat fifteen bullets of generic requirements. Recruiters spend an average of 7.4 seconds scanning a JD before deciding to read further. Each bullet must earn its place.
Should I include 'equal opportunity employer' language?
Yes — but the standard EEOC statement is required by law for employers with 15+ employees. Beyond the legal requirement, actions signal more than statements. If your JD includes the EEOC boilerplate but also says 'must be able to lift 50 lbs' for a desk job, candidates notice the gap. Authenticity matters more than the exact wording of your EOE statement.
Should job descriptions mention working hours or flexibility?
Yes — and be specific. 'Flexible hours' means different things at different companies. Some candidates read it as 'always on'; others read it as 'do whatever you want.' Instead say 'core hours 10am–3pm, flexibility outside those windows' or 'fully async, no set hours required.' Remote and hybrid roles especially need explicit expectations about schedule and availability.
What's the difference between a job description and a job posting?
A job description is the internal document: detailed, comprehensive, covers all edge cases, used by HR and hiring managers for evaluation criteria. A job posting is the external marketing version: shorter, more polished, candidate-centric, optimized for search and readability. Most companies treat them as the same thing — that's a mistake. Use your internal JD as the source of truth, but write the external posting for your audience, not for your HR system.
How do I write a job description for a startup vs. an enterprise?
Startups need to signal: speed, ownership, breadth of role, equity potential, and mission. Enterprise JDs need to signal: structure, scale, career path, and benefits. The biggest mistake startup JDs make is over-describing 'wear many hats' (every startup says this); instead, name specific domains someone will own. The biggest enterprise JD mistake is writing for internal HR systems instead of candidate experience.
Can I use AI to write job descriptions?
Yes — and you should. AI job description generators like JD Generator produce bias-checked, ATS-optimized JDs in under 60 seconds. The key is review: AI is a writing partner, not a replacement for domain knowledge. Edit the output to add your company-specific context, culture signals, and the nuances that only you know. The best workflow is AI draft → human refinement → bias check → post. Try JD Generator free.

Conclusion: Write Better JDs, Hire Better People

A job description is the first conversation you have with every candidate. Most companies treat it as a compliance checkbox. The best companies treat it as a competitive advantage — the clearest signal they can send about who they are, what they're building, and what kind of person belongs on their team.

The 2026 job market is candidate-driven in a way it hasn't been before. Salary transparency laws have raised the bar on honesty. ATS optimization has raised the bar on searchability. Skills-based hiring has raised the bar on requirements specificity. The companies that get these right fill roles faster, attract higher-quality applicants, and close offers more reliably.

The steps in this guide aren't complicated — but they require intention. Each one (from salary ranges to inclusive language to ATS optimization) produces measurable improvements in application quality and time-to-hire. Pick one, apply it to your next JD, and track the results. That's how you turn a blank page into a competitive advantage.

Ready to generate your next job description?

JD Generator writes bias-checked, ATS-optimized, legally compliant JDs in 60 seconds. Free plan — no credit card required.

Try JD Generator free →