The Job Description Is Broken. That's Why Your Pipeline Is Thin.

The job description is the first filter in your hiring pipeline — and for most companies, it's the most miscalibrated one. Research from LinkedIn's Global Talent Trends report shows that 44% of women and 30% of men will not apply to a role where they meet most but not all listed requirements [1]. That means the credential list someone wrote during a busy quarter is making a quiet hiring decision on your behalf, every single day, before a single recruiter opens the queue.

This isn't a sourcing problem. It isn't a screening problem. It's an origination problem, and it compounds every other investment you're making downstream.

The Credential Creep Nobody Reversed

Job descriptions accumulate requirements the way codebases accumulate technical debt: gradually, invisibly, and usually during periods of expansion when nobody is paying close attention to what's actually necessary versus what's merely comfortable.

A role gets posted during a high-growth year. The hiring manager wants a degree because the last three people in the role had one. They add "7+ years of experience" because that's what the team is used to seeing. Someone adds a certification that's tangentially related. The requisition closes, the hire works out, and those requirements get copy-pasted into the next version without examination. Three years later, the company is hiring for a different market, a different growth stage, and a function that's evolved. The job description hasn't. The credential list is filtering hard — but against a target that no longer exists.

The data is concrete: companies with high requirement lists see 14% fewer applications per role on average, with disproportionate drops from career-changers, returners, and candidates from non-traditional paths [2]. These aren't the people you'd filter out in screening anyway. They're the candidates who never showed up.

Why This Problem Scales Badly

When you're hiring one or two roles a quarter, a thin pipeline is manageable. You source harder, cast a wider net. The inefficiency stays invisible. When you're running 20 concurrent requisitions across departments, the JD problem is structural. Every over-specified role reduces inbound by some percentage. Multiply that across your open headcount and you've created a supply constraint before your recruiters have done a single thing wrong. The ATS is working. The sourcing tools are working. The screening process is working. But the top of the funnel is chronically undersized, and everyone downstream is managing scarcity instead of selecting quality.

The fix most teams reach for is sourcing budget: more credits, more job board spend, more agency retainers. That treats the symptom. The root cause is a document that could be rewritten in an afternoon — one that describes the actual work instead of listing credential proxies for it. What does success look like in this role at six months? What problem is this person actually solving? Write to that frame, and you stop pre-filtering for credential similarity. You start attracting people who can do the job, including people who got there a different way.

What Happens When You Open the Top of the Funnel

There's a real objection to loosening JD requirements: if you broaden the criteria, volume goes up but so does noise. The screening load increases. A team that processed 80 focused applications now has 180 mixed ones. Most teams stop there. The volume trade-off feels unfavorable. Better to have a thin pipeline of people who look right on paper than a large one that requires real work to sort. That calculus made sense before AI-powered screening existed at scale. It doesn't anymore.

Asendia AI is a voice-first AI recruiter that screens candidates 24/7. When someone applies, Asendia calls them — that evening, that weekend, whenever the application arrives — and conducts a structured, adaptive spoken conversation probing actual skills, relevant experience, and role-specific thinking. Not keyword matching. Not a form fill. A real-time voice exchange that follows up based on what the candidate actually says. The AI plugs directly into your existing ATS: screened candidates land in your normal pipeline with qualification summaries and verbatim conversation excerpts attached. Recruiters inherit a vetted shortlist, not a raw inbox.

A recruiter with a broader JD and Asendia running around the clock can surface genuinely qualified applicants from a larger, more diverse pool without anyone falling through the cracks of a manual queue. Recruiting agencies use this to run high-volume campaigns with lean teams — absorbing application spikes without adding headcount, because the AI handles every first conversation at any hour. The volume that used to feel like a liability becomes an operational advantage. For more on what skills-based assessment looks like at scale, the post on AI candidate screening for skills-based hiring covers how to evaluate actual capability rather than credential proxies.

Final Word

The job description is not a formality. It is the first filter in your hiring process — and for most companies, it's the most consequential one, because it operates before any human decision is made and shapes the entire downstream pool. Companies that have invested in sourcing tools, ATS upgrades, and structured interview processes often haven't examined the document that determines who applies in the first place. Loosening credential requirements isn't a risk to quality. It's a bet that what a person can do matters more than the path they took to be able to do it. The screening process that follows is what should surface that distinction. Most aren't built to do it at scale. The ones that are can afford to write job descriptions that actually describe the job.

Ready to transform your hiring strategy? Schedule a Demo with our founders today!