Phone screen interview questions are the questions a recruiter asks in a short first call, before anyone else on the hiring team spends time on a candidate. When each recruiter picks their own, two candidates for the same role answer different questions, and the hiring manager can’t tell whether the candidates differ or the calls did.

I recommend a fixed set of twelve questions in four blocks, asked in the same words and the same order to every candidate for a role. Each block of questions below comes with what to listen for in the answers, and a short script gives you the lines to say between the blocks.

This guide is for recruiters who run phone screens and the hiring managers who read what comes out of them. It covers what a phone screen has to find out, the twelve questions, what to say from the opening to the close, how to adapt the questions to a role, and how to check that they’re working.

Decide what the phone screen has to find out.

A phone screen is the first conversation a candidate has with your team, so it has to find out a few things fast and leave the deeper questions to later interviews. It has four jobs: rule out dealbreakers, gather evidence on two competencies, learn what draws the candidate, and find out their timing and doubts. Give each job its own block of questions. The table lists the four blocks, what each one finds out, and which of the twelve questions belong to it:

Block What it finds out Questions
Dealbreakers Whether location, work authorization, the start date, or pay rules the candidate out 1 to 4
Two competencies Evidence on the two competencies the hiring manager cares about most, from one recent piece of work 5 to 8
Motivation Why the candidate wants this role, and why now 9 and 10
Timing and doubts Where the candidate is with other employers, and anything about the role that doesn’t fit 11 and 12

Before the first call, agree with the hiring manager on the two competencies and on what a strong answer to each of questions 5 to 8 sounds like, so the second block tests what they’ll look for in later interviews.

The candidate is also deciding about you. You may be the first person from your company they’ve spoken to, so listen in the motivation block for what draws them, and speak to it when you describe the role at the end of the call. That’s where you give them a reason to keep going.

Running the stage itself, from preparing for the call to handing what you learned to the next interviewer, has its own guide on how to conduct a recruiter phone screen. This page gives you the questions and the words to say.

Ask twelve phone screen interview questions, in order.

Write the twelve questions into a shared document your team works from, and ask them in this order on every call for the role. The exact words count most in the competency questions, where a change of wording can pull out a different story. Under each block, you’ll find what to listen for in the answers.

Questions 1 to 4: the dealbreakers.

Ask these first, and plainly. If a requirement rules the candidate out, you both want to know in the first five minutes.

  1. This role is [on site, hybrid, or remote] in [location], on [schedule]. Where are you based, and does that work for you?
  2. Will you now or in the future need visa sponsorship to work in this role?
  3. How much notice do you need to give, or when could you start?
  4. Our range for this role is X to Y. Does that work for you?

Listen for a clear answer to each. A “probably” on sponsorship or the start date needs one follow-up question before you move on.

Question 4 gives your range before it asks whether the range works, so the candidate answers against a real number. If you need to know more about pay, ask what the candidate expects to earn rather than what they earn now: some places bar employers from asking about pay history, so check the rules where the candidate is based.

Questions 5 to 8: two competencies, from one piece of work.

Ask the candidate to choose one recent piece of work, and stay on it for all four questions. As written, questions 5 and 6 test ownership, and questions 7 and 8 test self-awareness. If the hiring manager names a different pair of competencies, rewrite these four questions to test that pair.

  1. Tell me about a piece of work from the last year you’d put your name on.
  2. What was the hardest decision you made on it, and what did you decide?
  3. What went wrong, and what did you do once you noticed?
  4. If you did it again with the same constraints, what would you change?

For questions 5 and 6, listen for the constraint the candidate worked under, the decision they made, and what they gave up to make it. If every answer says “we,” ask what they did themselves. Questions 7 and 8 should bring out a named mistake and what changed afterward. A rehearsed story can sound as convincing as a real one, so ask for a detail it didn’t cover, such as who pushed back on the decision or what the candidate tried first.

Questions 9 and 10: motivation.

These two questions find out what draws the candidate to this role.

  1. Why this role, and why now?
  2. What would need to be true a year from now for you to call this a good move?

Listen for a reason that’s about this role, beyond leaving the last one. An answer to question 10 also tells you what the candidate will check the job against later.

Questions 11 and 12: timing and doubts.

Ask question 11 before you tell the candidate more about the role, and question 12 after it, so the candidate can respond to what you described.

  1. What else are you interviewing for, and how far along are you?
  2. Is there anything about the role, as I’ve described it, that doesn’t fit what you’re looking for?

Question 12 is the easiest to drop when a call runs late. Ask it anyway, because it gives the candidate a chance to raise a doubt while you can still answer it.

Say the same lines from opening to close.

Script the lines between the questions as well as the questions, so every candidate hears the same call. Give each part a fixed number of minutes, too, so you know what to shorten when a 30-minute call falls behind. The table gives the minutes for each part of the call, what you cover in that part, and what to say to start it:

Minutes What you cover What to say
0 to 2 Consent to record, if your team records calls, then the plan for the call “Thanks for making the time. This should take about half an hour: some practical questions first, then your recent work, then anything you’d like to ask me.”
2 to 7 The dealbreakers, questions 1 to 4 “Before we get to your work, a few practical ones.”
7 to 20 Two competencies, questions 5 to 8 “Now I’d like to spend most of our time on one piece of your recent work.”
20 to 25 Motivation, questions 9 and 10, and the first timing question, question 11 “Three more quick ones, and then we’ll get to the role and your questions.”
25 to 30 The role, the candidate’s questions, question 12, and the next step “Let me tell you a bit more about the role, and then ask me anything you like.”

If your team records phone screens, ask for the candidate’s consent at the very start of the call, before the recording begins. Use your own words, in line with your recording policy. For example: “I record these calls so I can give you my full attention. Is that okay with you?”

When you fall behind, take the time out of your general description of the role, but keep the part that speaks to what draws this candidate. The twelve questions stay, and so does the time for the candidate’s own questions.

Close with a real date for the next step, such as “You’ll hear from me by Thursday either way.” Then keep to it.

A phone line hides the nods and reactions a video interview shows, so tell the candidate where you are in the call, such as “two more on logistics, then your recent work.” Send the job description before the call, too, since you can’t show it during the call. A separate guide covers what else a phone interview changes, including recording and notes.

Adapt the questions to the role.

The twelve questions are a starting set. Change them once, before the first call for a role, and then keep them the same until the role is filled. If a question changes partway through a search, the candidates before and after the change answered different questions, and their answers are harder to compare.

Rewrite questions 5 to 8 around the two competencies the hiring manager named, and keep the four-question shape: one piece of work, a decision, a mistake, and what the candidate would change. If the hiring manager names a competency you don’t have questions for, a separate interview question bank lists questions by competency.

Add the role’s own hard requirements to questions 1 to 4, such as shift availability for an hourly role or a license the job needs. Keep only requirements that rule a candidate out on their own, and leave preferences for later interviews.

Where Metaview fits.

It’s hard to listen closely to an answer while you type it, and once a phone screen ends, your notes are all that’s left of it. Metaview is the Agentic Recruiting Platform, and it handles phone screens as well as video interviews.

Where consent has been given, the Metaview Notetaker records and transcribes an interview, then turns the conversation into structured notes. The recording captures every spoken word, so you can keep your attention on the candidate during the call. Afterward, you can check the transcript to see whether each candidate heard all twelve questions in the same words.

A recorded interview in the Metaview Notetaker, with the transcript below it showing who spoke and when
An interview recording with its transcript, where the interviewer asks one question and then two follow-ups. The interviewer and candidate shown are sample data.

The Notetaker also drafts your scorecard from the same conversation. You review the draft, choose the rating, and submit it.

With the notes taken care of, you can listen for what the candidate is deciding about you, which questions 9 to 12 bring out. Metaview co-founder and chief technology officer Shahriar Tajbakhsh has written about what an interviewer loses by forgetting that the candidate decides, too:

Good interviewers know that failing to close an excellent candidate is a silent company killer.”
Shahriar Tajbakhsh Shahriar Tajbakhsh Co-founder and Chief Technology Officer · Metaview

Question 12 brings out the doubts that can lose you a candidate like that, while you can still answer them.

For roles where more people apply than your team has time to call, Metaview Screening holds a voice-led screening conversation with each candidate the team chooses to assess. It follows up when an answer is thin and lets the candidate ask questions back. Each completed call comes back with a fit rating and its reasons, the recording, and the transcript. For every completed call, a recruiter decides who moves forward, and Metaview does not make that decision.

Listen to the candidate on every phone screen.
Book a demo to see the Notetaker turn a phone screen into structured notes and a draft scorecard for you to review.
See it live

How to tell whether your phone screen questions are working.

After a few weeks of phone screens on a role, go back over a handful of calls with the hiring manager, and ask these five questions:

  1. Did every candidate hear all twelve questions, unless a dealbreaker ended the call early? If questions went missing, find out which ones recruiters drop, and why.
  2. Do the calls end on time? If they run long, find the block that overruns, and check whether it has drifted into a later interview’s job.
  3. Do questions 5 to 8 get specific answers? If the answers stay general, add a follow-up question that asks what the candidate did themselves.
  4. Do recruiters on the same role put candidates forward at similar rates? If not, compare their notes before you decide whether the candidates differed or the calls did.
  5. Does the hiring manager agree with the candidates you put forward? If not, go through the four blocks together, and revise what you agreed before the first call about a strong answer to questions 5 to 8.

Fix the questions these checks flag before the next role opens. That way, every candidate for a role keeps hearing the same twelve questions, and the hiring manager can compare their answers.

See it in action.

Review every phone screen from the recording.

See how Metaview records phone screens where consent has been given, turns them into structured notes, and drafts each scorecard for you to review and submit.

Frequently asked.

Who should run the phone screen, the recruiter or the hiring manager?

The recruiter usually runs it. Clearing the dealbreakers and selling the role are recruiting work, and the hiring manager’s time goes further in a later interview. Bring the hiring manager in early for senior roles where the candidate expects it, or for a requirement too technical for a recruiter to judge.

What’s the difference between a phone screen and a first-round interview?

A phone screen checks the basics and gathers some evidence on two competencies. A first-round interview tests skills in depth, usually with the hiring manager or someone on their team. The phone screen helps decide whether that deeper interview is worth everyone’s time.

Should you send candidates the questions before a phone screen?

Send the job description and the plan for the call, so candidates can think about which piece of work they’ll talk about. Exact questions sent ahead can come back as rehearsed answers, which are harder to follow up on.

Is it legal to record a phone screen?

It depends on where you and the candidate are, since some states in the United States require everyone on a call to agree before it’s recorded. Ask the candidate at the start of every call, before the recording begins, and check your recording policy with your legal team.

What if a candidate fails a dealbreaker in the first five minutes?

Tell them kindly and directly which requirement doesn’t fit, and end the call early so you don’t take more of their time. Then write down the reason in your notes, so anyone who reads them later knows why the call ended.