Recruitment19 min read

How to Write Job Descriptions That Actually Attract the Right Candidates

Klearskill TeamApril 15, 2026

Seventy-two percent of hiring managers say they receive applications from candidates who are clearly unqualified for the role. The culprit, more often than not, is a poorly written job description that either fails to communicate what the role actually requires or is so full of vague corporate language that it attracts everyone and filters out no one.

Knowing how to write job descriptions that genuinely serve your hiring process is one of the highest-leverage skills in recruitment. A strong job description does three things simultaneously: it draws in the candidates you want, it discourages those who are a poor fit, and it sets the foundation for a structured, defensible screening process. A weak one wastes everyone's time and undermines your employer brand before a single candidate has spoken to a recruiter.

This guide covers everything you need to write job descriptions that work - from structure and language to the specific signals that tell candidates whether they belong in your process.

Why Most Job Descriptions Fail

Before examining what good looks like, it is worth understanding what typically goes wrong.

According to LinkedIn's 2025 Global Talent Trends report, the average job description contains between 700 and 900 words, yet most candidates spend fewer than 60 seconds deciding whether to apply. That gap between what hiring teams write and what candidates actually absorb explains a lot about recruitment inefficiency.

Several patterns repeat across organisations that struggle with job description quality:

Copying last year's posting. Roles evolve, but job descriptions rarely do. You end up advertising a role that no longer exists.
Writing for HR, not for candidates. Internal jargon, compliance-driven language, and hierarchical titles that mean nothing to an external audience.
Listing every possible task. A responsibility section with 20 bullet points signals a lack of clarity about what the role actually entails.
Inflating requirements. Asking for a degree when experience would suffice, or demanding five years of experience in a technology that is only three years old.
Ignoring the employer brand. Generic descriptions that could belong to any company in any sector give candidates no reason to prefer you.

SHRM research found that 64% of job seekers say a poorly written job description makes them less likely to apply, even when the role itself appeals to them. That is a significant pipeline loss happening before your first screening call.

The Anatomy of an Effective Job Description

A job description that converts the right candidates and filters out the wrong ones has a consistent structure. Each section serves a specific purpose - remove one and the whole document becomes less effective.

Job Title

Your job title is the most-searched element of your posting. It needs to be clear, accurate, and aligned with how candidates actually search for roles. This is not the place for creative internal titles.

According to Indeed's hiring lab data, job titles between two and four words receive 30% more clicks than longer alternatives. "Senior Account Executive" outperforms "Senior Account Executive - EMEA Region Growth Division - UK Based." Give candidates enough information to recognise the role without burying it in qualifiers.

Practical rules for job titles:

Use standard industry terminology, not internal codes or acronyms
Avoid superlatives like "rockstar", "ninja", or "guru" - they attract mockery, not applications
Include seniority level only if it genuinely distinguishes the role from others on your careers page
Avoid gender-coded language - roles titled with masculine-associated words receive measurably fewer applications from women, according to research published in the Journal of Personality and Social Psychology

Opening Summary (2-3 Paragraphs)

This is the section candidates read first and most carefully. It should answer three questions immediately: what does this company do, what does this person do, and why does this role matter.

Avoid opening with the company's founding year or a list of awards. Candidates want to know about the role. Give them context about the team, the challenge the person will own, and the scale of impact they can expect.

A strong opening paragraph might read: "We screen over 50,000 applications per year for mid-market businesses across the UK. This role sits at the centre of that operation - you will build the workflows, manage the client relationships, and eventually lead a team of four analysts."

That tells a candidate far more than "We are a leading provider of innovative solutions seeking a talented professional to join our dynamic team."

Responsibilities: The Core of the Role

This section should describe what the person will actually do on a day-to-day basis, prioritised by where they will spend most of their time. Aim for six to ten bullet points, not twenty. Each bullet should begin with an action verb and describe an outcome, not just a task.

Weak: "Responsible for managing the onboarding process."

Strong: "Design and maintain a 30-60-90 day onboarding programme for new sales hires, tracking ramp time and first-quarter quota attainment as key success metrics."

The stronger version tells candidates what they will do, how they will do it, and what success looks like. CIPD guidance on role design consistently recommends anchoring responsibilities to outcomes rather than activities, as this produces clearer performance expectations and better candidate self-selection.

Group responsibilities by theme if the role is complex. A Head of People role might have separate clusters for talent acquisition, employee experience, and HR operations. This organisation makes it easier for candidates to assess whether they have the relevant breadth.

Requirements: Non-Negotiable vs. Preferred

This is the section most likely to inadvertently filter out good candidates. The discipline here is in distinguishing what is genuinely required from day one versus what would be helpful but can be learned.

A useful exercise: for each requirement, ask "if a candidate had everything else on this list but not this specific item, would we reject them outright?" If the answer is no, it should be in the "nice to have" column.

McKinsey's research on skills-based hiring found that organisations which removed unnecessary degree requirements saw a 14% increase in the diversity of their applicant pool with no measurable decline in hire quality. Credential inflation - requiring qualifications that do not actually predict job performance - is one of the most common and most correctable problems in hiring.

Format requirements in two distinct lists:

Essential (we will not hire without these):

Specific software proficiency or certifications where genuinely required
Years of experience in a specific domain where ramp time would make the hire unviable
Legal requirements (right to work, professional licence)

Desirable (we actively look for these):

Industry exposure that would accelerate onboarding
Additional skills that stretch the role's impact
Specific sector or company-size experience

This separation does something subtle but powerful: it tells strong candidates who lack one "nice to have" item that they should still apply. Without that separation, many will self-reject unnecessarily.

Salary and Benefits

This is the most debated section in job description design, and the evidence increasingly favours transparency.

LinkedIn's data shows that job postings that include salary ranges receive 30% more applications than those that do not. More importantly, the quality of applicant self-selection improves when candidates have the information they need to make an informed decision before applying.

In the UK, while salary transparency is not yet universally mandated (unlike several US states), CIPD advocacy for pay transparency is growing and more organisations are choosing to include it proactively. Candidates who reach interview stage and then discover the role pays below their expectation waste everyone's time. Transparency eliminates this friction.

Beyond salary, describe the benefits that are genuinely differentiated. Pension contributions, equity schemes, flexible working arrangements, and development budgets are the items candidates actually weigh when comparing offers. "Vibrant culture" and "friendly team" are not benefits - they are noise.

Company and Team Context

Candidates are evaluating your organisation just as much as you are evaluating them. A short section on the team structure, the company's stage, and what makes the working environment distinct helps candidates make that assessment.

Specifics matter here more than anywhere else. "We are a 40-person Series B company" tells a candidate something real. "We are a fast-growing innovative company" tells them nothing.

If your company has a specific working pattern - fully remote, hybrid with set in-office days, or fully co-located - state it plainly. According to Gartner research on employee preferences, flexibility arrangements are among the top five factors candidates consider when choosing between job offers. Withholding this information until late in the process is increasingly a candidate experience failure.

Language and Tone: The Signals You Send Without Realising

The words you choose in a job description communicate as much as the content itself. Research from Textio's language analysis platform - which analyses millions of job postings and their outcomes - consistently finds that specific language patterns correlate with both application volume and applicant diversity.

Some patterns to actively avoid:

Aggressive performance language - phrases like "relentless," "crushing targets," and "only the best need apply" correlate with lower application rates from women and candidates from underrepresented groups. They also tend to attract candidates who are over-confident relative to their actual qualifications.

Vague superlatives - "excellent communication skills" appears in approximately 80% of all job descriptions, according to Indeed's data. Because it is ubiquitous, it conveys nothing. If communication matters for the role, specify what kind and in what context: "presenting to C-suite stakeholders," "writing technical documentation for non-technical audiences," or "managing difficult conversations with underperforming direct reports."

Undefined cultural markers - "culture fit" as a requirement in a job description is both legally risky and practically meaningless. If you want to describe the working culture, describe it behaviourally: "we hold weekly retrospectives and expect team members to flag problems early rather than solve them alone."

Passive voice - "The successful candidate will be responsible for..." is weaker than "You will own..." and significantly weaker than "You will build the process from scratch, with no legacy systems to work around." Active, specific language creates a clearer picture and reads faster.

British English conventions apply throughout: optimise rather than optimize, behaviour rather than behavior, programme rather than program (for learning or development contexts), whilst and amongst where appropriate.

Job Description Formats: Which Works Best for Your Role

Not all roles benefit from the same format. The table below compares the most common approaches across key criteria:

Format	Best For	Application Volume	Screening Efficiency	Candidate Quality
Long-form (700-1000 words)	Senior, specialist, complex roles	Lower, more targeted	High	High
Short-form (300-500 words)	High-volume, entry-level roles	Higher, less filtered	Lower	Moderate
Skills-first (requirements up top)	Technical, skills-intensive roles	Moderate	High	High
Culture-first (company story up top)	Brand-led, early-stage companies	Higher	Moderate	Moderate
Outcome-based (results not tasks)	Sales, commercial, measurable roles	Moderate	Very high	High

The outcome-based format deserves particular attention. Rather than listing what a person will do, it describes what they will achieve. "Generate £1.2M in new business revenue in year one" is a responsibility statement that tells a senior sales candidate everything they need to know about the expectation - and tells you something about who applies.

For most professional and managerial roles, a long-form structured description will outperform a shorter alternative because it gives candidates more signal about fit. The drop in raw application volume is offset by the improvement in applicant quality.

Inclusive Language: Why It Affects Your Candidate Pool

Inclusive language in job descriptions is not just an ethical preference - it is a commercial one. Organisations that audit and improve the inclusivity of their job descriptions consistently report broader applicant pools and improved hiring outcomes.

Research from Stanford University found that job postings using masculine-coded words (dominant, competitive, assertive) received fewer applications from women, even when the role itself was gender-neutral. Conversely, postings using more communal language attracted a more balanced applicant pool without sacrificing quality.

Practical changes with measurable impact:

Replace "he or she" with "they" throughout
Audit for words like "aggressive," "dominant," "ninja," "guru," and "rockstar" - remove them
Avoid references to "young," "energetic," or "digital native" which can constitute age discrimination
Where physical requirements are not genuine occupational requirements, do not include them
Consider whether your educational requirements reflect actual job needs or historical assumptions

The Equality Act 2010 in the UK prohibits discrimination in recruitment based on protected characteristics. Job description language that implies a preference for candidates of a particular age, sex, or background creates legal risk alongside the talent cost.

The Screening Connection: How Your JD Sets Up Your Process

One aspect of job description writing that receives insufficient attention is its relationship to the downstream screening process. A well-written job description should define exactly what your screening criteria are - meaning the two documents (JD and scorecard) should be directly derived from each other.

If your job description lists "experience managing a team of five or more" as a requirement, your screening process should have a specific question or assessment that verifies this. If it does not, the requirement is decorative rather than functional.

This connection matters enormously for efficiency. Organisations that treat their job descriptions as the first step in building a structured hiring process - rather than as a standalone marketing document - screen candidates faster and more consistently.

According to SHRM, structured hiring processes reduce time-to-hire by an average of 20% and improve quality-of-hire scores by 25%. The job description is the document that makes structured hiring possible by defining, in advance, what you are looking for.

Klearskill's CV screening platform reads your job description requirements and uses them to build screening criteria automatically. When candidates apply, their CVs are assessed against the requirements you defined - 92% faster than manual review, with 97% accuracy in matching candidates to role specifications. Rather than spending hours reading applications that do not meet basic requirements, your team reviews only those who do.

SEO for Job Descriptions: Getting Found Before You Can Be Read

A job description that no one sees cannot attract candidates. Search engine optimisation for job postings has become a meaningful part of talent acquisition strategy, particularly for organisations that rely on organic traffic to their careers pages.

The primary considerations:

Job title as keyword. The title should match what candidates type into search engines. "Customer Success Manager" is searched far more than "Client Happiness Champion." This does not mean abandoning creative internal titles - it means ensuring your external posting uses the term candidates recognise.

Location specificity. "Marketing Manager - London" outperforms "Marketing Manager" for candidates searching in London. Be specific about location, including postcode for highly localised searches.

Salary range. Google Jobs (which aggregates job postings) surfaces salary information prominently. Including a salary range improves your visibility in structured search results.

Meta description. If your careers page generates its own meta description from job posting content, ensure the first 150 characters of your description are information-dense and include the role title and a key benefit.

Structured data. If your careers site is custom-built, implementing schema.org JobPosting markup enables Google Jobs to index your postings directly. This is a technical implementation but has a measurable impact on organic application volume.

Reviewing and Refreshing Job Descriptions

Job descriptions should be living documents, not set-and-forget archives. A description written two years ago for a role that has changed significantly is actively harmful - it attracts candidates whose expectations will not match the reality of the job.

Building a review cadence into your hiring process:

Before each new open requisition: Check that the description still accurately reflects the role. Talk to the hiring manager and, where the role has been filled before, to the current incumbent.
After each hiring round: If you consistently struggled to find candidates who matched the requirements, revisit whether the requirements were accurately described or whether they were set too high.
Annually for evergreen roles: Customer service, sales, and operations roles that are always open should be reviewed once a year against market norms.

CIPD's resourcing and talent planning surveys consistently show that organisations which review job descriptions more frequently report higher applicant quality and lower time-to-fill. The correlation is likely bidirectional: organisations that care about the quality of their process also care about the quality of their job descriptions.

A Checklist Before You Publish

Before posting any job description, run through this verification list:

Title uses standard industry terminology and avoids internal jargon
Opening two paragraphs explain the role, the team, and the impact without resorting to generic language
Responsibilities (6-10 maximum) are written as outcomes, not tasks, beginning with action verbs
Requirements are separated into essential and desirable, with genuine critical thinking applied to each
Salary range is included or there is a deliberate reason why it is not
Working pattern (remote, hybrid, in-office) is explicitly stated
Language has been checked for masculine-coded, aggressive, or exclusionary terms
No legally risky language referencing age, physical appearance, or implied preferences for protected characteristics
The description has been read aloud - does it sound like a person or a committee?
A colleague from outside the hiring team has read it and can explain what the role does

Ready to Screen Smarter?

A well-written job description is the starting point. The real efficiency gain comes from what happens after candidates apply.

Klearskill screens CVs against your job description requirements automatically - achieving 97% accuracy and reducing screening time by 92%. At $50/month for up to 10,000 applications, teams running high-volume or always-open roles see payback within days. Connect your existing ATS (Greenhouse, Workday, Lever, and 12 others) and your candidates flow straight into a ranked shortlist, with automated status emails keeping everyone informed.

You write the best job description you can. Klearskill ensures every qualified candidate who responds to it gets a fair, fast review.

Start screening smarter with Klearskill

Frequently Asked Questions

How to write job descriptions that attract the right candidates?

The most effective job descriptions combine three things: specificity, honest representation, and signal clarity. Be specific about what the role actually involves, including approximate time allocations across different responsibilities. Represent the role honestly - overpromising on autonomy, impact, or flexibility leads to early attrition from candidates who feel misled. Signal clarity means using language that tells the right candidates they belong and gently discourages those who do not. Separating essential from desirable requirements, using outcome-based responsibility statements, and including salary ranges all contribute to better candidate self-selection.

How long should a job description be?

For most professional and managerial roles, 600-900 words is the effective range. Research from Indeed suggests that descriptions in this range generate the best balance of application volume and applicant quality. Shorter descriptions (under 400 words) are appropriate for high-volume entry-level roles where candidates need less context to self-select. Longer descriptions (over 1,000 words) risk losing candidates' attention and should only be used for highly technical or senior roles where the additional detail is genuinely necessary for accurate self-assessment.

Should job descriptions include salary ranges?

The evidence strongly favours inclusion. LinkedIn data shows that postings with salary ranges receive 30% more applications. More importantly, salary transparency improves the efficiency of self-selection - candidates who would be dissatisfied with the range remove themselves from the process before consuming recruiter time. Several US states now require pay transparency in job postings, and UK legislation may move in the same direction. For most organisations, the commercial case for inclusion outweighs any concerns about internal equity exposure.

What is the difference between responsibilities and requirements in a job description?

Responsibilities describe what the person will do in the role - the tasks, projects, and outcomes they will own. Requirements describe what a candidate needs to bring to the role in order to do those things effectively. Both sections suffer from similar problems: too many items, too vague, and not genuinely thought through. Responsibilities should be written as outcomes with action verbs, prioritised by where the person will spend most of their time. Requirements should be ruthlessly separated into essential (genuine blockers to hiring) and desirable (helpful but not critical).

How often should job descriptions be updated?

At a minimum, every time a role is reopened for recruitment. In practice, roles evolve continuously - responsibilities shift, team structures change, and the market's expectation of what a role involves moves over time. The most effective organisations review evergreen job descriptions annually and conduct a brief update before any new posting, involving both the hiring manager and, where available, feedback from previous hiring rounds. A description that was accurate 18 months ago may now be actively misleading candidates about what they are signing up for.

Can a job description be too specific?

Rarely, but it is possible. Over-specification typically occurs when a hiring manager writes a description based on a very specific previous incumbent rather than on the role itself - creating a list of requirements so narrow that very few candidates could genuinely meet all of them. The test is whether your requirements are genuinely predictive of job performance or whether they reflect unnecessary specificity. If you can articulate exactly why each requirement matters for on-the-job success, the description is appropriately specific. If requirements are present because "that is how we have always done it," they deserve scrutiny.

How does a job description affect CV screening quality?

Directly and significantly. A well-written job description with clear, specific requirements provides an objective basis for screening. When requirements are vague or contradictory, screening becomes inconsistent - different reviewers apply different standards, bias is more likely to influence decisions, and good candidates are rejected for arbitrary reasons. Structured screening tools like Klearskill use the requirements defined in your job description to assess CVs consistently, which means the quality of your job description directly determines the quality of your shortlist. Clear requirements in, strong candidates out.

Job DescriptionsRecruitmentTalent AcquisitionHiring