How to Write a Job Description That Actually Gets Qualified Candidates

Most job descriptions are optimized to attract more applicants. That's the opposite of what a hiring team actually needs.

A hiring manager posts a role. Two hundred applications arrive in the first week. HR is relieved, the req is clearly popular, sourcing won't be a problem. Then screening starts, and it turns out maybe eight of those two hundred are worth a first call. Everyone assumes the market is tough, or the requirements weren't strict enough, or recruiting needs better tools.

Often, the real problem is upstream. It's the job description itself, and specifically, what it was written to optimize for.

This guide breaks down why most job descriptions attract the wrong candidates, what qualified candidates are actually scanning for, and a full framework you can reuse for your next req, backed by research from LinkedIn, Indeed, Gallup, and Harvard Business Review, not guesswork.

If your team is actively hiring and wants a second read on where a role is losing candidates, OnHires runs recruitment services for hard-to-fill technical and leadership roles across the US, Europe, LatAm, and Asia.

Why most job descriptions attract the wrong candidates

Most weak job descriptions fail for a small, repeatable set of reasons, not because whoever wrote them didn't care, but because job descriptions are almost always written under time pressure, by borrowing from whatever exists already.

They start from an outdated template. A description gets copied from the last time the role was open, sometimes years earlier, and updated just enough to feel current. The responsibilities no longer match how the team actually works, but nobody rewrites from scratch because the old version is "close enough."

They list every possible responsibility instead of the real ones. LinkedIn's own guidance to employers is to consolidate responsibilities and qualifications into four to six bullet points, and explicitly avoid trying to build an exhaustive list of every possible task (LinkedIn Talent Solutions). In practice, most descriptions do the opposite: fifteen bullet points, several of them redundant, none of them prioritized.

They blur must-haves and nice-to-haves into one list. When "5+ years of experience," "startup background," "MBA preferred," and "experience with our exact tech stack" all sit in the same bulleted list with the same visual weight, candidates have no way to tell which requirement is actually disqualifying and which is a bonus. Many self-select out over a requirement that was never a hard line to begin with.

They stack requirements into a role nobody has ever done. Harvard Business Review's research on skills-based hiring, based on an analysis of more than 50 million job postings, documented a well-known pattern often called degree and requirements inflation: employers gradually adding credentials and years-of-experience requirements to roles that hadn't materially changed (Fuller, Langer & Sigelman, Harvard Business Review, Feb. 11, 2022). The same research found that a meaningful share of employers have since started reversing this: 46% of middle-skill and 31% of high-skill roles saw employers relax degree requirements between 2017 and 2019. The companies that haven't caught up are still describing candidates who don't exist.

They omit the details candidates actually decide on. Salary, location, work format, and what the hiring process looks like are frequently missing entirely. Indeed's own data shows why this matters: job postings with employer-provided salary information get 5.1 times more impressions than those without, and postings that include salary, schedule, and benefits information get 49% more application starts on average (Indeed, "Can You Post a Job on Indeed Without Salary?," last updated May 7, 2026). Leaving this information out doesn't make a company look mysterious and exclusive. It makes qualified candidates move on to the next listing.

They talk entirely about what the company wants, not what the candidate needs to know. Company mission statements, culture paragraphs, and a long list of demands, with nothing about what success in the role actually looks like or why the role exists now.

They lean on clichés instead of specifics. "Fast-paced environment," "wear many hats," "rockstar," "ninja." None of this tells a serious candidate anything real about the job.

They create unicorn profiles. A senior engineering title that also expects five years in a specific niche framework, prior startup founder experience, and people-management skills, essentially several different careers compressed into one req. When a role requires a rare combination of unrelated skills, it usually gets filled by someone who's not actually a strong fit for most of what's listed, or it doesn't get filled at all.

‍

What qualified candidates actually need to decide

A strong candidate, someone with options, is not scanning a job posting to find reasons to apply. They're scanning it to find a reason not to waste their time.

LinkedIn's data on job seeker behavior puts a number on how fast that decision happens: candidates take about 14 seconds to decide whether to keep reading a job post or move on (LinkedIn Talent Solutions). In those 14 seconds, an experienced candidate is typically looking for:

• What they'd actually be doing, not a duty list, but the shape of the role
• Why the role exists right now, is this a new function, a backfill, a scaling need
• What "good" looks like in the first six to twelve months
• Whether they clear the real bar, which requires knowing what's actually non-negotiable
• Compensation and work model, so they can self-select in or out honestly
• Team and reporting context, who they'd work with and who they'd report to

Candidate experience research from Gallup reinforces why this matters beyond the application itself: new hires who had an exceptional candidate experience are 2.7 times more likely to say the job turned out to be as good as or better than expected, and 3.2 times more likely to strongly agree they feel connected to the company's culture (Gallup, "The Lasting Impact of Exceptional Candidate Experiences," updated Oct. 2025). The job description is where that experience starts, or breaks down, before a candidate has even applied.

‍

The OnHires job description framework

This is the structure we use with hiring teams when a role isn't converting. It isn't a fill-in-the-blank template, it's a set of decisions each section forces you to make explicit.

1. Clear, searchable job titlePurpose: help the right people find the role and immediately understand its level.Include: an industry-recognizable title, not an internal nickname.Avoid: "Growth Ninja," inflated titles that don't match the actual seniority, or invented titles unique to your company.Good example: Senior DevOps EngineerWeak example: Infrastructure Wizard

2. Short role summaryPurpose: give a candidate the shape of the job in two to three sentences before they read anything else.Include: what the role owns, at what level of seniority, on what kind of team.Avoid: restating the job title in longer words.

3. Why the role existsPurpose: context that helps a candidate understand urgency, scope, and opportunity.Include: whether this is new headcount, a backfill, or a function being built out for the first time.Avoid: skipping this. It's one of the fastest ways to signal whether a role is a real opportunity or a treadmill.

4. Key outcomes for the first 6 to 12 monthsPurpose: define success in outcomes, not tasks.Include: two to three concrete outcomes a strong hire would be expected to deliver.Avoid: vague statements like "hit the ground running."

5. Core responsibilitiesPurpose: give an honest picture of the day-to-day.Include: four to six specific, real responsibilities, consistent with LinkedIn's own guidance to employers on job post structure (LinkedIn Talent Solutions).Avoid: an exhaustive list covering every task the role might ever touch.

6. Must-have skills and experiencePurpose: state the real, non-negotiable bar.Include: only what would genuinely disqualify a candidate if missing.Avoid: treating years of experience as a stand-in for competence. This is precisely the pattern behind the requirements inflation documented in the Harvard Business Review research cited above (Fuller, Langer & Sigelman, 2022); a specific number of years rarely predicts whether someone can do the job.

7. Nice-to-have qualificationsPurpose: signal genuine bonuses without disqualifying strong candidates who lack them.Include: two or three items, clearly labeled as preferences.Avoid: mixing these into the must-have list, where they quietly become disqualifying.

8. Reporting line and team contextPurpose: help a candidate understand where they'd sit and who they'd work with.Include: who they report to, team size, key cross-functional partners.

9. Work model and locationPurpose: remove ambiguity before it costs you a candidate late in the process.Include: remote, hybrid, or onsite, and what that actually means in practice (how many office days, which time zones).Avoid: vague flexibility language that isn't backed by an actual policy.

10. Salary or compensation rangePurpose: filter for aligned expectations and increase serious applications.Include: a real, realistic range. Indeed's data shows salary-transparent postings get meaningfully more qualified engagement, not just more volume (Indeed, 2026).Avoid: an unreasonably wide range that reads as a placeholder.

11. Benefits and relevant conditionsPurpose: round out the full offer, not just cash comp.Include: the two or three benefits that genuinely differentiate you, not a generic list.

12. Hiring-process stagesPurpose: reduce anxiety and drop-off by setting expectations.Include: number of stages, roughly how long the process takes, what each stage involves.Avoid: leaving candidates to guess. Unclear or lengthy processes are consistently cited as a top reason candidates abandon applications (iCIMS, 2025 State of Frontline Hiring Report, cited in HR Dive, Aug. 28, 2025).

13. Equal opportunity or inclusion statementPurpose: signal genuine commitment, not boilerplate.Include: a real, specific statement, not just a legally required line buried at the bottom.

14. Clear call to actionPurpose: tell the candidate exactly what to do next.Include: how to apply, what to expect immediately after applying.

‍

Before and after: a Senior DevOps Engineer role

Before

Infrastructure Ninja Wanted

We're a fast-paced, hyper-growth startup looking for a rockstar DevOps engineer to join our world-class team. You'll wear many hats and help us scale to the next level.

Requirements: 7+ years DevOps experience, expert in Kubernetes, Terraform, AWS, GCP, and Azure, strong leadership skills, startup experience required, computer science degree preferred, excellent communicator, thrives under pressure, must be a culture fit.

Responsibilities: manage all infrastructure, own CI/CD, handle security, mentor junior engineers, participate in on-call, work with every team in the company, drive DevOps culture, and more.

This version is a template that's been recycled for three years, mixes seven-plus years of experience with expertise across four different cloud providers (a combination that describes almost no one), gives no indication of team size, reporting line, or comp, and buries the actual scope of the role under vague enthusiasm.

After

Senior DevOps Engineer

We're hiring a Senior DevOps Engineer to own our CI/CD pipeline and cloud infrastructure as we scale from 40 to 100+ engineers over the next year. This is a newly created role reporting to our Head of Engineering, on a team of three.

In your first 6 months, you'll: consolidate our deployment pipeline into a single, documented process; reduce average deployment time by 30%+; and own our AWS cost and reliability posture.

Core responsibilities: design and maintain CI/CD pipelines; manage AWS infrastructure via Terraform; lead incident response and on-call rotation (1 week in 4); partner with engineering leads on infrastructure decisions.

Must-have: production experience with Kubernetes and Terraform on AWS specifically; experience owning infrastructure decisions, not just executing them; comfort working in a small team without a large platform org around you.

Nice-to-have: experience with multi-region deployments; prior fintech or regulated-industry experience.

Work model: hybrid, 2 days/week in our [city] office. Salary: $150,000 to $185,000 base, plus equity. Process: intro call, technical interview, system design session, team meet, offer, typically completed within 3 weeks.

The rewritten version states a real range of experience without demanding an impossible combination of cloud platforms, gives a concrete first-six-months outcome, separates must-haves from nice-to-haves honestly, and answers the practical questions, comp, work model, timeline, that determine whether a strong candidate applies at all. If you're hiring this exact role, our DevOps hiring guide has current market salary and time-to-fill benchmarks for it.

‍

What most hiring teams get wrong, even with a polished description

A job description can look professionally written and still fail, because the problems aren't always in the document itself.

Using the description to align the internal team after it's published. If the hiring manager, recruiter, and interview panel don't agree on the must-haves before the role goes live, the description becomes a first draft of internal alignment instead of a clear signal to candidates, and requirements often shift mid-process as a result.

Changing requirements during the interview process. A candidate who was told the role was open to less experience suddenly hits a wall at the fourth interview because someone decided seniority matters more than originally stated. This is one of the fastest ways to damage candidate trust and waste everyone's time.

Advertising a title that doesn't match actual seniority. Inflating a title to attract more applicants creates a mismatch that surfaces in the first real conversation, wasting both sides' time.

Treating years of experience as a proxy for competence. As the Harvard Business Review research on skills-based hiring makes clear, this is a documented pattern, not a one-off mistake, and reversing it is specifically what the strongest employers are now doing (Fuller, Langer & Sigelman, 2022). If your team is trying to move toward skills-based hiring but doesn't have the internal bandwidth to screen for it consistently, working with a team that runs vetted, pre-screened candidates is usually faster than building that muscle from scratch.

Asking for skills the role won't actually use. Requirements copied from a job board template rather than the real day-to-day, which filters out well-suited candidates for no real reason.

Promising flexibility that isn't available in practice. "Flexible work" in the posting, followed by an unstated expectation of daily office presence, is one of the more common sources of early attrition once someone actually starts.

‍

Job description quality checklist

Before publishing a role, confirm:

• The title is industry-recognizable and matches actual seniority
• Responsibilities are limited to 4 to 6 specific, real items
• Must-have and nice-to-have requirements are clearly separated
• No requirement demands an unrealistic combination of skills or years
• The first 6 to 12 months' outcomes are stated, not just duties
• Salary or a real range is included
• Work model and location are specific, not vague
• Reporting line and team context are included
• The hiring process stages and rough timeline are stated
• The description has been reviewed by the hiring manager, not just written by them
• It has been read aloud once, if it sounds like a list of demands, it needs another pass

‍

How to measure whether the description is working

A high number of applications is not, by itself, evidence that a job description is doing its job. Track these instead:

• Qualified applicant rate, the share of applicants who meet the actual must-have bar, not just the share who applied
• Application completion rate, how many people who start an application finish it. Overly long or unclear applications are a documented driver of drop-off: separate 2025 research from iCIMS and LiveCareer both found that roughly 55 to 60% of candidates have abandoned an application mid-process, most often citing length or complexity (iCIMS 2025 State of Frontline Hiring Report and LiveCareer, Aug. 14, 2025, both cited in HR Dive, Aug. 28, 2025)
• Source-to-screen conversion, whether the candidates a specific channel sends you are actually passing initial screening
• Screen-to-interview conversion, a low rate here often means the description is attracting the wrong profile, not that screening is too strict
• Recurring candidate questions, if multiple candidates ask the same clarifying question, the description is missing that information
• Offer acceptance rate, low acceptance can mean the description set expectations the actual role or offer doesn't match
• Early attrition linked to mismatched expectations, the clearest signal that a description oversold or misrepresented the role

If applications are high but qualified interviews are low, the fix is almost never "write a more exciting job post." It's usually narrowing and clarifying what's actually being asked for. For a deeper framework on tracking hiring quality beyond the job description stage, see the OnHires Hiring Quality OS.