Skip to main content

Common Phone Interview Questions List (With Answers) for 2026

Phone interview questions in 2026 split across five call types: the recruiter screen (resume, salary, fit), the hiring-manager screen (projects, team-fit, narrative), the behavioral block (STAR without body language), the phone technical round (code without screen share), and the closing block (your questions, next steps). Below: 30+ real questions across all five, the voice-only delivery tactics that decide who advances, and the 24-hour prep checklist.

By , Founder, InterviewChamp.AI · Last updated

37 min read

TL;DR: The most common phone interview questions depend on who's calling: a recruiter checks fit-on-paper, salary, and availability, a hiring manager digs into one project and team fit, and an engineer has you talk through code out loud. Most calls mix two or three of these blocks in 30-60 minutes, and since your voice carries every signal, delivery is roughly half the score.

Phone screens feel random until you notice they're not. Almost every call comes from one of three people: a recruiter, the hiring manager, or a working engineer. Each one asks a predictable set of questions, and each set needs a different kind of answer.

This page gives you the full list first, then the questions grouped by who's asking, with answer guidance for each. After that come the questions you should ask at the end, the phone-specific delivery tactics, a 5-step prep routine, and the mistakes that sink new grads.

The common phone interview questions list at a glance#

Here's the short version. Each question is covered in detail further down.

QuestionWho usually asks itWhat they're checking
Walk me through your resumeRecruiterCan you tell your story in 90 seconds
What's your salary expectation?RecruiterWhether you fit the budget
Tell me about your interest in this roleRecruiterThat you didn't apply blind
Are you open to relocation?RecruiterLocation match for the headcount
When are you available to start?RecruiterTiming and seriousness
How did you hear about this job?RecruiterYour source and level of interest
Tell me about a project you're most proud ofHiring managerDepth and reflection
What's the biggest impact you've had?Hiring managerA real, measurable outcome
Why this company specifically?Hiring managerResearch, not enthusiasm
What kind of role and team are you looking for?Hiring managerA coherent target
Tell me about a time you handled a conflictHiring manager or behavioral roundComposure with people
Tell me about a time you failedHiring manager or behavioral roundSelf-awareness
Have you worked with our tech stack?Hiring manager or engineerHonest skill match
Two-sum, reverse a linked list, LRU cacheEngineerReasoning out loud, complexity sense
What is your greatest weakness?Recruiter or hiring managerHonesty and growth
Do you have any questions for me?EveryonePreparation and follow-through

The sections below cover every one of these with answer structures and examples.

What phone interview questions test in 2026#

Phone interview questions in 2026 check five different things, and which one you get depends on who picked up the call. The recruiter looks at fit-on-paper plus availability. The hiring manager wants project depth and team fit. The behavioral block tests composure and judgment with no body language to lean on. A phone technical screen tests how you structure your reasoning when your voice is the only tool, and the closing block shows whether you understand the role well enough to ask good questions and follow up cleanly.

Most candidates prep the questions and ignore the medium. That's a mistake, because the medium is half the score. Picture a strong answer from a noisy room, in a flat voice, still rambling at second 92. Now picture a slightly weaker answer from a quiet room, with energy in the voice, that wraps at second 65. The second one wins. On a call, your voice does the job the camera would do in person. If you've only prepped for in-person interviews, phone delivery is its own skill, and most of that gap can be fixed in the 24 hours before the call.

Three things shifted in the 2026 hiring market:

  • More first-round screens are phone-only, with no video. Recruiters are running 8-12 screens per week, and Zoom fatigue is real.
  • Hiring managers now use the phone round for the deep project dive that used to happen onsite, so the questions go further.
  • The closing block carries more weight, because hiring managers are openly grading whether you'll do the follow-up work after you hang up.

So how serious is a phone interview? Treat it as a real round. It isn't a formality, and the phone rounds decide whether you advance at all.

Honest take: the gap between "I bombed the phone screen" and "I crushed it" rarely comes down to content. It comes down to delivery. Say the same answer from a quiet room, with deliberate pacing and one "let me think about that for a second," and it reads completely differently than the rushed version from a noisy kitchen. The fix is reps under realistic timing, out loud, until the answer comes out in your own voice rather than read off a page. You can run a live practice phone screen to hear how your pacing and structure land before a recruiter does.

The person I picture when I write this is Jordan Patel. He's 23, a May 2025 CS grad with 487 applications, 14 interviews, 0 offers, and $1,847 in checking. His Meta phone screen is the cleanest example of the delivery gap I know. He took the call from his bedroom at his parents' house in suburban NJ. Somebody three doors down ran lawn equipment for the first 8 minutes, and for the next 20 he talked too fast because of nerves. He bombed it. His text afterward: "the engineer was nice tho." His content was fine. The room and the pacing sank him.

How phone interviews differ from video and in-person interviews#

A phone call strips away three signals you rely on in person: facial expression, body language, and visual rapport. It also adds two constraints. Everything has to travel through your voice, and you can't see what the interviewer is doing on their end. Good phone candidates make up for this by turning up the signals that survive and by being comfortable with the silences a call creates.

What the interviewer picks upPhoneVideoIn person
Your voice and pacingYes, and it's almost everythingYesYes
Facial expressionNoYesYes
Body languageNoPartlyYes
Eye contact and visual rapportNoPartlyYes
A thinking pauseReads as composureCan read as a freezeUsually fine

Facial expression. You can't smile through an awkward moment, and you can't read their reactions either. So say your structure out loud ("let me give you the situation, then what I did, then the outcome"). Then listen hard for vocal cues: laughter, a "mhm," or the small inhale that means they're about to cut in.

Body language. Nobody sees your gestures, but standing up still helps because it changes how you sound. Sitting hunched squeezes your diaphragm and flattens your voice. Stand for the answering blocks. Walking around while you think is fine too, as long as you stay close enough to the headset that your voice doesn't fade.

Visual rapport. There's no eye contact, so you build chemistry with vocal energy and with clear signs that you're listening. Use the interviewer's name now and then. Refer back to something they said. Acknowledge the question before you start answering it.

The phone also changes two structural things. Silences are normal and run longer than in person, so don't rush to fill every 2-second pause. And notes are normal on a call. A pen and paper, a printed resume, a one-page sheet of your stories. This advantage is real and most people don't use it. They prep their answers and skip the cheat sheet, even though building it is the single highest-ROI 30 minutes of phone-interview prep.

The 5 categories of phone interview questions#

Every phone interview in 2026 pulls from five categories. Knowing which one you're in is half the work, since each has its own answer structure.

First, a quick vocabulary check, because people mix these up. A recruiter screen is a 20-30 minute filtering call with a non-technical recruiter that checks fit-on-paper, salary, and availability. A hiring-manager phone screen is the deeper round with the person who'd manage you, and it tests project depth and team fit. A phone technical screen is a 45-60 minute coding round done by voice, sometimes with a shared editor and sometimes audio-only. It's the same medium with three different bars.

Recruiter screen. Resume walk-through, salary, availability, role fit. 20-30 minutes. This is the gatekeeper, and it's predictable.

Hiring-manager phone screen. Project depth, team fit, technical narrative. 30-45 minutes. This is the decision-maker, who goes deeper than the recruiter but rarely into live coding.

Phone-specific behavioral. STAR-format questions about past situations, with body-language signals stripped out. 30-45 minutes when behavioral is the main block, though it's often tucked inside the hiring-manager screen.

Phone technical screen. Coding or systems questions, either with a shared online editor or audio-only. 45-60 minutes, usually with a working engineer. It tests reasoning structure and complexity intuition more than syntax.

Closing the phone interview. Your questions, next steps, and follow-up confirmation. This is the last 5-10 minutes of every call. Most candidates throw it away, and hiring managers grade it more than candidates realize.

One 45-minute screen often covers 2-3 of these categories. A recruiter call might end with two behavioral questions, and a hiring-manager call might open with a resume walk-through. Once you know the categories, you can shift your delivery in real time. If you're searching by the usual labels (behavioral, technical, HR), the FAQ near the end maps them onto these blocks.

Recruiter-screen phone interview questions (6 Q)#

At most companies the recruiter is the first person you talk to. They usually don't have deep technical knowledge of the role. Their job is to filter: fit-on-paper, salary alignment, location, availability, and a basic check that you won't be a culture catastrophe. The questions are predictable, and if you get them down cold, you move on.

Q1

Walk me through your resume.

Show sample answerSay yours out loud first, then check.

This opens almost every recruiter screen. Keep it to 90 seconds total. A strong structure goes like this: your name, your education in one line, your current situation in one line, 2-3 highlights with one specific accomplishment each, and then what you're looking for now. The weak version reads the resume from top to bottom, in order, with nothing cut. The recruiter already has your resume. What they want is the story.

Sample (60-90 seconds): "I'm a CS grad from State University, finished May 2025. Internship at a fintech startup in summer 2024 where I built backend services for their payments pipeline in Python and Postgres, shipped one feature now processing 40,000 transactions a day. Since graduating I've been doing freelance backend work and grinding interviews. I'm specifically looking for backend or platform roles at mid-stage startups in the fintech or developer-tools space, which is why your role caught my attention."

That's ninety seconds, specific and crisp.

Q2

What's your salary expectation for this role?

Show sample answerSay yours out loud first, then check.

Every recruiter asks this, and most candidates fumble it. You have three options, from strongest to weakest.

  • Strong: give a range where the floor is your minimum acceptable number and the ceiling sits 15-20% above it. "I'm looking for $85,000 to $100,000 base, plus standard equity and benefits." That anchors the negotiation and shows you did your research.
  • Acceptable: turn it into a question. "I'd love to learn more about the scope of the role before discussing comp specifically. What's the budgeted range for this position?" Recruiters in 2026 usually share it when you ask directly.
  • Weak: one number, especially a low one. You can't negotiate up from "I'd be happy with $75,000." You can negotiate down from "I'm targeting $85,000 to $100,000."
Q3

Tell me about your interest in this role.

Show sample answerSay yours out loud first, then check.

The recruiter wants proof that you didn't fire off 200 applications blind. Connect three things: a detail from the job description, a detail about the company (from their site or recent news), and the part of your background that matches both. Sixty seconds is plenty. This is also where "How did you hear about this job?" and "Why are you looking?" tend to get folded in, so have a one-line answer ready for each.

Example: "I'm interested specifically because the JD mentioned the team owns the payments infrastructure end-to-end, and I built a small payments pipeline during my internship. I also noticed your company just raised a Series B and is expanding the platform team, which lines up with where I'm trying to grow."

Specifics beat enthusiasm every single time.

Q4

Where are you located and are you open to relocation?

Show sample answerSay yours out loud first, then check.

This is a logistics filter, so just answer honestly. If you'd move, name the cities. If you wouldn't, say that without apologizing. Recruiters value a clear answer more than a flexible one here, because they're matching headcount budgets to where candidates live.

"I'm based in NJ. I'm open to relocation for the right role to NYC, Austin, or Seattle, ideally with a relocation package."

Q5

When are you available to start?

Show sample answerSay yours out loud first, then check.

Another logistics filter. If you can start in 2 weeks, say 2 weeks. If you're in school until June, say June. If you have a job and need to give notice, say "standard 2-week notice once we have a written offer." Something vague like "oh, I'm flexible" makes you sound less serious than you are.

Q6

Is there anything else we should know about you or anything you want to ask me at this stage?

Show sample answerSay yours out loud first, then check.

This is how the recruiter wraps up, and you have two good moves. First, mention one relevant thing your resume doesn't show, like a recent project, a certification, or a skill that matches the JD. Second, ask one clarifying question about the role or team, such as "What's the team looking for someone to ship in the first 90 days?" or "Can you tell me about the interview process from here?" That second question eases you straight into next steps.

Knockout questions recruiters use to filter fast

Some recruiter questions work like yes-or-no gates. Get one wrong, or answer it vaguely, and the call can end early. Expect some version of these:

  • Do you have the required degree or certification? Answer directly. If you're close (say, finishing in June), give the exact date rather than hedging.
  • Can you travel or relocate? Treat it like Q4. Name cities or limits plainly. Clarity beats a fake yes you'll walk back later.
  • Are you authorized to work here? Give a straight, accurate answer. If you'll need sponsorship, say so now. It's far better than having it surface at the offer stage.
  • When can you start? Use the Q5 approach and give a real date or notice period.
  • What are your salary expectations? Use the Q2 playbook: a researched range, or a polite question back about the budget.

None of these needs a clever answer. They need an honest one that doesn't box you in for no reason.

Hiring-manager phone screen questions (6 Q)#

The hiring manager makes the call. They've read your resume and the recruiter's notes, and now they want to know two things: can you do the work, and will you fit the team? So they test whether you can talk about real work without a script. The questions go deeper than the recruiter's and lean on storytelling and judgment.

Q7

Tell me about a project you're most proud of.

Show sample answerSay yours out loud first, then check.

In 2026 this is the question hiring managers ask most. Pick one project and give it 90-120 seconds:

  1. What the project was (10 seconds)
  2. Why it mattered (10 seconds)
  3. What you personally did (60 seconds, which is the part they're grading)
  4. The result, with a number if you have one (15 seconds)
  5. What you'd do differently now (15 seconds)

That last piece is the detail most people skip, and it's the one doing the most work. It shows reflection and growth, which hiring managers grade on purpose. Leave it out and the answer sounds like a static brag.

Q8

What's your role on a team right now?

Show sample answerSay yours out loud first, then check.

This is a team-fit probe, and it overlaps with "How do you prefer to be managed?" The manager is trying to figure out whether you're a senior contributor acting junior, a junior contributor acting senior, or someone with an accurate read on yourself. A strong answer names your exact scope and how you work with the roles around you: "I own the backend for X, I work closely with the iOS team on the API contract, I escalate scope-creep to my manager."

New grad? Then shift the frame. Name the projects you've led, who you worked with, and what you specifically contributed.

Q9

What's the biggest impact you've had in your most recent role?

Show sample answerSay yours out loud first, then check.

They're looking for a measurable outcome, so bring one real number. Don't say "I improved performance." Say "I cut the p95 latency on the checkout endpoint from 800ms to 340ms by adding a Redis read-through cache." A specific number tells them you shipped the thing and didn't just talk about it.

No number from a job? Use a project. "I built a side project that hit 1,200 weekly active users in 3 months." "I contributed to an open-source library that has 800 GitHub stars." Hiring managers would much rather hear a real number than a vague claim.

Q10

Why this company specifically?

Show sample answerSay yours out loud first, then check.

Think of this as Q3 again, but the hiring manager expects more depth. It's also where "What do you know about our company?" usually gets answered. Name something specific: a thing they built, a recent decision, or a problem the team is working on right now. Two sentences pulled from their engineering blog or recent press is enough.

Example: "I read your engineering blog post last month about how you scaled the matching service from 100 to 10,000 requests per second, and the specific decision to move from Kafka to NATS caught my attention. I've been working on a similar throughput problem in my side project and I'd love to learn how that played out in production." A reference that specific moves you from generic applicant to someone who did the homework on them.

Q11

Walk me through your technical narrative on the last big thing you built.

Show sample answerSay yours out loud first, then check.

This is a depth probe, and it's also the long version of "describe a recent project and your role." Strong candidates can talk about one real piece of work for 8-15 minutes. The structure is Q7's, just stretched out: the problem, the options you looked at, the tradeoffs, what you built, what went wrong, and what you'd change.

The detail that separates strong candidates comes in the middle. Name the option you didn't choose and explain why. "I considered using Postgres triggers but rejected it because we needed the migration to be reversible." That rejected-alternative sentence carries more signal than anything else you'll say in a hiring-manager interview.

Q12

What kind of role and team are you looking for?

Show sample answerSay yours out loud first, then check.

Fit runs both ways here. The manager wants to see that you have a clear target and aren't applying to anything that moves. This is where questions about the work environment that suits you come up too. Cover team size (small enough to ship, big enough to learn), stack preference, problem domain, and where you want to grow.

Example: "I'm looking for a backend role on a team of 5-10 engineers where I can own a service end-to-end. Specifically interested in fintech or developer-tools because both involve careful API design and high-reliability systems. I'd want to grow into a senior engineer role over the next 2-3 years." Specific beats flexible. Candidates with clear preferences tend to stay in the role longer, and hiring managers know it.

Phone-specific behavioral interview questions (6 Q)#

On the phone, behavioral answers still follow STAR (Situation, Task, Action, Result), with two adjustments. First, slow down. The interviewer can't see you gathering your thoughts, and a 2-second pause on a call sounds like composure, while the same pause on video can look like a freeze. Second, say your structure out loud, because there's no facial cue telling them you've moved from the situation to the action. Keep setups short, land a clear result, then stop so they can follow up.

Q13

Tell me about a time you handled a conflict with a teammate.

Show sample answerSay yours out loud first, then check.

This tests composure under people stress. Choose a real story where things got uncomfortable but never catastrophic, and skip anything that makes either of you look unprofessional. The strongest action: you went straight to the teammate, named the issue without blame, listened to their side, and worked out a way forward together.

Phone delivery: go slower than you would in person. A 90-second answer with 2 deliberate pauses (one before the action, one before the result) lands cleaner than a 70-second version that rushes the whole story.

Q14

Tell me about a time you failed.

Show sample answerSay yours out loud first, then check.

This checks self-awareness. They're grading two things: was it a real failure, and what did you learn? The weak answer is the disguised brag ("I worked too hard on a project"). The strong one is a real failure with a real consequence, plus a specific lesson you used later.

Phone delivery: take the thinking pause openly. "Let me think about a real one for a second" is completely fine, and on a call it comes across as honest reflection.

Q15

Tell me about a time you had to learn something new under pressure.

Show sample answerSay yours out loud first, then check.

This measures how fast you learn. Use a story with a real deadline: a project ship date, interview prep, a job change. A strong structure names the gap (what you didn't know), how you closed it, what you shipped, and how you approach learning now because of it.

Q16

Tell me about a time you made a decision with incomplete information.

Show sample answerSay yours out loud first, then check.

Here they're testing judgment. The strong version goes like this: you said out loud what you didn't know, split what had to happen now from what could wait, made a call you could defend, and checked later whether it was right. "I just trusted my gut" with no reasoning behind it is the weak version.

Phone delivery: saying the structure out loud helps a lot on this one. "I'll walk you through what I knew, what I didn't, what I decided, and what I learned" gives the interviewer a map before you start.

Q17

Tell me about a time you disagreed with a manager.

Show sample answerSay yours out loud first, then check.

This one checks composure and judgment together. A strong story has three parts: the disagreement was about something real, you handled it professionally, and either you won them over or they gave a reason you accepted. Don't cast anyone as the villain.

The classic phone failure here is going way too long, since there's no face to tell you to wrap up. Practice it with a timer and aim for 90 seconds.

Q18

Tell me about a time you took initiative.

Show sample answerSay yours out loud first, then check.

This is about proactivity. The strong story shows you spotted something that needed doing, did it without being asked, and got a measurable result. New grads often get stuck because they don't have much work history. The fix is simple: use a school project, an open-source contribution, a side project, or a volunteer role.

Phone delivery: you want energy in your voice for this one, so stand up while you answer. The story is about ownership, and your voice has to carry that.

Other prompts in this family include making an unpopular decision, changing your approach to fit someone else's needs, and strengthening a work relationship through good communication. The same story bank covers them. For the full library, see the behavioral interview questions master guide.

Phone technical screen questions (6 Q)#

For most CS new grads, this is the round they dread. The format varies a lot. Some companies use a shared online editor (CoderPad, HackerRank, CodeSignal). Some are audio-only, where you talk through code structure without typing anything. Others are language-agnostic discussions of data structures and algorithms with no code at all. Either way, you're explaining your thinking with nothing for them to look at but your words. The questions below cover the patterns you're most likely to see, and the technical phone screen guide goes deeper on the format itself.

Q19

Two-sum (find two indices that sum to a target).

Show sample answerSay yours out loud first, then check.

This is the standard warm-up. A strong answer talks through the tradeoff between brute-force O(n^2) and a hash map at O(n), chooses the hash map, and walks a small example out loud: "input [2, 7, 11, 15], target 9, I'd return [0, 1] because 2 + 7 = 9." Then it states the complexity at the end. If you can't get the hash-map version working, brute force is an acceptable fallback.

Phone delivery: say your data structure choice before writing anything. "I'm going to use a hash map where the key is the number and the value is its index. I'll loop through the array once, and for each number I'll check whether the complement is already in the map." That outline is the most important thing you'll say. The code comes second.

Q20

Reverse a linked list.

Show sample answerSay yours out loud first, then check.

This checks how fluent you are with data structures. A strong answer walks through iterative reversal with three pointers (prev, current, next). It explains why the recursive version uses O(n) stack space while the iterative one uses O(1), and it pauses to draw the list out in words: "I'm at node A, B, C, D. I want D, C, B, A. I'll keep three pointers and walk through, flipping each next pointer one at a time."

On the phone, describing it out loud stands in for the whiteboard. Candidates who narrate the pointer walk land better than candidates who just write the code.

Q21

Detect a cycle in a linked list.

Show sample answerSay yours out loud first, then check.

This is about recognizing the pattern. Floyd's tortoise-and-hare is the expected answer: two pointers, one moving twice as fast as the other, and if they ever meet, there's a cycle. Say the intuition first ("if there's a cycle, the fast pointer eventually laps the slow one inside the loop"), then implement it.

The usual follow-up asks how you'd find where the cycle starts. Reset one pointer to the head, move both at the same speed, and the spot where they meet is the start. Knowing that follow-up shows depth.

Q22

Find the longest substring without repeating characters.

Show sample answerSay yours out loud first, then check.

This tests the sliding window. Keep a set of the characters in the current window. Move the right pointer until you hit a duplicate, then move the left pointer until the duplicate is gone, and track the max length the whole way. That's O(n) time and O(min(n, alphabet)) space.

Phone delivery: walk an example out loud. "Input 'abcabcbb'. Start at index 0, expand right until you hit the second 'a' at index 3. Window is now 'abca', contract left until you remove the first 'a'. Window is 'bca'. Keep going."

Q23

Implement a basic LRU cache.

Show sample answerSay yours out loud first, then check.

This is a design question. A strong answer pairs a hash map (O(1) lookup) with a doubly-linked list (O(1) eviction and move-to-head on access). Most candidates freeze on the pointer handling, so practice it ahead of time. If the round is audio-only, describe the data structures and operations, and say plainly that the pointer work is easier to show in a shared editor.

Q24

Given an array of integers, find the kth largest element.

Show sample answerSay yours out loud first, then check.

The real test is heap versus sort. You have two solutions. Sorting and returning arr[n-k] costs O(n log n). The heap approach keeps a min-heap of size k: push each element, pop when the size goes over k, and return the root. That's O(n log k) time and O(k) space. If you name both and pick the heap because of the size tradeoff, you show stronger algorithm instincts than someone who just sorts.

Expect softer questions here too, like "Have you worked with our tech stack?" or "What tools are you strongest in?" Those are covered in the section on more common questions below.

Closing the phone interview (6 questions you ask) (6 Q)#

The last 5-10 minutes of every call belong to you. Most people waste them on generic questions like "what's the company culture like?", which tells the interviewer you didn't prepare. Candidates who close with specific questions and a clean next-steps script move forward faster than the ones who trail off.

Match your questions to who's on the line. With a recruiter, lean on process and timeline. With a hiring manager or engineer, ask about the team, the work, and what success looks like. The best questions to ask your interviewer guide has a bigger list.

Q25

What does the team need this person to ship in the first 90 days?

Show sample answerSay yours out loud first, then check.

This scoping question does a few jobs at once. It shows you understand the role, it gives you a concrete answer to bring back up when you negotiate an offer, and it makes the interviewer spell out what the role covers. Most hiring managers have never said it out loud, and putting it into words sharpens how they evaluate you.

Q26

What's the team currently struggling with that this hire is meant to help with?

Show sample answerSay yours out loud first, then check.

This surfaces a real problem the team has right now. It also opens the door for a follow-up like "tell me how you've been handling that so far," which shows you get the problem space. Hiring managers like candidates who think about what they'll contribute, not just what the job description says.

Q27

How does the team measure success for this role at the 6-month mark?

Show sample answerSay yours out loud first, then check.

It's different from the 90-day question. This one shows whether the company has defined success at all. From the answer you'll learn whether there's a clear performance bar or whether they're winging it.

Q28

What's the most interesting problem the team has solved in the last 6 months?

Show sample answerSay yours out loud first, then check.

It sounds technical, but it's a culture question underneath. The answer tells you what they find interesting (so, what work they value) and whether they can name a specific example (so, whether they're doing the work they describe).

Q29

What are the next steps in your process and when should I expect to hear back?

Show sample answerSay yours out loud first, then check.

This is the single most important sentence in any phone interview. Ask it, wait, and write down the timeline. It tells you when to follow up and quietly signals confidence, since you're assuming you'll advance. It also hands you the script for your thank-you email.

Phone delivery: don't skip this, even if you're tired and the call ran long. Closing with a clean next-steps ask shows follow-through, and hiring managers grade that explicitly.

Q30

Is there anything you'd like me to follow up with after the call?

Show sample answerSay yours out loud first, then check.

This close signals initiative. Sometimes the answer is no. Other times they'll ask for a code sample, a portfolio link, a writing sample, or a description of a project. Either way, you offered. That offer alone moves you up in the post-call debrief, because most candidates never make it. For what to send and when, see the post-interview follow-up and thank-you guide.

More common phone interview questions to prepare for#

These come up often enough on recruiter and hiring-manager calls that you should have an answer ready. The structures above apply here, so the notes are short.

How did you hear about this job? Tell the truth, then add one sentence on why it caught your eye. "I found it on the company's careers page after reading their engineering blog" beats "LinkedIn, I think." If someone referred you, name them.

What do you know about our company? Treat it as a lighter Q10. Bring one fact about what they build and one recent piece of news, then connect either one to your background in a sentence. Reading the homepage back to them doesn't count as research.

How do you prefer to be managed? Describe how you work best, using a real example. Something like "I do well with clear goals and a regular check-in, and I'll flag blockers early rather than sit on them" is honest without being demanding. Don't claim you need zero guidance if you're a new grad.

What kind of work environment suits you best? Pull from your Q12 answer: team size, pace, and how you like to collaborate. Be specific enough to sound real, but don't describe an environment so narrow that it rules out the team you're talking to.

Have you worked with our tech stack? Be accurate. If you've used it, name the project and what you built. If you haven't, name the closest thing you've used and how you'd ramp up. Overstating your experience tends to come out in the technical round.

What is your greatest strength? Pick one strength that matters for this role and prove it with a story or a number, the way Q9 does. "I'm a fast learner" with nothing behind it won't stick. A short story where you picked up a new tool to fix a real problem will.

What is your greatest weakness? Use the same logic as Q14. Name a real weakness, then what you're doing about it now. The disguised brag ("I care too much") reads as dodging, and on the phone there's no smile to soften it.

Where do you see your career going? Keep it tied to the role. Name the kind of engineer you want to become and the skills this job would build. Your Q12 answer, with its plan to grow into a senior role over a few years, is a good template.

Phone-medium tactics that close the delivery gap#

The questions matter, but these tactics are what separate an answer that lands from one that was technically right and still fell flat. Get them into your habits and the same content sounds completely different on the other end.

Stand up while you talk. Your voice projects better, your energy reads higher, and your diaphragm opens up. The catch is that some people get more anxious on their feet. My honest call: stand for the blocks where vocal energy matters most, like the resume walk-through, the project deep-dive, and behavioral stories. Sit for the listening parts if that helps you focus, or use a high stool as a middle ground.

Keep a pen and paper on the table. Paper, not your laptop. It has three uses:

  • Write the interviewer's name down at the start so you can use it later.
  • Jot down a complex question so you don't lose the second half of a two-part prompt.
  • Sketch code or data structures during the technical block.

Writing also slows your speech, which on a call is usually a good thing.

Use the "give me one moment to think" line. It works especially well on the phone, so use it freely. "That's a fair question, let me think about it for a second" buys you 5-10 seconds of silence that's much more acceptable on a call than on video. A deliberate pause sounds composed. Filling every second of airtime sounds anxious.

Pause for 2 seconds after each answer. When you finish a behavioral answer, stop talking. No qualifiers, and no restating the conclusion. Two seconds of quiet forces the interviewer to follow up or move on, and either one is fine. The post-answer ramble is the most common phone failure, and it's the easiest to fix.

Keep water nearby. Phone interviews tend to run longer than you expect, and your voice is the whole signal. A dry mouth flattens your delivery and adds clicky sounds the headset will pick up. Sip between questions, never during an answer.

Treat the mic as hot if you're put on hold. Some companies put you on a brief hold (5-30 seconds) during the call. If there's any chance they can still hear you, assume they can. Hot-mic moments include an "ugh" after a hard question, talking to a family member who walked in, or anything else you wouldn't say to the interviewer's face. It's rare, but when it happens it's devastating.

Honest call: I used to leave the "stand up" tip out of my own advice because it felt corny. Then I ran two phone screens back-to-back with the same script, one sitting and one standing, and the standing one got noticeably warmer feedback. The link between body and voice is real even when nobody can see the body.

How to prepare for a phone interview (5 steps)#

This is a 24-hour routine for the night before and the morning of.

  1. Lock down your environment. Pick the quietest room, close the door, and warn housemates. Put your phone on Do Not Disturb for everyone except the interviewer. If home is noisy, try a library study room or your car.

  2. Test your phone, headset, and signal 30 minutes early. Call a friend on the same line with the same headset and confirm you both sound clear. Charge wireless headsets the night before, and write the recruiter's number on paper as a backup.

  3. Build a one-page cheat sheet. Include your top 5 resume bullets with metrics, your 5-story bank in keyword form, your 2 closing questions, and your next-steps script. Use bullets and keywords, not full sentences. This is also where your real numbers from your own projects go, so you aren't hunting for them mid-answer.

  4. Prepare a 5-story bank. Choose the 5 strongest stories from your last 18 months and break each into STAR keywords. Label which behavioral questions each one covers, then practice each at 60-90 seconds, out loud.

  5. Write your closing script word for word. That's your 2 specific questions plus the next-steps close ("What are the next steps in your process and when should I expect to hear back?"). Have it written down before the call. You don't want to improvise the most important sentence at minute 50, when your brain is tired.

Research fits into steps 3 and 5. Read the job description, the company's site, and their engineering blog, then turn what you find into one line for Q10 and one closing question.

Practicing with AI mock interviews

Reading answers silently doesn't build phone delivery. Saying them out loud, on a clock, does. That's where mock interviews help: run a phone-style practice round, drill your behavioral stories until each one fits in 60-90 seconds, and rehearse the technical patterns above by talking through them as if nobody can see your code.

The goal is to walk in able to say every answer in your own voice, not to recite something you memorized. If the next screen is days away, drill these blocks under live timing until the delivery is automatic. The candidates who turn phone screens into onsites are usually the ones who rehearsed the medium, not just the answers. The mock interview practice guide explains how to set up realistic timing pressure.

Phone interview cheat sheet (top 12 tactics)#

Use this one-page reference the morning of the call. Writing it out from memory is the prep. Having it on the table during the call is your safety net.

#TacticWhen to use
1Stand up while talkingBehavioral answers, project walk-throughs
2"Give me one moment to think" lineHard questions, follow-ups, freeze moments
3Pen and paper for notesAlways on the table
4Drop interviewer's nameMid-answer references, transitions
5Verbalize structureBehavioral STAR transitions, technical answer outline
6Sip water between questionsLong calls, 45+ minute screens
72-second post-answer pauseAfter every behavioral answer
8Ask clarifying questionsBefore any technical problem
9Use specific numbersProject impact, salary, timelines
10State complexity for codeEvery algorithm question
11Walk through small examplesAudio-only technical, complex problems
12Close with next-steps scriptEvery phone interview, no exceptions

Common phone interview mistakes for new grads#

These seven mistakes keep showing up in 2026 recruiter debriefs, and two more are worth adding at the end.

Taking the call somewhere noisy. A cafe, your car, family in the background, a dorm next to construction. On a call, background noise sounds like you didn't prepare, and the interviewer notices. Fix: a quiet room with the door closed, and housemates warned ahead of time.

Not testing your phone, signal, or headset. Half the technical glitches in phone interviews could have been avoided: a dead headset, a weak signal, a recruiter calling from a blocked number you ignored. Fix: do the 30-minute pre-call check, keep the recruiter's number on paper, plug in your laptop, and charge the headset.

Missing the call entirely. Recruiters often call from blocked or unfamiliar numbers. If your phone sends unknown callers straight to voicemail, you'll miss it. Fix: turn off call screening in the hour before the interview, and pick up every call during that window.

Hot mic during hold music. Some phone systems put you on hold for a few seconds while they transfer or start recording. If you mutter, talk to someone in the room, or sigh loudly, the interviewer often hears it. Fix: assume the mic is live for the entire call.

Talking too fast. Nerves speed you up. Someone who normally talks at 150 words per minute can hit 180 under stress, and on the phone, with no face to balance it, fast speech sounds anxious. Fix: practice with a timer, keep behavioral answers to 60-90 seconds, and use the "give me one moment to think" line freely.

No pen and paper on the table. Most candidates don't have notes ready. They forget the interviewer's name, lose the second half of a two-part question, and can't sketch a data structure during the technical block. Fix: one sheet of paper and one pen, on the desk, before the call starts.

Rambling past 90 seconds on behavioral answers. Without the interviewer's face as a cue, it's easy to lose track of time. They're too polite to cut you off at 2 minutes, but their notes will say "rambled" or "lost the thread." Fix: practice with a timer, aim for 60-90 seconds, and use the 2-second pause to make yourself stop.

Reading answers word for word. A script read aloud sounds flat, and the interviewer can tell. Keep notes in keyword form so you speak in your own words and only glance down for the next point.

Having no questions at the end. Saying "no, I think you covered everything" throws away the block hiring managers grade more than you'd expect. Always have your 2 closing questions and the next-steps ask written down.

One more from running phone screens with new grads: skip heavy food in the hour before the call. A full stomach makes you sleepy, and a sleepy voice reads as low energy. A small snack 90 minutes before is fine. A full lunch 20 minutes before is not.

Phone interview FAQ#

What is a phone interview?

It's an interview done by voice, usually early in the hiring process. For CS roles, it's typically a recruiter screen, a hiring-manager screen, or a phone technical screen, sometimes with a shared editor and sometimes audio-only.

How long does a phone screen usually last?

It depends on who's calling. Recruiter screens run 20-30 minutes, hiring-manager screens 30-45 minutes, and phone technical screens 45-60 minutes. Most calls mix two or three question types somewhere in the 30-60 minute range.

How serious is a phone interview?

Treat it as a real round, because it is one. The phone interviews decide whether you advance, and the onsite decides whether you get the offer. More first-round screens are phone-only now, and hiring managers increasingly use the call for deep project questions.

What are the most common phone interview questions?

Recruiters almost always ask you to walk through your resume, plus salary, location, and start date. Hiring managers ask about a project you're proud of, your biggest impact, and why their company. Nearly every call ends with "Do you have any questions for me?"

What behavioral, technical, and HR questions come up on phone screens?

The "HR" questions are mostly the recruiter set (Q1 to Q6) plus the knockout questions. Behavioral questions follow STAR: conflict, failure, learning under pressure, incomplete information, disagreeing with a manager, and taking initiative. Technical screens lean on patterns like two-sum, linked lists, sliding windows, LRU caches, and heaps.

What should I ask the interviewer at the end of a phone interview?

Ask two specific questions tied to the role, such as what the team needs shipped in the first 90 days or what they're struggling with, and then always ask about next steps and timing. The closing section above has six options.

Can I keep notes in front of me during a phone interview?

Yes. Notes are normal on a phone call, and a one-page cheat sheet is some of the best prep you can do. Keep it short: resume bullets with numbers, your story bank in keywords, your closing questions, and a pen to write down the interviewer's name. It's there to jog your memory, not to read from.

Key terms#

Phone screen. Any early-round interview done by voice. In CS hiring it usually means one of the three formats below.

Recruiter phone screen. The first phone interview at most companies. It's a 20-30 minute call with a recruiter (not an engineer or hiring manager) that filters for fit-on-paper, salary alignment, location, and availability. The questions are predictable, and clear answers beat sophisticated ones.

Knockout question. A yes-or-no style recruiter question, such as degree, work authorization, relocation, or start date, that can end a screen early if the answer doesn't fit.

Hiring-manager phone screen. The deeper phone round: 30-45 minutes with the person who'd manage you. It tests project depth, team fit, and technical narrative, and goes further than the recruiter screen but rarely into live coding.

Phone technical screen. A coding or systems interview done by phone, 45-60 minutes. It sometimes uses a shared online editor and is sometimes audio-only, with you describing code structure verbally. It tests reasoning and complexity intuition more than memorized syntax.

STAR framework. Situation, Task, Action, Result: the four-part structure for behavioral answers. On a call, say each transition out loud, since the interviewer can't see your face change.

5-story bank. A ready set of 5 STAR stories from your last 18 months, each labeled with the behavioral questions it fits. Five stories can usually cover 10+ questions if you adjust the framing. For behavioral phone interviews, it's the highest-ROI thing you can prepare.

Closing script. The 3-sentence sequence you use at the end of every phone interview: two specific questions about the role, then the next-steps ask ("What are the next steps in your process and when should I expect to hear back?"). You write it before the call so you aren't composing it on the spot.

Hot mic. A microphone that's live when you think it isn't, which often happens during hold moments. It's rare for an interviewer to overhear something bad, but when they do, it's devastating. Treat the mic as live for the whole call.

Give-me-one-moment line. Your phone-specific permission to pause. "That's a fair question, let me think about it for a second" buys 5-10 seconds of silence that sounds composed. Phone calls allow this in a way video doesn't.

Resume walk-through. The opening question at nearly every recruiter screen. Aim for 60-90 seconds of compressed story, not a line-by-line read. The recruiter has the resume already and wants the narrative.

Phone-screen-to-onsite progression. The usual hiring sequence: recruiter screen, then hiring-manager phone screen, then a phone technical round (or take-home), then an onsite (3-6 hours, several rounds). The phone interviews decide whether you advance, and the onsite decides the offer.


About the author: Sam K. is the founder of InterviewChamp.AI, building AI interview prep for the new-grad CS market and writing about the modern interview gauntlet from the inside.

Originally published on InterviewChamp.AI

Related guides

Interview Process

Beyz AI Alternatives: 7 Tools Compared on Price

Beyz AI lists $49.99 a month, or $24.99 a month billed every 6 months. Lower or shorter-commitment alternatives include Verve AI at $16.99 a month as shown (billing period unclear), Cluely at $19.99 a month and InterviewChamp at $15 a week. Pick by billing period, free plan and refund terms, not by the per-month figure alone.

Sam K. ·

Read more →
Interview Process

Cluely Alternatives: 7 Tools Compared on Price

The best Cluely alternative depends on what you need. Verve AI's card shows $16.99 a month, InterviewChamp Pro is $15 a week, and Sensei AI is $24 a month billed yearly. Cluely itself is free on Starter and $19.99 a month on its Pro card, so compare prices before you switch.

Sam K. ·

Read more →
Interview Process

Final Round AI Alternatives: 7 Tools Compared on Price

Final Round AI's free plan has no live sessions, and Pro is listed from $25 a month. If you want to test live help before you pay, Verve AI, LockedIn AI and InterviewChamp each have a free start with no card. This page compares seven alternatives on price, free plans and refund rules.

Sam K. ·

Read more →

Frequently asked questions

What questions do they ask in a phone interview?
Phone interview questions fall into five categories depending on who's on the call. Recruiter screens ask about your resume, salary expectations, location, availability, and high-level role fit. Hiring-manager screens go deeper on projects, team-fit, and the technical narrative behind your work. Behavioral phone blocks use STAR-format past-tense questions ('tell me about a time you...'). Phone technical screens cover one or two coding problems narrated out loud, sometimes with a shared editor and sometimes without. Closing blocks are your questions and the logistics of next steps. Most phone interviews mix two or three of these in a single 30-60 minute call.
How long is a phone interview?
Most phone interviews in 2026 run 30-60 minutes. Recruiter screens are 20-30 minutes. Hiring-manager phone screens are 30-45. Phone technical screens are 45-60. The full structure usually budgets 5 minutes for intros and resume warm-up, 20-45 minutes for the main content, and the last 5-10 minutes for the candidate's questions plus next-step logistics. A 90-minute phone interview is rare and usually means a small employer is compressing two rounds into one. Treat those as an onsite, not a phone screen.
How do I prepare for a phone interview?
Five-step prep the day before: set up a quiet environment with no background interruptions, test your phone and headset 30 minutes before the call, prepare a one-page cheat sheet of your resume bullets and stories, build a five-story bank that maps to common behavioral questions, and write down two specific closing questions plus a script for asking about next steps. The phone medium loses body language, eye contact, and visual rapport, so your voice has to carry all the signal. Standing up while talking helps. Notes on the table help. A pen and paper for jotting questions helps.
What questions should I expect from a recruiter phone screen?
Recruiter phone screens cover six recurring questions: walk me through your resume, what salary range are you looking for, what's your interest in this role, where are you located and are you open to relocation, when can you start, and is there anything else we should know. The recruiter is filtering for fit-on-paper plus availability plus salary alignment. They are not deeply technical. The strongest signal from a recruiter screen is clarity. The candidate who can crisply state target salary, target start date, and target role type in 30 seconds total moves to the hiring-manager round faster than the candidate who hedges every answer.
What does a hiring-manager phone screen test?
Hiring-manager phone screens test three things: depth on your strongest project (can you talk about it for 15 minutes without losing the thread), fit with the team's current problems (do your skills map to what they need to ship in the next quarter), and the technical narrative behind your work (not just what you built but why, with what tradeoffs, and what you'd do differently). The hiring manager is also screening for whether you can hold a conversation, ask clarifying questions, and handle ambiguity. They want to feel that they could put you in front of the team without supervision.
How do I answer behavioral questions on the phone?
Behavioral phone answers use STAR (Situation, Task, Action, Result) the same as in-person, with two phone-specific adjustments. First, pace slower. Without visual cues the interviewer can't see you collecting your thoughts, so a 2-second pause before answering reads as composure, not freezing. Second, signal your structure verbally. 'Let me walk through that situation, what I needed to do, what I did, and how it turned out' gives the interviewer a roadmap they can't get from your face. Target 60-90 seconds per behavioral answer. Use the give-me-one-moment-to-think line freely. It costs nothing on the phone and buys you 5-10 seconds of thinking.
Can I have notes during a phone interview?
Yes for most blocks, with two cautions. A one-page cheat sheet with your resume highlights, your five-story bank, and your two closing questions is normal and recommended. Reading full sentences off the page makes you sound slower and flatter, like a script, and that is a known weak signal. The honest middle ground: bullets and keywords on paper, not full sentences. For the coding portion of a phone technical screen, the interviewer expects you to think out loud from scratch, so work the problem live instead of reciting code from your notes.
What's the right answer to 'what's your salary expectation' on a phone screen?
Two strong options depending on your information level. Option A (if you've researched the role on Levels.fyi, Glassdoor, or peer data): name a range with the floor at your minimum acceptable and the ceiling 15-20% above. 'I'm looking for $85,000 to $100,000 base, plus standard equity and benefits.' Option B (if you don't have data yet): defer politely. 'I'd love to learn more about the role and team before discussing comp specifically. What's the budgeted range for this position?' Most recruiters in 2026 will share a range when asked directly. The weakest answer is naming a single number that's too low. You can't negotiate up from a stated number; you can negotiate down from a stated range.
How do I handle the awkward silence on a phone interview?
Silence on the phone is uniquely uncomfortable because you can't see whether the interviewer is taking notes, thinking, or waiting for you to continue. Three tactics. First, ask explicitly: 'Was there a specific part of that you wanted me to go deeper on?' That converts silence into a structured next question. Second, if you've just finished an answer and they don't follow up in 3-4 seconds, that's a normal note-taking pause, not a signal you should keep talking. Third, never fill silence by repeating yourself or weakening your answer. The most common phone mistake is the post-answer ramble that adds qualifiers and undercuts the original point.
What should I ask at the end of a phone interview?
Ask two specific questions and one logistics question. The first specific question shows you understand the role: 'What does the team need this person to ship in the first 90 days?' The second shows you've researched the company: 'I noticed the team recently shipped X. How did that change the priorities for this role?' The logistics question is the close: 'What are the next steps in your process and when should I expect to hear back?' That last one is the single most important sentence in any phone interview. It surfaces the timeline, sets you up to follow up appropriately, and signals confidence.
How do I do a technical phone interview without screen sharing?
Audio-only technical rounds shift the rules. Three tactics. First, narrate structure before code: 'I'm going to use a hash map for O(1) lookup, loop through the array once, and check whether the complement is already in the map.' That outline is the most important sentence; the implementation is the second-most. Second, state your data structures and complexity out loud. 'Hash map, O(n) time, O(n) space.' Third, walk through a small example out loud, like input [2, 7, 11, 15], target 9, you'd return [0, 1]. The interviewer is grading reasoning structure, not whether you can hold 40 lines of code in your head. Pseudocode beats code-in-your-head.
What are common phone interview mistakes?
Seven mistakes show up repeatedly in 2026 phone interviews: taking the call from a noisy environment (cafe, car, family at home), not testing your phone or headset before the call, missing the actual call because the recruiter dialed from a blocked number you didn't pick up, leaving your microphone hot during a hold-music moment so they hear you, talking too fast because nerves compress your speech, having no pen and paper to jot down the question or names, and rambling past 90 seconds on a behavioral answer because there's no visual cue to wrap up. Most of these are environmental, not knowledge gaps.
Should I stand up during a phone interview?
Yes. Standing up while talking measurably improves vocal clarity and projection. Your diaphragm opens up, your voice carries better, and the slight elevated energy reads as engagement on the other end. The trade-off: standing makes you slightly more nervous if you're already anxious. The honest call: stand for the answering blocks, sit for the listening blocks if you need to. Or compromise with a high stool. Most phone-interview coaching ignores this and it's one of the highest-impact adjustments you can make.
How do I follow up after a phone interview?
Send a thank-you email within 24 hours, ideally same-day if the call was in the morning. Three sentences: thanks for the conversation about [specific topic that came up], reiterate one specific reason you're a strong fit (pulled from something the interviewer mentioned), confirm the next step they outlined. Do not just send a generic 'thanks for your time' email. Specific beats sincere. If they said you'd hear back in a week and a week passes, send a brief check-in. The follow-up cadence is part of how hiring teams grade follow-through.
What's the difference between a phone screen and a phone interview?
In practice the terms are used interchangeably in 2026, but there's a useful distinction. A phone screen is shorter (20-30 minutes), usually with a recruiter, and tests fit-on-paper plus availability. A phone interview is longer (45-60 minutes), usually with a hiring manager or working engineer, and tests project depth or technical skill. Companies use the same word for both. When you get the calendar invite, look at the duration. Under 30 minutes is a recruiter screen; 45+ minutes is a phone interview with a hiring manager or technical contributor.
What are the best phone interview tips for a CS new grad?
The highest-leverage phone screen tips for a CS new grad in 2026: lock down a quiet room (background noise is the most common preventable failure), stand up during the answering blocks so your voice carries, keep a one-page cheat sheet and a 5-story bank on the table, narrate structure before code on the technical round, and close with the next-steps question every single time. Most candidates over-prep the answers and under-prep the medium. The voice carries every signal the camera would carry in person, so delivery is roughly half the score.
How many questions are asked in a phone interview?
A single 30-60 minute phone interview usually covers 5-12 questions depending on the call type. A recruiter screen runs through about 6 standard questions (resume, salary, interest, location, availability, anything-else). A hiring-manager screen goes deeper on 4-6 questions about projects and team-fit. A phone technical screen is often just 1-2 coding problems narrated out loud. Budget the last 5-10 minutes for your own 2-3 closing questions, which the interviewer grades more than most candidates realize.