Phone screen questions and a 20-minute script for the first call.

Updated 22 October 2026

What is a phone screen and what should it decide?

A phone screen is a short first call between a recruiter or hiring manager and a candidate who has applied or been sourced. It usually runs about 20 minutes. Its job is narrow. It decides whether the candidate moves to the next round, and it rules out clear mismatches on schedule, pay, location or basic experience.

It is not a full interview. You are not testing depth of skill or judging every competency. You are checking five things: that the candidate can work the hours, wants this kind of job, has done something close to it, can talk clearly, and agrees with the next step. Good phone screen questions are short, the same for every candidate, and easy to score in a line of notes.

Recruiters who fill roles at volume often run these calls back to back, so a fixed list matters. A fixed list keeps each call on schedule and makes candidates comparable at the end of the day. For deeper questions on one skill, move to a structured round. The structured interviews guide explains how to build that round.

Which phone screen questions should you ask?

Use the 20 questions below as a bank. Use all four in each group, or drop one that does not suit the role, and keep the same set for every candidate on that role. Each question has a line on what to listen for and one follow-up. If you hire for a specific role, the customer service and call center pages have questions written for those jobs.

Logistics and availability

Start with the facts that can end the process early. If the candidate cannot work the hours, cannot start in time or cannot accept the pay range, no other answer matters. Ask these four plainly and write down the exact words the candidate uses.

1. When could you start if we made you an offer, and what would you need to do first? Listen for: a specific date or a clear notice period, with the steps named, such as handing over current work. Follow-up: how firm is that date with your current employer?
2. What hours and days are you able to work, including evenings, weekends or shifts if this role needs them? Listen for: a direct answer that matches the schedule in the job description, with any limits stated at the start. Follow-up: which days or times are not possible for you?
3. How would you get to the workplace each day, or what is your setup if the role is remote? Listen for: a realistic plan for travel time, or a quiet space and a working connection for remote work. Follow-up: what would you do on a day when that plan falls through?
4. What pay are you expecting for this role, and how did you arrive at that number? Listen for: a figure or range tied to the role and the local market, and openness to the posted range. Follow-up: how flexible is that number if the rest of the job suits you?

A strong answer sounds like a clear date, a clear schedule and a pay figure near the range. For example, the candidate says they can start in two weeks, can cover weekends and are looking for a figure inside your posted range. They say what is fixed and what is flexible.

A weak answer sounds like 'any time, I am flexible' with no date, no hours and no number. The candidate may avoid the pay question or change the figure each time it comes up. Vague logistics often mean a problem appears later, so ask the follow-up until you have a concrete answer.

Motivation and fit

These questions show why the candidate wants this job and whether the reasons match what the job really is. A good fit is a person who wants the work itself, not just any job. Listen for reasons that connect to the tasks, the hours, the customers or the place.

1. What made you apply for this role? Listen for: a reason tied to the real work, such as the tasks, the type of customer or the schedule, and not only a need for any job. Follow-up: what in the job post stood out to you?
2. Why are you leaving your current job, or why did your last job end? Listen for: a calm, factual reason, with no blaming of former managers or colleagues. Follow-up: what would you want to be different in your next job?
3. What do you know about our company and what we do? Listen for: one or two true facts found in a few minutes of research, such as the product, the customers or the location. Follow-up: which part of that would you be working on?
4. What kind of work do you enjoy most, and what do you enjoy least? Listen for: an honest answer where the liked work overlaps with the main tasks and the disliked work is not the core of the job. Follow-up: when did you last do the work you enjoy most?

A strong answer sounds like a reason that matches the job. For example, the candidate says they like talking to people all day, that the role is mostly customer contact, and that the evening hours suit them. The reason for leaving is factual and calm, and the candidate knows one or two true things about the company.

A weak answer sounds like 'I just need something' or a long complaint about a past manager. It may also describe a job different from the one you posted, which suggests the candidate has not read the post. One weak answer is not a rejection, but several in a row are a clear signal.

Role basics

Here you check that the candidate has done work close to this job. Keep to facts. Ask for tasks, tools and examples, and avoid asking candidates to describe themselves in general terms, which gives you opinions instead of evidence.

1. Walk me through your most recent role. What did a normal day look like? Listen for: concrete tasks, tools and pace in the candidate's own words, and the month the role started and ended. Follow-up: which part of that day took most of your time?
2. Which tools or systems have you used for this kind of work? Listen for: named tools that fit the role, and an honest line between daily use and a one-time try. Follow-up: what is one thing you do in that tool that a new user would not know?
3. What have you done that is closest to this job? Listen for: a specific example with the same type of customer, task or pace, described plainly. Follow-up: what was the result of that work?
4. What would you need in your first month to do this job well? Listen for: realistic needs such as training on a system or time shadowing a colleague, and a sense of what the first tasks would be. Follow-up: what could you do on day one without any help?

A strong answer sounds like a plain walk through a normal day, with named tasks, named tools and a sense of volume, such as the number of calls handled or tables served in a shift. The candidate can point to one example that is close to your role and say what came of it.

A weak answer lists job titles and company names but cannot say what a normal day held. The candidate may claim many tools but give no detail on any of them. Ask for one concrete example and wait. If none comes, score the group low.

Communication

On a call, communication is on show for the whole 20 minutes. You are listening for content, but also for how the candidate organizes an answer, how well they listen and whether they check that they understood you. For deeper work on this skill, use the communication skills questions in a later round.

1. Can you explain your last job to me in two minutes, in plain words, as you would to someone outside your industry? Listen for: a clear order of what the job was, who it was for and what came of it, in short sentences without jargon. Follow-up: which part would you explain differently to a customer?
2. Think of a call where the person did not follow your first explanation. What did you say the second time? Listen for: spotting the confusion from what the person said, dropping jargon, and a short check that the new wording worked. Follow-up: how did you know it had landed that time?
3. If a caller gave you an order number, a name and a problem, how would you confirm you had all three right? Listen for: repeating the details back, spelling out unclear items, and a polite pause before moving on. Follow-up: what would you do if the line was poor?
4. When did you last have to give someone bad news over the phone, and how did you open the call? Listen for: the news stated plainly in the first few sentences, a calm tone, and a clear next step offered. Follow-up: what did the person say, and what did you say back?

A strong answer sounds like a short explanation in order. The candidate pauses before answering, does not talk over you, and repeats back details when a number or a name matters. When the first explanation does not land, they try different words.

A weak answer is long with no clear point, full of filler words and jargon the listener cannot follow. The candidate may need each question repeated or may answer a different question than the one asked. Score the evidence in the answer, not the accent.

Closing the call

The last few minutes show how serious the candidate is and whether any hidden problem remains. Leave time for the candidate's own questions, and answer them honestly, including what you do not yet know.

1. What questions do you have about the role, the team or the next steps? Listen for: questions about the work, the team or training, and not only pay or time off. Follow-up: what would help you decide whether this job suits you?
2. Are you speaking with other employers right now, and where are you in those processes? Listen for: an honest, calm answer with a rough timeline and no pressure tactics. Follow-up: when do you need to make a decision?
3. Is there anything about the role, the schedule or the pay that would stop you from accepting an offer? Listen for: concrete concerns said openly, which you can deal with now instead of at offer stage. Follow-up: what would need to change for that to work?
4. What have I not asked that you would like me to know? Listen for: a short, relevant addition, such as a skill or an example, which shows the candidate prepared. Follow-up: how does that connect to this job?

A strong answer sounds like specific questions about the work, an honest account of other interviews, and a clear statement of any concern, for example that the schedule is the only thing the candidate needs to check. Nothing is held back that would surface after an offer.

A weak answer sounds like no questions at all, or only questions about pay and time off. The candidate may be unwilling to say where else they are interviewing, or may raise a blocking issue only after you describe the next step. Raise any such issue now, while it is cheap to deal with.

A phone screen template you can follow

This template fits 20 minutes and leaves room for the candidate's own questions. Keep a copy open during the call and write a few words in the last column as you go.

Say the plan at the start of the call. Candidates relax when they know how long it will take and what comes next. If a candidate is strong early, do not skip the later groups, because every candidate should get the same chance to answer the same questions.

How do you score phone screen questions fairly?

Score each group on what the candidate said, not on voice, accent or how friendly the chat felt. Write the criteria before the first call, so the first candidate and the last candidate are judged by the same standard.

Use a 3-point scale for each group. A score of 3 means the candidate gave specific evidence and you have no concerns, for example a named start date, a named tool and a concrete example. A score of 2 means the answer was acceptable but general, for example a tool named with no detail on how it was used. A score of 1 means the answer was vague, avoided the question or showed a clear mismatch, for example hours that do not match the schedule. Write one line of evidence beside each score so another person can check it later.

Set the pass mark before the calls too. For example, move a candidate on if no group scores 1 and role basics scores at least 2. Adjust the rule to the role, but do not change it halfway through a batch. For customer-facing roles, give the communication group extra weight.

What mistakes do interviewers make on a phone screen?

• Changing the questions from call to call, which makes candidates impossible to compare.
• Talking more than the candidate. A recruiter who fills every silence loses the information the call exists to collect.
• Judging accent, voice or small talk instead of the content of the answer.
• Skipping notes during the call and writing them from memory at the end of the day, when the first calls have blurred together.
• Asking about age, family plans, health or past pay. Many hiring teams avoid these topics. Check the rules where you hire.
• Selling the job for most of the call and leaving too little time for the candidate's answers.

What do you do right after the call ends?

The ten minutes after each call decide how useful the call was. Notes written at once are accurate. Notes written the next morning are not.

• Finish your notes while the call is fresh, and write one line of evidence for each group.
• Give each group its score from the written criteria before you read any other candidate's notes.
• Choose to move on, hold or decline, and record the reason in one sentence.
• Send the next step the same day, with a date and a time or a link, so a good candidate does not wait.
• Tell candidates you decline in plain, polite words. A short note is better than silence.

If your team is deciding whether to keep placing these calls by hand, the post on AI interviews and phone screens compares the two ways of running a first round. For roles hired in large numbers, the page on high-volume hiring shows how teams set up the process.

How does an AI interviewer run this first round?

The same first round can run as a spoken browser interview instead of a call that you place yourself. The AI interviewer from AI Interview Agents (AIIA) holds a two-way spoken conversation with the candidate in their browser, with no app to install. Candidates join from a link sent by email or WhatsApp. You set the job title, the job description and the areas to cover, such as availability, motivation and communication, and the questions are built from that.

The interviewer listens and asks follow-up questions based on what the candidate said. Interviews run in 75 languages, including English, Hindi, Arabic and Spanish. You get a transcript, a scored report with written reasoning tied to what the candidate said, a recording when one is available, and short answer clips. A person on your team makes every hiring decision. There is a free plan to start and no per-seat fees. To draft your own question set first, use the free interview kit generator.