Every recruiter has lived through this, even if few hiring leaders say it out loud. A search starts with a reasonable set of requirements. A few interviews in, the requirements start to grow.
“Let’s find someone with industry experience.”
“Maybe they should have managed a larger team.”
“Let’s also require this ERP.”
“Oh, and cloud experience would be great too.”
Each addition sounds reasonable on its own. Together, they quietly turn a filled role into an unfillable one. This is the unicorn search, and it is one of the most expensive mistakes a hiring team can make without realizing it is happening.
How Requirements Expand Mid-Search
The drift is rarely intentional. A hiring manager meets the first round of candidates and starts noticing what they lack rather than evaluating them against the original job description. One candidate is missing a certification, and suddenly that certification feels like it should have been required all along.
Interview panels make this worse. Each interviewer walks away with a slightly different idea of what “great” looks like, and those impressions get folded into the next round of requirements instead of being weighed as one opinion among several. By the fifth or sixth interviewer, the role has effectively been redefined five or six times, and no single candidate can satisfy every version of it.
Recruiters end up sourcing against a job description that no longer reflects what is actually being evaluated, and strong candidates get screened out for reasons that were never part of the original conversation.
Essential Qualifications vs. Wish Lists
Most unicorn searches come down to one failure: not separating what a candidate must have from what would simply be nice.
Essential qualifications are the things a candidate cannot succeed without, such as a proven track record leading a major system migration or direct experience managing a budget of a certain size. Wish list items are the ones that help but do not determine success, like experience with one specific platform over another or a background in the exact same industry vertical.
The problem is that wish list items tend to migrate into the essential column as a search drags on, especially when a team is struggling to differentiate between strong candidates. The conversation shifts from “who best meets the core needs of this role” to “who has the most boxes checked,” and a nice-to-have becomes a disqualifier.
A useful gut check: sort every requirement into two columns, cannot succeed without it, and would be a helpful bonus. If you cannot explain why the role fails without a given item, it belongs in the second column.
The Opportunity Cost of Waiting for Perfect
Holding out for the ideal candidate feels responsible. It is often one of the more expensive decisions a hiring team can make.
Every week a critical role sits open has a real cost. Projects stall. Existing team members absorb the extra workload, which raises the risk of burnout and turnover on a team already stretched thin. Institutional knowledge that should be transferring to a new hire sits idle instead, or leaves with departing employees.
The strongest candidates also do not stay available long. A candidate who looked great in week two has often accepted another offer by week six. The longer a search chases a perfect match, the more likely it is that the truly qualified candidates have already moved on, leaving a weaker pool than existed at the start. Perfect becomes the enemy of filled, and filled with a highly capable candidate is usually the better outcome.
Questions to Ask Before Adding Another Requirement
Before tacking on a new requirement mid-search, ask:
Would this role fail without it, or would a strong candidate just need a short ramp-up period? Most skills, technical and leadership alike, can be developed quickly by a capable professional.
Is this based on the needs of the role, or a reaction to one recent candidate? It is common to adjust requirements to chase, or avoid, a specific profile rather than evaluate what the role truly needs.
How many people on the current team would meet this requirement if they applied today? If the answer is few or none, the bar may be set higher than the team’s own standard.
What does continued vacancy actually cost, compared to hiring a strong candidate now and closing the gap?
Has this been discussed with the recruiter? Recruiters are often the first to notice a role has drifted, since they are the ones absorbing the candidate feedback.
Flexibility Produces Better Hires
Teams that stay flexible on non-essential qualifications consistently land stronger hires, not weaker ones. Flexibility widens the pool to candidates with adjacent, transferable experience instead of an exact match.
Someone who led a comparable transformation on a different platform often outperforms a candidate who checks every box but lacks the judgment the role actually requires. It also brings in more diverse professional backgrounds, which strengthens a team’s problem-solving range instead of narrowing it.
Most importantly, flexibility lets a team move fast on a strong candidate instead of continuing to search for an even better one. In a competitive market for senior technical talent, speed is itself a competitive advantage.
Which Requirement Is Actually Non-Negotiable?
The next time a search stalls, gather the hiring team and ask one question: of everything on this list, which requirement is actually non-negotiable?
The answer is usually shorter than expected, and the clarity it produces can be the difference between a search that drags on for months and one that closes with a strong hire in place.
By Jessica Werlinger | Paradigm Group