Phone Screen Questions and How to Answer Them

TL;DR — The recruiter phone screen is a 15-to-30-minute filter, not a test of your talent. A recruiter is checking a short list of boxes: can you do the basics, do you actually want this job, can you start when they need you, and does your number fit the budget. Prepare a 90-second background summary, one honest reason you're looking, a researched salary range, and your availability — then take the call somewhere quiet with your résumé in front of you.

The email says "quick 15-minute call to learn more about you," and most candidates treat it as a warm-up. It isn't. It's the narrowest gate in the whole process, and people fail it for reasons that have nothing to do with whether they could do the job — a fumbled salary answer, a vague reason for leaving, a start date that didn't work. This guide covers what the recruiter screen is for, how it differs from the interview that follows it, and the questions you'll actually get with sample answers for each.

What a recruiter screen actually is

The University of Houston's Rockwell Career Center describes a phone screen as "a short phone call, lasting from 15 to 30 minutes" — and, critically, one "usually conducted by a recruiter or coordinator on a company's talent acquisition team," not by the person you'd report to. The purpose is subtraction: they're "trying to further narrow down the pool for the people who will hold more comprehensive interviews and decide who to hire." The University of San Francisco's career services frames the screening interview the same way — it exists to "confirm that you have the skills and qualifications needed to perform the job," and to verify what you put on your résumé.

Read those two descriptions together and the strategy falls out. The recruiter usually can't hire you. They can only advance you or stop you. So your job on this call isn't to be dazzling — it's to give them nothing to flag.

That's the real difference from the interview that comes next:

• The recruiter screen tests basics and deal-breakers: qualifications, motivation, timing, money, logistics. Answers should be short, clean, and consistent with your résumé.
• The hiring-manager interview tests judgment and depth. That's where detailed stories earn their keep — see the STAR method for behavioral interviews for how to build them.

Bring a five-minute story to a phone screen and you'll lose the recruiter. Bring a one-sentence answer to the hiring manager and you'll look thin. Match the answer to the stage.

"So, walk me through your background."

What it's testing: whether you can summarize yourself coherently, and whether what you say matches the résumé open on their screen.

This is the same opener as "tell me about yourself," but the phone-screen version should be shorter — 60 to 90 seconds, present-past-future, ending on why this role. Don't narrate every job in order.

"I'm a data analyst at a mid-size logistics company, coming up on three years. Most of my work is the reporting layer our ops team uses daily — I rebuilt the on-time-delivery dashboard last year and it's now what the weekly leadership meeting runs on. Before that I spent two years in operations, which is why I'm decent at this: I know what the people reading the dashboard are trying to decide. I'm looking for a role with more modeling work, which is what caught my eye here."

The full breakdown of this answer lives in our guide on how to answer "tell me about yourself".

"Why are you looking to leave?"

What it's testing: flight risk and professionalism. Recruiters are listening for bitterness, and for a reason that this job would actually solve.

Point forward, not backward. Even if the real answer is a bad manager, frame it as what you're moving toward. Never criticize your current employer, teammates, or boss — it's the single fastest way to get quietly filed.

"I've gotten a lot out of the last three years, but the scope of the role has settled and the next step I want isn't really available there. I'm looking for a place where I can go deeper on the modeling side, and this team seems to be doing exactly that."

If you were laid off or your contract ended, just say so plainly — it's common, and hedging makes it sound worse than it is: "My role was eliminated in a restructuring in March along with most of my team, so I've been searching since."

"What are you looking for in your next role?"

What it's testing: whether the job they're filling is actually the job you want. A mismatch here saves everyone four rounds of interviews.

Answer with two or three concrete things that the posting genuinely offers. Vague answers ("growth, good culture") tell them nothing and read as if you'd take anything.

"Three things, really: more ownership of a problem end to end rather than ticket-by-ticket work, a team where I'd have people to learn from — I've been the only analyst for a while — and somewhere the analysis actually changes decisions. That's most of why I applied here specifically."

"What are your salary expectations?"

What it's testing: budget fit. Recruiters ask early because a mismatch is the most expensive thing to discover late.

You have three legitimate moves, in order of preference.

First, ask them for the range. This is normal, and in some places it's your right. California's Labor Code section 432.3 says an employer "upon reasonable request, shall provide the pay scale for a position to an applicant applying for employment." Elsewhere the number should already be in the posting: Washington's Equal Pay and Opportunities Act requires employers with 15 or more employees to put a wage scale or salary range in the job posting, and New York's pay transparency law requires businesses with four or more employees to list compensation ranges for advertised jobs. These rules vary by state and city, so check the ones that cover you — but "what range is budgeted for this role?" is a fair question everywhere.

"Before I give you a number — I want to make sure I'm anchored to the right scale. What range do you have budgeted for this position?"

Second, if they push back, give a researched range. Ohio State's Engineering Career Services advises quoting from the midpoint to the high end of your researched range — that avoids both underselling yourself and pricing yourself out. Use posted ranges on comparable roles in your metro as the data; transparency laws mean there are more of them than there used to be.

"Based on what I've seen for similar roles in this market, I'd be looking at somewhere in the 95 to 110 range, though I'd weigh the whole package. Does that line up with what you have?"

Third, you can decline to name a past salary. Some states bar the question outright — the same California statute says an employer "shall not ... seek salary history information." Wherever you are, you can redirect: "I'd rather anchor on the market rate for this role than what I happened to be paid before."

"What's your notice period? When could you start?"

What it's testing: logistics, and whether you'll leave your current employer gracefully — because that's how you'd leave them, too.

Two weeks is the US convention for most roles; longer is normal for senior positions and in many countries. Give a real date, not a shrug.

"I'd give my current team two weeks, and I have a couple of days of handover I'd want to do properly — so realistically about three weeks from an offer. If timing is tight I have some flexibility on the front end."

"Are you interviewing anywhere else?"

What it's testing: urgency and market validation. It's not a trap, and it's not an invitation to bluff.

Be honest and non-specific. Don't name companies, don't invent a fake offer — recruiters talk, timelines slip, and a fabricated deadline can collapse on you.

"I am — I'm in later rounds with a couple of other teams. Nothing at the offer stage yet. This one's the role I'm most interested in, so I'd want to keep the timelines roughly aligned if I can."

If you're not interviewing elsewhere, say something true and neutral: "I've been selective, so this is one of only a few processes I'm in right now."

"Are you authorized to work in the US? Will you need sponsorship?"

What it's testing: whether the company can legally hire you, and whether hiring you costs them a visa process.

Answer factually and briefly. Note what the question should not be: the EEOC's guidance on pre-employment inquiries and citizenship states that "most employers should not ask whether or not a job applicant is a United States citizen before making an offer of employment," and that verifying identity and work eligibility happens through the required form upon hire, not during screening. Asking whether you can work and whether you'll need sponsorship is routine; asking what passport you hold is a different question, and one that guidance says shouldn't come before an offer.

"Yes, I'm authorized to work in the US and I don't require sponsorship now or in the future."

If you will need sponsorship, say it early rather than late — finding out in round four wastes your time more than theirs.

"I'm authorized to work now on a student visa, and I would need sponsorship down the line. Happy to walk through the timeline if that's useful."

"Are you open to being in the office?"

What it's testing: a hard deal-breaker. Many postings say "hybrid" and mean three fixed days; some say "remote" and mean remote within one state.

Get specific before you commit, then answer specifically. A cheerful "I'm flexible!" that turns into "actually, no" in round three burns real goodwill.

"The posting said hybrid — can you tell me what that looks like in practice, days per week and which ones? For context, I'm about 40 minutes out, and two or three days on-site works well for me. Five would be a stretch."

"Why this company?"

What it's testing: whether you read anything before applying. On a phone screen this needs to be one crisp, true, specific reason — not the four-minute version.

"Two things. I've used your scheduling product at my current job, so I know the problem you're solving from the customer side. And the posting mentioned you're rebuilding the forecasting pipeline, which is the exact work I've been trying to move toward. That combination is rare."

"How much experience do you have with X?"

What it's testing: the literal must-have from the requisition. The recruiter often can't evaluate the skill — they're confirming a keyword and a rough number of years.

Lead with the direct answer, then one line of proof. Don't oversell something you've touched once, because the hiring manager will find out.

"About two and a half years of daily SQL — it's most of my job. Python I use weekly for cleanup and scripting rather than production work, so I'd call myself solid but not an engineer."

"What questions do you have for me?"

What it's testing: engagement — and never having questions is a real mark against you.

Ask recruiter-appropriate questions: process, timeline, team, what the manager is prioritizing. Save deep strategy questions for the hiring manager. Two or three is plenty on a short call.

• What does the rest of the process look like, and how many rounds?
• What's the timeline for a decision?
• What's the top thing the hiring manager wants this person to fix in the first six months?
• Is this a new role or a backfill?

Our questions to ask the interviewer guide has the deeper set for later rounds.

Logistics: it's a call you can't see

The University of Georgia's career center has the practical checklist, and it's worth following literally:

• Take it somewhere quiet. "Choose a quiet interview location that is free from distractions." A parked car counts. A coffee shop does not.
• Keep your notes and résumé up. "Keep your resume and notes nearby" — the recruiter is looking at your résumé, so you should be too. This is the one interview format where notes are free, so use them: your bullet points, your salary range, your two questions.
• Check your signal, and silence everything else. Reliable service or Wi-Fi, notifications off, phone charged.
• Sit up or stand. UGA notes it helps you "sound more confident and alert," and smiling genuinely changes your voice.
• Don't read a script. Reading aloud "is often noticeable." Bullet points, not sentences.
• Fix your voicemail before you start applying, in case you miss the call.

What happens after

A recruiter screen usually ends with them describing next steps. If they don't, ask. Send a short thank-you note the same day, then start preparing differently — the next conversation is the substantive one, with real behavioral questions and a hiring manager who can actually evaluate you. That's what our guide to common interview questions and how to answer them is for.

Everything above is easier to deliver if you've said it out loud once. Salary answers in particular fall apart in the mouth even when they're perfect on paper. Run the four that matter most — background, why you're looking, your number, and your start date — until they sound like sentences instead of a script.

Sources

• University of Houston, Rockwell Career Center — What's a Phone Screen?
• University of San Francisco Career Services — Interview Types
• University of Georgia Career Center — Phone and Video Interviews
• The Ohio State University, Engineering Career Services — Answering the "Desired Salary" Question
• California Legislative Information — Labor Code Section 432.3
• Washington State Department of Labor & Industries — Equal Pay and Opportunities Act
• New York State Department of Labor — Pay Transparency
• U.S. Equal Employment Opportunity Commission — Pre-Employment Inquiries and Citizenship