Phone Screen Interview Questions: What to Ask, What Good Sounds Like, and How to Score It

A phone screen should answer four questions in twenty to thirty minutes: is there a dealbreaker (right to work, location, salary, start date), does the resume hold up when the candidate talks about it, do they actually want this role, and is there enough evidence on the key requirements to justify a full interview. Ask every candidate the same questions in the same order, note the evidence as you go, and score immediately after the call.

That is the job. It is not a mini-interview, a culture chat or a sales pitch for the company, although good screens do a little of the last one. Below are the phone screen interview questions worth asking, grouped by what they are for, with what a good answer sounds like, the red flags worth probing, and a scoring sheet you can copy.

What a phone screen is for

The screen sits between screening the resume and a proper interview. Its purpose is narrow:

• Remove dealbreakers early, before anyone spends an hour on an interview that could never lead to a hire.
• Check the resume is real — not in the sense of catching liars, but confirming the candidate can talk in specifics about the work they list.
• Test motivation — whether this role is something they want, or just the next application in a long list.
• Get a first signal on the one or two requirements that matter most and cannot be read off a document.

What it is not for: deep technical assessment, testing "culture fit", or forming a general impression of whether you like the person. Those either belong in a structured interview with a real rubric or do not belong in the process at all.

A 25-minute phone screen structure

The order matters. Logistics goes first because a dealbreaker found in minute 24 wastes the other 23 — for both of you. Motivation goes near the end because candidates give more honest answers once the call has settled.

Tell the candidate the structure at the start. It reduces nerves, which means you hear the candidate rather than their anxiety.

The questions, grouped by purpose

Logistics and dealbreakers

Ask these directly and neutrally. They are not trick questions, and the candidate should know why you are asking.

Ask about salary expectations, not salary history. Several jurisdictions restrict questions about current or past pay, and expectations are the more useful number anyway. If you have a published band, share it — it saves everyone time.

If you ask these same questions for every role, put them in the application form instead and spend the call on things only a conversation can reveal. See job application forms.

Verifying the resume

The core of the screen. The aim is to hear specifics about what the candidate personally did.

The single most useful follow-up across all of these: "What did you personally do?" Ask it once, politely, whenever an answer stays at the team level. Most strong candidates answer it easily. Candidates who have been close to good work without doing it tend to stay vague.

Role-specific questions

One or two questions tied directly to the requirements with the highest weight on your hiring scorecard. Write them before the first call and ask them identically every time.

Examples:

• Customer support lead: "Tell me about a time your team's queue got out of control. What did you change?"
• Backend engineer: "Describe the last production incident you were involved in. What was your role in resolving it?"
• Account executive: "Walk me through a deal you closed recently — who the buyer was, how long it took, and what nearly lost it."
• Finance: "Which parts of the month-end close do you own, and which do you review?"

These are not full interview questions — you are looking for evidence that the experience exists and is recent, not assessing depth. Depth is what the interview is for.

Motivation

Motivation answers are the easiest to rehearse, so do not over-weight them. Their real value is spotting mismatches early: a candidate who wants to manage people applying for an individual contributor role is better told now.

Closing

• "What questions do you have for me?" — leave at least four minutes. Thoughtful questions about the work are a mild positive signal; no questions is not a negative one on its own.
• "Is there anything relevant we haven't covered?" — occasionally surfaces something important that was not on the resume.
• Then tell them exactly what happens next and when they will hear back. Then make sure they do — including if the answer is no. We have rejection email templates for every stage.

Questions you should not ask

Some questions are unlawful to base a decision on in most jurisdictions, and asking them creates the appearance that you did. This is general guidance, not legal advice, but the safe list is short and consistent:

• Age or date of birth, or questions that reveal it ("What year did you graduate?")
• Marital status, children, pregnancy or plans to have a family
• Religion, or which holidays they observe
• Health, disability or medical history — beyond, where lawful, whether they can perform the essential tasks of the job with or without reasonable adjustments
• Nationality, ethnicity or place of birth — ask about the right to work instead
• Salary history, where local rules restrict it

If a candidate volunteers any of this, do not follow up on it, and do not write it down.

Red flags worth probing — and ones that are not

Worth probing:

• Consistently team-level answers after a direct "what did you do?" follow-up.
• Dates, titles or scope that do not match the resume.
• Skills listed as core that the candidate cannot describe using recently.
• A salary expectation or location constraint that makes the role unworkable — probe it, then be honest.

Not red flags, however they feel in the moment:

• Nerves, pauses, or asking to think for a second.
• An accent, or a less polished phone manner — unless spoken communication on the phone is itself a core, defined requirement of the job.
• A gap on the resume. Ask neutrally if it is relevant; accept the answer.
• Short tenures in fields where contract and project work is normal.
• Not knowing much about your company. It is a screen, not a quiz.

The test for any concern: could you connect it to a specific requirement on the scorecard? If not, it is an impression, and it should not decide the outcome.

A simple scoring approach

Score immediately after each call, before your next one, and before discussing the candidate with anyone else.

Logistics: pass / fail. Any genuine dealbreaker ends the process here, with the reason recorded.

Then four dimensions, each scored 1 to 3:

Advance at 8 or above out of 12, with no 1 on the key requirement. Set your own threshold if that does not suit the role — but set it before the first call, not after you have heard who is in the pool.

Next to each score, write one line of evidence: "Led the helpdesk migration and personally rewrote the support macros" rather than "strong". That line is what lets a hiring manager trust your recommendation without redoing the call, and it is what you draw on if a candidate later asks for feedback.

Running phone screens at volume

Once there are more than a handful of candidates per role, the screen becomes a process problem rather than a conversation problem:

• Use one script per role. The same questions in the same order are what make scores comparable across candidates and across recruiters.
• Batch the calls. Blocks of three or four screens with ten minutes between each for scoring beats scattering them through the week.
• Move logistics upstream. Every dealbreaker question answered on the application form is five minutes back on every call.
• Prepare from the resume, not in the call. Read each resume for the one or two points you most need to verify, and plan those follow-ups before you dial.

That last step is where tooling helps. In Resume World, skill gaps, experience discrepancies and tenure variances are surfaced as interview questions rather than silent rejections, and you can ask the candidate AI assistant about a candidate's timeline or accomplishments before the call — see AI resume screening software. It prepares you for the conversation. It does not replace it, and the decision stays with the person who made the call.

The short version

1. Twenty to thirty minutes, with the structure explained up front.
2. Logistics first, so a dealbreaker does not waste the call.
3. Most of the time on specifics: what did you personally do?
4. One or two role-specific questions, straight from the scorecard.
5. Motivation last, and never over-weighted.
6. Score immediately, with one line of evidence per dimension, against a threshold set in advance.
7. Tell every candidate what happens next — and follow through.