Interviewing vs screening

The difference in one table

What a screen is actually for

A screen exists to protect expensive interviewer time, and it should be judged on that. It checks relevance of experience, basic communication, genuine motivation and logistics — compensation range, notice period, location, work authorisation. These are the things that, if misaligned, make everything that follows a waste for both sides. A screen is not a shallow interview; it is a different instrument with a different question.

Why screening deeply backfires

Technical screening that tries to assess ability in thirty minutes over a phone is where good candidates are most often lost. The sample is too small, the conditions are unrepresentative, and the format rewards fluency under pressure rather than skill. If a screen is rejecting more than about half of sourced candidates on ability rather than on fit or logistics, it has stopped being a screen and become an unreliable interview.

Why interviewing shallowly backfires too

• One conversation, one attribute. Deciding to hire from a single generalist chat means deciding on impression, which is the least reliable input available.
• No rubric means no comparability. Two shallow interviews cannot be compared, so the decision defaults to who was more likeable.
• No follow-ups means no evidence. The first answer to any question is a summary; the evidence is two follow-ups deeper.

Who should run which

• Recruiters screen well when given explicit criteria, and badly when asked to judge technical depth.
• Hiring managers screen well for senior roles, where motivation and level are the main filters.
• Peers interview well, because they know what the work requires and candidates ask them more honest questions.
• Nobody should do both for the same candidate in the same conversation. The two questions pull in opposite directions.

Both deserve the same courtesy

A screen is cheap for you and not cheap for the candidate: they still prepared, still took the call in a stairwell on their lunch break, still rearranged something. The asymmetry is worth remembering when deciding how quickly to send a rejection. A few days is reasonable; three weeks of silence after a thirty-minute call is how companies acquire the reputation that makes sourcing harder later.

The handoff between them

The screen should pass forward what it learned, not just a verdict. Note what was covered, what the candidate is looking for, their constraints, and anything the loop should probe. Loops frequently re-ask the same context questions at every stage, which wastes assessment time and signals to the candidate that nobody is talking to each other.

Where resume review fits

Resume review is a third thing, earlier and cheaper than both, and it is where most candidates are actually rejected. It should run against written criteria applied in a fixed order, because an unstructured read is where names, schools and employer brands do the filtering. Treat it as a coarse relevance check rather than an assessment: a resume can tell you someone has probably done work of this shape, and almost nothing about whether they did it well.

Common failure modes

• The screen that became a technical interview. Thirty minutes of trivia over the phone, rejecting on ability from an unrepresentative sample.
• The interview that became a screen. One generalist conversation, no rubric, a decision from impression.
• The screen nobody acts on. If every screened candidate advances, the stage is theatre and should be removed or fixed.
• Re-asking context at every stage. A sign the handoff is not working, and candidates read it as disorganisation.

Getting the ratio right

A healthy screen passes somewhere between a fifth and a half of candidates. Much above that and it is not filtering; much below and the problem is upstream in sourcing rather than in the screen itself. Tracking that number is the quickest way to tell whether your screen is doing its job. See phone screen questions to ask candidates and how to design an interview loop.

Where Interviewer Mode fits

Disclosure: we make CoPilot Interview, which includes Interviewer Mode for the hiring side and a real-time assistant used by candidates. We have an interest in you using the first, and our view of the second is that interviews should be designed to measure something an assistant cannot fake. Weigh the advice below accordingly.

Frequently asked questions

What is the difference between screening and interviewing?

A screen decides whether a candidate is worth the team's time; an interview decides whether to hire them. Screens are short, check a few disqualifying criteria and output yes or no. Interviews are longer, assess several attributes against a rubric, and output evidence plus a rating.

How long should a screening call be?

Twenty to thirty minutes. The question a screen answers does not get more accurate with sixty minutes, and longer calls are harder to schedule for candidates who are currently employed.

Should a recruiter or hiring manager do the screen?

Recruiters screen effectively when given explicit written criteria. Hiring managers are better for senior roles where motivation and level calibration are the main filters. Either way, keep the screen's question separate from the interview's.

What percentage of candidates should pass a screen?

Roughly a fifth to a half. Passing more suggests the screen is not filtering; passing far fewer usually points at a sourcing problem upstream rather than at the screen itself.