Why Most Job Descriptions Repel the Candidates You Actually Want
If you've ever posted a role and watched your inbox fill with mismatched applicants — or, worse, stay eerily quiet — the problem likely started with the job description. This guide is for recruiters and hiring managers who want to know how to write a job description that does its actual job: attracting qualified people who are genuinely interested in the role.
Most JD failures trace back to three fixable problems.
Bloated requirement lists. When every possible skill ends up in the must-have column, qualified candidates assume they won't make the cut and scroll past. The posting ends up attracting people who either oversell themselves or genuinely don't fit.
Vague role summaries. A two-line summary that says "you'll be part of a dynamic team driving impactful outcomes" tells a candidate almost nothing. They can't picture the job, so they either take a shot in the dark or move on.
Jargon and coded language. Phrases like "rockstar," "ninja," or "must thrive in a fast-paced, high-pressure environment" signal a culture before anyone has applied — and they push away exactly the thoughtful, skilled candidates you want.
Fix those three things and the rest of the funnel gets noticeably easier.
How to Write a Job Description That Works (Section by Section)
A well-structured JD has six sections. Every one of them earns its place.
1. Job Title
Use the term candidates actually search for. If your internal title is "Revenue Growth Ninja," post it as "Sales Development Representative." Unusual titles confuse candidates and get buried in job board search results. Applicant tracking systems (ATS) — the software employers use to collect and filter applications — also parse non-standard titles inconsistently. Save the creative nickname for the offer letter.
2. Role Summary
Two to three sentences maximum. Answer:
- What does this person do day-to-day?
- Who do they impact — customers, team, or leadership?
- Why does the role exist right now?
Example:
Vague: "You'll support the HR team in various people-related functions."
Clear: "You'll own the full-cycle onboarding experience for 50+ new hires each month, partnering with department leads to reduce ramp time and improve 90-day retention."
The second version gives candidates a reason to care and tells them what success looks like before they've applied.
3. Responsibilities
Lead with outcomes, not tasks. "Manage onboarding" is a task. "Own the onboarding experience for 50+ monthly new hires and cut average time-to-productivity by coordinating across IT, HR, and department leads" is an outcome. Outcomes help candidates assess whether they're actually equipped for the role.
Keep the list to five to eight bullets. If you have fifteen responsibilities, you're either describing three jobs or you haven't prioritized.
4. Requirements
Covered in depth below.
5. Compensation and Benefits
Include a salary range. It improves applicant quality and reduces time-to-fill. More on this below.
6. Application Instructions
Tell candidates exactly what to submit, how, and by when. "Apply here" with a link is not enough if you want a cover letter or work sample. Ambiguity at this stage creates drop-off.
Must-Have vs. Nice-to-Have: Drawing the Line Honestly
This is where most job descriptions go wrong — and where the self-selection problem begins.
When required and preferred qualifications are mixed into one undifferentiated list, candidates can't tell what's actually necessary. Some people who would excel in the role rule themselves out. Others who aren't qualified apply anyway because they see a few checkboxes they can tick.
The Day-One Test
For every requirement on your list, ask: Could someone succeed in this role without this on day one?
If the answer is yes — or even "probably yes with some onboarding" — it's not a must-have. Move it to the preferred list or cut it entirely.
The Experience Trap
"5+ years of experience in X" is a proxy, not a requirement. What you actually need is the skill or knowledge that experience is meant to signal. Name that directly.
Instead of: "5+ years of experience in project management" Write: "Demonstrated ability to run concurrent projects with cross-functional stakeholders and shifting deadlines"
This opens the role to career changers, people who built skills in non-traditional settings, and candidates from underrepresented backgrounds who may have progressed faster than a year-count reflects.
Degree Requirements
Ask honestly: Is a degree legally or operationally required for this role? Or is it a default carried forward from a posting written years ago? For many roles — particularly in technology, operations, and creative fields — removing the degree requirement widens the pool without reducing quality.
A Format That Works
You need:
- [Must-have 1]
- [Must-have 2]
- [Must-have 3] (keep this list to six items or fewer)
Bonus if you have:
- [Nice-to-have 1]
- [Nice-to-have 2]
Two clearly labeled lists. Candidates know where they stand.
Language That Widens Your Pool Instead of Narrowing It
Word choice shapes who applies. If your language consistently attracts one type of candidate, you're narrowing the pool before a single resume comes in.
Gendered and Coded Language
Words like "aggressive," "dominate," "rockstar," and "killer instinct" aren't universally off-putting, but research on job posting language consistently finds they correlate with a narrower, more homogeneous applicant pool. Neutral equivalents perform as well or better:
| Avoid | Use instead |
|---|---|
| Aggressive self-starter | Takes initiative and drives projects forward |
| Rockstar communicator | Communicates clearly across audiences |
| Dominate your market | Grow market share in your territory |
Ableist and Exclusionary Phrasing
"Must be able to lift 50 lbs" belongs in a posting where it's genuinely required. As a default filler in office roles, it creates legal exposure and signals carelessness. The same logic applies to "fast-paced environment" — if it's true and relevant, say why (e.g., "we operate on two-week launch cycles"). If it's just shorthand for "we're chaotic," fix the culture before advertising it.
The Confidence Gap
Candidates from many backgrounds are more likely to skip applying if they don't meet every listed criterion. The fix isn't a disclaimer at the bottom ("we encourage you to apply even if you don't meet all requirements"). The fix is a shorter, more honest list so that most qualified candidates see themselves in it from the start.
Signal Belonging Explicitly — and Honestly
A genuine sentence about your team's commitment to inclusion, tied to a real practice ("We review all applications anonymously in the first round" or "Our interview panel includes people from outside the hiring department"), outperforms boilerplate EEO copy. If the language doesn't reflect what actually happens, cut it.
Readability
Aim for a Grade 10–12 reading level. Use short paragraphs. Prefer active voice. A job description isn't a legal document — write it like you'd explain the role to someone you met at an industry event. Your goal is a frictionless read for the widest qualified audience.
Compensation, Benefits, and the Case for Transparency
Candidates self-select far more accurately when they know what a role pays. That's good for you — it reduces late-stage offers that fall apart over compensation and cuts the time you spend screening candidates who were never in range.
Post the realistic hiring range, not the theoretical ceiling of your internal band. If your band runs $80K–$130K but you're hiring at $90K–$100K, post $90K–$100K. A $50K spread signals that you either don't know what you're hiring for or you're planning to anchor low.
Prioritize high-value benefits in your description:
- Schedule flexibility (remote, hybrid, core hours)
- Healthcare and leave policies
- Career growth and development support
- Retirement matching
De-emphasize perks that don't meaningfully affect a candidate's decision to join or stay.
Pay transparency laws exist in a growing number of jurisdictions. Leading with disclosure — regardless of whether your location requires it — signals that your organization operates with integrity and positions you ahead of the curve.
JD Best Practices: A Pre-Publish Checklist
Run through this before you post. It takes ten minutes and regularly catches issues that create weeks of screening problems.
- Length: Is the JD between 400 and 700 words? Cut anything that doesn't change a candidate's decision to apply.
- Requirement audit: Have you run each must-have through the day-one test? Remove any that are really onboarding goals.
- Language scan: Check for coded words, vague superlatives ("passionate," "self-starter," "detail-oriented"), and unnecessary degree or experience proxies.
- Consistency check: Does your job title in the JD exactly match what's posted on the job board and what your ATS will parse? Mismatches create downstream screening problems.
- Keyword alignment: Have you included the terms candidates realistically search for? This matters for job board discoverability and for accurate keyword parsing when ATS tools evaluate inbound resumes.
- Compensation included: Is there a salary range? If not, add one.
- Application instructions: Are they explicit? Does a candidate know exactly what to submit?
Using a job description template doesn't mean copying the same text every time — it means having a reliable structure you fill in consistently, so nothing gets skipped under deadline pressure.
From JD to Screening: Making Sure Your Criteria Match Your Process
A well-written job description creates a problem if your screening process doesn't reflect it. If your JD lists six must-haves but your ATS is filtering on ten different fields — or different reviewers are prioritizing different things — you're losing good applicants before they get a fair look.
Map your must-have list directly to your screening scorecard. Every criterion in the "You need" section should have a corresponding evaluation step. If a criterion isn't being screened for, it shouldn't be a must-have in the JD.
At higher volume, this consistency gets harder to maintain manually. ATSEye's batch screening and multi-JD matching let recruiters apply the same structured criteria across a large applicant pool — reducing the drift that happens when different reviewers are effectively using different standards.
What to Do Next
Pick your next open role — or one currently posted — and run it through the checklist above. Count your must-haves. Remove the ones that don't pass the day-one test. Scan for coded language or degree requirements that are really just defaults. Confirm your job title matches what candidates search for.
A well-written JD is the first filter in your hiring process. Make it accurate instead of aspirational, and every stage after it — screening, interviews, offers — gets a little cleaner.
Written by
ATSEye Recruiting Team
Screening & talent-acquisition specialists
The ATSEye Recruiting team works with recruiters and hiring managers on high-volume screening — turning stacks of resumes into ranked, defensible shortlists against real job requirements.