There’s a moment in almost every hiring cycle where the numbers stop making sense.

The posting went up. Traffic looks fine. Applications are coming in. And yet the people you actually wanted, the ones who’d change the shape of the team, never show up in the pipeline.

Most job descriptions are written for the company that publishes them, not the person reading them, and the best applicants can smell that in about four seconds.

This article covers why that happens, what it costs, and what the teams pulling in better-than-average candidates are doing that most hiring teams still aren’t.

The Shortcomings of Traditional Job Descriptions

Before getting into fixes, it’s worth being honest about what the standard format actually does to a reader. Two things kill most postings: how they’re read, and who they’re written for.

People scan

Nobody reads a job posting word for word.

Decades of usability research back this up: people skim web pages for meaning and decide fast whether to stay. A posting structured as five paragraphs of company history followed by a nineteen-bullet responsibilities block is built for a reader who doesn’t exist.

So the “why this role matters” line, usually the only line that could actually hook someone, sits buried under buzzwords, and the candidate is gone before they reach it.

The language points inward

The second problem is direction. Most descriptions describe what the company needs right now.

‍

Read full article here