Hiring Fails at the Intake Call: The Role Nobody Actually Defined
Most hiring problems get blamed on the wrong stage. Companies point to weak candidate pools, slow interviews, or a competitive market. But if you trace a bad hire, a stalled search, or a role that reopens six months later, the cause is often the same: the role was never clearly defined. The problem starts before the job post goes live, in a 30-minute intake conversation that most teams treat as a formality.
The intake call that isn't
In theory, intake is where the recruiter and hiring manager align on what success looks like. In practice, it often goes like this:
- The hiring manager pastes in a job description from two years ago, lightly edited.
- The recruiter asks a few questions, gets vague answers ("someone senior, a self-starter, strong communicator"), and moves on.
- Nobody writes down what the person will actually be doing in their first 90 days.
- The "must-haves" list quietly grows to twelve items, half of which are really nice-to-haves.
The search then begins on a foundation that is already unstable. Every downstream decision, from sourcing to screening to interview questions to the offer, inherits that ambiguity.
Why vague roles are expensive
Sourcing drifts: If the brief is fuzzy, recruiters optimize for keywords and titles instead of capability. You get a pipeline that looks right on paper and feels wrong in conversation. Screening becomes subjective: Without agreed criteria, each interviewer applies their own definition of "good." One person values leadership presence, another values technical depth, and a third goes with gut feel. The debrief turns into a debate about taste instead of evidence. Candidates sense the confusion: Strong candidates ask sharp questions about scope, priorities, and success metrics. When different interviewers give different answers, that is a red flag, and top talent leaves for teams that seem to know what they want. The goalposts move mid-search: Three weeks in, the hiring manager sees a candidate who doesn't match the brief and says, "Actually, I think we need someone different." The search resets, the timeline slips, and everyone is frustrated.
The real gap: expectations, not information
It's tempting to fix this with a longer intake form. But the issue usually isn't missing information. It's missing alignment. Hiring managers often haven't decided what tradeoffs they're willing to make. Can they hire someone strong in strategy but lighter on tooling? Is domain experience more important than growth potential? Will they pay above band for the right person? These are hard questions, and they're much cheaper to answer in week zero than in week six.
What a strong intake looks like
The best hiring teams treat intake as a decision-making session rather than a data-collection exercise. A few practices make the difference:
- Define outcomes, not duties: Instead of "manages the customer success team," write "reduces churn in mid-market accounts by 15% within the first year." Outcomes give candidates and interviewers something concrete to evaluate against.
- Force-rank the requirements: Ask the hiring manager to split criteria into three groups: non-negotiable, strongly preferred, and nice to have. If everything is a must-have, nothing is.
- Agree on what a great candidate looks like, and what a "no" looks like. Discussing disqualifiers up front prevents wasted interview cycles later.
- Align on the process, not just the profile: Who interviews? What does each stage assess? What's the decision timeline? Ambiguity here creates the silence and delays candidates notice most.
- Write it down and share it: A short, shared brief that the recruiter, hiring manager, and interviewers all reference keeps everyone anchored when the search gets messy.
Where technology should help (and where it shouldn't)
AI can be a powerful ally here, but only if it's pointed at the right problem. Many tools jump straight to the visible steps, like sourcing faster, screening faster, and scheduling faster. Speeding up a search built on a poorly defined role just gets you to the wrong answer sooner. The more valuable use of AI is upstream. It can help structure intake conversations, surface inconsistencies between what a hiring manager says they want and what they later approve, translate outcomes into consistent evaluation criteria, and keep every stakeholder working from the same definition of the role. Used this way, technology doesn't replace judgment. It creates the conditions for better judgment.