Back to blog

Phone Screen Questions That Actually Filter

Treat the phone screen as a knock-out gate. Ask salary, logistics, and proof questions that can fail someone today, then clear them to a real interview.

A wide view of rugged Alpine mountain ridges under a blue sky with scattered clouds.
Photo by natashadudler on Pixabay

Quick answer: Most phone screens just re-read the resume out loud. In my opinion that is expensive small talk. A good screen should knock people out fast, or clear them to a real interview. SHRM’s 2025 recruiting benchmarks put screening and interviewing at about 8 to 9 days each in the hire timeline. Gem’s 2025 report shows hiring teams now run about 20 interviews per hire, up from 14 in 2021. So every weak phone screen multiplies calendar load later. Ask salary band, logistics, and one proof question. Skip the warm-up essay.

I write this for hiring managers and founders on small teams. Google mixes this query with jobseeker prep. That is not who this post is for. You are trying to filter. You are not coaching candidates on polished answers.

What is a phone screen actually for?

A phone screen is a cheap knock-out gate, not a mini interview.

Its job is binary. Keep someone, or stop them today. SHRM has long described phone screening as a way to check whether an applicant has the qualifications needed before a fuller interview. That definition still holds. You are not measuring culture fit in fifteen minutes. You are checking hard constraints and one signal that the CV is not fiction.

Gem’s 2025 Recruiting Benchmarks report (data through 2024) found average time to hire at 41 days, up from 33 in 2021, with 42% more interviews per hire. If your screen only confirms what the PDF already said, you paid for a second resume read.

Which phone screen questions actually filter candidates?

These six questions filter. Each one can fail someone on the call, or clear them to the next step.

1. What salary range are you targeting for this role?

This filters compensation mismatch early.

Pass sounds like a number inside your posted or budgeted band, or a clear willingness to discuss inside that band.

Fail sounds like a floor well above budget with no flexibility, or refusal to share any range after you shared yours first.

Why it works: salary surprises kill late-stage offers. Asking early is honest. Share your band first if you can. That keeps the question fair.

2. When could you start, and what notice period do you have?

This filters timing and commitment risk.

Pass sounds like a concrete date and a notice period you can live with.

Fail sounds like vague someday language, an open-ended consulting unwind with no date, or a start window that breaks your delivery plan.

Why it works: a great candidate who cannot start for five months may still be right for a later search. They are not right for this seat if you need coverage next month.

3. This role is [onsite / hybrid X days / remote in Y]. Does that work for you for the next year?

This filters location and schedule reality.

Pass sounds like a clear yes, with any constraints stated up front.

Fail sounds like hoping the policy will change, needing fully remote when you are hybrid three days, or a commute that only works if traffic is perfect.

Why it works: people apply broadly. Logistics are not soft skills. They are constraints. Confirm them out loud.

4. Walk me through one project on your resume that maps to [the hardest must-have in the job]. What was your part, and what shipped?

This filters resume inflation.

Pass sounds like specific ownership, tools, outcomes, and a crisp answer to what they personally did versus the team.

Fail sounds like we language with no personal slice, fuzzy timelines, or inability to name the result.

Why it works: AI-polished resumes are common. Depth still shows up when you ask for one concrete project. For more on screening AI-written resumes without chasing detectors, see Better Ways to Screen AI-Written Resumes.

5. Which parts of this job description are a stretch for you right now?

This filters honesty and self-diagnosis.

Pass sounds like one or two real gaps, plus how they close them, without pretending to be expert at everything.

Fail sounds like I can do all of it with no friction, or a gap list so long that the must-haves are clearly missing.

Why it works: people who cannot name a stretch either have not read the job, or will not admit limits. Both waste interview panels later.

6. Are you interviewing elsewhere, and is there any offer timeline we should know about?

This filters process urgency.

Pass sounds like a calm status update: other processes, none, or an offer deadline with a date.

Fail is not other interviews. Fail is total opacity after you explained why you ask, or a surprise explosion deadline that only appears after three panel interviews.

Why it works: you need to know if your five day process will lose them. Speed is a filter too. For practical ways to shorten the path after a clean screen, see 5 Ways to Reduce Time to Hire.

What phone screen questions should I skip?

Skip questions that cannot fail anyone today.

Skip tell me about yourself. You will get a rehearsed monologue and learn almost nothing new.

Skip why do you want to work here as a screen opener. Motivation essays belong later, once you know they can do the job and accept the terms.

Skip hypothetical culture riddles. Soft signal without a pass or fail rule becomes vibes hiring.

Skip repeating every bullet on the CV in order. That is a reading comprehension test for you, not a filter for them.

LinkedIn’s 2025 Future of Recruiting report pushes standardized, skills-focused interview protocols over gut feel. That advice applies even more on a short screen. Same questions. Same knock-out rules. Same notes format.

How do I run the call so it stays a filter?

Open with time and purpose. Say this is a short screen to check fit on a few hard points, then decide on a full interview.

Ask logistics and compensation before the deep proof question. If salary or location already fails, end politely. Do not drag them through a twenty minute project story you will not use.

Take notes against the questions, not against charm. Pass, fail, or unclear. Unclear means one follow-up email, not a second full screen.

Keep the panel out of this step. One interviewer. Same script. Then hand only the clears to the real interview.

Before you dial at all, knock out CV-checkable must-haves. Work authorization, required license, years in a named stack, location. That is what tools like CriteriaMatch are for: up to five CV-verifiable criteria, then a Meets all criterias filter so you are not calling people you cannot hire. Written screening questions on the application (max three, 200 characters each in Canvider) can catch the same blockers before the calendar invite. The phone call should not be the first time you learn they need a visa you cannot sponsor.

After a clear screen, use the gaps you heard to plan the real interview. InterviewGen suggests interview questions from gaps between that candidate’s resume and the job requirements once AI analysis has run. Treat them as a starting list you edit, not an autopilot interview. More on that handoff here: InterviewGen candidate gap questions. The screen filters. The interview digs.

Canvider does not ship a named phone-screen module or a formal phone-screen scorecard. Collaborative notes and custom statuses are enough for this stage. Do not invent a fake ten-point rubric for a fifteen minute call.

What does a strong pass or fail sound like in practice?

Here is the pattern I want on every note.

Question: salary range.

Pass: Candidate targets 70 to 80k. Our band is 65 to 85k. Aligned.

Fail: Candidate needs 110k minimum. Band tops at 85k. Stopped here.

Question: proof project.

Pass: Owned the Stripe billing migration. Cut failed renewals by naming the metric and their role. Could explain the failure mode.

Fail: Spoke only in we. Could not name their tickets, metrics, or decision. Resume claims lead. Screen does not support it.

If you cannot write pass or fail in one line, the question was too soft.

How should small teams sequence the early filter?

Sequence matters more than clever scripts.

  1. Application answers for true knock-outs.
  2. CV-verifiable criteria check.
  3. Optional triage score if volume is high.
  4. Short phone screen with the six questions above.
  5. Real interview with gap-based questions and a proper scorecard later.

That order protects founder time. You do not need more conversations. You need fewer, sharper ones.

SHRM’s 2025 cost-per-hire average for nonexecutive hires is about $5,475. Burning panel hours on people who fail salary or logistics is an expensive habit.

Try Canvider free. No credit card required.

Frequently asked questions

How long should a phone screen be?

Keep it short. Fifteen to twenty minutes is enough if you only ask knock-out and proof questions. If you are still explaining the company history at minute twenty, you turned a filter into a chat.

What phone screen questions should I skip?

Skip tell me about yourself, why do you want to work here, and any soft culture chat that cannot fail the candidate today. Those belong in a later interview. On a screen, ask things that can end the process.

Should a phone screen use a formal scorecard?

Not a heavy one. Write pass or fail notes against the same three or four questions for every candidate. Save the full scorecard for the real interview. Fake precision on a fifteen minute call wastes more time than it saves.

What should I filter before the phone screen?

Knock out work authorization, location, and other CV-checkable must-haves before you dial. Then use the call for salary range, notice period, schedule fit, and one concrete proof question. That order protects interviewer time.