How to Write a Job Description That Attracts the Right Candidates

A job description does two jobs at once: it attracts candidates, and it filters them, ideally before either side wastes time on an interview that was never going to work out. Most small business postings only do the first job, listing everything that sounds good, and skip the filtering entirely — which is how a stack of forty applications turns into forty phone screens nobody had time for.

The structure that does both

A specific, searchable title. "Operations Coordinator," not "Operations Ninja" or an internal title nobody outside the company would search for. Cleverness costs you candidates who are searching for the job by its actual name.

A two- or three-sentence summary of purpose, not a list of duties yet — what this role exists to accomplish, and how it fits into the team. This is what a candidate reads first, and it's what tells them in ten seconds whether to keep reading.

Actual day-to-day responsibilities, five to seven of them, written as real tasks rather than abstractions. "Manage vendor relationships and negotiate contract renewals" tells a candidate something. "Support key business functions" tells them nothing.

Requirements, separated honestly from nice-to-haves. This is the section most postings get wrong, and it's covered in its own section below because it matters enough to get wrong carefully.

Salary range. Increasingly a legal requirement, and even where it isn't, it does real filtering work — candidates who need materially more or would accept materially less can self-select before applying, saving both sides an interview that was never going to close.

What makes this role worth taking, specifically — not generic perks language, but something true and particular to this job: real autonomy, a specific growth path, flexibility that's actually offered rather than claimed.

The requirements problem

Listing fifteen requirements when the role genuinely needs five is the most common, most damaging mistake in small business job postings. Research on this consistently shows that candidates — particularly those from groups statistically more likely to under-apply — will skip a posting entirely if they don't meet every listed requirement, even when several of those requirements were never actually essential.

The fix is a genuine split: a short list of things a candidate truly cannot do the job without, and a separate, clearly labeled list of things that would help but aren't disqualifying. "3+ years in a coordinator or admin role" might be a real requirement. "Experience with our specific project management tool" is almost never one — it's learnable in a week and shouldn't cost you a strong candidate who's never used that particular software.

Phrases that quietly repel good candidates

"Fast-paced environment" and "wears many hats" — code, to an experienced candidate, for understaffed and disorganized, whether or not that's actually true of your business.

"Rockstar," "ninja," "guru" — signals a company that prioritized a fun-sounding posting over a clear one, which is a real, if small, negative signal about how seriously the hiring process itself was run.

A wall of generic company boilerplate before the actual role description — by the time a candidate reaches what the job is, they've often already decided not to read further.

Unstated or vague compensation ("competitive salary") — increasingly read as a red flag rather than neutral, since candidates reasonably assume it's being withheld because it's below market.

A fillable template

Title: [Specific, searchable job title]

About the role: [Two to three sentences on purpose and fit within the team]

What you'll do:

• [Responsibility 1]
• [Responsibility 2]
• [Responsibility 3–5]

What you need: [Genuine requirements only — aim for three to five]

Nice to have: [Skills that help but aren't disqualifying]

Salary range: [$X–$Y]

Why this role: [One or two specific, true things about the job or team]

How to apply: [Clear, simple instructions]

Where this connects to onboarding

A job description that accurately reflects the actual role sets up onboarding to succeed rather than immediately disappoint — a new hire who was sold one job and lands in a different one starts their first week already recalibrating trust rather than building it. The onboarding checklist works considerably better when the posting that got someone in the door was honest about what the day-to-day actually involves.

Where the posting gets tested against reality

A job description is also a promise, and the interview process is where a candidate quietly checks whether it holds up. If the posting emphasized autonomy and the interview reveals a manager who describes closely supervising every task, that mismatch is usually noticed — by a good candidate, immediately. Before publishing a posting, it's worth having whoever will actually manage the role read it and confirm it describes the job as it genuinely will be, not as an aspirational version of it. A posting that oversells the role produces exactly the early turnover a business is trying to avoid, once the gap between the pitch and the reality becomes apparent within the first few weeks.

Posting in more than one place

Where a job is posted shapes who applies as much as what it says. A single generic job board often produces a large volume of low-fit applicants for a specific small-business role; a more targeted channel — an industry-specific board, a referral from an existing employee, a professional community relevant to the role — often produces fewer applicants but a meaningfully higher fit rate. For a small business without capacity to screen a hundred applications, that tradeoff usually favors quality of channel over sheer reach.

The short version

A job description should filter as much as it attracts: a specific title, an honest and short requirements list separated clearly from nice-to-haves, a real salary range, and language that describes the actual job rather than a generic version of any job. Getting this right reduces the number of mismatched applications a small business has to sort through, which matters more at a size where there's no dedicated recruiter to do that sorting for you.