Job Descriptions That Filter Instead of Attract
How an inflated requirements list quietly shrinks a candidate pool, and who it shrinks it from the most.
Published April 23, 2026
A requirements list padded with everything that would be nice to have, rather than what the role actually needs on day one, doesn't attract more candidates. It filters out qualified ones, and the effect isn't evenly distributed across who applies.
The research behind this isn't a hunch
Multiple studies on job applications have found that many candidates, particularly women and people from underrepresented groups in a given field, are meaningfully less likely to apply to a role unless they meet nearly all of the listed requirements, while candidates from majority groups are more likely to apply even when they meet only a partial match. A bloated requirements list doesn't just reduce the applicant pool, it skews who's left in it.
What a wish list looks like next to an actual requirement
"10+ years of experience" for a role that genuinely needs five is a wish list item wearing a requirement's clothing. A real requirement is something the role cannot function without on day one; everything else belongs in a separate, clearly optional "nice to have" section, or shouldn't be listed at all.
What actually attracts strong candidates instead
A specific, concrete description of the actual day-to-day work does more than a long list of credentials. Candidates evaluating a role are trying to picture themselves doing the job; "build and maintain our core web application, work directly with design on new features" gives them something real to picture, where a generic list of years-of-experience thresholds doesn't.