How to Write a Job Description That Gets Applicants

Why Job Descriptions Are Your First Filter (and Your First Impression)

A job description is not a bureaucratic formality. It is the first touchpoint between your company and every potential candidate who sees the role. It answers three questions every candidate asks within the first 10 seconds of reading: What would I actually do? Do I qualify? Is this worth my time?

The stakes are high. LinkedIn's research shows that job seekers spend an average of 14 seconds deciding whether to apply after landing on a job posting. A poorly written description - vague, bloated with requirements, or missing salary information - sends qualified candidates elsewhere.

Conversely, a well-crafted job description does three things simultaneously: it attracts the right candidates, it self-selects out the wrong ones (saving your screening time), and it sets accurate expectations that reduce first-year attrition. The quality of your hiring class begins with the quality of your job posting.

This guide walks through every section of a high-performing job description - what to include, how to write it, and what to remove - with before/after examples for the sections teams get wrong most consistently.

The Anatomy of a High-Performing Job Description

A job description has seven functional sections. Each serves a specific purpose. Skipping or merging sections is where most teams go wrong.

1. Job Title

The job title is the single highest-impact element of your posting. It determines whether your role appears in search results, whether candidates click on it, and whether they share it with qualified friends.

Rules for effective job titles:

• Use the title people search for - not your internal naming convention. "Revenue Operations Specialist" will get fewer relevant applicants than "Sales Operations Analyst" if the latter is what candidates search. Check search volume via LinkedIn Insights or Google Trends before finalizing.
• Avoid invented portmanteaus. "Marketing Ninja", "Customer Success Rockstar", "Growth Hacker" are all searchable but attract candidates who value novelty over craft. If you want senior professionals, use senior professional titles.
• Include seniority level explicitly: "Junior", "Senior", "Lead", "Principal", "Director". This is the fastest self-selection filter you have.
• Keep it under 60 characters. Longer titles truncate in search results and on mobile.

2. Role Summary (2–4 Sentences)

The role summary appears directly under the title and is the second thing a candidate reads after deciding to click. Its job is to answer: What does this person do and why does the role exist?

Write it from the candidate's perspective, not the company's. Instead of "We are looking for a talented individual to join our growing team," write "You will own the end-to-end demand generation function for our EMEA market, building pipeline for a 12-person enterprise sales team."

The best summaries include: (1) the core function, (2) the team or business context, (3) the impact the role has. Four sentences maximum. This is not the place for company history.

3. Responsibilities

This is what the person will do, day-to-day and week-to-week. It is the most important section for candidate qualification - and the one most frequently written badly.

How to write responsibilities well:

• Start each bullet with an action verb in present tense: "Own", "Build", "Manage", "Analyze", "Partner with", "Define". Not "Responsible for" or "Will be expected to".
• Be specific about scope and output. "Manage social media" is useless. "Own organic social strategy across LinkedIn and Twitter for the UK market, targeting 20% quarterly follower growth" is useful.
• List 6–10 bullets. Fewer than 5 suggests you do not know what the role does. More than 12 suggests the role is overstuffed or you are listing tasks instead of responsibilities.
• Sequence from most important to least. Put the critical success factor first - candidates weight the first few bullets most heavily.

4. Requirements (Must-Haves vs. Nice-to-Haves)

Requirements are what a candidate must bring to the role before day one. This section requires the most discipline to write well - because the instinct is always to list more, not less.

Separate must-haves from nice-to-haves explicitly. Call them exactly that: "Requirements" and "Nice to Have" (or "Preferred"). This is not a stylistic choice - it directly affects application volume. Research from Harvard Business Review shows that women apply to jobs when they meet approximately 100% of listed requirements, while men apply at 60%. When everything is listed as a requirement, you are implicitly filtering by gender.

Audit each requirement against two questions:

1. Would the best candidate I have ever hired for a similar role actually have this?
2. If a candidate lacked this, could they realistically learn it in their first 3 months?

If the answer to question 1 is sometimes "no" or the answer to question 2 is "yes", it belongs in nice-to-haves.

Requirement inflation checklist - remove these unless genuinely required by the role:

• "Degree required" - for roles where a portfolio or work sample would serve equally well
• "X years experience" - replace with competency-based criteria where possible ("demonstrated ability to...")
• Specific software tools that could be learned in a week
• "Excellent communication skills" - this is assumed for all roles; remove it

5. Compensation and Benefits

This is the section most companies still get wrong in 2026 - either by omitting it entirely or by providing a range so wide as to be meaningless ("$50,000 – $150,000").

The case for salary transparency: LinkedIn data shows job postings with salary ranges receive 30–40% more applications than those without. Candidates who apply knowing the range are better-qualified leads - they have already self-selected as interested at that compensation level. This reduces wasted screening time for both parties.

What to include:

• Base salary range (keep the spread to ±15–20% to signal you know what you are willing to pay)
• Equity, if offered (at least describe the structure - options, RSUs, percentage range)
• Key benefits: health coverage, pension/retirement, PTO policy, remote/hybrid arrangement, parental leave
• Performance bonus structure, if applicable

Legal note: Several US states (Colorado, New York City, California, Washington) now legally require salary range disclosure in job postings. This trend is expanding. Even where not legally required, voluntary disclosure is now a competitive differentiator for attracting candidates who have multiple options.

6. Company and Culture Section

Every candidate evaluating your role is also evaluating your company. The culture section is where you help them make that decision with accurate information - not marketing copy.

The worst version of this section reads: "We are a fast-paced, innovative startup that values collaboration and excellence." It communicates nothing. Every company says this.

A useful culture section answers specific questions: How does the team make decisions? What does a typical week look like? What does good performance look like in the first year? What makes this a better opportunity than a comparable role at a competitor?

Keep it to 3–5 sentences or 3–5 bullets. Be honest. A candidate who joins based on an accurate company description will stay longer than one who joins based on aspirational marketing and finds a different reality.

7. Application Process and Timeline

Describe what happens after a candidate applies. How many interview rounds? What does each round involve? What is the expected timeline? Will there be a technical test or take-home project?

This section reduces candidate anxiety, improves completion rates, and signals organizational respect for candidates' time. A simple four-line paragraph covering these points can meaningfully improve application rates and reduce candidate ghosting at later stages.

Inclusive Language: What to Remove and What to Add

Language in job descriptions systematically attracts or deters candidates from underrepresented groups, often without the author's awareness. This is not a political position - it is a measurable effect on application volume from the talent pools you are trying to reach.

Words to audit and often remove:

• Masculine-coded words (Gaucher et al., 2011): "aggressive", "dominant", "driven", "competitive", "strong", "independent". These correlate with lower female application rates.
• Performative culture words: "rockstar", "ninja", "guru", "hacker". These attract junior/novelty-seeking profiles and deter senior professionals.
• "Culture fit": This phrase is a documented proxy for in-group bias. Replace with "culture contribution" or describe the specific values and behaviors you are looking for.
• "He/she": Replace with "they" or rewrite the sentence entirely to avoid gendering.

What to add:

• An explicit equal opportunity statement
• Accommodation language: "We are happy to accommodate accessibility needs - please let us know"
• A note if the salary range is the same for all candidates regardless of negotiation (increasingly valued)

5 Common Job Description Mistakes That Hurt Application Volume

Mistake 1: Writing It for the Hiring Manager, Not the Candidate

The hiring manager knows exactly what the role involves. Candidates do not. Every sentence should pass the test: "Does this tell a stranger something useful about whether to apply?" Internal acronyms, team names, and project codenames fail this test. Rewrite for someone who does not work at your company yet.

Mistake 2: Making It Too Long

Research from Textio and LinkedIn consistently shows that job descriptions over 900 words see significantly lower application rates. Anything beyond what is needed to answer "what do I do, do I qualify, and what do I get paid" is wasted words. Edit ruthlessly. The final version should not exceed 700 words for most roles.

Mistake 3: Listing Requirements Without Prioritizing Them

When every requirement looks the same weight, candidates cannot tell what actually matters. A candidate with 4 of your 5 requirements may be excellent - but if they cannot distinguish which 4 are critical and which is a nice-to-have, they may not apply. Use the must-have / nice-to-have separation every time.

Mistake 4: Omitting Remote/Hybrid Policy

In 2026, candidates filter by remote availability before reading the rest of the posting. If your posting does not state the location and work arrangement in the first paragraph, you lose a significant portion of candidates before they engage with the content. State it clearly and early: "Remote (US time zones)", "Hybrid - London office 2 days/week", "On-site - [City]".

Mistake 5: Using the Same Description for Every Opening of the Same Role

Copying last year's job description for a new opening seems efficient but produces worse results over time. Requirements drift (tools change, team structures evolve), calibrations shift, and the role the team actually needs may differ from the one documented 18 months ago. Invest 30 minutes per new opening to review and update each section with the hiring manager. The improvement in applicant quality is consistently worth it.

Using AI to Write Job Descriptions

AI-powered job description generators - including Treegarden's built-in tool - can dramatically accelerate the drafting process. You provide the role title, key responsibilities, and requirements, and the AI generates a structured, inclusive first draft that follows best practices.

The value of AI here is not in replacing human judgment but in eliminating blank-page paralysis and ensuring structural completeness. The output still requires review and customization - particularly for the culture section, compensation details, and any highly specialized technical requirements.

Treegarden's AI job description generator is available directly within the platform when creating a new job. You can generate, edit, and publish to multiple job boards in one workflow - without switching between tools. See also the ATS buyer's guide for how job description management fits into the wider ATS feature set.

Publishing, Multiposting, and Ongoing Optimization

A great job description that lives only on your careers page will underperform. Effective distribution is as important as effective writing.

Where to publish: Your careers page (always), LinkedIn (highest volume for most roles), Indeed (high volume, particularly for non-technical roles), industry-specific boards relevant to your role, and Google for Jobs (automatic if your careers page has proper structured data).

Multiposting: An ATS like Treegarden lets you publish one job description to multiple boards simultaneously from a single interface - without manually recreating the posting on each platform. This saves 45–90 minutes per role and ensures consistency.

Optimization over time: After 2–3 weeks, review your application volume and quality. If volume is low, the issue is usually the title or the top of the description. If volume is high but quality is low, the requirements section is too broad. If volume is high but offer acceptance is low, the compensation or culture section is misaligned with market expectations. Each metric gives you a specific diagnosis.

Frequently Asked Questions

How long should a job description be?

Research consistently shows 300–700 words is the optimal range, with 400–600 words being the sweet spot for most roles. Descriptions shorter than 200 words lack enough information to qualify candidates; those exceeding 900 words see meaningfully lower application rates. Shorter is almost always better once all required sections are covered.

Should you include salary in a job description?

Yes. Postings with salary ranges receive 30–40% more applications than those without, and the candidates who apply are better-qualified leads (they have already self-selected). Several US states now legally require salary disclosure. Even where it is not required, transparency is increasingly a competitive differentiator for attracting professionals with options.

What is requirement inflation?

Requirement inflation is listing more qualifications than the job actually requires - such as demanding a degree for a role that does not need one, or requesting 5+ years for a role where 2–3 years of demonstrated competency is genuinely sufficient. It disproportionately filters out women, career-changers, and candidates from underrepresented backgrounds, and reduces application volume without improving quality.

What is the difference between responsibilities and requirements?

Responsibilities describe what the person will do in the role. Requirements describe what they must bring to the role before starting. These are two distinct things and should be presented as separate sections. Mixing them creates scanning difficulty for candidates and confusion about what the role actually involves.

How do you write an inclusive job description?

Use gender-neutral language, avoid masculine-coded words (aggressive, dominant, competitive in the cultural sense), audit requirements to remove unnecessary thresholds, include an explicit equal opportunity statement, and add accommodation language. Tools like Gender Decoder can flag problematic language automatically.