Writing Effective Job Descriptions

Why It Matters

Your job description is often a candidate’s first interaction with your company. Describe the work, requirements, and pay clearly so candidates can assess the role before applying.

Structure and Length

Start with 200-400 words. In Appcast’s analysis, descriptions containing 201-400 words achieved apply rates of 8-8.5%; above 701 words, rates fell below 5%. These figures describe that dataset. Choose a length that gives candidates the information they need.

Use the 3 R’s framework to organize content:

1. Requirements: Place qualifications first so candidates can self-screen quickly
2. Responsibilities: Focus on outcomes and goals, not minute-by-minute task lists
3. Rewards: Close with compensation, benefits, and culture

Formatting for Mobile

Candidates also read job postings on phones. Make the text easy to scan:

• Keep paragraphs to 3-4 sentences
• Use bullet points for lists (aim for ~30% of content)
• Add clear headings so candidates can scan non-linearly

Do	Don’t
Target 200-400 words	Exceed 700 words
Use the 3 R’s order	Bury requirements at the bottom
Use bullet points and short paragraphs	Use walls of unbroken text
Focus on the top 5-7 tasks and requirements	Copy-paste internal HR job specs

Language and Tone

Use Gender-Neutral Language

Describe skills and responsibilities without assigning them to a gender. Help candidates assess the work rather than whether they match a personal stereotype suggested by the posting.

Use instead	Avoid
collaborate, build, manage	ninja, rockstar, dominant, aggressive
culture add	culture fit
proficiency in	native speaker

Be Inclusive

• Replace physical requirements with outcomes: “Move throughout the warehouse” instead of “Must be able to walk”
• Avoid age-signaling terms: “digital native,” “recent grad,” “young team”
• Skip idioms that may confuse non-native speakers (“hit the ground running,” “wear many hats”)

Write in Active Voice

Use “You will lead the sales team” rather than “The sales team will be led by the successful candidate.” Active voice is more engaging and concise.

Mix “We” (company culture) and “You” (role duties). Avoid “The Ideal Candidate.”

Requirements and Qualifications

Separate Must-Have from Nice-to-Have

Separate essential requirements from additional strengths. Candidates should be able to tell what they need to do the job and what they can learn after joining.

• Required: Limit to 3-5 bullets, only non-negotiable skills, licenses, or logistical needs
• Preferred: 3-5 bullets, skills that are beneficial but learnable on the job

Prefer Skills Over Credentials

Unless legally required (medicine, law), replace degree requirements with demonstrated skills. “Demonstrated proficiency in Python and software architecture” is better than “Bachelor’s degree in Computer Science required.”

Do	Don’t
Separate Required from Preferred	Mix essential and bonus skills in one list
Limit total requirements to 6-10 bullets	List 15+ requirements
Focus on skills and outcomes	Require degrees unless strictly necessary
Use growth-oriented language	Demand expertise in everything upfront

Compensation and Benefits

Include a Salary Range

Publish the range so candidates can compare the offer with their expectations before starting interviews.

• Use a realistic band with its currency and period (e.g., “$80,000-$100,000 USD per year based on experience”)
• State whether the range is base salary or total compensation
• Avoid overly broad ranges (e.g., “$50,000-$150,000 USD per year”) that say little about the expected offer

Make Benefits Specific

Describe what each benefit includes. For health coverage, for example, explain the consultations and tests covered and whether family members are eligible. List only benefits your company provides.

Job Titles and SEO

Use standard, searchable titles. Candidates search for “Software Engineer,” not “Code Ninja.” Unusual titles make the role harder to recognize.

• Be specific about location: city/state, “Remote,” or “Hybrid (2 days onsite in Chicago)”
• Include the top 5-10 relevant skills naturally in the text
• Avoid keyword-stuffing long lists of technologies at the bottom

Common Anti-Patterns

Anti-Pattern	Why It Fails	Fix
Wall of text	Unreadable on mobile, signals bureaucracy	Use headers, bullets, short paragraphs
Pasted internal job spec	Contains irrelevant codes, no candidate appeal	Rewrite as a marketing document
Laundry list of technologies	Signals unclear role or “Frankenstein job”	List 3-5 core technologies, rest as nice-to-have
Threatening language (“not for the faint of heart”)	Red flag for toxic culture	Describe pace objectively
Unrealistic requirements (“10 years with a tool released last year”)	Undermines employer credibility and discourages candidates	Verify requirements with a subject matter expert

Quick Checklist

Before publishing, verify:

• Title is standard and searchable
• Word count is between 200-700 words (ideally 200-400)
• Structure follows Requirements, Responsibilities, Rewards
• Formatting uses bullets (~30% of text) and short paragraphs
• Language is gender-neutral (no “ninja,” “rockstar,” “aggressive”)
• Must-haves are limited to 5 or fewer essential items
• Physical requirements describe the tasks without omitting genuine job requirements
• Salary range is included and realistic
• Voice is active (“You will…”) using “We” and “You”
• Location is specific (City, State / Remote / Hybrid)