.png)
"Hard to fill" is not a diagnosis. It is a distress signal. Here are the seven failures actually behind a stuck role, and the sequence for fixing the right one.
Every recruiter knows the nightmare requisition. Not the difficult one. Difficult is fine. Difficult is Tuesday.
The nightmare requisition sits open so long it begins to develop a personality. It appears in pipeline meetings with the dead-eyed inevitability of a recurring dental appointment. It attracts commentary from people who have not read the job description, do not understand the market, and are nevertheless certain the solution is "more sourcing."
So the recruiter searches harder. Posts wider. Rewrites the first sentence. Changes "manager" to "lead." Re-runs the same intake conversation under the polite fiction that this time it will reveal something new. Maybe an agency gets called. Maybe a sour little sentence appears in a meeting: "Is TA prioritizing this?"
And still nothing moves. Or worse, the funnel moves but the problem does not. More applicants, still wrong. More interviews, still no hire.
This is when The Usual Way reaches for its favorite answer: activity. More volume, more pressure, more dashboards, more "quick syncs" that are quick in the same way airport security is quick when viewed from space.
But most nightmare requisitions are not activity problems. They are choice problems. The right people are not choosing the role because the role does not yet feel clear, valuable, believable, differentiated, or worth the risk. All of that hides under the innocent phrase "we need more candidates," which sounds practical and measurable and much safer than saying, "I am not sure this role, as currently designed and explained, is compelling enough to win the people we say we want."
The role that refuses to get filled is telling you something. The answer is not always to push harder. Sometimes the answer is to diagnose sharper.
"Hard to fill" is not a diagnosis
Calling a role hard to fill names the pain, not the problem. It is like telling a mechanic, "The car is bad." Is the battery dead? Is the transmission failing? Is there a raccoon in the engine? These require different solutions, and one hopes, different levels of emotional preparation.
A role can be stuck for completely different reasons, and they should not get the same fix. That is the first discipline: stop treating "hard to fill" as the diagnosis and classify the failure. There are seven.
The seven failures
1. The market failure. Sometimes there genuinely are not enough people who match the spec, salary, location, and requirement stack. This is real and should not be dismissed. But companies invoke "the market is tight" before actually studying it, and the phrase becomes a soothing fog in which nobody has to reconsider the spec, the money, or the hiring manager's favorite impossible combination: someone who has done the exact job, in the exact industry, with the exact systems, for less money, ready in two weeks. Lovely. Does that person exist? And if they exist, why would they choose this? The fix is a market map that shows what the company is asking the market to do: who exists, what they earn, what alternatives they have, which requirements are true must-haves and which are preferences dressed as standards. If the ask is unrealistic, say so. Safely, but clearly.
2. The value failure. A role can be findable and still not be choosable. The internal view says "this role is critical." The candidate view says "this looks like more work for a slightly different logo." That gap is lethal, and its signals are subtle because there is activity: people take the recruiter call, then cool off. Outreach creates curiosity but not momentum. Strong candidates say "interesting, but not enough of a move." The fix is not hype. It is answering the central question: why would a great person leave something known for this? Map the role's actual value using [The Role Value Stack]: what they will build, learn, own, influence, and be able to say they did. A role with real value can still fail if the value is invisible. The JD says "manage cross-functional initiatives." The recruiter says "great opportunity." The candidate hears "meetings."
3. The clarity failure. Candidates cannot choose what they cannot understand. Many stuck roles describe responsibilities but not outcomes, name stakeholders but not authority, and use internal language no outsider would parse. Recruiters explain the role differently each time. Interviewers evaluate against different mental models. The role becomes a rumor. The fix is forcing precision: "strategic" how? "Hands-on" with what? "Fast-paced" because the company is growing, or because nobody plans, or because priorities change whenever someone important has lunch with a new idea? These are morally different forms of fast. A clear role may still be hard to fill, but at least the market is rejecting the real opportunity rather than a foggy imitation of it.
4. The credibility failure. Sometimes candidates understand the promise. They just do not believe it. Ownership, impact, growth, flexibility: all possibly true, all identical to the claims of five other companies this month, two of which recently laid people off with a LinkedIn post about "difficult decisions" and "gratitude." Candidates have been trained to discount unsupported claims. The fix is proof. If the claim is ownership, show the decision rights. If growth, show the path or the pattern. If collaboration, show how disagreement actually gets resolved. A real example beats an elegant adjective. The strongest candidates do not need you to sound more excited. They need you to sound more credible.
5. The audience failure. A role can be accurate and still aimed at the wrong person. The team wants a Builder but writes for a Maintainer. It wants a Craftsperson but sells speed and chaos. The role is not wrong; the audience definition is. Skills are not enough. Define the right-fit candidate by motivation: who would see this mess and think, "Good, there is something to build here"? Then write to that person. Not "7+ years managing operational initiatives," but "this is for someone who likes turning repeated operational pain into a system other teams can trust." That sentence creates identity pull. The right person feels named. The wrong person quietly exits. That is not a problem. That is selection.
6. The tradeoff failure. Every role has a catch. More autonomy means less structure. More visibility means more pressure. The Usual Way hides the catch behind euphemism: "fast-paced" for chaotic, "ownership" for under-supported, "dynamic" for the plan changes weekly. Candidates are not stupid. They sense the catch, and when the company will not name it, suspicion grows and late-stage dropouts follow. The fix is not making the role sound easy. It is making the hard part feel chosen: "You will have real room to shape the approach, but you will not inherit a fully built playbook." A hidden downside becomes a late-stage dropout. A named tradeoff becomes informed consent. Recruiting should not be a surprise party where the surprise is preventable disappointment.
7. The process failure. Sometimes the role is attractive enough, and then the hiring process ruins it. The company says the role is high priority, then takes twelve days to give feedback. The recruiter says the team is decisive, then the candidate has six conversations with people asking the same question in different sweaters. Compensation appears late. Criteria shift after good candidates appear. Every step of the process is evidence. A clean process says, "This company knows what it is doing." A messy process says, "Imagine working here." Candidates often do. Then they choose someone else.
Most nightmare reqs suffer from more than one of these. But name them. A named problem can be worked. A vague problem can only be endured.
The "before more ads" rule
When a role is stuck, the reflex is to buy more attention. Sometimes more distribution is genuinely needed. But more distribution does not fix a weak choice. If the job is unclear, more people will misunderstand it. If the value is weak, more people will reject it. If the process is broken, more people will be lost after you have paid to attract them. Paid distribution makes a broken role fail faster and more visibly.
So before spending, run the seven failures as a checklist: value obvious, audience specific, role differentiated, tradeoffs named, proof credible, process candidate-safe, market reality understood. If any answer is no, fix the choice before buying the attention.
This produces a useful sentence for finance, incidentally: "Before we increase spend, I want to make sure we are not paying to drive more people toward a role that is not yet clear or compelling enough to convert." That sentence changes the room. It moves TA from defense to diagnosis.
The reset meeting
A nightmare req will not be saved by the normal status meeting, which in these cases becomes a ritualized reading of the bad news. Run a reset meeting instead, with five questions.
What have we learned? Start with pattern, not volume: who responded, who dropped, what candidates kept asking, what strong candidates chose instead, what the market kept telling us that we kept politely ignoring. A failed pattern is still a pattern. Use it.
What problem are we actually solving? Make the hiring manager explain the business reason. A role without one sounds like headcount. A role with one sounds like a mission.
Who is the actual right-fit candidate? Not the fantasy. Where are they now, what are they tired of, what would they have to believe for this to feel like a smart risk?
What is the role's value proposition? Where is the value real but invisible? Where are we assuming candidates will infer the upside? Candidates are busy. Inference is expensive.
What are we willing to change? Title, level, salary, scope, requirements, process, decision speed. This is where the truth appears. If the answer is "nothing," say the firm thing carefully: "If nothing about the role can change, then the hiring team has to accept what that choice costs." Recruiting cannot repeal market reality through effort.
Relaunch it as a choice
After diagnosis, do not quietly tweak the job post and hope. Rebuild the role content around the questions a serious candidate is actually asking: why this role exists, why now, what you will actually own, what makes it hard, why the right person might want it anyway, who thrives, who may not, and what you will be able to say you did afterward.
The difference is audible. The nightmare version: "We are seeking a highly motivated Senior Operations Manager to oversee cross-functional initiatives, improve processes, and partner with internal stakeholders in a fast-paced environment." This sentence has the fascinating property of being both full and empty. The candidate cannot tell what is broken, what they own, why now, or whether this is strategy, execution, or being politely blamed for everyone else's inability to decide.
The rebuilt version: "This role exists because our growth has outpaced the way our operations currently work. Teams have solved problems locally, but the business now needs someone who can turn repeated friction into systems other teams can trust. You will not inherit a clean operating model. You will help build one. This is a strong fit if you like making order from complexity, can influence without hiding behind authority, and want your work to show up in how the business actually runs."
The second version does not make the role easier. It makes the role a choice. Then relaunch properly: new role story, new outreach, aligned interview team, one shared answer to why this role exists. And measure the new pattern by quality, not just movement: stronger candidate questions, fewer confused screens, fewer late-stage dropouts, faster decisions.
The bigger lesson
A nightmare requisition is not just a recruiting headache. It is a strategy signal. It exposes the gap between what the company wants, what the market offers, what candidates believe, and what the hiring team is willing to change. Sometimes the market is saying no. Sometimes the job is valuable but described so poorly the right people cannot see it. Sometimes the team wants recruiting to solve a role design problem, a compensation problem, or a leadership alignment problem.
That is not failure. That is information.
The Usual Way says push harder. The better way says diagnose sharper. Fix the right failure and the search changes. Not because hiring suddenly becomes easy; hard roles may stay hard. But the recruiter is no longer throwing activity at a fog bank, and leadership is no longer staring at days-open as if the number itself contains the answer.
The role that refuses to get filled is often the role that has not yet been made worth choosing.
