A job description is often the first thing a candidate reads about your company, and for many it is the only thing they read before deciding whether to apply. A vague, copy-pasted posting attracts hundreds of poor matches and quietly repels the people you actually want. A clear one does the opposite: it helps the right people recognize themselves and the wrong ones opt out. This guide answers the practical questions on how to write one that works.
Why does the job description matter so much?
It does three jobs at once. It is a marketing page that sells the role, a filter that sets expectations, and later a reference point for interviews, onboarding and performance reviews. If it is unclear, you pay for it in screening time, mismatched hires and early resignations. If it is honest and specific, you receive fewer applications but better ones.
What should a job description include?
A clear, searchable job title
Use the title people actually search for, such as “Accounts Payable Specialist” rather than “Finance Ninja”. Internal levels and jargon mean nothing to outsiders.
A short summary of the role
Two or three sentences on why the role exists, what it will achieve and who it reports to. A candidate should understand the point of the job within ten seconds.
Key responsibilities
List five to eight main duties, starting each with a verb and ordering them by importance. Describe outcomes where you can, for example “Reduce invoice processing time” instead of only “Process invoices”.
Requirements, split into must-have and nice-to-have
This is where most postings go wrong. Separate what the person truly needs on day one from what they could learn. Research and recruiter experience both suggest that some qualified candidates, women in particular, skip roles when they do not tick every box, so a long wish list shrinks your pool for no good reason.
Pay, benefits and working arrangement
State the salary range, location, remote or hybrid expectations and the main benefits. In a growing number of countries and regions, pay transparency is becoming a legal requirement, and even where it is not, candidates respond better to postings that include it.
About the team and how to apply
Say a little about the team and what the first months look like, then explain the steps and timeline of the hiring process so people know what to expect.
How do you write it, step by step?
- Step 1: Talk to the hiring manager and the team. Find out what the person will actually do, what success looks like after six months and what has gone wrong with past hires.
- Step 2: Define the outcomes first. Write down three to five results the role should deliver, then derive the responsibilities and skills from them.
- Step 3: Write in plain language. Short sentences, active verbs and “you” instead of “the candidate”. Skip clichés such as “dynamic”, “rockstar” and “fast-paced environment” unless you can explain them.
- Step 4: Separate must-haves from nice-to-haves. Keep must-haves to a handful. Ask whether each one is truly required or just a habit copied from the last posting.
- Step 5: Be honest about the hard parts. If the role involves night shifts, difficult stakeholders or a lot of repetitive work, say so. Candidates who accept with open eyes stay longer.
- Step 6: Review it with fresh eyes. Ask someone outside the team to read it and explain the job back to you. If they cannot, it is not clear enough.
What mistakes drive good candidates away?
- Listing everything the team has ever wanted. A posting that asks for ten years of experience in a seven-year-old tool is a signal that nobody checked.
- Hiding the salary. Many strong candidates will not spend an hour applying without knowing whether the pay is realistic.
- Using gendered or exclusionary wording. Phrases like “young and energetic” or “native speaker” (when fluency is what you need) can discourage qualified people and, in many places, create legal risk.
- Confusing the role with the company brochure. Half a page about your mission and a few lines about the job leaves candidates guessing.
- Requiring a degree by default. If skills and experience can do the job, say so, and widen your pool.
- Writing it once and forgetting it. Roles change. A description copied from three years ago describes a job that no longer exists.
How do you make it more inclusive?
Focus on skills and results rather than personality traits. Use neutral language, avoid unnecessary physical or age-related requirements, and mention flexibility, accessibility or adjustments you can offer. Run the text past a colleague with a different background from the author. Inclusive wording is not about politeness alone; it widens the pool of capable applicants.
How do you keep job descriptions current?
Treat them as living documents. Review a description every time you open the role, when responsibilities shift significantly and during annual reviews. Keep one approved version in a shared place so recruiters, managers and employees all work from the same text instead of five slightly different copies.
A shared folder and a template are enough for many small teams. If you want your job descriptions, openings and hiring pipeline in one place, FulcrumGrid HR Suite can help you keep approved role descriptions next to the candidates and onboarding steps that depend on them. Either way, the discipline matters more than the tool.
Write for the person you want to hire, be specific about the work and the pay, and keep the requirements honest. A good job description will not fill the role by itself, but it will make sure the people who apply know exactly what they are applying for.
Frequently asked questions
How long should a job description be?
Aim for roughly 400 to 700 words. That is enough to cover the summary, responsibilities, requirements, pay and process without losing readers. If it needs more, the role is probably too broad.
Should I include the salary in the job posting?
Yes, a realistic range is best. It saves time for both sides, attracts better-matched applicants and is increasingly required by law in many countries. Check the rules where you hire.
How many requirements are too many?
More than five to seven must-haves is usually too many. Move anything that can be learned on the job into a separate nice-to-have list, and drop anything nobody would actually check.
How often should job descriptions be updated?
Every time you open the role, and whenever responsibilities change in a meaningful way. Reviewing them once a year alongside performance reviews is a good minimum.
FulcrumGrid HR Suite
Keep roles and hiring in one place
FulcrumGrid HR Suite helps you keep job descriptions, openings and onboarding together, so every hire starts from the same clear information.