Recruitment

By The HR Horizon | Recruitment | Future of Work

Reading time: approximately 10 minutes

Most businesses write job descriptions that describe a role. The best businesses write job descriptions that describe a direction — because the role you’re hiring for in January may not look the same by July.

That’s not exaggeration. AI tools are changing what “doing the job” means at a pace most HR processes haven’t caught up with yet. A marketing coordinator hired to write social captions in January might be prompting and editing AI-generated campaigns by July. A finance assistant hired for data entry might be spending most of their week interpreting AI-assisted forecasts instead of building spreadsheets by hand.

If your job descriptions are static documents — written once, filed away, and never revisited — you’re not just risking a mismatch between the ad and the actual job. You’re setting new hires up to feel blindsided when their role shifts underneath them, and setting managers up with no documented basis for the performance conversation six months in.

This guide walks you through how to write a job description that works today and still makes sense as the role evolves: one that’s clear, compelling, inclusive, and built with enough flexibility to survive contact with a fast-changing tool stack.

Why Most Job Descriptions Fail

The typical job description is a copy-paste from an old document, a wish list of requirements, or a dry list of duties that reads more like a legal contract than an invitation. It treats the candidate as a supplier of labour, rather than a person you’re recruiting into a growing organisation.

The result? You attract candidates who are simply job-hunting, rather than people genuinely excited about your specific opportunity. You over-specify requirements and screen out capable people who don’t tick every box. And you give no real sense of your culture, your direction, or what it’s actually like to work for you — today or a year from now.

The evidence here is consistent: job postings that lean on exclusive language, excessive requirement lists, or corporate jargon get fewer applications, particularly from women, underrepresented groups, and experienced professionals who are selective about where they invest their energy.

A job description that only describes today’s tasks is already out of date the moment AI touches the role.

The Anatomy of an Effective Job Description

A well-structured job description has six core components. Here’s what each should contain, and why it matters.

1. Job Title

Use a clear, searchable title that reflects how the role is known in the market. Avoid internal jargon or creative titles candidates won’t be searching for. “Growth Marketing Manager” will attract more qualified applicants than “Brand Ninja”, and it’ll perform better in search results on job boards and AI-powered platforms.

2. The Role Overview (The Hook)

This is the most underused section in most job descriptions, and the most important. In two to four sentences, tell the candidate: what this role does, why it matters, and what makes it an exciting opportunity. Treat it like the opening paragraph of a compelling article. If it doesn’t make a qualified reader want to keep reading, you’ve already lost them.

Example: “We’re looking for an experienced HR Business Partner to help us scale our people operations across a fast-growing regional team. This is a high-impact role with direct access to senior leadership, real ownership over people strategy, and the opportunity to build systems that will shape our culture for years to come.”

3. Key Responsibilities

List the core activities and outputs of the role, not every possible task, but the eight to twelve things that define success in the position. Use action verbs. Be specific. And focus on what the person will do and achieve, not just what they’ll be responsible for.

Good: “Design and implement a performance management framework that supports quarterly goal-setting across all departments.” Poor: “Responsible for performance management.”

Action Tip: Write responsibilities around the outcome (“keeps the applicant pipeline moving”) rather than the tool (“manages our ATS”). Tools get replaced. Outcomes don’t.

4. Requirements — Qualifications and Experience

This is where most job descriptions go wrong. They list every possible requirement — years of experience, specific degrees, certifications, software knowledge — and build a barrier that excludes capable candidates who could do the job well.

Best practice is to separate requirements into two categories. Essential (non-negotiable): the skills, experience, or qualifications without which a candidate genuinely can’t do the job — keep this list short, typically four to six items. Desirable (nice to have): things that would accelerate a candidate’s effectiveness but can be learned on the job.

Also, audit your requirements for bias. Is a specific degree genuinely required, or have you always just assumed it? Is five years of experience truly necessary, or does it exclude talented people who learned faster?

Skill-based hiring, whereby you’re assessing what candidates can do rather than what their CV says about where they’ve been, consistently produces better outcomes. It’s also worth asking whether a listed software skill will even matter in a year, or whether it’ll have been automated or replaced by something new.

5. What You Offer (Your EVP in Action)

This section is non-negotiable in a competitive hiring market. Tell candidates what they’ll receive: compensation range (or at minimum a clear sense of the level), benefits, flexibility, development opportunities, culture, and anything else that makes your organisation a genuinely good place to work. If you’ve done the work to develop your Employee Value Proposition, this is where it lives. (Psssst! If you want some insights on how to build your Employee Value Proposition, we wrote a whole article about it. Check it out here!)

Increasingly, this is also where you signal how you invest in your people as the work itself changes: structured time to learn new tools, a genuine upskilling budget, or a track record of promoting people who’ve grown into a bigger version of their original role. Candidates are evaluating you as much as you’re evaluating them.

6. How to Apply

Be explicit and frictionless. What should they submit? How? By when? Who will they hear from, and when? Ambiguity here leads to dropped applications and a poor candidate experience, which damages your employer brand even before the interview stage.

Why Your Job Description Can’t Be a Static Document Anymore

Here’s where employers often get it wrong: they treat the job description as a one-time artifact, something written for the hiring process and forgotten the moment the offer letter goes out.

That approach doesn’t hold up anymore. AI-driven tools are compressing the distance between what a role looked like at hire and what it looks like six months later. We’ve seen clients bring someone on as an HR coordinator to manage onboarding paperwork, and within two quarters that same person is overseeing an AI-assisted onboarding process and spending their freed-up time on employee experience projects nobody budgeted for at the start.

This isn’t confined to tech-forward companies. It’s happening in finance, in customer service, in marketing, in HR itself. As staff get upskilled, whether through formal training or just learning to use the tools already available to them, the shape of what “doing the job well” means keeps moving.

If your job description doesn’t account for that movement, three things tend to happen:

• New hires feel misled when the job doesn’t match what they signed up for
• Managers have no documented basis for a performance conversation about work that wasn’t in the original brief
• Pay and role banding fall out of step with what the person is actually delivering

None of that is inevitable. It just means the job description needs to be built differently from the start.

A hire made in January should recognise their own job description in July, even if half the tasks on it have changed.

Writing Job Descriptions Built to Evolve

Anchor to Purpose, Not Just Tasks

Write the role around the problem it exists to solve, not only the tasks it currently involves. “Owns the candidate pipeline from application to offer” survives a tool change. “Manages applications in [specific ATS]” doesn’t.

Separate the Stable Core from the Evolving Edge

Every role has a stable core, the parts of the job that don’t change regardless of tooling, and an evolving edge, the parts that will shift as AI, automation, and upskilling change how the work gets done. Structure the job description to make that distinction visible, even naming it directly: “This role’s day-to-day tools and specific tasks will evolve as our systems and your skills develop; the core purpose above will not.”

Build in a Review Trigger, Not Just a Review Date

Instead of only reviewing job descriptions once a year, build in a trigger: when a new tool is adopted that materially changes how the role’s outcomes get delivered, when someone completes a significant upskilling milestone, or when a manager notices the day-to-day work no longer matches the document. A job description left stale for two years is as much a compliance risk as a management one, particularly if it ever becomes relevant to a disciplinary, grievance, or redundancy conversation.

Action Tip: Add a single line at the bottom of every job description: “Last reviewed: [date]. This role is expected to evolve as tools and skills develop; see your manager for current scope.” It costs nothing and protects everyone.

Talk About Growth and Tools in the Job Description Itself

Candidates today are reasonably asking whether a role will still exist, or still be worth doing, in two years. Say something about it. A line like “this role will evolve as we adopt new AI-assisted tools, and we invest in upskilling our team to grow with it” does two things: it’s honest, and it signals to ambitious candidates that you’re a business worth growing with, not one that’ll make their skills redundant without warning.

Language Matters: Writing Inclusively and Compellingly

The words you use in a job description send signals, intentional or not, about who you’re looking for and whether your organisation is inclusive. A few key principles:

• Avoid gendered language: words like ‘aggressive,’ ‘dominant,’ and ‘competitive’ have been shown to deter female applicants, while words like ‘collaborative,’ ‘supportive,’ and ‘empathetic’ can deter male applicants. Use neutral, competency-focused language.
• Cut the jargon: phrases like ‘synergistic self-starter’ or ‘rockstar ninja’ are meaningless and off-putting. Write in plain, direct language.
• Use ‘you will,’ not ‘the ideal candidate will’: second-person language is more engaging and speaks directly to the reader.
• State your inclusion commitment explicitly: a brief statement welcoming applications from all backgrounds, including neurodivergent candidates and those with non-traditional career paths, significantly broadens your talent pool.

Optimising Your Job Description for AI and Modern Job Platforms

A significant share of job searches now happen through AI-powered platforms and aggregators. Your job description needs to work as a structured document, not just a readable one. In practice, that means:

• Using standard, searchable job titles, not creative internal titles
• Including key skills and technologies explicitly in the text, not buried in attachments
• Structuring the document with clear headings so AI tools can parse and categorise it correctly
• Including your location and whether the role is remote, hybrid, or on-site
• Using the language candidates use, not internal company language

The Job Description Checklist

Before you post, run through this checklist:

1. Does the title match how this role is known in the market?
2. Does the overview make a qualified person want to read further?
3. Are responsibilities described in terms of outcomes, not just today’s tools?
4. Have you separated essential from desirable requirements?
5. Have you audited requirements for unnecessary barriers?
6. Have you named the role’s stable core separately from its evolving edge?
7. Have you built in a review trigger, not just a review date?
8. Have you described what you offer, including growth and upskilling?
9. Is the language free of jargon and gendered terms?
10. Have you included a clear, frictionless application process?
11. Have you stated your commitment to inclusion?

Final Thoughts

A job description is often the first impression a talented candidate has of your organisation, and increasingly, it’s also the document that either sets a new hire up to grow with you or sets them up to feel blindsided six months in.

The businesses that get this right aren’t the ones with the longest requirement lists. They’re the ones who write for the direction the role is heading, not just the tasks it involves today. In a world where AI is reshaping how quickly work changes, that’s no longer a nice-to-have; it’s the difference between a job description that still makes sense in July and one you’re already rewriting.

Write for the person you want to grow with, not just the role you need filled right now.

→  Access Job Description Templates Built to Evolve with our Sunrise Subscriptions – find the right tier for your business!

About The HR Horizon

The HR Horizon is a Caribbean-based HR consultancy and learning platform helping SMEs, startups, and emerging leaders build future-ready organisations. We offer HR consulting, executive coaching, online courses, and a library of ready-to-use HR templates and policies designed for businesses across the Caribbean and beyond. Visit us at thehrhorizon.com or email hello@thehrhorizon.com