The classic recruiter-manager scene
The recruiter sends five candidates they believe are strong. The hiring manager rejects all five with "not what I'm looking for." The recruiter is frustrated because they hit every requirement on the job description. The manager is frustrated because the candidates didn't match their actual mental model. Meanwhile, per iCIMS (2025), the candidates have a 60% chance of having abandoned the process by the time you regroup.
This misalignment is one of the most common and most expensive problems in recruiting. Every rejected batch means restarting sourcing, which adds weeks. And the rejected candidates were often qualified by every stated criterion. They just failed an unstated one.
What's actually causing it
- Vague descriptions. "Strong communicator" and "team player" mean different things to different people. No behavioral anchors, no shared interpretation.
- Unstated preferences. The hiring manager has a mental model that goes beyond the written requirements. Industry background, communication style, the type of company they came from. Never discussed.
- Evolving requirements. The role shifts as the manager learns from early candidates, and the shift never gets back to the recruiter.
- Different evaluation frames. The recruiter evaluates against the JD. The manager evaluates against the gap on their team this quarter. Those aren't the same thing.
The structured intake meeting
The single biggest fix is a real intake meeting before sourcing starts. Not a 15-minute JD review. A 45- to 60-minute working session that covers:
- The ideal candidate profile, including what success looks like at 90 days
- Must-haves vs. nice-to-haves, ranked explicitly so the recruiter knows where to flex
- Deal-breakers, stated specifically
- Example candidates: who on the current team exemplifies what you want? Who at a competitor would you steal tomorrow?
- Evaluation criteria: agree on the scorecard before any interviews happen
Calibrate with the first three candidates
Even after a strong intake, calibration is iterative. Treat the first two or three candidates as a calibration batch, not a final slate. The hiring manager reviews them and gives specific feedback. "Technical depth is right; I need more client-facing experience" is useful. "Not what I'm looking for" is not.
Async interviews make this loop fast. The manager watches recorded responses and gives feedback in hours, not days. scheduling delays are a top reason candidates drop out; for calibration specifically, async pulls the loop in tighter without burning candidate goodwill.
Shared visibility kills drift
When both sides can see candidate evaluations in real time, misalignment surfaces early. The recruiter rates a candidate highly, the manager rates them low; the gap shows up on the dashboard before it turns into a batch rejection. This requires a platform both sides actually use, not separate tools that need manual reconciliation.
How StormInterview supports alignment
Shared rubrics, real-time score visibility, and structured feedback tools live in one place. Both sides evaluate against the same criteria; disagreements are surfaced automatically. Calibration happens in the platform instead of an email thread. Try a free trial and run an intake plus a calibration batch against the next role.