Why Your Job Descriptions Are Attracting the Wrong Candidates
Recroot - Practise Work Conversations
Train for meetings, reviews, and promotions
Let's say you've posted a job. Applications are rolling in. But when you sit down to review them — none of them are right. Too junior. Wrong industry. Clearly didn't read the role properly.
Sound familiar?
Here's the uncomfortable truth: in most cases, it's not a talent shortage. It's a messaging problem. And it starts with your job description.
A job description isn't just an HR document. In 2026, it's the very first thing a candidate sees before deciding whether your company is worth their time. Get it wrong, and the best people move on before you ever speak to them.
Most job descriptions are written by committee. One person drafts it, three people add requirements, someone from legal reviews it, and by the time it's live it reads like a terms and conditions document.
That's exactly the problem.
The best candidates — the ones with options — aren't reading job descriptions out of desperation. They're evaluating you just as much as you're evaluating them. If your post is vague, bloated, or full of buzzwords, they're gone in 30 seconds.
A 2026 study found that over half of candidates won't apply if a job description is vague, generic, or missing pay information. Not "might hesitate." Won't apply.
Your job post is a conversion tool. Treat it accordingly.
1. You're writing for internal alignment, not external attraction
The most common mistake. Job descriptions are often built to satisfy internal stakeholders — HR templates, compliance language, org chart context. All of that makes sense internally. None of it helps a candidate understand why the role is worth their next three years.
Candidates need to answer one question when reading your JD: "Is this role designed for someone like me to succeed?" If your description doesn't answer that quickly and clearly, qualified candidates move on.
2. The requirements list is impossible
We've all seen it. Seven years of experience in a technology that's only existed for four. A degree requirement for a role that doesn't need one. Ten "must haves" that are actually "nice to haves."
Overloaded requirements shrink your candidate pool and discourage the exact people you want. Research consistently shows that qualified candidates — especially those from underrepresented groups — self-select out when they don't meet every single criterion, even when they'd do the job brilliantly.
If it's not truly essential, cut it.
3. You're using vague language that means nothing
"Fast-paced environment." "Rockstar." "Ninja." "Self-starter." "Passionate team player."
These phrases say nothing concrete and attract everyone, which means they attract no one specific. When your description could apply to any company in any industry, you get applicants who are applying to any company in any industry.
Specificity attracts alignment. Vagueness attracts volume.
4. No salary range
In 2026, this is a dealbreaker for serious candidates. Nearly one in four job seekers says compensation is the first thing they look for. When it's missing, candidates fill in the blanks themselves — and those assumptions rarely favour you.
Hiding the salary range doesn't protect your negotiating position. It just increases drop-off and delays the conversation you'll have to have anyway.
5. The tone is off-brand
If you're a startup but your job ad reads like a government procurement document, you're sending the wrong signal. The candidates who would thrive in your environment will assume it's not for them — and they'll be right to.
Your tone is part of your employer brand. It tells people what working there actually feels like, before they've spoken to anyone.
6. The post is outdated
A surprising number of job descriptions are built on templates from three or four years ago. They reference roles, tools, or structures that no longer exist. Experienced candidates notice immediately, and it raises questions about how organised you actually are.
The structure isn't complicated. What's hard is the discipline to keep it focused.
That's it. Clean, specific, honest.
Here's something worth sitting with: when job descriptions consistently fail to attract the right candidates, it's often not a writing problem. It's a clarity problem at a higher level.
If the hiring manager can't articulate what success looks like in the role, no amount of polished copy will fix it. If four people have four different ideas of what the role is for, the description will reflect that confusion — and candidates will feel it.
The best-performing hiring teams treat the job description process as a forcing function for internal alignment. Before you write a word, you need to answer: what does this person actually do, how will we know if they're excellent at it, and why would a great candidate choose this over their other options?
One of the most practical shifts in 2026 is using AI tools to screen candidates against the role — not the other way around. Rather than throwing a vague description at a job board and hoping, platforms like Recroot.io let you define exactly what the role requires, then screen candidates against those criteria through AI-powered calls and assessments.
The result: the candidates who make it to your desk are already pre-qualified against what the role actually needs — not just whoever happened to apply.
It doesn't fix a poorly written JD. But it does dramatically reduce the noise between "applications received" and "people worth your time."
How long should a job description be?
Short enough to read in under three minutes. Most effective JDs are 400–600 words. Beyond that, you're either repeating yourself or adding requirements that don't need to be there. Candidates scan quickly — the top of the description is the most important real estate you have.
Should I include salary in a job description?
Yes. In 2026, candidates increasingly expect it — and in several regions, pay transparency is now legally required. Including a salary band improves application quality and saves everyone time later in the process.
Why do good candidates keep dropping out of our process?
Often, it starts with misalignment created by the JD itself. If candidates arrive at an interview with a different understanding of the role than you have, that's a signal to revisit what the posting actually communicates — not just how long the process takes.
How often should job descriptions be updated?
Any time the role meaningfully changes, or at minimum once a year. A JD from 2022 almost certainly doesn't reflect what the role looks like today in terms of tools, team structure, or expectations.
Can AI write job descriptions for me?
AI can help draft and refine them — but the clarity has to come from you. The most important inputs are: what does success look like, what's truly required, and what makes this role worth a great candidate's time. Those answers can't be generated. They have to be decided.
If you're spending more time sifting through unqualified applications than talking to strong candidates, the issue is probably earlier in your process than you think. Recroot.io screens and shortlists candidates for you — so your time goes to the conversations that actually matter.
About the author
Gokul Srinivasan
Tags
Recent Blogs
