How to Write a Job Description That Attracts the Right Candidates

The job description is the first thing a candidate sees about your opportunity. Before they speak to anyone from your company, before they visit your website, before they form any opinion of you as an employer — they read the job description. And in most cases, they decide within two minutes whether to apply or move on.

The problem is that most job descriptions are not written to attract candidates. They are written to satisfy internal stakeholders, to mirror an old role that no longer exists, or to cover every possible requirement so nobody can be blamed later. The result is a document that reads like a bureaucratic checklist rather than a compelling invitation to consider a new opportunity.

Strong candidates have options. They are not trawling through every listing hoping to find something passable. They are looking for roles that sound genuinely interesting, companies that seem worth working for, and hiring processes that signal competence and respect. A poor job description ends the conversation before it begins.

Why Your Job Description Is the First Filter

Every application starts with the job description. A well-written one attracts candidates who understand what the role involves and believe they can do it well. A poorly written one either attracts everyone (because it's so vague that nobody is disqualified) or nobody worthwhile (because the requirements are so inflated that qualified people self-select out).

The best candidates, particularly those who are already employed and performing well, apply selectively. They look for roles where the description matches what they are actually good at, where the company sounds credible, and where the expectations seem realistic. If your job description reads like it was written in 2018 and copied from a template, those candidates will assume the hiring process will be equally uninspired.

A job description is not just a filter for candidates. It is also a signal about what kind of company you are.

The Mistakes That Cost You Good Candidates

Inflated requirements

The most common mistake is listing every qualification that would be ideal in a perfect world, rather than what you genuinely need. Requiring ten years of experience for a mid-level role, a master's degree for a position that doesn't need one, or fluency in five tools when two of them are learnable in a week: these are the things that stop qualified people from applying. Research consistently shows that women, in particular, tend to self-select out of roles where they don't meet every listed requirement. Men are more likely to apply anyway. If you want a diverse pool of strong applicants, write requirements that reflect reality.

Generic company descriptions

"We are a fast-growing, innovative company with a great culture." Every company says this. None of it means anything to a candidate who is trying to decide whether to invest time in your process. Tell them something specific: what you do, who your customers are, what makes the team interesting to work with, and where the company is headed.

Vague responsibilities

"Drive strategic initiatives and contribute to team performance." This could apply to almost any role in any company. What will this person actually do on a Tuesday afternoon? What decisions will they make? Who will they work with? What will success look like at six months?

Copying the old job description

If someone left the role, the company has almost certainly changed since the job description was written. If it is a new role, you are writing from scratch. Either way, copying an old document is a mistake. The role you need today is not the same role you needed three years ago, and a description that reflects the past will attract the wrong people.

A Structure That Works

There is no single correct format, but the following structure tends to produce better results than the traditional requirements-first approach:

• Company context (2–3 sentences): Who you are, what you do, something specific that makes the company interesting.
• The role in one sentence: What this person will own or lead. Not a list of tasks — a single clear statement of the position's purpose.
• What you will be doing: Four to six specific responsibilities, written as outcomes rather than activities. "Own the sales pipeline and hit agreed revenue targets" is more useful than "responsible for sales".
• What success looks like in the first 90 days: This is unusually specific and almost always appreciated. It signals that you have thought seriously about the role.
• What we are looking for: A short list of genuine requirements, separated from desirable extras. Be honest about what is essential versus helpful.
• What we offer: Salary, benefits, flexibility, growth. Include the things that actually matter to people, not just what is easiest to write.

How to Write Requirements That Don't Overclaim

Before you list a requirement, ask yourself: if a candidate didn't have this, could they still do the role well? If the answer is yes, it should either be listed as desirable or cut entirely.

Separate the list into two sections: what you genuinely need from day one, and what would be a bonus. This is not just semantically honest — it actively changes who applies. Candidates who have most of what you need but not everything on a one-dimensional list will apply more readily if they can see that their profile fits the essential criteria.

Avoid credential requirements that function as proxies for things you can test more directly. If you want someone analytical, describe the analytical problems they will face. If you want someone with good judgment under pressure, say that. Requiring a specific degree from a specific type of institution often says more about assumptions than about what the role needs.

The Salary Question

Include a salary range. Not a vague "competitive package" — a real number or band. The argument for withholding salary is usually that it creates negotiating room. In practice, it filters out good candidates who won't apply without knowing the range, and it generates a wave of applications from people whose expectations turn out not to match, wasting everyone's time.

Salary transparency also signals confidence. A company that publishes its salary range is telling candidates: we have thought about what this role is worth, we pay fairly, and we are not going to waste your time with a bait-and-switch at the offer stage. That is a meaningful signal in a market where many candidates have experienced exactly the opposite.

Tone and Language

Write the way a person talks, not the way a policy document is written. Avoid jargon ("leverage synergies", "thought leader", "rockstar"), buzzwords that have been drained of meaning ("passionate", "dynamic", "results-driven"), and anything that is there to make the company sound impressive rather than to inform the candidate.

Read the finished description back and ask: does this sound like a real person wrote it? Does it give someone a genuine picture of the role? Would you apply for this job if you saw it posted somewhere?

If the answer to any of those is no, rewrite until it is.

Frequently Asked Questions

How long should a job description be?

A good job description is typically 400 to 600 words for the body. Long enough to give a clear picture of the role and company, short enough to hold attention. Avoid padding the requirements section with a laundry list of qualifications that the ideal candidate may not tick perfectly.

Should you include salary in a job description?

Yes. Including a salary range in the job description increases application quality and reduces time wasted on candidates whose expectations don't match. It also signals transparency, which strong candidates value. If you are not comfortable with a precise range, give a realistic band rather than omitting it entirely.

What is the biggest mistake companies make in job descriptions?

The most common mistake is writing the job description for the role you wish existed rather than the role you actually have. This creates inflated requirements that deter good candidates, and unrealistic expectations for whoever you hire. Write honestly about what the role involves, what you need from day one, and what success looks like in the first six months.

---