Phone screen questions for recruiters: 30 questions with strong answers and red flags

Good phone screen questions for recruiters do two jobs in 30 minutes: rule out candidates who cannot take the role, and collect enough evidence to argue for the ones who can. The 30 questions below are role-agnostic and grouped in call order: knockouts, motivation, experience check, working style, logistics and the close. Each comes with what a strong answer sounds like and the red flags to listen for.

Pick 10 to 14 per call. Always ask the knockouts and the close; choose the rest from the client's or hiring manager's must-haves. To record the answers in a consistent order, use the recruiter phone screen template.

Knockout questions: ask these first

Ask only the knockouts the client or hiring manager has confirmed as fixed. Tell the candidate why you are asking early: "A few quick checks so neither of us wastes time."

1. "Are you legally authorized to work in [country]? Will you now or in the future require visa sponsorship?"
   • Strong answer: a direct yes or no to both parts. Candidates on time-limited status often volunteer the end date, which is useful.
   • Red flags: "It should be fine" with no detail. Ask again, in the same two parts. Do not ask about citizenship or country of origin instead.
2. "The role is [on-site / hybrid with X days / remote within Y time zones] in [location]. Does that work for you as it stands today?"
   • Strong answer: yes, with how they would do it: commute time, relocation plan and timing.
   • Red flags: "I'm sure they'd be flexible." They may not be, and the candidate is telling you the pattern does not work.
3. "This role requires [license / certification / clearance]. Is yours current, and in which state or issuing body?"
   • Strong answer: the credential, where it was issued, the expiry date, and willingness to share the number for verification.
   • Red flags: "I'm in the process" without a date; a credential issued somewhere that does not meet the requirement.
4. "The range for this role is [$X to $Y] base. Does that work for what you're looking for?"
   • Strong answer: a clear yes, or a clear "I'd need the top of it, and here's why."
   • Red flags: a yes followed later in the call by a number above the range. Note the gap and raise it before the close. For wording when they push back, see salary expectation questions.

Motivation questions

5. "What has you open to a conversation right now?"
   • Strong answer: a specific reason that connects to something this role offers: scope, progression, stability, a type of work.
   • Red flags: "Just seeing what's out there" from someone you approached is normal. From someone who applied, it suggests a low chance of accepting.
6. "What's missing in your current role that you'd want in the next one?"
   • Strong answer: one or two concrete things. "I haven't led a project end to end" is useful. "Growth" is not, until you ask what it means to them.
   • Red flags: only complaints about people, with nothing they want to move toward.
7. "What would your current employer have to do to keep you?"
   • Strong answer: "Nothing realistic", with a reason, such as the team being closed or relocated.
   • Red flags: "A raise would probably do it." That is counteroffer risk, and you should say so in the submittal.
8. "When you picture your next role, what does a good week look like?"
   • Strong answer: a description close to the actual job: the mix of tasks, people, pace.
   • Red flags: a week that looks nothing like this role. Better to find out now than in the second interview.
9. "What else are you interviewing for, and how far along are you?"
   • Strong answer: company type and stage for each process, without names if they prefer, plus any offer dates.
   • Red flags: "Nothing else" from a strong candidate in a tight market is sometimes true, often not. Ask again at the close.
10. "What do you know about [company or role] so far, and what caught your attention?"
    • Strong answer: they have read the job description or looked the company up, and name something specific.
    • Red flags: no idea which role this is, for an applicant rather than a sourced candidate.

Experience check questions

This is where the must-haves get tested. Ask for examples, then follow up on their part versus the team's part. You do not need to be an expert in the field to hear the difference between a story with detail and a list of keywords.

11. "Give me the two-minute version of your current role: what you own, who you report to, and how you're measured."
    • Strong answer: clear ownership, a reporting line, and a measure: targets, deadlines, volumes, service levels.
    • Red flags: ten minutes of history with no mention of what they are accountable for.
12. "Walk me through a piece of work you're proud of from the last two years. What did you personally do?"
    • Strong answer: "I" for their decisions and "we" for the team's, a problem, what they tried, a result with a number or a before-and-after.
    • Red flags: only "we", even when you ask directly what they did.
13. "The role needs [must-have, in the client's words]. Tell me about the last time you did that."
    • Strong answer: a recent example at similar scale, with specifics such as volume, systems, stakeholders.
    • Red flags: an example from many years ago, or one where they observed rather than did it.
14. "Which tools or systems do you use every day, and which do you just know your way around?"
    • Strong answer: they separate daily use from familiarity without prompting. That honesty is itself a good sign.
    • Red flags: everything on the resume described as expert-level.
15. "Tell me about something that went wrong on your watch. What did you do next?"
    • Strong answer: they own their part, describe the fix, and say what they changed afterwards.
    • Red flags: nothing has ever gone wrong, or every problem was caused by someone else.
16. "What's the biggest [budget / team / account / caseload / volume] you've been responsible for?"
    • Strong answer: a number, and whether they were accountable for it or contributed to it.
    • Red flags: a number much larger than the job title suggests, with no explanation. Ask how it was measured.
17. "I see you moved from [company] after [short tenure]. What happened there?"
    • Strong answer: a short, factual reason such as a layoff, a reorganization, a relocation or a role that changed, consistent with the dates.
    • Red flags: a pattern of short stays each blamed on a manager. Do not press if they indicate health or family reasons.
18. "If I spoke to your last manager, what would they say you should work on?"
    • Strong answer: a real development area and what they are doing about it.
    • Red flags: a strength disguised as a weakness ("I care too much") after a second prompt.

Working style questions

19. "What kind of manager gets the best work out of you?"
    • Strong answer: specific and plausible, such as clear goals with a weekly check-in or direct feedback in the moment. You can compare it to the hiring manager's style from the intake.
    • Red flags: a description that is the opposite of the hiring manager you are recruiting for.
20. "Tell me about a disagreement with a colleague about how to do something. How did it end?"
    • Strong answer: they argued a position, listened, and moved forward with the decision even when it was not theirs.
    • Red flags: the story ends with the other person being wrong and nothing resolved.
21. "How do you plan a week when three deadlines land at once?"
    • Strong answer: a method: prioritize by impact, flag the conflict early, negotiate a date.
    • Red flags: "I just work late." Fine once; as a system it predicts burnout or missed deadlines.
22. "What kind of environment have you not done your best work in?"
    • Strong answer: an honest answer about pace, structure or team size, with self-awareness.
    • Red flags: they describe this client's environment exactly.
23. "How do you like to work with people you don't see in person: other offices, remote teammates, clients?"
    • Strong answer: concrete habits such as written updates, agreed response times and a regular call.
    • Red flags: for a distributed team, a strong preference for working everything out in person.

Logistics questions

24. "When you resign, how much notice will you give, and could anything extend that?"
    • Strong answer: a number of weeks and any known constraint such as a bonus date, a project handover or a contract clause.
    • Red flags: "I could start Monday" while employed. Either they will not give notice, which the client may note, or they have not thought about it.
25. "What are you looking for in base pay for your next role, and how firm is that number?"
    • Strong answer: a number or narrow range, plus what else matters: bonus, benefits, schedule.
    • Red flags: a number that moves every time you mention the range. Never follow up with "what are you on now?"
26. "The role involves [travel percentage / shift pattern / on-call rota]. How does that fit with your current commitments?"
    • Strong answer: a straightforward yes, or a clear limit you can take back to the client.
    • Red flags: hesitation followed by "I'll make it work". Ask what would make it hard, and stop there if the answer is personal.
27. "If the client wants to meet you, what does your availability look like over the next two weeks?"
    • Strong answer: specific windows.
    • Red flags: no availability for two weeks during an active search. Ask whether now is the right time.

Closing questions

28. "What questions do you have about the role or the company?"
    • Strong answer: questions about the work, the team or how success is measured.
    • Red flags: none at all, or only questions about time off and remote days. Those are fair questions, but not as the only ones.
29. "Based on what you've heard, where does this sit against the other things you're looking at?"
    • Strong answer: a ranking with a reason.
    • Red flags: "It's all the same to me." Expect low engagement in interviews.
30. "If they offered you the role within the range we discussed, is there anything that would stop you accepting? And do I have your okay to put you forward for it?"
    • Strong answer: a clear yes to both, or one named hesitation you can resolve.
    • Red flags: "I'd have to see." Find out what they would have to see before you submit. Record the consent to submit with the date and time.

Questions not to ask on a phone screen

Ask about the job and the candidate's ability to do it. The EEOC's guidance on prohibited practices says pre-employment questions should be limited to what is needed to judge whether someone is qualified. Steer clear of:

• Age: date of birth, graduation year asked to work out age, "how long until you retire?"
• National origin and citizenship: where they are from, accent, native language (unless a language is a job requirement). Ask only the two-part authorization question above.
• Family and pregnancy: children, childcare, plans for a family, marital status.
• Disability and health: medical conditions, medication, sick days taken, workers' compensation history. Before an offer, the EEOC's ADA guidance allows asking whether a candidate can perform the job's functions, with or without reasonable accommodation, but not disability-related questions.
• Religion: religious holidays or observance. Describe the schedule and ask whether they can work it.
• Pay history: current or past salary is prohibited in many US states and cities. Ask expectations instead; the state rules are in salary expectation questions.
• Criminal record on the screen: many states and cities restrict when you may ask. Leave it to the employer's compliant background check process.

How to score answers quickly

You do not need a detailed rubric on a screen, just a consistent one. Rate the answer to each must-have question on evidence, not delivery:

Two or more "shown" across the must-haves, with no knockout problems, is usually enough to put someone forward. The examples in the table are invented; the pattern is what matters.

Role-specific question banks

These go deeper on the checks that general questions cannot cover:

• Nurse phone screen questions: license state and compact status, unit, certifications, charting systems.
• Software engineer phone screen questions: probing depth without being technical.
• Sales rep phone screen questions: quota, attainment and pipeline math.
• IT contractor screening questions: engagement type, rate, right to represent.
• Light industrial screening questions: shifts, reliability, safety and high-volume flow.
• Truck driver screening questions: CDL class, endorsements, routes and clearinghouse.
• Executive search screening questions: P&L scope, board exposure, confidentiality.