How to Write a Job Description That Attracts the Right Candidates

Maya, the only HR manager at a 180-person logistics company in Lagos, once showed me two job descriptions for the same operations role. The first had 23 requirements, no salary range, and the phrase "must thrive under pressure" three times. It produced 417 applications, most from people who had never managed a warehouse shift. The second had seven requirements, a clear range, a normal week-in-the-life section, and three examples of decisions the hire would make. It produced 74 applications and a shortlist in two days.

That is the job of a job description: not to attract everyone, but to attract the right people and help the wrong people opt out early.

Start with the job's real purpose

Lead with the answer: why does this role exist now?

Weak opening:

We are looking for a dynamic, results-oriented Marketing Manager to join our fast-paced team.

Better opening:

AtlasPay is hiring a Marketing Manager to turn our founder-led sales pipeline into a repeatable demand engine. In the first six months, this person will own customer webinars, lifecycle email, and two industry reports for HR buyers in Nigeria and the UK.

The second version tells candidates the company stage, the business problem, the first six months of work, and the market. It also filters out people who want a brand-only role or a large team on day one.

Use a consistent structure

Write responsibilities as outcomes

Responsibilities should tell candidates what they will own. Avoid vague verbs like "assist with" unless the role is genuinely assistant-level.

Before:

• Responsible for recruitment.
• Support employee engagement.
• Handle HR tasks.

After:

• Run end-to-end hiring for 8-12 open roles per quarter, from intake meeting to signed offer.
• Build monthly engagement pulse reports and agree actions with department heads.
• Maintain employee records in the HRIS and complete contract changes within two working days.

The after version gives volume, ownership, and quality expectations. A candidate can picture the work.

Separate must-haves from nice-to-haves

Most job descriptions ask for too much. A 60-person startup posting for a "Senior People Partner" often asks for payroll, learning design, employee relations, HR analytics, employment law, HRIS administration, compensation strategy, and culture work. That is not one role. That is a department.

Use this test: if a candidate lacks this requirement, would you reject them even if everything else is excellent? If no, it belongs in nice-to-have.

Be specific about pay

Salary transparency is becoming normal, and in some markets it is required. Indeed Hiring Lab reported that pay transparency in US job postings continued rising in 2024, even as growth slowed from earlier surges. Candidates are learning to treat missing ranges as a signal.

You do not need to publish your entire compensation philosophy. You do need to give a serious range.

Weak:

Competitive salary based on experience.

Better:

Salary range: NGN 18m-24m annual gross, depending on depth of B2B SaaS experience. This role is eligible for a 10% annual performance bonus and private medical cover.

If your range is wide, explain why. A range of $70,000-$130,000 without leveling context creates mistrust. A range of $70,000-$95,000 for mid-level and $100,000-$130,000 for senior gives candidates a real signal.

Remove exclusionary language

Inclusive job descriptions are not about making the role sound soft. They are about removing irrelevant barriers.

Common problems:

• "Native English speaker" when "professional written and spoken English" is enough.
• "Young and energetic" when the role needs stamina or high-volume work.
• "Rockstar" or "ninja" when the role needs a specific craft.
• "Must be available 24/7" when the real need is one weekend on-call rotation per month.
• "No employment gaps" when a gap has no relationship to performance.

Show the hiring process

Candidates hate mystery. Tell them what will happen.

For example:

1. Recruiter screen, 30 minutes.
2. Hiring manager interview, 45 minutes.
3. Work sample, maximum two hours of preparation.
4. Structured panel interview, 60 minutes.
5. References after verbal offer.

If you use AI screening, say how. If you require a case study, give time expectations. If you pay for assignments, say so.

Before and after rewrite

Before:

We need a driven HR generalist with 7+ years experience. Must be able to handle pressure, multitask, work independently, and support all HR functions. CIPD preferred. Payroll knowledge essential. Must be a culture fit.

After:

We are hiring an HR Generalist to support 220 employees across Nigeria and Kenya. In the first six months, you will own onboarding, employee letters, HRIS data quality, first-line manager advice, and monthly payroll inputs. You should have handled employee documentation and manager queries in a company of at least 100 people. Payroll experience is useful, but our Finance team owns final processing. We value clear judgment, confidentiality, and calm follow-through.

The rewrite removes vague pressure language, separates payroll support from payroll ownership, and replaces "culture fit" with behaviors.

Where AI-generated job descriptions go wrong

AI drafts are useful, but they tend to overgeneralize. The common failures are predictable:

• Too many responsibilities for one role.
• Generic benefits language that says nothing.
• Requirements copied from market clichés.
• No real numbers on team size, volume, salary, tools, or first-six-month outcomes.
• Inclusion language that sounds pasted on.

Use AI for structure, then force the draft through your actual hiring intake.

Run a proper hiring intake before posting

Most weak job descriptions are not writing problems. They are intake problems. HR receives a vague request, turns it into a polite document, and discovers during interviews that the hiring manager wanted something else.

Use a 45-minute intake meeting. Do not let it become a wish-list session. The agenda should force trade-offs:

• Why is this role open now: growth, replacement, backfill, new capability, or restructuring?
• What will this person own in the first six months?
• What decisions can they make without approval?
• What problems are currently sitting with the manager because this role is empty?
• What experience is truly non-negotiable?
• What can be learned in the first 90 days?
• What is the approved salary range and level?
• What will make us reject a candidate after interview?

If the manager says "we need someone strategic and hands-on," ask for the calendar version. How many hours per week are strategy, delivery, manager support, reporting, and administration? A 40-hour week cannot be 70% strategy, 70% execution, and 40% stakeholder management.

Tailor by company size

A good job description for a 30-person startup reads differently from one for a 3,000-person bank.

For a startup, candidates need to know scope, ambiguity, funding or runway context where appropriate, and whether they will build systems from scratch. "You will design our first onboarding process" is more honest than "manage onboarding."

For a scale-up, candidates need to know what is already built and what is breaking. "You will improve a hiring process that supports 25 hires per quarter" is more useful than "support rapid growth."

For an enterprise, candidates need to know decision rights, matrix relationships, and process load. "You will partner with three regional HRBPs and own reporting for EMEA sales" tells more truth than "work cross-functionally."

Quality-check the final draft

Before posting, read the job description through three lenses.

First, the candidate lens: can a qualified candidate tell whether this role fits their skills, life, and compensation needs? If salary, location, travel, or working hours are hidden, the answer is no.

Second, the manager lens: would the hiring manager evaluate candidates against these responsibilities and requirements? If not, the JD is marketing copy, not a hiring document.

Third, the compliance lens: could any requirement exclude people for a reason unrelated to the job? Examples include unnecessary physical demands, "native speaker" language, age-coded words, or location restrictions that conflict with remote policy.

Source note

For pay transparency trends, review current jurisdictional requirements and market data such as Indeed Hiring Lab's 2024 pay transparency analysis. Laws and posting norms change quickly, especially in US states and large metros.

A complete mini-example

Here is a compact example for a mid-level People Operations Specialist.

Role purpose: You will keep employee operations accurate and calm for a 260-person company operating in Nigeria, Kenya, and the UK. Your work will reduce manager confusion, improve employee documentation, and make monthly payroll inputs reliable.

Responsibilities:

• Maintain employee records in HiBob and complete employee changes within two working days.
• Prepare contract amendments, promotion letters, and confirmation letters using approved templates.
• Coordinate monthly payroll inputs with Finance for three countries.
• Answer first-line manager questions on onboarding, probation, leave, and employee documentation.
• Run a monthly audit of missing employee documents and policy acknowledgements.
• Improve one recurring HR operations process per quarter.

Must-haves:

• Has supported employee documentation for at least 150 employees.
• Has coordinated payroll inputs or employee changes with Finance or payroll vendors.
• Writes clear, accurate employee-facing communication.
• Can manage confidential information with good judgment.

Nice-to-haves:

• HiBob, BambooHR, Workday, or similar HRIS experience.
• Multi-country HR operations exposure.
• Experience improving onboarding or employee-record processes.

This is specific enough for candidates and concrete enough for screening.

Key takeaways

• A job description should filter, not flatter.
• Start with why the role exists and what the hire will own.
• Keep must-have requirements short and defensible.
• Publish a serious salary range whenever possible and whenever required.
• Remove coded language and irrelevant barriers.
• Name the hiring process so candidates know what they are agreeing to.
• Use AI for speed, but use manager intake for accuracy.