Frozen in 2019: The Job Descriptions Still Running Your Hiring Process

Pull up the job description for the last position you filled. Now ask a simple question: does the document describe the work as it is performed today, or as it was performed four or five years ago?

For a surprising number of American employers, the honest answer is the latter. Job descriptions are among the most durable documents in any organization — written once, saved as templates, and recycled at every opening. But the workplace they were written for has been dismantled and rebuilt several times over. Remote and hybrid arrangements, AI-assisted tooling, flattened teams, and redefined supervisor roles have quietly rewritten the day-to-day of most positions. The postings, in many cases, never got the memo.

The result is a hiring process aimed at a target that has moved. Candidates read a description of a job that isn't the one they'd be doing, screening managers filter against requirements that no longer matter, and both sides waste time on a mismatch that was baked in before the first interview was scheduled.

Why Legacy Descriptions Persist

There is rarely a villain here. Job descriptions survive because updating them is nobody's assigned job. HR owns the template; the hiring manager owns the role; the requisition deadline owns everyone. When an opening appears, the fastest path is to pull last cycle's posting, adjust the salary band, and publish.

The trouble is that each shortcut compounds. A description written in 2019 reflects the team structure of 2019, the tooling of 2019, and the assumptions about where and how work happens that prevailed in 2019. Multiply that by a few hiring cycles and you have a document that is less a blueprint than an archaeological record.

The Three-Part Audit

Refreshing a stale description does not require a consulting engagement. It requires a structured hour with the people closest to the work. We recommend a three-part review.

First, inventory the skills. Sit down with the current incumbent — or, if the seat is empty, the person absorbing the duties — and list what they actually did last month. Compare that list against the requirements section of the posting. The gaps usually fall into two buckets: skills the document demands that nobody uses (a legacy enterprise platform, a certification inherited from a departed manager's preferences), and skills the work now requires that the document never mentions (AI-assisted research, distributed collaboration, a compliance landscape that has shifted).

Second, interrogate the requirements. Requirements sections accrete like sediment. Each past hiring disappointment tends to add a line; almost nothing is ever removed. Ask of every listed qualification: what happens, concretely, if a strong candidate lacks this? If the answer is "probably nothing," it is a preference, not a requirement, and it belongs in a different section — or nowhere at all. This is also where degree inflation and arbitrary year-counts tend to hide. A posting demanding twelve years of experience with a technology that has existed for nine is not a filter for excellence; it is a filter for inattention.

Third, describe the reality of the arrangement. If the role is hybrid, say so plainly, including which days. If the team is distributed across time zones, say that. If the description still implies five days at a desk in a city where the team no longer sits, you are not protecting flexibility — you are filtering out every qualified candidate who reads carefully and concludes the posting is fiction.

What a Refresh Actually Changes

The concern we hear most often from hiring managers is that softening a job description means lowering the bar. In practice, the opposite tends to occur. A precise, current description raises the quality of the applicant pool because it attracts people who want the job as it genuinely exists — and deters those who want a job that was retired in 2020.

Consider the arithmetic. A posting trimmed from fifteen requirements to six is not less rigorous; it is more legible. A responsibilities section rewritten around outcomes rather than tasks gives a strong candidate something to respond to. And a description that acknowledges modern tooling signals an organization that pays attention — a small but real advantage in a labor market where skilled candidates routinely hold multiple offers.

Make the Audit a Habit, Not an Event

The best-run organizations we work with have stopped treating job descriptions as static documents. They attach a review date. They ask every departing employee whether the posting matched the job. They require the hiring manager to confirm, in writing, that the requirements list reflects the current work before a requisition is opened.

None of this is glamorous. But hiring is where strategy meets the labor market, and a stale description is a strategy document nobody has read since the last presidential administration. If you cannot remember why a line is in your posting, that is not a reason to keep it. It is a reason to find out — before another strong candidate reads it and moves on.