Writing effective job descriptions

Why a clear job description matters for recruitment

A job description is the first structured contact a candidate has with your organisation, and it does far more than list tasks. It sets expectations, filters applicants, and provides a reference point for interviews, onboarding, and later performance reviews. When the document is vague, you attract a wide but poorly matched pool: people apply because they can imagine the role fitting them, then withdraw or underperform once reality sets in. A precise description does the opposite, encouraging suitable people to apply and gently discouraging those who are not a fit, which saves screening time on both sides. Consider a warehouse team leader posting that simply says 'manage the team'. One applicant assumes a desk-based planning role, another expects hands-on shift supervision. Both may interview, and both may leave disappointed. Rewriting it as 'supervise a team of eight during the 6am–2pm shift, allocate daily picking tasks, and report stock discrepancies to the site manager' immediately clarifies who should apply. Beyond recruitment, the description becomes a legal and managerial anchor. In France, it supports the contrat de travail, informs the classification under the applicable convention collective, and helps justify decisions if a dispute arises. It also protects the employer: if a role's duties are documented, changes and expectations are easier to communicate. Managers who invest an hour in a clear description often recover that time many times over by avoiding mismatched hires and repeated re-advertising.

Key components of an effective job description

A complete job description follows a predictable structure so candidates can scan it quickly and find what they need. Start with the job title and a short summary of two or three sentences that state the purpose of the role. Follow with the main responsibilities, usually five to eight bullet points that describe what the person will actually do day to day. Next, separate the required skills and qualifications from those that are merely desirable; mixing the two is one of the most common reasons good candidates self-reject. Add practical conditions: contract type (CDI, CDD, or interim), working hours, location, shift patterns, and any travel. Where relevant, indicate the salary range or the classification level under the convention collective, as transparency here improves application quality. Close with a brief line about the team or reporting structure so the candidate understands where the role sits. For a retail sales assistant, a workable outline would be: a one-line summary about serving customers and maintaining the shop floor; six responsibility bullets covering till operation, stock replenishment, and customer advice; a required list stating availability for weekend work and basic numeracy; a desirable list mentioning previous retail experience; and practical details such as '35 hours per week, Tuesday to Saturday, store located in central Lyon'. Keeping each section visually distinct with headings and short bullets helps mobile readers, who make up a large share of applicants. Avoid burying essential information, such as a mandatory driving licence, at the bottom of a long paragraph.

Defining the role: responsibilities and required skills

Responsibilities describe outcomes and actions, not vague aspirations. Write each one as a verb-led statement that a candidate could picture themselves performing: 'prepare weekly delivery schedules', 'handle customer complaints within 24 hours', or 'train new team members during their first month'. Aim for concrete, measurable phrasing where possible, because it helps both candidates and interviewers assess fit. Distinguish carefully between what is genuinely required and what would simply be nice to have. If you list ten years of experience and three software certifications as mandatory for an entry-level role, you exclude capable people and inflate the salary expectations of those who do apply. A practical test is to ask, for each requirement, 'Could a strong candidate succeed without this in the first three months?' If yes, move it to the desirable list. For a bilingual customer service role, fluent French may be essential while English is desirable; stating this clearly widens your pool without lowering the bar where it matters. Be honest about physical or scheduling demands too. A role requiring the lifting of 20kg loads or night shifts should say so plainly, so candidates can make an informed choice and you avoid early turnover. When defining skills, separate technical abilities (operating a forklift, using a specific ERP) from behavioural ones (working under pressure, communicating with clients). This separation makes it easier to design interview questions later and to explain, if needed, why one candidate was preferred over another.

Writing job titles and summaries that attract the right candidates

The job title carries a surprising amount of weight because it is what appears in search results and email alerts. Use standard, recognisable titles rather than internal jargon or inflated labels. 'Customer Service Advisor' will be found by more relevant candidates than 'Client Happiness Champion', which few people search for. If your internal title is unusual, add a common equivalent in the summary so search engines and jobseekers can connect the two. Avoid stacking multiple roles into one title, such as 'Accountant / Office Manager / HR Assistant', as it signals an unclear or overloaded position and deters focused applicants. The summary that follows should answer three questions in a few sentences: what the role is, why it exists, and what makes it worth applying for. Keep it grounded and specific. Instead of 'exciting opportunity in a dynamic environment', write 'You will lead the morning delivery team at our Marseille depot, ensuring orders leave on time and customers receive accurate stock'. Concrete detail is more persuasive than generic enthusiasm. Where a role suits people at different career stages, say so: 'suitable for candidates with one to three years of experience' sets a realistic frame. If the position offers a defined path, such as progression from assistant to team leader, mention it factually without over-promising. A strong title and summary together should let a candidate decide within thirty seconds whether to keep reading, which respects their time and improves the quality of the applications you receive.

Using clear, inclusive language in job postings

Clear language means short sentences, common words, and no unexplained acronyms. If a term is specific to your industry, spell it out the first time. Inclusive language means writing so that a wide range of qualified people feel able to apply, which broadens your talent pool and supports fair recruitment practice. In France, non-discrimination rules cover criteria such as age, gender, origin, and family situation, so avoid any wording that could imply a preference on those grounds. Practical steps help. Use gender-neutral phrasing, for example 'H/F' after the job title, which is standard practice, and prefer 'the person will' over gendered pronouns in the body text. Focus requirements on what the job needs rather than on personal characteristics: 'able to lift 15kg regularly' is fair and relevant, whereas 'young and energetic' is both discriminatory and unnecessary. Watch for subtle exclusionary phrasing. Words like 'native French speaker' can exclude perfectly fluent bilingual candidates; 'fluent in French' is more accurate and lawful. Long lists of demanding requirements can discourage under-represented groups who tend to apply only when they meet every point, so trimming the essentials to what truly matters improves the diversity of your applicants. Read the posting aloud or ask a colleague to review it; if any phrase would feel off-putting or confusing to a capable outsider, revise it. Clarity and inclusivity usually go hand in hand, because both reward plain, purposeful writing over decoration.

Common mistakes to avoid when writing job descriptions

Several recurring errors weaken otherwise good postings. The first is length without substance: a two-page description full of generic corporate phrases loses readers before they reach the important details. Keep it focused and put essentials near the top. The second is the wish-list trap, where every desirable trait becomes a hard requirement, shrinking the pool to almost nobody or attracting only overqualified people who will soon leave. The third is copying an old description without checking it still matches the role; duties drift over time, and a stale document misleads candidates. A fourth mistake is omitting practical facts that candidates weigh heavily, such as location, hours, contract type, and pay range. Leaving these out increases drop-off during screening when the applicant discovers a deal-breaker late. A fifth is inconsistent tone or formatting, which makes the organisation look disorganised; use the same structure across all your postings. Also avoid overselling. Describing a demanding role as effortless or promising rapid promotion that you cannot guarantee erodes trust and increases early turnover once reality sets in. Finally, beware of vague verbs such as 'assist', 'support', or 'help' without saying with what; 'support the finance team' tells the reader little, whereas 'reconcile supplier invoices and prepare monthly expense reports' is concrete. A useful final check is to hand the draft to someone unfamiliar with the role and ask them to explain what the person would do all day. If they cannot, the description needs more specific detail before it goes live.

Reviewing and updating job descriptions over time

A job description is a living document, not a one-time task. Roles evolve as tools change, teams grow, and priorities shift, so a description written two years ago may misrepresent today's work. Set a simple review rhythm, for example checking each description before you re-advertise a role and once a year during performance or planning cycles. Involve the current jobholder and their manager, since they know which duties have grown, shrunk, or disappeared. When you review, compare the listed responsibilities against what the person actually does, and update the required skills to reflect any new systems or processes. A retail role that adopted a new till and inventory system, for instance, should now mention comfort with that technology rather than the old manual method. Keep records of changes so you can explain, if questioned, why a role's scope evolved. This is useful both for internal fairness, such as justifying a reclassification, and for maintaining accurate documents alongside employment contracts. Reviewing descriptions also surfaces useful management insights: if one role has quietly absorbed the work of two, that may signal a need to hire or restructure. Treat each update as a small opportunity to improve clarity, trim outdated requirements, and align the wording with current legal and collective-agreement terms. A short, disciplined review is far less work than untangling the confusion that stale descriptions cause during recruitment and appraisal.

Example

Essential sections of a job description and their purpose

FAQ

How long should a job description be? Aim for one page or roughly 400 to 600 words. Include a short summary, five to eight responsibility bullets, separated required and desirable skills, and practical details such as hours, location, and contract type. Length matters less than clarity, but overly long postings tend to lose readers before the key information.

Should I include a salary range in the job description? Stating a salary range or the classification level under the applicable convention collective usually improves application quality, because candidates can self-assess before applying. It also reduces wasted screening time. If a fixed range is difficult, indicating the classification level or a banded estimate still helps candidates make an informed decision.

How do I keep a job posting non-discriminatory in France? Focus requirements on what the job genuinely needs rather than personal characteristics, use gender-neutral phrasing such as 'H/F', and avoid references to age, origin, or family situation. Replace phrases like 'native speaker' with 'fluent', and describe physical demands factually, for example 'able to lift 15kg regularly'.

How often should job descriptions be reviewed? Review each description before re-advertising a role and at least once a year during planning or appraisal cycles. Involve the current jobholder and manager to capture how duties have changed, and update skills to reflect new tools or processes so the document stays accurate.

Read next

• /guides/
• /service/
• /guides/how-to-hire-line-staff/
• /contact/

Request staffing support