The Intake Meeting: Align Recruiters and Hiring Managers Before the Search

An intake meeting is a working session, held before a role is posted, where the recruiter and hiring manager agree in writing on what they are hiring for and how they will decide. It takes forty-five minutes. Skipping it is how searches restart in week four: the recruiter sources against one picture of the role, the hiring manager interviews against another, and the disagreement surfaces in a debrief after candidates have spent hours in your process.

This guide gives you the agenda, the questions that expose hidden disagreements, and the definition of done.

Why searches fail at the start

When a search drags, the visible symptoms show up late: rejected shortlists, “good but not quite” debriefs, an offer approved two levels too low. Trace them back and the cause is almost always the same: the role was never actually agreed. Common versions:

• The hiring manager wants a senior; finance approved a mid-level band. Nobody said either number out loud.
• “Must know our stack” was assumed by one person and considered trainable by the other.
• Three stakeholders each believed they held a veto.
• The role was really two roles, and every candidate was weak at one of them.

Every one of these is discoverable in forty-five minutes of direct questions. That is the entire case for the intake.

The agenda

1. The problem (10 minutes)

Not the title, the problem. “What breaks, or fails to happen, if this role stays empty for six months?” A hiring manager who can answer that crisply has a real role. One who cannot has a headcount slot, and the intake just saved a doomed search.

Follow-ups that sharpen it:

• What will this person own that nobody owns today?
• What does success look like at six months, in one sentence?
• Is this one role? (If the success statement needs “and also,” it may be two.)

2. Must-haves versus trainables (10 minutes)

Take the wish list and force-rank it. The question that separates the categories: “Would you reject an otherwise excellent candidate who lacked this?” If the answer is no, it is not a must-have. Most roles survive with three to five true must-haves; outcome-based hiring requirements covers reframing requirements around outcomes rather than keywords.

Write both lists down. The must-haves become your screening criteria and your interview competencies; the trainables become explicit non-filters so screeners stop rejecting for them.

3. Level and compensation (10 minutes)

Say the numbers in the meeting. The level, the band, and whether the band is approved or aspirational. This is the disagreement most often discovered at offer stage, which is the most expensive possible moment; approved-at-intake bands are how offers go out within a day of a decision. Developing salary bands and the leveling guide cover the groundwork.

4. The process itself (10 minutes)

Design the loop now, while calendars are still empty:

• How many stages, and what does each stage evaluate? (Designing effective interview stages)
• Who is on the panel, and which competency does each interviewer own?
• What format for the technical evaluation? (Take-home vs. live coding)
• What is the target timeline, stage to stage? (Benchmarks)

5. Decision rights (5 minutes)

One explicit sentence: who holds the Vote, who holds a Veto, who holds a Voice. Deciding this now costs five minutes; deciding it in a split debrief costs the candidate. Yogen’s Hiring Decision Matrix makes the assignment explicit (Vote/Veto/Voice per stakeholder), and the decision models comparison helps pick how the final call gets made.

The output: a written artifact

An intake that ends in nods produces nothing. The output is a document: problem statement, must-haves and trainables, level and band, loop design, panel assignments, decision rights, timeline. Everyone who touches the search can point at it, and week-four drift gets caught against it (“we agreed Kubernetes was trainable; why are we rejecting for it?”).

This document is exactly what Yogen’s Internal Intake Summary generates: a shared strategy document that aligns all stakeholders before the search begins, produced from the intake conversation itself. Yogen’s Risk & Warning Summary reads the same intake and surfaces risks early (an under-market band, an overloaded panel, a two-roles-in-one definition) so the team can address them before they derail the process. From there, the rest of the Hiring Kit generates the downstream artifacts (job description, interview stages, role-specific questions, candidate packet), saving 30 minutes to 3 hours each.

Red flags to catch in the room

• “We’ll know it when we see it.” You will not. This is the unstructured search announcing itself; see structured interviews for why it fails.
• A wish list with twelve must-haves. That candidate does not exist at that band. Rank or restart.
• “Everyone should meet them.” Spectator interviews inflate loops and burn engineer hours (interviewers × $150/hour × stages × hours adds up fast). Panel membership means owning a competency.
• Band not yet approved. Fine, but then the search has not actually started. Sourcing against an unapproved band is how finalists get lost at offer.
• Recruiter silent throughout. An intake is a negotiation between market reality and team wishes, not a requirements download. If the recruiter cannot push back here, the market will do it later, slower. The hiring manager collaboration playbook covers building that working relationship.

Re-intake when the search tells you to

An intake is a hypothesis. If three weeks of sourcing produces nothing at the band, or every strong candidate fails the same must-have, the market has voted: hold a fifteen-minute re-intake and adjust the document rather than quietly bending the process. Searches that drift silently are the ones that end in mis-hires; searches that re-intake end in offers.