Direct answer
Aging reqs usually fail for one of five reasons: unclear evidence, impossible tradeoffs, wrong source lane, poor compensation reality, or stale feedback loops.
The first diagnostic
Ask whether candidates are missing, unqualified, uninterested, rejected, or stuck after submittal. Each failure mode needs a different fix.
Operating notes
- Separate no candidates from wrong candidates.
- Look for hidden rejection patterns.
- Test adjacent lanes.
- Document the tradeoff recommendation.
Search lane rescue
If no candidates exist in the strict lane, test adjacent titles, donor companies, and evidence-first searches before declaring the role impossible.
Manager calibration rescue
If candidates are rejected, show the patterns. The HM may be applying a hidden standard that never made it into the intake.
SourcingOS workflow
Use the Aging Req Rescue tool to turn frustration into a diagnosis and next experiment.
Copy-paste starting strings
("aging req" OR "hard to fill role") recruiter sourcing("no candidates" OR "low yield") AND recruiter AND sourcing("hiring manager" calibration AND sourcing strategyFAQ
When is a req truly impossible?
Usually only after strict, adjacent, donor, and compensation reality lanes have been tested.
What should I show the HM?
Show evidence, not excuses: pool size, lane results, rejection patterns, and tradeoff options.