All posts

The Unicorn Job Description: How Wishlists Scare Away the Candidates You Actually Want

Open almost any job posting today and you’ll find a familiar pattern: eight years of experience required for a role that didn’t exist seven years ago, proficiency in a dozen unrelated tools, a bachelor’s degree mandated for work that has nothing to do with a classroom, and a closing line about thriving in a “fast-paced, ever-changing environment.” Somewhere in the drafting process, a reasonable job turned into a wishlist for someone who doesn’t exist. This isn’t a minor wording problem. It’s one of the most overlooked reasons strong candidates never apply in the first place.

29 Oct 20264 min read

How job descriptions get inflated

Multiple people add requirements, nobody removes any. A job description often passes through a hiring manager, a department head, HR, and sometimes a skip-level executive, and each one adds a line they’d personally like to see. Almost nobody goes back through and asks what can be cut. Past hires become the template. When a role opens up, the easiest starting point is the previous person’s actual skill set, including things they picked up on the job rather than arrived with. The posting ends up describing an experienced incumbent, not an entry point for a new hire. Fear drives over-specification. A hiring manager who got burned by a bad hire often responds by adding more requirements to the next posting, as if more criteria automatically means better filtering. It usually just means a smaller, more homogenous pool. Nobody is distinguishing “needed on day one” from “will grow into it.” Every skill gets treated as a hard requirement, when in reality some are genuinely essential and others are things a capable hire picks up within a few months.

Who actually gets filtered out

Qualified women apply at lower rates to inflated listings. Research on job application behavior has repeatedly found that many candidates, and women in particular, are less likely to apply unless they meet the large majority of listed requirements, even when they’re genuinely capable of doing the job. Men, on average, apply with a looser read of the same list. A bloated requirements section doesn’t just reduce volume. It skews who’s left in the pool. Career changers and self-taught candidates opt out. Someone who learned a skill through real project work rather than a formal degree often self-eliminates the moment they see a degree requirement, even when the role has nothing to do with credentials. Senior candidates get bored, junior candidates get scared off. An inflated posting often ends up requiring senior-level experience while offering a junior-level title and salary, which confuses both ends of the market simultaneously. Your best-fit candidates assume they’re not good enough. The candidates most likely to be genuinely excellent at a role are often the most honest self-assessors. They read “10+ years and expert in five platforms” literally, and they walk away instead of taking a chance.

What it costs you

A bloated job description doesn’t just shrink the applicant pool. It shrinks the right part of the pool. The candidates who remain are often either wildly overqualified and will leave within a year for something bigger, or they’re comfortable inflating their own resume to match the inflated post, which reintroduces the evaluation problem further down the funnel. Meanwhile, the role sits open longer than it needs to, because you’re sourcing against a profile that barely exists in the market.

How to write a job description people actually apply to

Separate “must have” from “nice to have,” and mean it. A requirement only belongs in the must-have list if a candidate genuinely cannot succeed without it on day one. Everything else goes in a clearly labeled second tier, or gets cut entirely. Cap the list. If a role needs more than five or six hard requirements to do the job, that’s usually a sign the role itself needs to be scoped more tightly, not a sign the list needs to be longer. Replace tools with capabilities where possible. “Experience with a modern CRM” opens the door to someone who’s used a different platform than the one you happen to use, while still filtering for the underlying skill. Question every degree requirement. For a meaningful share of roles, a degree is used as a rough proxy for other things, reliability, communication, baseline knowledge, that can often be assessed more directly through the actual hiring process. Read it as a candidate would. Before posting, ask whether someone genuinely qualified but a little less confident would read this and think “that’s me,” or “I’d be wasting everyone’s time.” If it’s the second reaction for a candidate you’d actually want, the listing needs editing. Write the actual first-90-days work, not an aspirational wish list. A posting grounded in real, near-term responsibilities naturally pulls in people who can do that work, rather than people who happen to match an idealized long-term vision of the role.

See WorkGlide in action

Book a 30-minute walkthrough and see how teams cut time-to-hire by 80%.

Book a demo