A poorly written job description wastes time on both sides of the hiring process. It attracts the wrong applicants, filters out qualified ones, and sets unclear expectations that lead to early turnover. A well-written one does the opposite — it draws in the people most likely to succeed in the role, communicates what the company genuinely expects, and starts the working relationship on an honest footing.
This guide covers what makes a job description effective, how to structure one, and common mistakes that undermine even well-intentioned postings.
Start With a Specific, Accurate Job Title
The job title is the first filter. It determines who clicks on your listing and how it ranks in search results on job boards and aggregators. A few principles:
- Use the most common title for the role, not an internal one. If the internal title is “Client Success Ninja,” post it as “Customer Success Manager.” Candidates search for standard market titles; unusual ones generate fewer clicks and attract candidates who may not be the right match.
- Be specific about level. “Accountant” and “Senior Accountant” attract different pools. “Marketing Manager” and “Marketing Coordinator” attract different experience levels. If the level is not clear from the title, it needs to be in the first line of the description.
- Avoid clickbait titles. “Rockstar Developer Needed!” attracts applicants who do not take the role seriously and wastes both sides’ time.
Write a Clear Role Overview
The first paragraph of a job description should answer three questions in plain language: What is this role? Who does the person work with? What is the broader purpose of the work?
Example of a weak opener: “We are a fast-growing company looking for an energetic team player to join our dynamic marketing department!”
Example of a strong opener: “The Marketing Coordinator supports the marketing team’s content calendar and social media operations, working closely with the content and design teams to produce and schedule material across digital channels.”
The strong version tells a qualified candidate immediately whether the role matches their skills. The weak version tells them nothing except that you like adjectives.
List Responsibilities Specifically and Honestly
The responsibilities section is where most job descriptions go wrong. Common problems:
- Using vague verbs (“assist with,” “support,” “contribute to”) that do not convey what the person actually does
- Listing responsibilities that belong to a different role or level
- Including aspirational responsibilities you hope the person will eventually take on but that are not part of the current role
- Making the list so long that the actual core duties are buried among nice-to-haves
A better approach: lead with the four or five core responsibilities that define 80% of the role’s work. Use concrete action verbs and include enough specificity that the candidate can evaluate whether they have done this type of work before.
Instead of: “Support the HR team with employee relations matters”
Write: “Conduct initial screening calls for open roles, coordinate interview scheduling, and maintain applicant tracking system records for a team that makes 15–20 hires per year”
Distinguish Required From Preferred Qualifications
This distinction is more important than most employers realize. Research consistently shows that underrepresented job seekers — including women and candidates from non-traditional backgrounds — apply only when they meet nearly all stated requirements, while other candidates apply when they meet 60% or fewer. Inflated requirements reduce diversity and narrow your candidate pool without improving quality.
Guidelines for the qualifications section:
- Required qualifications should include only what is genuinely non-negotiable: specific certifications required by law or regulation, years of experience that the role genuinely cannot function without, and hard technical skills the job cannot be done without.
- Preferred qualifications are things you would like but are willing to train or develop. If you have a great candidate who checks eight of ten preferred qualifications, you should be able to hire them. If you cannot, move those items to required.
- Remove degree requirements that are not substantively necessary. Many roles that have historically required a bachelor’s degree do not genuinely need one. Removing unnecessary degree requirements expands your candidate pool significantly.
Include Compensation and Work Arrangement
Several states and cities now legally require salary ranges in job postings. Beyond compliance, including compensation information dramatically improves applicant quality and reduces time wasted on candidates with incompatible expectations.
What to include:
- Pay range (base salary or hourly rate)
- Pay type (hourly vs. salaried, non-exempt vs. exempt)
- Bonus or commission structure if applicable
- Key benefits (health insurance, 401k match, PTO) if competitive
- Work arrangement: fully on-site, hybrid (how many days?), or fully remote
- Shift or schedule information for hourly roles
Candidates evaluate all of these factors simultaneously. A listing that omits compensation forces candidates to guess, and many will pass on listings where they cannot estimate fit before investing time in an application.
Write for the Candidate, Not for the Company
The tone of a job description communicates cultural expectations. A description that is 80% about how great your company is and 20% about what the candidate will actually do signals a culture where the company’s perspective dominates. A description that leads with the candidate’s impact and growth opportunity communicates differently.
Practical test: read the description and count how many sentences start with “We” vs. “You.” A higher “you” count typically indicates a more candidate-centered description.
Be Honest About the Challenges
Every role has less appealing aspects — high-volume email, repetitive tasks, tight deadlines, travel requirements, physical demands. Describing these honestly serves everyone. Candidates who cannot handle those realities self-select out before applying. Candidates who accept them have done so with accurate information and are less likely to leave prematurely when they encounter what you warned them about.
The same care applies once candidates arrive for interview. Our guide to interview questions employers should not ask lists safer, job-related alternatives.
Optimize for Job Board Search
Most job seekers find listings through job boards that index descriptions for keyword search. A few practices improve discoverability:
- Use the standard industry title for the role in the title and first paragraph
- Mention key skills explicitly rather than implying them (write “SQL” not “database experience”)
- Include location clearly — hybrid and remote arrangements should still mention the base city for candidates using location-based search
- Keep the description under 700 words where possible — very long postings perform worse on most platforms
When posting roles, general job boards like AllJobBoard.com reach active job seekers across all experience levels and industries without the per-posting fees of premium platforms.
Review the Description Before Each Hire
Job descriptions should not live in a folder untouched for years. Before posting a role you have hired for before, review the description to confirm it still reflects what the role actually requires. Responsibilities shift, technology changes, and teams evolve. A description written three years ago for a role that has changed significantly will attract the wrong candidates and set incorrect expectations for the actual hire.
Frequently Asked Questions
How long should a job description be?
Most research on job posting performance suggests descriptions in the 300–600 word range perform best on job boards. Descriptions longer than 1,000 words see declining application rates on most platforms. Aim for enough detail to give a qualified candidate a clear picture of the role without overwhelming them.
Should I use bullet points or paragraphs in a job description?
Use bullet points for lists (responsibilities, qualifications, benefits) and short paragraphs for the overview and company description. Avoid walls of text. Job seekers scan rather than read; formatting that supports scanning increases engagement.
Can I legally require a specific degree for every role?
You can include degree requirements, but requiring a degree that is not genuinely necessary for job performance can create legal risk under disparate impact doctrine if the requirement disproportionately screens out protected groups. Courts and the EEOC have scrutinized blanket degree requirements. Use them only where the degree is substantively related to the work.
Should I list a specific salary or a range?
A range is more practical than a specific number and gives you flexibility while setting clear expectations. The range should reflect where most hires would realistically land — posting a range of $50,000–$100,000 to seem open-minded is counterproductive and signals that you have not thought through the role clearly.
How do I write a job description for a new role that has never been filled before?
Start by defining the core problem you are hiring to solve, then work backward to what the person needs to know and be able to do to solve that problem. Talk to peers in similar organizations who have the equivalent role. Look at how competitors describe similar positions. Write a first draft, have someone in the target function or at the target level review it, and revise based on their feedback.