Crafting Job Descriptions That Attract Quality Candidates

Why Your Job Description Is Your Most Underrated Hiring Tool

Most small business owners spend more time writing a product description than a job description — and then wonder why they keep interviewing the wrong people. A job description that works hard for you does several things at once: it filters out poor-fit candidates before they ever apply, it sets the foundation for how you’ll evaluate and onboard whoever you hire, and it communicates your company’s standards from the very first touchpoint.

This chapter walks through how to build a job description that does all of that, not just check a box.

Understand What the Job Description Actually Has to Do

Before you write a single bullet point, get clear on the four jobs your job description is doing simultaneously.

• Attraction: It needs to make the right candidates want to apply and give the wrong ones a clear reason not to.
• Clarity: It defines what success in the role actually looks like, which becomes the basis for your interview questions, onboarding plan, and performance reviews.
• Legal grounding: A well-written description documents the legitimate requirements of the role, which matters if you ever face a hiring discrimination complaint or need to justify a termination decision.
• Brand signal: For many candidates, this is the first thing they read about your company. The tone, precision, and priorities you show here tell them what kind of place you are.

When you keep all four of these functions in mind, you stop treating the job description as an afterthought and start treating it as the strategic document it is.

Start With a Role Analysis, Not a Title

The most common mistake is opening a blank document and typing a job title at the top, then free-associating from there. Instead, spend twenty to thirty minutes answering these questions before you write anything:

• What specific outcomes do I need this person to produce in their first ninety days?
• What does this person do on a typical Tuesday?
• What decisions will they make independently versus bring to me?
• What skills or credentials are genuinely required to do this job safely and effectively, versus which ones would just be nice to have?
• What has made past people in this role succeed or fail?

This exercise forces you to separate what you actually need from what you’ve always assumed you need. A lot of small businesses discover they’ve been requiring a four-year degree for a role that has never once required one, or listing ten years of experience for a job a strong three-year candidate could do well. Those kinds of bloated requirements quietly shrink your applicant pool without improving hire quality.

Structure the Description So It Filters, Not Just Informs

A well-structured job description moves from broad context to specific requirements in a deliberate order. Here’s a practical structure that works for most roles.

1. The Role Summary (3–5 sentences)

Open with what the role is, how it fits into your business, and what a successful person in it will accomplish. Skip the generic filler like “we are a fast-paced, dynamic company.” Write something true and specific. For example: “We run a twenty-person bookkeeping firm serving independent contractors and freelancers. Our Client Success Associate handles the ongoing relationship with roughly 80 active clients, making sure their books stay clean and their questions get answered within one business day. This role is the main reason our clients renew.”

That last sentence matters. It tells the candidate their work is consequential, not just administrative.

2. Core Responsibilities

List five to eight responsibilities in plain language. Use active verbs and be specific about scope. Instead of “manage social media,” write “plan and publish four posts per week across Instagram and LinkedIn, respond to comments daily, and produce a monthly performance summary.” The more specific you are, the more candidates can honestly self-assess whether this is work they’re equipped and motivated to do.

Avoid listing every possible task the person might ever touch. That creates noise and makes the role look chaotic. Focus on what the role is fundamentally about.

3. Requirements vs. Preferences

Divide your qualifications into two clear buckets: what is genuinely required, and what would be a plus. Be honest with yourself about which is which. Required qualifications are things without which the person simply cannot do the job safely, legally, or effectively. Preferred qualifications are things that would reduce ramp-up time or add value but are learnable on the job.

Keeping these lists separate does two things: it signals that you’ve thought carefully about the role rather than just copy-pasting from a template, and it gives strong candidates who don’t check every preferred box the confidence to apply anyway.

4. Compensation and Key Logistics

State the salary range, whether the role is full-time or part-time, where it’s located or whether it’s remote, and any scheduling requirements. Omitting compensation is increasingly a deterrent for serious candidates, who have plenty of roles to consider and limited time to invest in a process that may not fit their needs. Listing a range, even a broad one, is better than silence.

5. A Short Company Statement

Two to four sentences about your company — what you do, who you serve, and what it’s like to work there. Keep it honest. Candidates have become good at recognizing culture-speak that means nothing. Something straightforward like “We’re a ten-person team, entirely remote, and we value getting work done well over long hours or busy appearances” will resonate more than a paragraph about passion and innovation.

Write for the Candidate You Actually Want

Think concretely about the person you’re trying to attract and write directly to them. This shapes your word choice, your level of detail, and your tone.

If you’re hiring for an experienced operations manager, they don’t need you to explain what KPIs are. If you’re hiring for an entry-level customer support role, you can be encouraging about applications from people who are newer to the workforce. If the role requires deep technical skill, use the precise vocabulary of that field — vague language signals to specialists that you don’t really understand the work.

Also consider the level of autonomy the role involves. If this person will be making judgment calls independently, say so explicitly. High-autonomy language attracts self-directed candidates and filters out people who need more structure. If the role is highly process-driven and collaborative, say that instead. Neither is better — they’re just different, and the right candidate for each is different too.

Common Mistakes That Cost You Good Candidates

Even well-intentioned job descriptions regularly make a handful of mistakes worth avoiding.

• Requirements inflation: Asking for more experience, credentials, or skills than the role actually needs. This disproportionately filters out women and candidates from underrepresented groups, who research suggests are more likely to screen themselves out if they don’t meet every listed requirement.
• Vague responsibilities: Phrases like “support the team,” “assist with projects,” or “handle various tasks” tell a candidate almost nothing. They also make it impossible to evaluate someone against the role later.
• Culture code language: Phrases like “must be a rockstar,” “entrepreneurial spirit required,” or “we work hard and play hard” communicate very little while signaling a culture that may put off exactly the experienced, grounded professionals you want.
• Enormous bullet-point lists: A job description that runs to forty bullet points across eight sections looks like it was assembled by committee with no clear thinking about what actually matters. It exhausts the reader and buries the most important information.
• Passive or bureaucratic language: If your description reads like it was generated from a compliance template, the candidates who are in demand will skip to the next posting. Write like a human is hiring another human.

Use the Job Description Beyond the Hiring Process

A job description that’s carefully built doesn’t get filed away after you make a hire. Put it to work.

Use the core responsibilities section as the backbone of your onboarding checklist. Use the required qualifications as criteria in your interview scorecard. Schedule a review of the description at the three-month and twelve-month marks: is this person actually doing what the description said? Has the role evolved? If there’s a significant gap, either the description was off to begin with or the role has grown and the description needs to catch up. Both are worth knowing.

When a role opens again — whether due to turnover or growth — a maintained, accurate job description means you’re not starting from scratch. You’re refining something that already reflects what the role actually is.

The Practical Takeaway

Set aside an hour for this — not fifteen minutes. Work through the role analysis questions before you open a blank document. Build the description in the five sections outlined here. Read it once from the perspective of the candidate you want to attract and once from the perspective of the candidate you want to screen out. If both filters are working, you’re ready to post.

The job description is the first real test of whether you know what you’re looking for. Get it right, and the rest of the hiring process gets easier at every step.

Related reading

• Crafting Job Descriptions That Attract the Right Talent
• Complete Guide: Small Business HR Playbook: Job Descriptions, Interviews & Onboarding for Growing Teams
• Complete Guide: The Small Business Hiring Playbook: Essential HR SOPs for Growing Teams
• Interview Kits for Non-HR Managers
• Foundation Setting: Your First HR Infrastructure