Interview guide · Interview types
Phone screen questions
In short
Phone screen questions are the short set a recruiter asks in a 10 to 20 minute first call to confirm a candidate meets the must-have requirements, wants the job on its real terms, and communicates well enough to move forward. This page gives 30 questions in the order to ask them, with what to listen for and red flags.
A phone screen has one job: decide, quickly and fairly, whether this person should get a full interview. It is not a mini interview. The best recruiters run it like a checklist with a conversation wrapped around it. Confirm the knockouts first (schedule, location, pay, required licenses or work authorization), then check one or two signs of real interest and basic job skill, then sell the role honestly and book the next step. For the definition and where it sits in the funnel, see our glossary entry on the phone screen.
Use the same questions in the same order for every candidate on a requisition and write the answers into a standard form, such as our phone screen template, while you talk. That keeps the screen fair, makes handoffs to hiring managers clean, and lets you compare candidates across recruiters. Twelve to fifteen minutes is enough for most hourly and frontline roles. Professional roles may need 20 to 30.
What these questions assess
- Meets the real must-havesSchedule, location, pay range, required certifications and work authorization. If any of these is a hard no, the rest of the call does not matter, so ask them first.
- Accurate understanding of the jobCandidates who know the shift, the pay and the actual work before the interview show up more often and quit less in the first 30 days.
- Clear, organized communicationFor phone-based roles the screen is a work sample. Listen for pace, clarity and whether the candidate answers the question asked.
- Specific reasons for wanting this jobGeneric interest is normal at this stage, but candidates who can name something about the role, team or schedule that suits them convert and stay better.
- Reliability signalsAnswering the scheduled call on time, having the details you asked them to prepare and following through on what they say are early predictors of attendance.
Opening and interest
What do you know about this role so far, and what made you apply?
- Why ask it
- Checks whether the candidate read the posting and gives you a starting point for correcting any misunderstanding.
- A strong answer
- Names something concrete from the posting, such as the shift, the type of customer or the pay, and links it to their own situation.
- Red flags
- Does not remember applying or which job this is, and shows no curiosity once told.
Can you give me a quick overview of your current or most recent job?
- Why ask it
- Gives you the context to judge the rest of the call in about two minutes.
- A strong answer
- Covers employer type, role, main duties and how long, in a clear order, without reading the resume aloud.
- Red flags
- Rambles for five minutes or cannot describe what they actually did day to day.
Why are you looking to leave your current job, or why did your last one end?
- Why ask it
- Reveals motivation and possible fit problems, such as leaving because of the exact schedule you offer.
- A strong answer
- Gives a straightforward reason (pay, hours, growth, commute, contract ended) without attacking the previous employer.
- Red flags
- Long complaints about every manager or a story that changes when you ask a follow-up.
What are you looking for in your next job that you do not have now?
- Why ask it
- Tells you what will make this candidate accept and stay, and whether you can offer it.
- A strong answer
- Specific and realistic, such as weekday shifts, a chance to move into a lead role or a shorter commute.
- Red flags
- Wants something the role clearly cannot provide, such as full remote work for an on-site job.
Logistics and must-have requirements
This role works [shift and days]. Is that schedule something you can commit to, including [weekends or overtime expectations]?
- Why ask it
- Schedule mismatch is the most common reason frontline hires quit in the first month.
- A strong answer
- A clear yes, or an honest statement of the specific limits so you can check whether another shift works.
- Red flags
- A vague probably, or yes followed later in the call by commitments that clash with the schedule.
The job is based at [location]. How would you get there, and how long would that take you?
- Why ask it
- Commute is a strong predictor of early attrition for hourly roles. Ask about the commute, not about car ownership unless driving is a job requirement.
- A strong answer
- Has a realistic plan and has thought about the time it takes at shift start.
- Red flags
- Has not considered it, or the plan depends on a ride they are unsure of.
The pay range for this role is [range]. Does that work for you?
- Why ask it
- State the range rather than asking for salary history, which is restricted in many states and cities. Many jurisdictions also require the range in postings.
- A strong answer
- Confirms the range works or gives a clear target so you can decide quickly.
- Red flags
- Expects far above the range and is not open to discussion, or agrees without seeming to have heard the number.
Are you legally authorized to work in the United States? Will you now or in the future require sponsorship for an employment visa?
- Why ask it
- These two questions are the lawful way to check work authorization. Ask every candidate the same wording.
- A strong answer
- Clear yes or no answers to both.
- Red flags
- None from the candidate. The red flag would be an interviewer asking about citizenship, birthplace or accent instead.
This role requires [license, certification or minimum age required by law]. Do you hold it, and is it current?
- Why ask it
- Confirms a true legal or job requirement before anyone spends more time.
- A strong answer
- Yes, with the type and expiration date, or a credible plan to complete it before the start date if your policy allows.
- Red flags
- Unsure whether the license is current or describes it in a way that does not match the requirement.
When would you be available to start if you received an offer?
- Why ask it
- Lets you match candidates to class start dates or project timelines.
- A strong answer
- A specific date that accounts for notice to their current employer.
- Red flags
- Would leave their current job with no notice, which often predicts how they will leave yours.
Are you interviewing anywhere else, and where are you in those processes?
- Why ask it
- Tells you how fast you need to move and whether you are likely to lose the candidate.
- A strong answer
- An honest answer about stage and timing. Most good candidates are talking to more than one employer.
- Red flags
- Has a final offer elsewhere expiring today and expects you to skip steps.
Experience and skills check
Walk me through a typical day in your current role. What takes most of your time?
- Why ask it
- Shows whether the resume reflects real day-to-day work and how close it is to this job.
- A strong answer
- Describes tasks in order with rough proportions and the tools or systems used.
- Red flags
- Repeats job-title buzzwords without describing actual tasks.
This job involves [main task, for example handling 50 to 70 inbound calls a day]. Where have you done something similar?
- Why ask it
- Tests directly for the experience that matters most, rather than general experience.
- A strong answer
- Gives a comparable example with volume or scale, or explains clearly how a related experience transfers.
- Red flags
- Claims the experience but cannot give any detail when asked about volume or tools.
Which systems or tools have you used that you would expect to use here, such as [CRM, POS, scanner or ticketing system]?
- Why ask it
- Gauges ramp-up time and training needs.
- A strong answer
- Names specific tools and their comfort level honestly, including what they have not used.
- Red flags
- Says they know everything, then cannot name any tool.
On your resume you list [specific achievement or responsibility]. Tell me a bit more about that.
- Why ask it
- A quick credibility check on the strongest claim in the resume.
- A strong answer
- Expands with context, their own role and a result, consistent with what is written.
- Red flags
- Struggles to explain it or the story shrinks noticeably when asked.
I see a gap between [date] and [date]. What were you doing during that time?
- Why ask it
- Gaps are common and usually innocent. Asking neutrally clears them up rather than letting a hiring manager assume.
- A strong answer
- A short, plain explanation. Candidates do not need to share personal or medical details and you should not press for them.
- Red flags
- None from a reasonable explanation. Do not probe into health, family or pregnancy.
What kind of training or onboarding helps you learn a new job fastest?
- Why ask it
- Shows self-awareness about learning and helps the hiring manager plan.
- A strong answer
- Specific preferences, such as shadowing first then taking calls with someone listening, and an example of learning a new job quickly.
- Red flags
- Expects to be fully productive on day one with no training or cannot say anything about how they learn.
Short behavioral checks
Tell me briefly about a time a customer or coworker was upset with you. What did you do?
- Why ask it
- A short behavioral probe that predicts how the candidate handles friction on the job.
- A strong answer
- Stayed calm, listened, took one practical step to fix it and can say how it ended, all in under two minutes.
- Red flags
- Blames the other person or cannot think of any example in a customer-facing role.
Tell me about a time you had to learn something new quickly at work.
- Why ask it
- Learning speed matters for any role with a short training period.
- A strong answer
- Names what they learned, how they approached it and how long it took to be confident.
- Red flags
- Waited to be taught everything and did not seek out help or resources.
How did your last supervisor describe your attendance and reliability?
- Why ask it
- Invites honesty about a common failure point and sets up a later reference check.
- A strong answer
- An honest answer with specifics, including any issue and what they changed.
- Red flags
- Hesitates, then claims perfect attendance in a way that does not fit the rest of the conversation.
What is one thing a previous manager told you to work on?
- Why ask it
- A fast coachability check.
- A strong answer
- A real piece of feedback and what they did about it.
- Red flags
- Says no manager has ever given them development feedback.
Motivation and closing
What would make you say no to an offer from us?
- Why ask it
- Surfaces dealbreakers early so you do not lose the candidate at the offer stage.
- A strong answer
- Names something specific and honest, such as a pay floor or a start date.
- Red flags
- Nothing at all, which often means they are not being straight with you.
What questions do you have about the role, the team or the schedule?
- Why ask it
- The questions a candidate asks show what they care about and how seriously they are considering the job.
- A strong answer
- Asks about the work itself, training, schedule or how success is measured.
- Red flags
- No questions at all, or only about how soon they can take time off.
Here is what the next step looks like: [interview format, who they will meet, timing]. Does that work for you?
- Why ask it
- Confirms commitment to the next stage and cuts no-shows.
- A strong answer
- Confirms a time on the spot and asks what to prepare.
- Red flags
- Will not commit to any time in the next week.
What is the best way and time to reach you over the next few days?
- Why ask it
- Speeds up scheduling and shows whether the candidate is easy to work with.
- A strong answer
- Gives a clear channel and window, and confirms text messages are fine if you use them.
- Red flags
- Difficult to pin down, which usually predicts a slow, drawn-out process.
Extra questions for professional and experienced candidates
What is the scope of your current role in numbers: team size, budget, accounts or volume?
- Why ask it
- Calibrates the candidate's level against the role quickly.
- A strong answer
- Gives specific numbers and is clear about what they own versus support.
- Red flags
- Inflates scope and backs off when asked a follow-up.
What is one result from the last year you are most proud of?
- Why ask it
- Gives the hiring manager a headline to explore in the full interview.
- A strong answer
- A specific outcome, their role in it and why it mattered to the business.
- Red flags
- A list of responsibilities with no result.
Who would you report to in your current role, and how would they describe your work?
- Why ask it
- Sets up reference checks and tests self-awareness.
- A strong answer
- Balanced description with strengths and one area of growth.
- Red flags
- Will not say who they report to or describes the relationship as strained without explanation.
How does this role fit into what you want to be doing in three years?
- Why ask it
- Shows whether the job is a step forward or a stopgap.
- A strong answer
- Connects the role to a realistic direction and shows they understand what the job involves.
- Red flags
- Plans to leave this function as soon as possible.
Is there anything about your background you would like the hiring manager to know that we have not covered?
- Why ask it
- Lets candidates add relevant context and makes your summary fairer.
- A strong answer
- Adds a relevant project, skill or explanation in a sentence or two.
- Red flags
- None. Silence is fine here.
Sample answers
I have been at a grocery chain for three years, first as a cashier and for the last year as a customer service desk lead. I like the work, but my hours were cut from 38 to about 24 a week in the spring, and they have not come back. I need full-time hours and benefits. I applied here because the posting said the day shift is guaranteed at 40 hours, and handling returns and complaints at the service desk is most of what I do now. My store manager knows I am looking, and I have told her I would give two weeks of notice so she can cover the desk.
At my current job with a utility company I take about 60 calls a day, mostly billing questions, payment arrangements and start or stop service requests. Our target handle time is six minutes and I average around five and a half. I use a CRM to pull up the account and a separate system for payments, so I am used to switching between screens while I talk. The part I find hardest is when someone has been on hold a long time and starts the call angry. What helps me is to apologize for the wait first and then get straight to the account so they can hear I am working on it.
Interview scorecard
| Competency | Weight | Strong (4–5) | Weak (1–2) |
|---|---|---|---|
| Must-have requirements | 30% | Meets schedule, location, pay, authorization and license requirements without conditions. | One or more hard requirements are not met or the answers are uncertain. |
| Relevant experience | 25% | Has done comparable work at similar volume or level and can describe it in detail. | Experience is vague, unrelated or does not hold up to a follow-up question. |
| Communication | 20% | Clear, organized and concise, answers the question asked. | Hard to follow, rambling or does not answer the question. |
| Motivation and understanding of the role | 15% | Knows what the job involves and has specific reasons it fits. | Unclear about the job or motivated by something the role cannot offer. |
| Reliability signals | 10% | On time for the call, prepared, commits to next steps. | Missed or late for the call, unprepared, avoids committing to a time. |
Score each competency from 1 to 5 straight after the interview, before discussing the candidate with anyone else, then multiply by the weight.
How to structure a 15-minute phone screen
Most recruiters run the screen in four blocks. Minute 0 to 2: introduce yourself, say how long the call will take and what you will cover. Minute 2 to 6: knockouts, in a fixed order (schedule, location, pay, authorization, license). If a knockout fails, be honest and end the call politely, or offer a different opening if one fits. Minute 6 to 12: experience and two short behavioral questions. Minute 12 to 15: the candidate's questions and booking the next step.
Book the call through a short invitation that sets expectations; our phone screen invitation email gives you wording that tells candidates the length, who will call and from what number, which alone cuts missed calls noticeably. Take notes in a standard form during the call, not after. Then write a two-line summary for the hiring manager: recommend or not, and the one or two facts that drove the decision.
For roles where the hiring manager wants to see the candidate or hear more depth, a recorded or live video interview can replace the second phone call, but do not use video for the first screen unless appearance on camera is part of the job. It adds friction and no real information for most frontline roles.
Legal do's and don'ts on the phone
Phone screens feel informal, which is exactly why they produce risky questions. The chat before the questions start is where recruiters ask where are you from, is that a Spanish accent, do you have kids at home, or how old were you when you graduated. All of these invite information about protected characteristics under federal law (Title VII, the ADEA, the ADA) and many state laws, and once you know it, it is hard to prove it played no part in the decision.
Stick to the job: ask whether the candidate can work the schedule, not why they might not. Ask the two work authorization questions exactly as written above and nothing about citizenship or national origin. Do not ask about salary history where it is banned (a growing list of states and cities); state the range instead. Ask about criminal history only where your state and local fair-chance laws allow it at this stage, which in many places is only after a conditional offer. Our list of illegal interview questions covers the common traps in more detail. Rules vary by state and city, so check with counsel for your locations.
Common phone screen mistakes
- Selling before qualifying. Recruiters who spend ten minutes pitching the company before asking about schedule waste both people's time on candidates who cannot work the shift.
- Hiding the hard parts of the job. Mandatory weekends, a 6 a.m. start or a hot warehouse floor should come up on the call. Candidates who opt out now would have quit in week two.
- Different questions for different candidates. If one recruiter asks about reliability and another does not, the shortlist reflects the recruiter, not the candidates.
- Writing no notes. Hiring managers ask why someone was advanced, and in an audit you will need the answer.
- Letting good rapport replace evidence. Pleasant conversation is not the same as meeting requirements. Score the form, not the feeling.
- Leaving the next step open. Every call should end with a booked time or a clear decision date.
Phone screens at high volume
A recruiter doing live screens can handle roughly four to six an hour once you count no-shows and notes. If you need 200 screens a week for a contact center ramp, that is a full-time job for one to two people and the queue still grows on Mondays. This is where most high-volume teams automate the knockout portion. Short text or chat questionnaires can confirm schedule, location, pay and authorization in two minutes, any time of day, and AI-assisted voice or chat screens can ask the same experience and behavioral questions in the same order and score them against the same rubric.
The principle is the same whether a person or a system asks: identical questions, scored consistently, with a recruiter reviewing borderline cases and anyone flagged out. Keep the final screen call short and human for candidates who pass, and spend it on selling the job and answering questions. Measure screen-to-interview and interview-to-offer conversion by source every month. If more than half of screened candidates fail at the interview, your screen is not asking the right questions. Our recruiter interview questions cover what to look for in the people running these screens.
Frequently asked questions
How long should a phone screening interview last?
Ten to fifteen minutes for hourly and frontline roles, and 20 to 30 minutes for professional and management roles. If you regularly run over, you are interviewing rather than screening, and that work belongs in the next stage.
What are good pre-screening questions to ask candidates?
Start with the knockouts: can you work this schedule, can you get to this location, does this pay range work, are you authorized to work in the US, and do you hold any required license. Then ask one or two questions about relevant experience and one short behavioral question.
Should recruiters ask about salary expectations in a phone screen?
Yes, but state your range first and ask whether it works. Asking about current or past salary is banned in many US states and cities, while asking about expectations is generally allowed. Pay transparency laws in several states also require you to share the range.
What is the difference between a phone screen and a phone interview?
A phone screen confirms basic fit and requirements, usually run by a recruiter in about 15 minutes. A phone interview is a full interview conducted by phone, usually with the hiring manager, and goes deeper into skills and behavior.
What should a recruiter do if a candidate fails a knockout question?
Say so honestly and kindly during the call, for example that the role requires weekend shifts every week. If another opening fits, offer it. Otherwise thank them and close the application promptly, so they are not left waiting.
Can phone screening be automated?
The knockout and basic experience questions can be, through text, chat or AI-assisted voice screens that ask everyone the same questions. Keep a recruiter reviewing borderline cases and make sure candidates can request an accommodation or a live call.