Phone Screen Questions: 18 Answers Recruiters Score You On

Last updated: September 2026

Quick Answer

A phone screen is a 15 to 25 minute call, most commonly reported at around 20 minutes, in which a recruiter checks four things: that you can describe your work clearly, that your salary expectation and notice period fit the role, that your motivation is specific, and that nothing on your resume falls apart under one follow-up question. Fewer than ten questions get asked. Rehearse them out loud in OphyAI Interview Practice, because the phone screen rewards brevity and almost nothing else.

#	Question	What the recruiter is really checking
1	Tell me about yourself	Can you be structured and finish in two minutes
2	Why are you looking to leave?	Is the reason stable, or will it recur here
3	Why this company?	Did you read anything, or are you applying in bulk
4	Walk me through this role on your resume	Do the claims survive a follow-up
5	What are your salary expectations?	Are you inside the band before anyone spends time
6	What is your notice period or availability?	Does your timeline match their urgency
7	Are you authorised to work here?	A hard eligibility gate
8	Where else are you in a process?	Urgency, and how to sequence you
9	What are you looking for in your next role?	Will this job actually satisfy you
10	Do you have any questions for me?	Interest, and how you use limited time

This page is the question-and-answer companion to our phone screening interview preparation guide, which covers the format, setup and follow-up, and to our 15 phone interview tips. Read those for the mechanics. Read this one for the words.

What a Phone Screen Is Not

It is not a shortened version of the interview. Recruiter guidance published for hiring teams recommends five to eight questions in the call, split between general questions such as motivation, compensation and timeline, a small number of role-specific questions, and time for your own. That means most of the technical evaluation you prepared for is not happening yet.

The practical consequence: on a phone screen, a complete answer is a short answer. Candidates lose here not by being wrong but by being long. If your answer to question two is four minutes, the recruiter has lost a fifth of the call and has learned less than they would have in forty seconds.

The second consequence is that the recruiter is writing notes that follow you. The hiring manager will read a summary, not a transcript. Say the two or three things you most want written down, early, in plain language.

The Questions, With Sample Answers

1. “Tell me about yourself.”

Why they ask it: To hear whether you can impose structure on your own history without help. It is also a warm-up that tells the recruiter how long your answers will run.

Sample answer: “I’m a backend engineer, six years in, mostly on payments systems. I started at a small logistics company building internal tooling, then moved to a fintech where I’ve spent the last four years on the ledger and settlement services. The thing I’ve gotten good at is making systems behave correctly when something downstream fails, which is most of what payments engineering actually is. I’m looking now because I want to work on that problem at a bigger scale, and this role sits directly on it.”

What weak answers look like: Starting at university. Reciting the resume in chronological order. Running past two minutes. Ending without saying why you are on this call.

2. “Why are you looking to leave your current role?”

Why they ask it: To find out whether the reason you are leaving would also be true at their company. A recruiter who thinks it would will not advance you.

Sample answer: “I’ve been at my current company four years and I’ve done the interesting version of this job. The team’s roadmap for next year is maintenance and cost reduction, which is necessary work but not what I want to spend two years on. I’d rather move now, while I can leave things in good shape, than wait until I’m frustrated. What I’m looking for is a role where the system is still being built rather than being wound down.”

What weak answers look like: Criticising a manager or a colleague. Vagueness that reads as concealment. Anything that could plausibly describe the role you are applying for.

3. “Why our company?”

Why they ask it: To separate targeted applicants from bulk ones. It costs the recruiter nothing to ask and it is the single fastest filter they have.

Sample answer: “Two reasons. First, the specific problem: you’re building the reconciliation layer in-house rather than buying it, which I read in your engineering blog post in June, and that’s the exact work I’ve spent three years on. Second, the stage. You’re past the point where everything is a rewrite but not so large that a single engineer can’t affect the design. That combination is narrower than it sounds, and it’s why this is the application I care most about right now.”

What weak answers look like: Praise for the brand, the mission statement, or the fact that the company is well known. Anything you could say to five employers by swapping the name.

4. “Walk me through this role on your resume.”

Why they ask it: To check that the claims are yours. The recruiter may not understand the technical detail, but they can hear the difference between someone describing their own work and someone describing their team’s.

Sample answer: “That was two years on the payouts team, four engineers. I owned the retry and reconciliation path. When I joined, a failed payout needed a manual ticket, which took about two days. I rebuilt it around idempotent retries and an automated reconciliation job, and manual intervention dropped to a handful of cases a month. The part I’d do differently is that I built the reconciliation report before the alerting, so for the first two months we found problems after our finance team did rather than before.”

What weak answers look like: “We” throughout with no “I” anywhere. Numbers with no method behind them. An inability to name what went wrong.

5. “What are your salary expectations?”

Why they ask it: Purely practical. If you are outside the band, everybody’s time is better spent finding that out in minute nine than in week five. In several US states and cities the recruiter must also disclose the range on request, so this is often a two-way question.

Sample answer: “Based on what I’ve seen for this scope in this market, I’d be looking in the range of $X to $Y in base, and I’m flexible on the mix between base and bonus. Before I anchor too hard, can you tell me the band you have approved for the role? I’d rather work out quickly whether we’re in the same neighbourhood.”

What weak answers look like: Refusing to engage at all. Naming a single number with no range. Giving a figure you have not sanity-checked against published data for that market and level. Recruiting guidance from Robert Half and others is consistent that a researched range plus a request for their band is the strongest posture.

6. “What is your notice period, and when could you start?”

Why they ask it: The recruiter is matching your timeline against the urgency of the requisition. If they need someone in three weeks and your notice is three months, they may run a parallel candidate.

Sample answer: “My notice is one month, so realistically four to five weeks from signing, and I’d want a few days between roles rather than starting the following Monday. If there’s a business reason to move faster I can ask about flexibility, but I’d rather commit to a date I can actually meet.”

What weak answers look like: Promising an immediate start you cannot deliver. Being vague when you know the answer. Forgetting to account for annual leave already booked, which then surfaces awkwardly at offer stage.

7. “Are you legally authorised to work in this country, and will you need sponsorship now or in the future?”

Why they ask it: It is a hard eligibility gate on many requisitions, and the recruiter has to record the answer.

Sample answer: “Yes, I’m authorised to work here without restriction. I won’t need sponsorship now or in the future.” Or, if the answer is different: “I’m authorised to work here on a visa valid until March 2028, and I would need sponsorship to transfer it. I’ve been through the process once and can talk you through the timeline if it’s useful.”

What weak answers look like: Hedging. Answering a different question. Hoping it will not come up later. It will, and a surprise here at offer stage costs you the offer.

8. “Where else are you in the process?”

Why they ask it: To sequence you. If you have a final round elsewhere next week, a good recruiter compresses their loop rather than losing you.

Sample answer: “I’m at final stage with one other company and early stage with two more. I’m not trying to create pressure with that, but the final-stage process is likely to conclude in about two weeks, so if that matters for how you schedule things, it’s worth knowing.”

What weak answers look like: Inventing competing offers. Naming companies and salary figures you cannot substantiate. Saying “nothing else” when you are actively interviewing, which removes the recruiter’s reason to move quickly.

9. “What are you looking for in your next role?”

Why they ask it: To check that what you want and what the job is are the same thing. A candidate who wants management and is applying to a senior individual contributor role is a future decline.

Sample answer: “Three things, in order. Ownership of a system end to end rather than a slice of one. A team where code review is a real conversation, because that’s where I’ve learned most. And a company that’s still changing its mind about the product, because I find maintenance work draining. Salary matters, but it’s fourth on that list, not first.”

What weak answers look like: A list of benefits. “Growth” and “challenge” with nothing concrete attached. Requirements that contradict the job description you were sent.

10. “Can you tell me about a recent project you’re proud of?”

Why they ask it: To get one usable paragraph for the hiring manager. This is the answer most likely to be quoted verbatim in the recruiter’s notes.

Sample answer: “Last quarter I led the migration of our notification service off a queue that was dropping messages under load. The tricky part wasn’t the new queue, it was doing it without a maintenance window, so we dual-wrote for two weeks and reconciled the two streams before cutting over. We went from about forty dropped notifications a week to zero, and the cutover was invisible to customers. I’m proud of it because the boring part, the reconciliation, is what made it safe.”

What weak answers look like: A project with no result. A result with no mechanism. A story so long the recruiter cannot summarise it in one line.

11. “What do you know about what we do?”

Why they ask it: A lighter version of “why us”, aimed at whether you did fifteen minutes of homework.

Sample answer: “You’re a B2B payments platform, mostly mid-market, and the thing that seems to differentiate you is that you handle the compliance side rather than pushing it back onto the customer. I saw you launched in two new markets this year, which I’d guess is what’s driving hiring on this team. What I don’t know is how the engineering organisation is split, and I’d like to.”

What weak answers look like: A recital of the homepage tagline. Confidently describing the wrong business model. Saying you did not have time to look.

12. “What is your current or most recent title, and who do you report to?”

Why they ask it: Levelling. Titles are inconsistent between companies, so the recruiter is triangulating your actual scope.

Sample answer: “My title is Senior Engineer, and I report to the engineering manager for the payments group. In practice the scope is a bit wider than the title suggests: I’m the technical owner for two services and I’m the person who reviews design docs for the team. Happy to talk about what level that maps to on your ladder, because titles vary a lot.”

What weak answers look like: Inflating the title. Being defensive about a title that undersells you rather than describing the scope plainly.

13. “Are you comfortable with the working pattern for this role?”

Why they ask it: Hybrid and on-site requirements are now the most common late-stage deal-breaker, so recruiters front-load them.

Sample answer: “The posting says three days on site in the city centre. That works for me, I’m forty minutes away and I’d rather have the office days than not. If the days are fixed, I’d want to know which ones, because I have a standing commitment on Fridays that I can move if it’s needed but would rather plan around.”

What weak answers look like: Saying yes to a pattern you intend to renegotiate later. Asking about remote work in a way that reads as an attempt to opt out of the stated requirement.

14. “Tell me about a time you had to deal with a difficult situation at work.”

Why they ask it: Some recruiters carry one behavioural question. It is a preview, not a full evaluation, so the bar is coherence rather than depth.

Sample answer: “We had a release that corrupted a subset of customer records. I found it, and the honest situation was that my change caused it. I stopped the rollout, told the on-call lead and our support manager within about ten minutes, and we restored the affected records from the previous night’s snapshot with about ninety minutes of data loss for eleven customers. Afterwards I added the validation step that would have caught it. The part I got right was telling people fast; the part I got wrong was shipping without that check.”

What weak answers look like: A difficulty that was somebody else’s fault. A story longer than ninety seconds. No outcome. For the full treatment of these, see our behavioral interview questions and answers.

15. “What is your visa, relocation or travel situation?”

Why they ask it: Logistics that affect whether the role is viable at all, especially for roles with client sites, security clearance requirements or multi-country teams.

Sample answer: “I’m based in Manchester and I’d be relocating to London for this role. I’ve budgeted for that and I can be in place within six weeks of an offer. On travel, the posting mentions occasional client visits, which is fine for me at roughly monthly. Anything much more than that I’d want to talk through.”

What weak answers look like: Agreeing to relocate with no intention of doing so. Discovering the travel requirement at offer stage. Not asking who pays for relocation.

16. “What would you want to be doing in two or three years?”

Why they ask it: Retention. The recruiter is checking that the obvious next step from this role is a step you would want.

Sample answer: “Technically deeper rather than broader. In two years I’d want to be the person the team routes the hardest design questions to, and to have mentored one or two engineers properly rather than casually. I’m not chasing a management track. If that’s the direction this role naturally leads, that suits me, and if it leads to management instead, I’d rather know now.”

What weak answers look like: Ambitions the role cannot support. “Your job” as a joke. Refusing to answer because you do not know.

17. “Is there anything on your resume you’d like to explain?”

Why they ask it: An invitation. The recruiter has already spotted the gap, the six-month role or the career change and is giving you the chance to handle it before the hiring manager sees it cold.

Sample answer: “Yes, the eight-month gap in 2024. I was caring for a family member full time. I kept up with the field during it and did a contract project towards the end to get back into rhythm. It’s settled now and there’s no ongoing constraint on my availability.”

What weak answers look like: Declining the invitation and hoping. Over-explaining. Apologising at length for something that needs one sentence. See our guide on how to explain employment gaps.

18. “Do you have any questions for me?”

Why they ask it: Interest, and calibration. A recruiter can answer process, team shape, timeline and compensation questions well; they usually cannot answer deep technical ones, so asking those wastes your slot.

Sample answer: “Three. What does the rest of the process look like and how many stages? What is the team’s current biggest problem, as the hiring manager describes it? And is there anything in my background that you think the hiring manager will want more detail on, so I can prepare it?”

What weak answers look like: No questions. Questions answered in the job posting. Benefits and holiday allowance as your only question on the first call. For a longer list, see our guide to questions to ask the interviewer.

How to Practice These

Say them out loud, on a timer, in the order a recruiter would ask them. Almost every phone screen failure is a timing failure, and you cannot hear your own timing when you rehearse silently.

Run the whole call as a voice mock in OphyAI Interview Practice, which asks follow-up questions and gives you a transcript plus per-answer feedback, so you can see which of your answers doubled in length under pressure. Aim for 90 seconds on the opening question, 45 on the logistics questions, and never more than two minutes on anything.

If your live screens are on Zoom, Microsoft Teams or Google Meet rather than a phone line, Interview Copilot can give you live structure prompts and a running transcript during the call. Check the employer’s policy first, since some employers prohibit candidate use of AI tools during interviews, and note that a recruiter screen is mostly facts about you rather than problems to solve, so the value is in staying concise rather than in generating content. Start practicing →

Frequently Asked Questions

How long is a typical phone screen?

Recruiter-facing guidance and candidate reports converge on 15 to 25 minutes, with around 20 to 22 minutes the most commonly cited figure. Some hiring manager screens run to 30 or 45 minutes, but the initial recruiter call is deliberately short because its job is to filter rather than to evaluate. Plan your answers so the whole set fits inside twenty minutes with time left for your own questions at the end.

How many questions will a recruiter ask on a phone screen?

Published guidance for recruiters recommends five to eight questions: two or three general ones covering motivation, compensation and timeline, two or three role-specific ones, and space for the candidate’s questions. In practice that means you will be asked a small subset of the eighteen on this page. Prepare all of them anyway, because you cannot predict which subset, and preparing the answer is what makes it short.

Should I give a salary number on the phone screen?

Give a researched range rather than refusing or naming a single figure, then ask what band the role is approved at. Guidance from Robert Half and similar career advisers is consistent on this: a range based on published market data for your level and location protects you from anchoring too low while still letting the recruiter check fit. In several US jurisdictions the employer must disclose the range on request, so ask.

What is the difference between a phone screen and a phone interview?

A phone screen is a short filtering call run by a recruiter, focused on logistics, motivation and resume verification. A phone interview is a longer evaluative conversation, usually with the hiring manager or a team member, that assesses your actual capability with behavioural or technical questions. Many processes have both, back to back in the same week. Our phone screening interview preparation guide covers the three common screen types in detail.

How do I answer “tell me about yourself” on a phone screen?

Give a present-past-future structure in under two minutes: what you do now and at what scope, the one or two moves that got you there and what you got good at, and why this specific role is the next step. Do not start at university and do not narrate your resume in order. End on the connection to this job, because that sentence is what the recruiter writes down.

What questions should I ask the recruiter?

Ask about process and shape, not deep technical detail, because that is what a recruiter can answer accurately. Good ones: how many stages remain and what each involves; what the hiring manager says the team’s biggest current problem is; whether the role is a new headcount or a backfill; what the timeline is; and whether anything in your background needs extra explanation for the hiring manager. That last one frequently produces useful, actionable feedback.

Do phone screens ever include technical questions?

Sometimes, but lightly. A recruiter screen may include two or three factual questions supplied by the hiring manager, such as which languages or tools you have used at production scale, or how many years you have worked with a specific technology. Deep technical evaluation almost always happens in a later stage. If the invitation says “technical screen” rather than “recruiter screen”, expect a real evaluation and prepare accordingly.

Can I use notes during a phone screen?

Yes, and you should. A phone screen is one of the few interview stages where notes are entirely normal and invisible, and recruiters expect you to have the job description in front of you. Keep them to a single page: your two-minute opening, your salary range, your notice period, three facts about the company and your three questions. Reading a script aloud is audible, so use prompts rather than sentences.

Related Guides

• Wells Fargo interview guide: an on-demand recorded screen instead of a live recruiter call
• American Express interview guide: a recorded HireVue round used as the first real gate
• Booz Allen Hamilton interview guide: a 30-minute recruiter screen that decides whether the whole loop happens
• Visa interview guide: a published screening stage covering authorisation, compensation and values alignment
• Revolut screening call questions: a 20-30 minute recruiter round with a specificity filter on “why Revolut”
• Fidelity interview guide: a compact loop where the screen carries more weight than usual
• Accenture interview guide: a multi-stage process that begins with a short eligibility-focused call
• Interview process steps explained: where the screen sits in the full hiring sequence

Sources and verification notes

Sources checked September 2026. Direct first-party fetches were blocked by this environment’s network policy, so third-party material was consulted through search summaries and is labelled below by origin. Sample answers on this page are illustrative compositions written to demonstrate structure, not transcripts of real interviews.

• Robert Half, how to answer “what are your salary expectations”: staffing firm guidance on giving a researched range rather than a single figure.
• Pin, phone screening questions and templates: recruiter-facing guidance on the five-to-eight question structure and the mix of general and role-specific questions.
• Hiration, the recruiter phone screen and what it filters for: reported screen length, question set and the notice-period filter.
• Journey Search, a complete guide to screening interviews in 2026: reported screen durations and the distinction between recruiter and hiring manager screens.
• Perfect, 30 pre-screening interview questions to ask: recruiter-side question bank used to check which questions are actually standard.