How to Write a Job Description That Doesn't Shrink Your Pool

How to Write a Job Description That Doesn't Shrink Your Pool

Mercedes Gordo runs delivery and customer success at Nova and spent two years at LinkedIn in Dublin. Her test for a job description: strike every requirement you'd hire someone without, and see what's left.

Updated 6 min read

Most job descriptions are written by someone copying the last one and changing the title. That’s not laziness, it’s the absence of a method, and the cost is paid later in a pipeline that’s thinner and narrower than it should be.

The useful thing to understand is where that cost actually comes from. It isn’t the writing. It’s the requirements list.

Every extra must-have costs you candidates

Here’s the mechanic, and it’s the reason to care about any of this.

A requirements list gets padded because padding feels safe. Nobody was ever criticised for asking for too much. So the hiring manager adds the certification, the tool, the sector experience, the extra two years, and every one of them lands in the “required” column because that’s the column that exists.

Each of those shrinks your pool, and it shrinks it unevenly. The candidates who read a requirements list literally and count themselves out are not a random sample. They’re disproportionately the people who already suspect they don’t belong, which tends to mean the people least represented in the role already. Meanwhile the ones who apply regardless of the list apply regardless of the list.

So you’ve filtered on confidence rather than on capability, before anyone has read a single CV.

The test for each requirement: would you reject a candidate who had everything else but not this? If you wouldn’t, it isn’t a must-have. Move it or cut it.

Numbers do the work adjectives can’t

The second failure is the opening paragraph, and it’s the most visible.

“A dynamic, agile market leader in a fast-paced environment.”

That’s what gets written when nobody gave the writer a fact. Compare:

“Profitable, growing 75% year over year, with 500,000 customers across 10 countries.”

Same length, completely different information. One of them a candidate can evaluate; the other is noise they’ll skim past, if they haven’t already.

Lead with what the company actually is, in one sharp sentence, then the strongest concrete facts you have: revenue, growth, customers, markets, funding, whatever’s real. Then, optionally, the problem the team is solving. Then one line on the role itself: what this person will own, who they report to, and why the role exists now.

That last part is the one most postings skip, and candidates read for it. “Why now” is the difference between a vacancy and an opportunity.

The four blocks

Keep it scannable. People skim job descriptions, which is not a character flaw.

1. The company and the role. Two or three short paragraphs, as above.

2. What you’ll do. Three to seven bullets. Each starts with a verb the person will actually perform, then a clause that explains it:

• Lead the global finance function across multiple countries and entities, managing a team of 6+. • Own the financial strategy: capital structure, cash management, profitability and scenario modelling. • Drive M&A activity, leading buy and sell-side processes from origination to execution.

Outcomes, not daily tasks. A list of what someone’s calendar looks like describes a job nobody wants. A list of what they’ll own describes one people apply for.

3. What we’re looking for. Five to eight bullets, must-haves separated from nice-to-haves, with the discipline from the section above applied to the first group.

4. What we offer. Short and concrete. Salary band if you’re publishing it, bonus, equity, and only the benefits that actually exist. Padding this section is transparent, and a candidate who counts six perks and arrives to find two remembers.

On the salary band

Publish it if you can.

Pay transparency is moving from good practice to legal requirement across more jurisdictions, including in the EU, so the first thing to do is check what applies where you’re hiring rather than assume. Beyond that, publishing raises application rates and saves both sides the conversation that otherwise happens at the final stage, after four interviews, when it’s expensive for everyone.

If the company won’t publish, say something honest, like compensation based on experience, and leave it at that. Don’t publish a band nobody confirmed, which is the one version of this that’s worse than saying nothing.

Copy an example, don’t follow rules

This is the part that actually moves quality, and it’s slightly deflating given that you’ve just read a list of rules.

The biggest single lever on a job description is a good one to imitate. Tone is close to impossible to specify and trivial to copy. Whether your company writes in the third person or as a founder in the first, whether it’s warm or precise, whether it opens with the mission or with the numbers: pick one or two of your own best postings and work from those.

Three at most. More dilutes the pattern rather than reinforcing it.

And there are three registers worth knowing, because picking the wrong one is jarring:

  • Corporate, neutral and third person. The default, and right for most established companies and senior roles.
  • Founder voice, first person, warm, usually with a quick-facts list up top. Only if the company already writes this way. Imposing it reads as costume.
  • Confidential search, when you can’t name the company. Describe the stage and the appeal honestly without identifying details, rather than being vague about everything.

Never invent anything

One rule holds the rest together: don’t make up facts about the company, the compensation or the requirements.

This matters more now that most postings pass through a model at some point, because the failure mode of a model is a confident paragraph of plausible facts about a company it knows nothing about. Growth figures that sound right. Benefits that sound standard. A mission statement assembled from the sector.

Candidates notice this before recruiters do, because they read ten postings a day and the hollow ones have a texture. If you don’t have the number, ask for it or leave it out. A short, specific posting beats a long one built on assumptions.

For any team hiring continuously, the highest-return change is the must-have list, because it’s the only part of a job description that mechanically determines who can apply. If you post occasionally, the opening paragraph is where the time goes: replace the adjectives with whatever is true and concrete about the company.

If you’d rather not start from a blank page, this method is one of eleven free AI skills our customer success team packaged up. It takes one to three of your previous postings to copy the voice, asks for what it doesn’t know rather than inventing it, and pushes back when the requirements list gets padded.

Then the posting does its job and the applications arrive, and the next question is how to read a hundred of them without losing the good ones. We wrote that one too: screening CVs without losing the good ones.

Frequently asked questions

How do you write a good job description?

Four blocks: the company and why this role exists now, three to seven responsibilities written as outcomes, five to eight requirements with must-haves separated from nice-to-haves, and what you offer. Lead with concrete facts rather than adjectives, keep it scannable because candidates skim, and be ruthless about what goes in the must-have list. Most of the work is deciding what to leave out.

How many requirements should a job description have?

Five to eight in total, with must-haves and nice-to-haves clearly separated. The important discipline is on the must-have side: every requirement marked as required shrinks your pool and skews it, because the candidates who already wonder whether they belong read the list literally and don't apply. The test is simple. For each one, ask whether you'd reject a candidate who had everything else. If you wouldn't, it's a nice-to-have.

Should you publish the salary band in a job description?

Publishing it is increasingly expected and increasingly required: pay transparency rules are spreading across jurisdictions, including in the EU, so check what applies where you're hiring rather than assuming. Beyond compliance, it raises application rates and saves both sides a conversation that ends at the last stage. If the company won't publish a band, say something honest like compensation based on experience rather than padding the section.

What makes a job description sound generic?

Adjectives where facts should be. Dynamic, agile, fast-paced and market leader are what companies write when nobody gave them a number. The fix is specifics: what the company does in one sentence, then revenue, growth, customers, markets or funding. The second cause is responsibilities written as a task list rather than as what the person will own, which reads like a description of someone's calendar rather than of a job.

Can you use AI to write a job description?

Usefully, as long as it works from your inputs rather than from its own assumptions. The failure mode is a posting full of plausible-sounding facts about a company it has never heard of. What works is giving it one to three of your own previous postings to copy the voice from, then the real material: responsibilities, must-haves, logistics, pay. Anything it doesn't have, it should ask for or leave out.

Sources and method

The method described here is the one behind Nova's JD Creator skill, built and published by the customer success team. It's free to download as part of the Inbound pack.

Mercedes Gordo
Mercedes Gordo

Head of Delivery and Customer Success

Mercedes Gordo is Head of Delivery and Customer Success at Nova. Mercedes spent two years at LinkedIn in Dublin as a relationship manager and account director, and previously ran Customer Alliance's Spanish operation.

Connect on LinkedIn →
Sourcing and outreach How to Screen CVs Without Throwing Away Good Candidates Sourcing and outreach The Interview Scorecard: How to Score Candidates on the Same Yardstick