Writing Job Descriptions That Actually Attract the Right People

A good job description does three things at once. It attracts people who would be great in the role. It deters people who wouldn't. And it captures, in writing, what the company is actually hiring for — which the hiring manager and the recruiter then have to agree on.

Most job descriptions fail at all three. They read like an internal task list pasted into a posting template, full of duties no candidate cares about and requirements no one really meant. The complete step-by-step guide to writing job descriptions is the longer companion to this overview.

What a job description is for

A job description has at least four jobs of its own.

It's a marketing asset — for many candidates it's the first thing they read about the company, and it sets expectations about how serious and thoughtful the employer is.

It's a filter — it should make some candidates self-select out, not just in. A good filter saves everyone time.

It's an internal contract — once it's signed off, it's the document the hiring manager, the recruiter, and HR are all working from. Disagreements at offer stage usually trace back to a fuzzy job description at the start.

It's a legal artifact — depending on jurisdiction, it can affect what counts as a fair process, what reasonable accommodations look like, and how performance is measured later.

If the document you're writing only does one of these things, you're underusing it.

Outcomes versus duties

The single biggest shift you can make is to write outcomes instead of duties.

A duties-based JD reads: Manage the social media calendar. Liaise with internal stakeholders. Prepare weekly reports. It tells the candidate what they'd do but not what success looks like, and it could describe a hundred different jobs.

An outcomes-based JD reads: In your first 12 months, you'll grow our paid social channels from 4 to 7, double inbound leads from social, and produce a quarterly report that the leadership team uses to decide spend. For a worked example of the same idea, compare the standard social media manager job description against an outcomes-led version.

The outcomes version does several things at once. It makes the role concrete. It shows the candidate what they'd be measured on. It forces the hiring manager to be honest about what they actually want — which is harder than listing tasks.

How to write outcomes

Pick three to five things the role exists to deliver in the first year. Not 15. Make each measurable where possible. State the starting point and the target.

Then — and only then — add a short section on the day-to-day, so candidates can picture the work. The day-to-day is context, not the headline. A well-structured role like the operations manager job description shows the pattern in practice.

Must-haves versus nice-to-haves

The fastest way to ruin a JD is to inflate must-haves.

A must-have is something the person literally cannot do the job without on day one. Nice-to-haves are things you'd train, adapt around, or value in a tiebreaker.

Inflating must-haves shrinks your applicant pool and slows everything down. If "5 years of experience" is really "can do the job from day one," say that — and consider whether someone with 3 years and a strong track record qualifies. If "degree in X" is really "knows the fundamentals of X," say that, and accept that there's more than one way to know fundamentals.

The test is simple: would you reject a clearly strong candidate for missing this single thing? If no, it's not a must-have. The same discipline shows up in technical roles too — the data analyst job description is a useful reference for separating real requirements from inflated ones.

Splitting the list

A clean structure: three to five must-haves, three to five nice-to-haves, and nothing else. If your list is longer than that, you're hiding indecision.

Inclusive language

This is not a political topic. It's an effectiveness topic. Inclusive language widens your pool without lowering your bar.

A few principles that move the needle.

Drop coded language. Words like "rockstar," "ninja," "aggressive," and "young, dynamic team" filter out people who would be excellent but read those phrases as not-for-them.

Mind the gendered defaults. Research across multiple markets shows certain phrasings skew the applicant gender mix without intent. Replace "he/him" with "they," and watch words like "dominant," "competitive," "nurturing," "supportive" — not because any are wrong, but because you should choose them deliberately.

Be careful with "required" lists. Long lists of requirements deter candidates who don't tick every box, disproportionately so. Trim hard.

Name accommodations explicitly. A short, plain-language line about how you handle accommodations, accessibility, and flexible working tells candidates what they need to know without making them ask. For senior roles where the language is most loaded, the chief people officer job description is worth contrasting with older templates.

Salary transparency

In most markets the question has shifted from "should we publish pay" to "why wouldn't we."

Stated salary brackets attract more applicants, more relevant applicants, and fewer wildly mismatched ones. They also shorten the recruitment cycle — candidates who see the bracket and decide it's not for them save you a screening call.

If you're going to publish, publish a real bracket. A range that spans 40 percent of base from low to high signals that you don't actually know what you'll pay, which is worse than not publishing at all. Aim for a narrower band and be ready to explain how someone moves through it.

If you can't publish, be specific about why. "We benchmark to market and will share the bracket on the first call" is a reasonable answer. "It depends on experience" is not.

Internal versus external versions

Most companies write one job description and use it everywhere. This is a mistake.

The internal version is the contract — what the role is for, what success looks like, what level it sits at, how it relates to other roles, what the budget is, what the success metrics are. It can be longer and drier. It's read by the hiring manager, HR, finance, and possibly the executive team.

The external version is the marketing — the same role, told from the candidate's perspective. Less about what the company needs and more about what the candidate gets. Shorter sentences. Plainer language. The outcomes, the team, the manager, the trajectory, the bracket.

Write the internal version first. Derive the external version from it. If you skip the internal version, you'll discover six weeks in that the hiring manager and the recruiter were hiring for two different jobs. For roles where this alignment problem is most expensive — like the CEO job description — the internal contract matters more than the external posting.

Tone

Match the tone to the company and the role. A senior finance role and a junior marketing role shouldn't read the same way.

Two rules that travel well.

Sound like a human. Read the JD aloud. If you wouldn't say it in a conversation, rewrite it.

Be specific. Generic language ("fast-paced environment," "exciting opportunity," "passionate team") signals that the writer didn't have anything specific to say. Replace each generic phrase with a concrete one or cut it.

Common job description mistakes to avoid

• Listing 15 must-haves when only four genuinely matter — every extra item costs you applicants
• Copying the previous version of the role without checking whether it's still accurate
• Writing duties instead of outcomes, so candidates can't tell what success looks like
• Burying the interesting parts — team, manager, trajectory, bracket — under boilerplate
• Using language that's been on the company careers page for five years and shows it
• Forgetting that the JD is also a contract with the hiring manager — and signing it off without reading it carefully

Where to go next

A job description is one piece of a hiring process that includes sourcing, screening, interviewing, and offer. A few places to dig in next:

For HR leaders building or refreshing role libraries, the HR generalist job description and the HR director job description are useful side-by-sides for showing how scope shifts across the same function.

When the role is technical, the project manager job description is a good template to adapt — most companies inflate it.

For commercial roles, the sales manager job description is the cleanest worked example of outcomes versus duties.

And when you're hiring a strategic operator, the chief of staff job description shows how to write for a role that doesn't have a standard shape.