The Nightmare Requisition
What to Do When the Role Refuses to Get Filled
By James Ellis, June 24, 2026
Every recruiter knows the nightmare requisition.
Not the difficult one. Difficult is fine. Difficult is Tuesday.
The nightmare requisition is different.
It 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.”
The hiring manager says, “We just need more candidates.”
Leadership asks, “Why is this still open?”
The recruiter searches harder. Posts wider. Sends more outreach. Rewrites the first sentence. Changes “manager” to “lead.” Adds a line about impact. Removes a line about travel. Re-runs the same intake conversation under the polite fiction that this time it will reveal something new.
Maybe someone buys ads.
Maybe an agency gets called.
Maybe a sour little sentence appears in a meeting: “Is TA prioritizing this?”
And still, nothing really moves.
Or worse, the funnel moves but the problem does not.
More applicants. Still wrong.
More screens. Still weak.
More interviews. Still no hire.
More urgency. Still no clarity.
This is when The Usual Way reaches for its favorite answer: activity.
More activity. More volume. More pressure. More candidates. More reminders. More dashboards. More “quick syncs” that are quick in the same way airport security is quick when viewed from space.
But many 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.
A nightmare req is rarely just a sourcing problem.
It is usually a value problem, clarity problem, market problem, manager problem, proof problem, audience problem, tradeoff problem, or process problem hiding under the innocent little phrase, “We need more candidates.”
That phrase is where good recruiting work often goes to die.
Because “more candidates” sounds practical. It sounds measurable. It sounds like something TA can own. It sounds much safer than saying, “I am not sure the role, as currently designed and explained, is compelling enough to win the people we say we want.”
But the role that refuses to get filled is telling you something.
The job is not being understood.
Or valued.
Or believed.
Or differentiated.
Or chosen.
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” feels useful because it names the pain.
But it does not name the problem.
It is like telling a mechanic, “The car is bad.” The mechanic may sympathize, but the sentence does not help much. Is the battery dead? Is the fuel pump gone? Is the transmission failing? Is there a raccoon in the engine? These require different solutions, and one hopes, different levels of emotional preparation.
Hiring works the same way.
A role can be hard to fill for completely different reasons.
The market may be tiny.
The salary may be misaligned.
The title may be wrong.
The job may be overloaded.
The hiring manager may want a unicorn, but with better Excel skills and lower compensation expectations.
The company may be unknown to the target audience.
The role may sound smaller than it is.
The role may sound riskier than it is.
The job post may hide the only interesting parts.
The real work may be unattractive to the people being targeted.
The process may be slow enough to feel like a preview of the company’s decision-making culture.
The hiring team may not agree on what great looks like.
The strongest candidates may be comparing the opportunity to better, clearer, or safer options.
These are not the same problem.
So they should not get the same solution.
This is the first discipline of the nightmare requisition: stop treating “hard to fill” as the diagnosis.
It is not.
“Hard to fill” is a distress signal.
The work begins when you classify the failure.
The seven failures behind a nightmare requisition
When a role refuses to get filled, do not begin by asking, “Where else can we post it?”
Begin by asking, “Why is this failing as a choice?”
That question opens up the real diagnostic work.
Most nightmare reqs suffer from one or more of seven failures.
1. The market failure
Sometimes the market is the problem.
There may not be enough people who match the spec, salary, location, level, industry background, clearance requirement, schedule, technology stack, travel expectation, or experience mix.
This is the classic supply and demand problem. It is real. It should not be dismissed.
The trouble is that companies often invoke “the market” before they have actually studied it. “The market is tight” becomes a soothing fog in which no one has to reconsider the spec, the money, the location, the level, or the hiring manager’s favorite impossible combination of requirements.
A true market failure has signals.
Very few qualified people exist in the reachable market.
Competitors are paying meaningfully more.
Required skills rarely appear together.
The location or on-site expectations shrink the pool.
The role requires a combination of experiences that does not naturally occur in one human person, except perhaps in a LinkedIn profile written by someone with a heroic relationship to the truth.
When this is the problem, the answer is not motivational shouting.
The answer is market mapping.
Who exists?
Where are they?
What do they likely earn?
What alternatives do they have?
Which requirements are true must-haves?
Which are preferences dressed as standards?
Which skills can be learned?
Which adjacent talent pools could succeed with support?
What would have to change to make the role competitive?
This is where recruiting has to move the conversation from preference to reality.
The hiring manager may prefer someone who has done the exact job, in the exact industry, at the exact stage, with the exact systems, for less money, within commuting distance, and ready in two weeks.
Lovely.
Does that person exist?
And if they exist, why would they choose this?
That second question matters because market availability is not the same as candidate availability. A person can exist and still be unreachable because their current situation is better, safer, clearer, more prestigious, more flexible, or more lucrative.
A market map should not merely prove scarcity. It should show what the company is asking the market to do.
If the ask is unrealistic, say so.
Safely, but clearly.
“We can keep searching for this exact profile, but the available market suggests we are asking for a rare combination at a compensation and flexibility level that will limit our reach. We need to decide which part of the profile creates the most business value and which parts can be adjusted.”
That is not being negative.
That is being useful.
2. The value failure
A role can be findable and still not be choosable.
This is the value failure.
The company may be asking for a lot while offering too little perceived value in return.
That does not only mean salary. Salary matters, but candidates do not experience value as one number. They experience it as a bundle:
Money.
Scope.
Learning.
Status.
Flexibility.
Manager quality.
Stability.
Impact.
Autonomy.
Career capital.
Interesting problems.
Association with a serious company, mission, category, product, or technical challenge.
A nightmare req often gets stuck because the company sees the role as important, but the candidate sees it as lateral labor.
The internal view is:
“This role is critical.”
The candidate view is:
“This looks like more work for a slightly different logo.”
That gap is lethal.
Signals of a value failure are easy to miss because there may be activity.
People respond, but do not commit.
Candidates take the recruiter call, then cool off.
Outreach creates curiosity, but not momentum.
The best candidates say things like, “It sounds interesting, but not enough of a move.”
Candidates compare the role unfavorably to their other options:
The job sounds like responsibility without upside.
The fix is not to add hype.
The fix is to make the value visible.
Why would a great person leave something known for this?
That is the central question.
Not why the company needs the role.
Not what the person will do.
Not what the hiring manager wants.
Why would a strong person with other options decide this move is worth the disruption?
Use the Role Value Stack.
What will they build?
What will they learn?
What will they own?
Who will they influence?
What will they become stronger at?
What future resume story can they earn?
What business problem will they help solve?
What status, exposure, or credibility will the role create?
What rhythm of work will they get?
What tradeoff will they accept, and what do they get in return?
A role with real value can still fail if the value is invisible. The job description says, “manage cross-functional initiatives.” The recruiter says, “great opportunity.” The candidate hears, “meetings.”
But if the real role is to turn a messy operating model into a system the business can scale, say that.
If the real role gives someone access to executive decisions earlier than they would get at a larger company, say that.
If the real role helps a candidate build rare experience in a regulated, high-consequence environment, say that.
If the real role is hard because the company has outgrown the old way, say that.
Candidates do not choose the role because it is important to you.
They choose it when it becomes valuable to them.
3. The clarity failure
Candidates cannot choose what they cannot understand.
This sounds obvious until you read most job descriptions.
Many nightmare reqs are vague in precisely the places where they need to be sharp. They describe responsibilities but not outcomes. They name stakeholders but not authority. They mention strategy and execution without explaining the balance. They use internal language no one outside the company would naturally understand.
The result is a job that technically contains information but does not produce understanding.
A clarity failure has signals:
The job description is full of abstractions.
Recruiters explain the role differently each time.
The hiring manager describes tasks, not outcomes.
Candidates ask basic clarifying questions late in the process.
Interviewers evaluate against different mental models.
The team cannot agree whether the role is strategic, operational, technical, managerial, advisory, transformational, or an unlucky blend of all six.
This is when the funnel starts to wobble.
Candidates hesitate because they cannot tell what they are being asked to join. Recruiters compensate with interpretation. Hiring managers hear different things from different candidates. Interviewers select for whatever version of the role they personally understood.
The role becomes a rumor.
The fix is a Role Decision Brief.
Not another job description. Not a longer list of tasks. A decision brief.
It should answer:
Why does this role exist?
Why now?
What problem does it solve?
What will success look like after six to twelve months?
What decisions will this person own?
What is hard about the role?
What is not part of the role?
Who thrives?
Who struggles?
What tradeoffs should candidates understand?
What will this role make possible for the business?
What will this role make possible for the person who takes it?
This forces the hiring team to stop hiding behind adjectives.
“Strategic” is not enough.
Strategic how?
“Hands-on” is not enough.
Hands-on with what?
“Cross-functional” is not enough.
Which functions? What decisions? What conflicts? What authority?
“Fast-paced” is not enough.
Fast because the company is growing? Fast because no one plans? Fast because customers are demanding? Fast because priorities keep changing? These are morally different forms of fast.
A confusing role creates a weak funnel because the right candidates cannot see why it is for them.
A clear role may still be hard to fill.
But at least it becomes possible to tell whether 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.
This is the credibility failure.
It is especially common when companies make the usual claims: ownership, impact, innovation, flexibility, growth, mission, collaboration, strong culture.
These may all be true.
They may also be the same claims candidates have heard from five other companies this month, two of which recently laid off people with a LinkedIn post about “difficult decisions” and “gratitude.”
Modern candidates have learned to discount unsupported claims.
Not because they are cynical by nature. Because the market has trained them.
The career site says “ownership.”
The candidate asks, “What decisions would I actually own?”
The job post says “impact.”
The candidate asks, “Impact on whom, through what mechanism, at what level of consequence?”
The recruiter says “growth.”
The candidate asks, “Growth into what, and who has done it?”
The hiring manager says “collaboration.”
The candidate asks, “Does that mean healthy partnership or endless negotiation with no decision rights?”
A credibility failure has signals.
Candidates seem skeptical.
The role sounds too polished.
Employee stories are generic.
The job promises impact but gives no mechanism.
The hiring manager cannot explain what the person will actually own.
The company leans on words that feel attractive but cheap.
The fix is proof.
For every promise, ask:
What would prove this?
What example shows it?
Who can say it credibly?
What decision rights make it real?
What artifact, story, metric, or operating norm supports it?
If the claim is ownership, show the decision rights.
If the claim is growth, show the path or the pattern.
If the claim is impact, show the before and after.
If the claim is flexibility, show how it works when things are busy.
If the claim is collaboration, show how disagreement gets resolved.
Proof does not have to be theatrical. It has to be concrete.
A real example beats an elegant adjective.
A manager explaining the actual challenge beats a generic employee quote.
A named tradeoff beats a page of culture language.
This is why nightmare reqs often need better evidence, not better adjectives.
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.
This is the audience failure.
It happens when a company describes a role according to internal need rather than external motivation. The job post says what the business wants. It does not speak to the kind of person who would want to solve that problem.
This is how companies accidentally attract people who are qualified but not interested, or interested but not suited.
The team wants a Builder but writes for a Maintainer.
The team wants a Craftsperson but sells speed and chaos.
The team wants a Scaler but lists tasks instead of system-building.
The team wants a Mission Pragmatist but speaks only in lofty purpose and never explains the operational reality.
The team wants a strategic partner but posts a role that sounds like administrative coordination with more meetings.
The role is not wrong. The audience definition is wrong.
Skills are not enough.
A nightmare req often requires a motivational profile:
What kind of person would find this problem energizing?
Who would see the mess and think, “Good, there is something to build here”?
Who would see the constraints and think, “This is where craft matters”?
Who would see an immature process and think, “I know how to make this repeatable”?
Who would see a mission blocked by poor execution and think, “That is my kind of work”?
Define the right-fit audience by motivation, not just experience.
Builder/problem-solver.
Craftsperson.
Scaler.
Stabilizer.
Mission pragmatist.
Customer solver.
Operator/fixer.
Career accelerator.
Lifestyle protector.
These are not personas for a decorative slide. They are decision clues.
A Builder wants unfinished systems, room to shape, and visible consequence.
A Craftsperson wants quality standards, technical seriousness, and time to do the work properly.
A Scaler wants the second version of the company, not the first improvisation.
A Stabilizer wants to reduce risk, build reliability, and make the work less dependent on heroics.
An Operator/Fixer wants messy problems, decision rights, and the satisfaction of making things work.
Once you know the audience, rewrite the role around what that person values.
Not:
“We need someone with 7+ years of experience managing operational initiatives.”
Try:
“This is for someone who likes turning repeated operational pain into a system other teams can trust.”
That sentence does not merely describe experience.
It 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.
This does not mean every role is bad. It means every role has tradeoffs.
More autonomy may mean less structure.
More visibility may mean more pressure.
More growth may mean more ambiguity.
More mission may mean more emotional weight.
More speed may mean less polish.
More stability may mean less blank-canvas ownership.
More flexibility may mean more asynchronous complexity.
The Usual Way tries to hide the catch.
It softens the edges. It uses euphemisms. It says “fast-paced” when it means chaotic. It says “ownership” when it means under-supported. It says “dynamic” when it means the plan changes whenever someone important has lunch with a new idea.
Candidates are not stupid. They sense the catch.
When the company will not name it, suspicion grows.
A tradeoff failure has signals.
Candidates leave after interviews.
Candidates ask versions of “what is really going on here?”
The role has been re-opened multiple times.
New hires in similar roles churn.
The hiring manager says “resilient” a little too often.
The company describes the upside with enthusiasm and the hard part with mist.
The fix is not to make the role sound easy.
The fix is to make the hard part feel chosen.
Instead of:
“Fast-paced environment.”
Say:
“Priorities can change inside a quarter. This works best for people who can keep moving without needing every variable settled.”
Instead of:
“High ownership.”
Say:
“You will have real room to shape the approach, but you will not inherit a fully built playbook.”
Instead of:
“Collaborative culture.”
Say:
“Most meaningful decisions here require influence across product, sales, operations, and finance. You will need to make tradeoffs visible and bring people with different incentives to a practical answer.”
This kind of honesty does not weaken the role. It strengthens it.
It tells the right candidate what they are choosing.
And that is the point.
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.
Then the hiring process ruins it.
The company says the role is high priority, then takes twelve days to provide feedback.
The recruiter says the team is decisive, then the candidate has six conversations with people asking the same question in different sweaters.
The hiring manager says the person will have ownership, but the process suggests no one owns the decision.
Compensation appears late.
Criteria shift.
Interviewers are misaligned.
The candidate gets homework with no context.
The process feels less like an evaluation and more like a warning sign with calendar invites.
A great opportunity can still lose if the process teaches the candidate not to trust the company.
Signals of process failure are familiar.
Strong candidates drop mid-process.
Feedback takes too long.
Interviews repeat the same questions.
The process feels disorganized.
Hiring criteria shift after good candidates appear.
The hiring manager is slow, vague, or overly picky.
Candidates decline before offer because another company made the choice easier.
The fix is to treat the hiring process as part of the offer.
Because it is.
Clarify the stages.
Clarify decision criteria.
Clarify compensation range early.
Clarify timeline.
Clarify interviewer roles.
Clarify what each conversation is meant to assess.
Clarify how candidates should prepare.
Clarify what the company is trying to learn.
Every step in 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 imagine it.
Then they choose someone else.
The “before more ads” rule
When a role is stuck, the instinct is to buy or create more attention.
Post it again.
Sponsor it.
Send more outreach.
Ask for agency help.
Widen sourcing.
Push recruiters harder.
Sometimes more distribution is necessary. But it should not be the reflex.
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 audience is wrong, more people will ignore it.
If the tradeoffs are hidden, more people will drop later.
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.
Before spending more money, answer seven questions.
- Is the role’s value obvious?
- Is the target audience specific?
- Is the role differentiated from alternatives?
- Are the tradeoffs named?
- Is the proof credible?
- Is the process candidate-safe?
- Is the market reality understood?
If the answer is no, fix the choice architecture before buying more attention.
This is 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 is the kind of sentence that changes the room.
It moves TA from defense to diagnosis.
The nightmare req reset meeting
The normal status meeting will not save a nightmare requisition.
The normal status meeting asks:
How many applicants?
How many screens?
How many interviews?
How many rejects?
How many offers?
How many days open?
These questions have their place. But in a nightmare req, they often become a ritualized reading of the bad news.
What you need is a reset meeting.
Not a meeting to defend recruiting. Not a meeting to blame the hiring manager. Not a meeting to admire the dashboard with grave faces.
A reset meeting exists to re-diagnose the role.
The agenda is simple.
1. What have we learned?
Do not begin with volume.
Begin with pattern.
Who responded?
Who ignored us?
Who dropped?
Who got rejected?
Who rejected us?
What questions did candidates ask?
What did they seem to misunderstand?
What did they not value?
Where did confidence break?
What did strong candidates choose instead?
What did weak candidates fail to understand?
What did the market keep telling us that we kept politely ignoring?
This reframes the funnel as intelligence, not merely throughput.
A failed pattern is still a pattern.
Use it.
2. What problem are we actually solving?
Make the hiring manager explain the business reason.
Why does this role exist?
What breaks if we do not hire?
What will this person make possible?
What must be true six months after they start?
What decisions will they own?
What will improve because this person is here?
This is where many roles get exposed.
They have a list of responsibilities, but no sharp business reason. Or they have a business reason, but it never made it into the job content. Or the hiring manager knows it intuitively but has never translated it into language candidates can use.
A role without a business reason sounds like headcount.
A role with a business reason sounds like a mission.
Not in the cheesy sense. In the practical sense.
There is a problem. This person will help solve it.
3. Who is the actual right-fit candidate?
Not the fantasy candidate.
The actual candidate.
Where are they now?
What are they tired of?
What do they want more of?
What would make them move?
What would make them skeptical?
What alternatives are they considering?
What would they have to believe for this to feel like a smart risk?
This is where the hiring team needs to stop writing to the category and start writing to the person.
A Senior Operations Manager is not a person. It is a label.
The person may be an operator who loves untangling broken systems. Or a stabilizer who wants process maturity. Or a career accelerator who wants visibility. Or a lifestyle protector who values predictability. Each will read the same role differently.
If you do not know which one you need, your messaging will become generic enough to miss all of them.
4. What is the role’s value proposition?
Now use the Role Value Stack.
Financial value.
Career value.
Skill value.
Status value.
Identity value.
Impact value.
Lifestyle value.
Where is the role strong?
Where is it weak?
Where is the value real but invisible?
Where are we relying too much on salary?
Where are we assuming candidates will infer the upside?
Where is the role asking for risk without showing the reward?
This is the conversation most nightmare reqs have avoided.
It is also the conversation that often unlocks the search.
5. What are we willing to change?
This is where the truth appears.
The team may need to change the title.
Or level.
Or salary.
Or location.
Or remote flexibility.
Or required experience.
Or team structure.
Or reporting line.
Or scope.
Or interview process.
Or decision speed.
Or evaluation criteria.
Or job messaging.
Or sourcing audience.
If the answer is “nothing,” then recruiting is not the only constraint.
Say it carefully.
“If nothing about the role can change, then the hiring team has to accept what that choice costs.”
That sentence is firm without being reckless.
It tells the truth.
Recruiting cannot repeal market reality through effort.
Rebuild the role as a candidate choice
After diagnosis, rebuild the role content.
The normal job description is usually not enough. It may be necessary for compliance, structure, and internal consistency. Fine. Keep it.
But the candidate needs a better decision artifact.
Build the role around the questions a serious candidate is actually asking.
Why this role exists
Start with the business problem, not the task list.
“This role exists because our customer onboarding process was built in pieces as we grew, and the experience now depends too much on individual heroics.”
That is better than:
“Responsible for improving customer onboarding.”
One explains why the work matters. The other assigns a chore.
Why now
Timing creates consequence.
Why is this hire important at this moment?
What changed?
Growth? Customer expectations? Regulation? Product complexity? Scale? Technical debt? Leadership priorities? Market pressure?
“Why now” tells the candidate the role is not random.
It gives the work urgency.
What you will actually own
Ownership is one of the most abused words in hiring.
Make it concrete.
What decisions will the person own?
What outcomes?
What systems?
What relationships?
What budget?
What roadmap?
What process?
What tradeoffs?
If they influence rather than own, say that too. Influence can be valuable, but pretending influence is
ownership creates resentment later.
What makes this hard
Do not hide the complexity.
Is the process immature?
Are stakeholders misaligned?
Is the market changing?
Is the system old?
Is the company scaling faster than its operating model?
Is there technical debt?
Is there customer pressure?
Is there ambiguity around priorities?
The hard part is often the thing that attracts the right person, provided it is framed honestly.
Why the right person might want it anyway
This is where the Role Value Stack comes in.
What will the person build?
What will they learn?
Who will they influence?
What will they be able to say they changed?
How will the work make them stronger?
What future opportunity might this experience unlock?
The phrase “might want it anyway” matters. It respects the fact that the role has real tradeoffs.
You are not selling paradise.
You are explaining why the tradeoff may be worth it.
Who thrives here
Describe motivation and work style.
Not demographics. Not personality theater. Not culture-fit mush.
People who like building clarity while the work is moving.
People who can influence without hiding behind authority.
People who get energy from turning repeated friction into systems.
People who want visible ownership and can handle the exposure that comes with it.
People who care more about making the work useful than making the deck elegant.
This helps the right candidate recognize themselves.
Who may not thrive
This is where credibility rises.
The role may frustrate people who need mature process before they can do their best work.
It may frustrate people who want narrow ownership.
It may frustrate people who prefer a famous brand to explain their career move for them.
It may frustrate people who want low-change work.
It may frustrate people who dislike influencing across functions.
This is not exclusion.
It is clarity.
What success looks like
Define concrete six to twelve month outcomes.
Not “be successful in the role.”
What will be different?
The onboarding process is clearer.
The reporting rhythm works.
The hiring manager experience has fewer avoidable stalls.
The customer escalation path is cleaner.
The team can make decisions without reinventing the process each time.
The business can scale without adding more chaos.
Concrete outcomes help candidates understand the seriousness of the role.
They also help interviewers evaluate better.
What you will be able to say you did
This may be the most candidate-centered question in the whole exercise.
What future story can the person earn?
Not the company’s story. The candidate’s.
“I helped a company move from local fixes to scalable operating systems.”
“I rebuilt how customer pain became product priority.”
“I turned an overloaded hiring process into a decision system hiring managers trusted.”
“I helped a regulated company move faster without becoming sloppy.”
That is career value.
Put it on the page.
Questions you should ask us
This is a confidence move.
A serious role can invite serious questions.
Ask us how decisions really get made.
Ask us what has failed before.
Ask us what authority this role has and where it will need influence.
Ask us how we will measure success six months in.
Ask us what tradeoffs we are not willing to make.
Ask us why the last person left, if there was a last person.
This kind of section tells candidates, “We are not afraid of your intelligence.”
Strong candidates appreciate that.
Weak ones may not know what to do with it.
Also useful.
Before and after
Here is the sort of job language that creates nightmare reqs.
“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.
It contains words. It does not contain meaning.
The candidate cannot tell what is broken.
They cannot tell what matters.
They cannot tell what they own.
They cannot tell why now.
They cannot tell what level of authority they have.
They cannot tell whether this is strategy, execution, firefighting, reporting, or being politely blamed for everyone else’s inability to decide.
They cannot tell why the role is worth leaving for.
Now try this:
“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. That means mapping where work breaks, aligning leaders who see different pieces of the problem, and creating the rhythms, tools, and decisions that let the company scale without adding more chaos.
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.”
This version does not make the role easier.
It makes the role clearer.
It shows the business problem.
It names the hard part.
It creates identity pull.
It explains the value.
It gives the candidate something to compare against their own ambition.
Most important, it makes the role feel like a choice.
Not a list of duties.
A choice.
The nightmare req playbook
When a role refuses to get filled, follow the sequence.
Step 1: Stop calling it hard to fill
Name the specific failure.
Market failure.
Value failure.
Clarity failure.
Credibility failure.
Audience failure.
Tradeoff failure.
Process failure.
It may be more than one. It often is.
But name it.
A named problem can be worked.
A vague problem can only be endured.
Step 2: Map the real market
Who exists?
Where are they?
What do they likely earn?
What alternatives do they have?
What are competitors offering?
Which requirements shrink the pool?
Which requirements are negotiable?
Show the hiring team the actual market, not the imagined one.
Step 3: Rebuild the right-fit audience
Define the candidate by motivation, not just skill.
Are you trying to attract a Builder?
A Craftsperson?
A Scaler?
A Stabilizer?
A Mission Pragmatist?
An Operator/Fixer?
A Career Accelerator?
A Lifestyle Protector?
The same role can be framed very differently depending on who will thrive.
Step 4: Clarify the business reason
Why does this role exist?
Why now?
What breaks if the role stays open?
What will the person make possible?
A req without a clear business reason will struggle to become a compelling candidate story.
Step 5: Make the value visible
Use the Role Value Stack.
Show the financial value, career value, skill value, status value, identity value, impact value, and lifestyle value.
Do not assume the candidate will infer the upside.
Candidates are busy. Inference is expensive.
Step 6: Name the hard part
Turn hidden risk into informed tradeoff.
“This is not for everyone” is often the beginning of real attraction.
The right people do not need the role to be easy.
They need the role to be honest.
Step 7: Replace claims with proof
Show ownership through decision rights.
Show impact through outcomes.
Show growth through examples.
Show collaboration through how decisions are made.
Show culture through behavior under pressure.
Proof is what turns employer brand from decoration into evidence.
Step 8: Fix the process
Make the hiring experience reinforce the value of the role.
If the role requires decisiveness, be decisive.
If the role requires collaboration, coordinate the interview team.
If the role requires strategic clarity, do not run a vague process.
The process is not separate from the offer.
It is the candidate’s first experience of how the company works.
Step 9: Relaunch the role
Do not quietly tweak the job post and hope.
Relaunch with a new role page, new outreach, new recruiter talk track, new hiring manager alignment, and new interview criteria.
If the diagnosis changed, the market-facing story should change too.
Step 10: Measure the new pattern
Do not measure only volume.
Look for better response quality.
Stronger candidate questions.
Fewer confused screens.
More qualified self-selection.
Improved interview-to-offer ratio.
Fewer late-stage dropouts.
Faster hiring manager decisions.
Better offer acceptance.
The goal is not merely more movement.
The goal is better movement.
The bigger lesson
A nightmare requisition is not just a recruiting headache.
It is a strategy signal.
It reveals the gap between what the company wants, what the market offers, what the role is worth, what candidates believe, and what the hiring team is willing to change.
That is why these roles become so emotional.
They expose the uncomfortable truth that recruiting is not simply a delivery function. It is where business ambition meets market reality.
Sometimes the market is saying no.
Sometimes candidates are saying the role is not worth the risk.
Sometimes the hiring manager is asking for a profile that does not exist at the price offered.
Sometimes the job is valuable but described so poorly that the right people cannot see it.
Sometimes the process is teaching candidates to distrust the company.
Sometimes the team wants recruiting to solve a role design problem, compensation problem, clarity problem, or leadership alignment problem.
The nightmare requisition reveals all of this.
That is not failure.
That is information.
The Usual Way says:
Push harder.
The better way says:
Diagnose sharper.
The nightmare requisition is not asking for more noise. It is asking for a better choice.
When you make the role clearer, more valuable, more honest, more believable, and more specific to the right person, the search changes.
Not because hiring suddenly becomes easy.
Hiring hard roles may remain hard.
But the work becomes more intelligent.
The recruiter is no longer throwing activity at a fog bank. The hiring manager is no longer waiting for a miracle candidate produced by effort alone. Leadership is no longer staring at days-open as if the number itself contains the answer.
The role becomes something the market can understand.
The right candidate can see the value.
The wrong candidate can opt out earlier.
The hiring team can talk about the same opportunity.
The process can reinforce the story.
The search can finally become strategic.
The role that refuses to get filled is often the role that has not yet been made worth choosing.
Two powerful ways to leverage AI to make your company more choosable:
