Phone Screening Questions: 35 Questions Recruiters Ask and What to Listen For
A phone screen has one job: decide in 15 to 30 minutes whether a candidate should move on. These 35 screening questions, grouped by what they test, come with the answer you want to hear and the ones that should make you pause.
Ece Badak • Oct 17, 2026 • 8 min read

A phone screen is the first real conversation between a recruiter and a candidate. It is short, usually 15 to 30 minutes, and it has one job: decide whether this person should move on to the hiring manager.
Most phone screens go wrong in one of two ways. Some turn into a friendly chat that ends with "they seemed nice" and no evidence. Others become a checklist read aloud, where the candidate answers ten logistics questions and nobody learns whether they can do the job.
A good screen sits between the two. It checks the dealbreakers fast, then spends most of the time on a few questions that show real experience. This guide gives you 35 phone screening questions grouped by what they test, with what a good answer sounds like and what should make you pause.
What a phone screen should decide
Before you write a single question, write down the three to five things that would make you reject a candidate at this stage, and the two or three things that would make you excited. Everything else can wait for later interviews.
For most roles, the screen decides four things:
- Dealbreakers. Work authorization, location or schedule, required certificates, salary range.
- Relevant experience. Did they actually do the work the CV describes, at the level you need?
- Motivation. Why this role, why now, and does the reason hold up?
- Communication. Can they explain their own work clearly? For customer-facing roles, this is part of the job.
If a question does not help you decide one of these, cut it.
Logistics and dealbreaker questions
Ask these first. If one fails, you save both sides 25 minutes.
- "This role is based in [location] with [number] days in the office. Does that work for you?" Listen for a clear yes or a specific condition. "I'll figure it out" for a long commute often turns into a decline later.
- "Are you legally authorized to work in [country] for any employer?" Ask every candidate the same way. Do not ask about nationality or citizenship directly unless the role legally requires it.
- "The salary range for this role is [range]. Is that in line with what you're looking for?" Sharing the range first saves time, and in many US states and EU countries pay transparency rules expect it anyway.
- "What is your notice period, or when could you start?"
- "The role needs [certificate or license]. Do you hold it today?" Ask for the exact name and expiry date if it matters.
- "This team works [shift pattern or time zone]. Can you work those hours on a regular basis?"
- "Are you interviewing elsewhere? Is there a timeline I should know about?" This tells you how fast you need to move, not whether to reject.
Experience questions
This is where most of your time should go. The goal is to hear specific examples, not summaries of the CV.
- "Walk me through what you do day to day in your current role." A strong answer names tasks, tools and people. A weak answer repeats the job title.
- "Which part of your work takes most of your time?" This often reveals the real job behind the title.
- "Tell me about a project on your CV you are proud of. What was your part in it?" Listen for "I" with concrete actions, not only "we".
- "What was the result, and how did you measure it?" Good candidates know their numbers, even rough ones.
- "Your CV mentions [skill]. When did you last use it, and for what?" This is the single best question against CVs that copy the job post. If the answer is vague, ask one follow-up.
- "What does a hard week in your current job look like?"
- "Tell me about a time something went wrong at work. What did you do next?"
- "Who do you work with most, and how do you keep them updated?"
- "Which tools or systems do you use every day?" Ask about the ones your team uses.
- "What would your manager say you should get better at?" Honest answers name something real and what they are doing about it.
The follow-up matters more than the question. If an answer sounds polished but general, ask "What exactly did you do?" or "Can you give me the last example?" A real story gets more detailed under a follow-up. A rehearsed or AI-written one gets vaguer.
Motivation questions
- "What made you apply for this role?" A good answer connects something specific about the role or company to something specific about them.
- "Why are you looking to leave your current job?" Listen for a reason, not for complaints. Frustration is normal; a pattern of blaming everyone is a signal.
- "What would make the next job better than your current one?" Compare the answer with what your role actually offers.
- "Where do you want to be in two or three years?" You are not testing ambition. You are checking that this role is a step on their path, not a detour.
- "What do you know about what we do?" Basic research is a fair expectation for most roles.
Role-specific questions
Write two or three of these for every role, based on the criteria that matter most. Some examples:
- Sales: "How many calls or meetings did you run in a normal week, and what was your conversion rate?"
- Customer service: "Tell me about the last difficult customer you handled. What did they want, and what did you do?"
- Software engineering: "Describe a system you built or changed recently. What trade-off did you make?"
- Operations or warehouse: "How many people did you supervise on a shift, and how did you plan the work?"
- Recruiting: "How many open roles did you carry, and how did you decide which candidates to push first?"
- Finance: "Which month-end tasks did you own, and how long did the close take?"
Culture and working-style questions
- "Describe the best team you have worked in. What made it work?"
- "How do you prefer to get feedback?"
- "Tell me about a time you disagreed with a decision. What did you do?"
- "How do you organize your work when everything is urgent?"
Closing questions
- "Is there anything on your CV you'd like to explain or add?" Gaps and short jobs often have simple answers.
- "What questions do you have about the role or the team?" Good questions show interest. No questions at all is worth noting, not disqualifying.
- "Here are the next steps and the timeline. Does that work for you?" Always end with a clear next step.
Questions you should not ask
Some questions create legal risk in the US, the UK and the EU, even when asked with good intentions. Do not ask about:
- Age or date of birth, unless you only need to confirm a legal minimum age
- Marital status, children, pregnancy or plans to have a family
- Religion, ethnicity, national origin or sexual orientation
- Health conditions or disabilities. You can ask whether the candidate can do the essential tasks of the role.
- Salary history, in the many US states and cities that ban the question
The safe rule: ask only about what the job requires, and ask every candidate the same way.
How to score a phone screen
Notes like "great energy" do not survive a debrief. Before the first call, turn your criteria into a short scorecard, and score each criterion right after the call:
| Criterion | 1: No evidence | 2: Some evidence | 3: Clear evidence | 4: Strong evidence |
|---|---|---|---|---|
| Relevant experience | Repeats the CV | One vague example | One specific example | Several specific examples with results |
| Motivation | No clear reason | Generic reason | Specific to the role | Specific and consistent with their career |
| Communication | Hard to follow | Clear with prompting | Clear and structured | Clear, structured and concise |
Write one line of evidence next to each score, ideally the candidate's own words. That line is what the hiring manager will read. For a full template, see our interview scorecard guide.
How to run phone screens at volume
Phone screens do not scale. With 200 applicants for one role, 20 minutes each is more than 60 hours of calls before a single hiring manager interview. That is why many teams screen only the first 20 CVs that look right and never see the rest.
There are two common ways out:
- Screen CVs against clear criteria first, so you only call the candidates whose experience matches. Firstview's CV screening reads every CV against your criteria and gives a reason for each one, so nobody is rejected because their CV was the 150th in the pile.
- Replace the first call with a structured AI interview. Firstview's AI Interviewer runs a live, two-way voice interview with every candidate, whenever they are ready. It asks your questions, follows up when an answer is thin and writes a report with the candidate's words for each criterion. A person still decides who moves on.
Whichever way you choose, the principle is the same: the same questions, the same criteria and written evidence for every candidate.


