Most companies hire the way they've always hired, using criteria nobody has questioned in years. If you run a team or a company, it's worth asking whether your own shortlist rules are quietly filtering out the people who would actually be good at the job — and replacing them with people who are merely good at looking qualified on paper.
Every hiring process has a set of rules nobody wrote down on purpose. A degree requirement. A minimum number of years of experience. A preference for candidates who’ve held the exact same title before. These rules feel like common sense. They are rarely examined, and they are rarely tested against actual job performance. That gap is where good people get filtered out before anyone on your team even sees their resume.
Where the criteria actually came from
Most hiring requirements were not designed. They were copied. Someone wrote a job description years ago, borrowed language from a similar role, and added a credential because it seemed like a safe bar to clear. Over time, that language gets reused for every opening in the department, whether or not it has anything to do with what the job requires day to day.
The problem is that credentials are easy to screen for and hard to challenge. A degree is a single data point an applicant tracking system can sort on. Whether someone can actually do the work is much harder to measure from a resume, so companies default to the proxy instead of the thing itself. The proxy becomes the standard. Nobody revisits whether it was ever a good one.
What gets screened out when you do this
The people most likely to be filtered out by rigid criteria are often the ones with the most relevant real-world skill. Someone who built a career through apprenticeship, military service, or a nontraditional path may do the job better than someone with the expected credential, but never gets an interview because the applicant tracking system discarded them automatically. A parent who stepped out of the workforce for a few years to raise children gets flagged for a resume gap, even though the gap has nothing to do with capability. A career-changer with transferable skills gets passed over because their most recent title doesn’t match the one in the posting.
None of this is intentional bias in the way people usually picture it. It is structural. The system is built to reward resumes that look like the last ten resumes that got hired, which means it reproduces the same type of hire over and over, regardless of whether that type was ever the best fit.
How to test your own process
If you want to know whether your hiring criteria are actually doing their job, look at your current team. Pull up the people who are performing best in a given role and compare their original resumes against the criteria you currently use to screen candidates for that same role. Often you’ll find that your top performers wouldn’t have made it past your own filters if they applied today. That’s a signal the filter is wrong, not that the people are exceptions.
Another test: separate the requirement from the reason for the requirement. If a job posting asks for five years of experience, ask what that number is actually protecting against. Usually the honest answer is something like judgment under pressure, or comfort managing a team, or familiarity with a specific kind of problem. Once you name the real thing you’re looking for, you can write a requirement that tests for it directly instead of using years as a stand-in.
What to change in the process itself
Small, structural changes tend to do more than rewriting the job posting. Consider these shifts:
- Replace credential requirements with skills assessments where possible, so candidates are judged on what they can do rather than what they’ve been told to list.
- Have more than one person review resumes that get auto-rejected by software, at least occasionally, to catch good candidates the system is discarding.
- Ask hiring managers to write down what success in the role actually looks like after six months, then check the job posting against that description.
- Remove requirements that were copied from a template and never verified against actual job needs.
These changes take more time up front than running a resume through a filter. They tend to pay off in retention, because people hired for actual fit stay longer than people hired for matching keywords.
The takeaway
A hiring process that has never been questioned is not a safe default. It is an untested assumption that gets repeated because nobody has had a reason to look at it closely. If you’re responsible for building a team, the filters you inherited deserve the same scrutiny you’d give any other business decision that affects who gets through the door — and who never gets the chance to.