The phone-screen questions bank: what they ask and what a working answer looks like
Most phone screens use a small repeating set of questions. Here are the eight that show up most often, with what recruiters are listening for in each.

On this page
Phone screens look like open-ended conversations. They aren't. The recruiter is moving through a small set of questions, in roughly the same order, with a roughly fixed set of things they're listening for. Knowing the questions and what they're actually evaluating turns a high-variance call into a much more predictable one.
This post is the question bank — what they ask, what they're listening for, and what a working answer sounds like.
The eight questions you'll actually hear
Eight phone-screen questions you'll actually hear
Question bankWhat they're listening for: can you describe your work in three sentences? They want a working summary of role + scope + one specific outcome, in about 60-90 seconds. The single most common phone-screen question.
Listening for: do you have a real direction, or are you just looking for a job? Fit between your direction and their role. 'Looking for more scope in X, with a team like Y' beats 'open to anything that's a good fit.'
Listening for: are you running toward or away? Frame the answer toward what you want next, not what you didn't like. Don't bad-mouth past employers — it's the single fastest way to fail this question.
Listening for: are you in their band? Give a range that starts at the floor of what you'd accept. 'I'm targeting $X-Y, depending on the full package' is a working answer; 'open to discussion' is not.
Listening for: visa sponsorship implications. Direct yes/no plus relevant detail. Federal roles also check citizenship. International candidates: address authorization up front, not as a side note.
Listening for: are you actively interviewing, considering offers, or browsing? Honesty helps. 'I have two other processes in late stages, expect to decide within 2-3 weeks' positions you better than vague answers.
Listening for: did you do any homework? Even five minutes on the website beats nothing. A specific recent product, news item, or company milestone is enough. 'Not much, I haven't looked into it' is a phone-screen killer.
Listening for: engagement and seriousness. Two role-specific questions and one process question is the right number. 'No, I think you covered everything' is a missed opportunity at minimum.
These eight questions cover about 90% of what comes up in any 25-30 minute phone screen. The order varies; the substance doesn't.
1. Walk me through your last role. The single most common phone-screen opener. The recruiter is testing whether you can describe your work in three sentences and whether the work you describe matches what's on your resume. Aim for 60-90 seconds: scope, what you owned, one specific outcome. For the deeper structure, see tell-me-about-yourself-90-seconds.
2. What are you looking for in your next role? They're checking direction. A real direction — "more scope," "deeper technical work," "switch to a smaller team" — beats "open to anything." Tie the direction to their specific role.
3. Why are you leaving / why did you leave? They're listening for whether you're running toward or away. The right framing is forward: "I'm looking for the next step, and this role is closer to that than my current one." Avoid criticism of past employers — even justified criticism reads as a yellow flag in this format.
4. What are your salary expectations? They have a band; they want to confirm you're in it. Give a real range starting at the floor of what you'd accept. "$X to $Y, depending on the package" is fine. "Open to discussion" wastes their time and reads evasive. For the deeper play, see salary-band-asking-question-early.
5. Are you authorized to work in [country]? Direct yes/no, plus relevant detail. If you require sponsorship, say so explicitly. International candidates: see international-experience-translating-for-us. Federal and security-clearance roles will also ask about citizenship.
6. What's your timeline? Are you actively interviewing or just browsing? Honest answer helps. "I have two other processes in late stages, expect to decide in 2-3 weeks" creates productive urgency. "Just kicking the tires" tells them not to invest much in your candidacy.
7. What do you know about us? They're checking whether you did the minimum prep. Five minutes on the website is enough to surface one specific thing — a recent product, a public talk, a known initiative. "Not much, haven't looked into it" is a near-instant phone-screen failure.
8. Do you have any questions for me? This is part of the evaluation, not the wrap-up. Two questions about the role and one about process is the right number. Engagement matters here.
For the wider phone-screen framework, see phone-screen-what-recruiters-evaluate.
Working answers vs. ones that flatten the call
Working answers vs. answers that flatten the call
Side by side- Specific, 60-90 seconds, one example per question
- Numbers when honest, named systems when relevant
- Forward-looking on the 'why leaving' question
- Real salary range with a floor, not 'flexible'
- Two role-questions and one process-question at the end
- Long meandering answers without a clear point
- Vague descriptions ('I worked on various things')
- Negative about past employers
- 'Open to whatever pays well' on the comp question
- 'No questions, thanks' when they ask if you have any
The pattern that distinguishes a working answer from a flat one is specificity. A vague answer in a phone screen doesn't get you rejected outright; it just doesn't help the recruiter make the case for you to the hiring manager. The candidates who advance are the ones the recruiter can describe in specific terms ten minutes after the call.
A specific example: "I worked on data infrastructure" vs. "I built the ingestion pipeline for our event data — 2B events/day, replaced a legacy Kafka setup, took us from 4-hour latency to under 5 minutes." The second sentence tells the recruiter what to write in their notes and what to forward to the hiring manager. The first doesn't.
The same applies to most phone-screen questions. Specific answers translate forward into the next round; vague ones don't.
How the time actually breaks down
What a typical phone screen actually covers
Time distributionOf the call is spent on your background — recent role, projects, decisions, outcomes.
Of the call covers logistics — comp, timeline, authorization, location, notice period.
Of the call is reserved for your questions. Treat this as part of the evaluation.
Knowing where the time goes in a phone screen helps you calibrate. About 60% of the call is on your background — recent role, projects, decisions. About 25% covers logistics — comp, timeline, authorization, notice period. About 15% is for your questions.
This breakdown has a practical implication: the background section is where most candidates make or break the call, but most candidates over-prep on the logistics. The right balance is to know your numbers (comp range, notice period, timeline) cold so they take 60 seconds total, leaving more time for the substantive background discussion.
The questions-at-the-end window is also under-used. Most candidates either ask one polite question or none. Two well-aimed questions about the role plus one about process puts you in the top quartile of candidates by engagement.
The follow-up patterns
After the phone screen, three things tend to happen:
- The recruiter advances you. They explicitly say "let me set up the next round" or "I'll send over scheduling." Good signal.
- They want time to consult internally. "Let me sync with the team and circle back this week." Neutral signal — could go either way. Follow up in 5-7 days if you haven't heard.
- They politely close. "We'll be in touch if there's a fit." Usually a soft no. Sometimes a delayed yes if the team revisits later, but plan as if it's not advancing.
If the call goes well and the recruiter is engaged, they'll typically share the rest of the interview process before you ask. If they don't volunteer it, asking is appropriate: "What does the rest of the process look like, and what's the typical timeline?"
A specific recoverable mistake
If you blank or fumble a question, the recovery move is simple: name it briefly and move on. "Let me restart that — I was overcomplicating it. Here's the short version: [actual answer]." Recruiters expect candidates to be slightly off-balance and recover; what they don't want is candidates who don't notice they're rambling.
Don't apologize repeatedly. Don't make a long meta-comment about the question. One sentence of recovery, then the real answer.
What this isn't
A few clarifications:
- It's not the only kind of screen. Some companies do technical phone screens (different mechanics) or skip the recruiter call entirely.
- It's not a script. Memorizing answers verbatim produces the rehearsed-cadence problem covered in other posts.
- It's not the place to negotiate. Anchoring comp is fine; bargaining is premature.
The short version: eight questions cover most of any phone screen. Walk through last role, what you want, why leaving, comp, authorization, timeline, what you know about them, your questions. Specific beats vague. Forward-looking beats backward-looking. Have three questions ready. 30 minutes of prep clears most of it.
More to read
6 min readPre-interview research on the company: the 90-minute version that actually matters
Most candidates either over-research the company (and run out of energy) or under-research (and sound generic). Here's the 90-minute version that hits what interviewers actually notice.
interviewsresearch
5 min readAI mock interview tools: which actually help and which are theater
AI mock-interview platforms promise practice at scale. A few are useful. Most are distraction. Here's a comparison of what actually helps.
interviewsai-tools
5 min readCoding interview prep without burning out: how to not over-prep
Most coding-interview prep advice points to 500 LeetCode problems. The realistic floor is much lower — here's what actually moves your pass rate.
interviewscoding
5 min readQuestions to ask the interviewer: a working bank, sorted by interview stage
'Do you have any questions for us?' is graded. Here's a bank of questions that work, sorted by who you're talking to and when in the loop you are.
interviewsquestions