Phone Interview: How to Sound Strong When They Can't See You

A phone interview can be a recruiter screen, a manager call or a coding screen. What each one tests, and how to come across well on audio alone.

A phone interview is any interview where the person deciding about you mostly hears you rather than sees you, and it comes in several forms: a recruiter screen, a call with the hiring manager, a technical screen with a shared code editor, or a panel on speakerphone. Each tests something different, and on a voice-only call you cannot see a nod or a frown or tell whether an answer is landing, while a video call with a shared editor gives you little more to read. You compensate by making your structure audible: say where an answer is going, keep it shorter than in person, explain your silences and check you have been understood.

The kinds of phone interview, and what each one is checking

The word "phone" is loose: Amazon's phone screening page says you may meet on Zoom or Amazon Chime, so a "phone screen" can be a call on a meeting platform. Ask the recruiter three things when the invitation arrives: who will call, how long it will last, and whether you need a computer.

The recruiter screen

Google says candidates typically have one or two shorter conversations with a recruiter over phone or video that "usually assess key skills you'll need for the role", share information about the organization and team and ask about preferences such as your preferred location. Google says this call covers key skills, information about the team and your preferences, so in our view it rewards a clean two-minute background, a specific reason for applying and a ready answer on salary and notice. Our recruiter phone screen guide covers that call question by question, so this page concentrates on the other formats.

The hiring manager or senior leader call

A call with the person you would work for, or someone senior in that function, can go deeper. Amazon's program manager page says that phone screen is with a senior leader, lasts 60 minutes, and splits evenly between behavioral questions on its Leadership Principles and functional questions about your project and program management experience. Expect follow-ups on what you personally did and why, so prepare four or five detailed stories rather than polished summaries; our behavioral interview guide explains how to structure them. If your call is with Amazon specifically, our Amazon phone interview questions page lists the questions to rehearse for that call.

The technical phone screen with a shared editor

For engineering roles, the first screen can be a coding session. Meta's preparation post says its initial technical screen, run over video chat or in person with a Meta engineer, gives 5 minutes to introductions, 35 minutes to two coding problems on fundamentals such as algorithms and data structures, and 5 minutes to your questions, with a collaborative editor when it is remote. On video you may both end up looking at the editor more than at each other, so in our experience it can behave much like a phone call. Salesforce says its virtual screening uses a shared screen "so the interviewer can see how you decompose problems", and Amazon's SDE II page says to expect to write "syntactically correct code—no pseudo code" and suggests getting comfortable coding with Livecode.

Meta adds that the way you solve problems "can be as important as having the right answer", and on a call your reasoning only exists if you say it. Practise in a plain editor while narrating, because the two compete for attention. For a role-specific example, our data engineer interview guide walks through the modeling and pipeline design questions that role brings.

The panel or structured HR call

Public-sector employers may run a phone interview as a structured interview with pre-defined questions. The USAJOBS Help Center lists phone among the formats hiring officials use and says "an applicant may have a phone interview and then an in-person interview", while OPM's guidance says structured interviews can be conducted "over the telephone", that the most highly structured ones ask all applicants the same set of pre-defined lead and probe questions, and that they are usually scored by a panel whose members rate each answer individually before discussing differences. Amazon's program manager page also says a second interviewer may join a remote interview to shadow.

On a panel call you cannot see who is speaking or still writing, so ask for names at the start, address whoever asked each question, and give every answer a predictable shape for raters scoring on their own sheets.

Scheduled calls and unexpected ones

Not every call is booked in advance, and Carnegie Mellon's career centre plans for that: it advises a professional voicemail greeting, answering as "Hello, this is [your name]", and letting unknown calls go to voicemail when you have nothing scheduled. If a recruiter catches you somewhere noisy, our view is that proposing a set time later that day reads as organised, not evasive.

What disappears when the interviewer can only hear you

In a room, a nod tells you to keep going and a puzzled look tells you to explain. On the phone those signals are gone, silence becomes hard to read, and your voice carries everything, which is why Stanford's Oral Communication Program advises you to "use your voice to show enthusiasm (and any other emotion you might express through non-verbals)".

These habits replace the missing signals:

• Signpost before you answer, for example "There are two parts to that, the migration itself and what I would change", so the listener knows the shape and can tell when you have finished.
• Keep first answers short and offer depth, such as "I can go into how we tested it if that is useful", which lets the interviewer steer as a nod would in person.
• Say when you are thinking, because a few seconds of silence on a call can sound like a dropped line; CMU suggests waiting one or two seconds after a question before answering anyway.
• Ask for a repeat when the line is poor, as Stanford recommends, rather than answering a question you half heard.
• Write down a thought that arrives while the interviewer is talking instead of interrupting, which is Hillsdale College's advice and matters more on a call, where you cannot see that the interviewer is about to finish.

CMU says smiling "actually changes the tone of your voice" and suggests standing, which Stanford says can help with projection or nerves; neither changes what you say, but both change how you sound to someone with nothing else to judge.

On a technical screen, silence is worse because the interviewer watches code appear with no commentary. Announce each step before you type, such as "I'll use a hash map from value to index so the lookup is constant time", and say which example or edge case you are tracing; when stuck, Meta's post says to ask questions.

Your setup: phone or computer, and what to have in front of you

Published advice disagrees here. Hillsdale College says not to have a laptop in front of you, because the interviewer can hear you typing; Amazon says to have a computer with a reliable internet connection and access to email, and recommends a headset with a microphone; Stanford suggests a land line if possible. The difference is the call type: a voice call needs nothing on screen, while a meeting-platform call or coding screen cannot happen without the computer.

So for a voice-only call, use a headset or wired earphones on your phone, close the laptop and keep paper notes, and for a platform call or coding screen, use the computer with a headset and notifications off. Amazon says to find strong coverage if you join from a mobile, and CMU says to call straight back if disconnected, so get a number at the start.

Keep your resume, a short list of accomplishments and your questions, a pen and paper and a glass of water in front of you, as Stanford and Hillsdale suggest, and in our view the job description too. CMU says notes are for quick reminders, not reading aloud, and on a call reading is easy to hear because the rhythm flattens, so write key words and numbers rather than sentences.

An illustrative "walk me through your background" for audio only

This example is illustrative: we wrote it to show the techniques, and it does not come from a real candidate. The speaker is a backend developer applying for a platform engineering role; time your own version aloud.

"Happy to. I'll give you three parts: what I do now, the two things I've done that matter most for this role, and why this job.

Right now I'm a backend developer at a payments company, on a team of six that owns our transaction APIs.

The first thing that matters for you: last year I led our move from a single database server to a managed cluster. That took about four months, and we did it without a customer-facing outage.

The second: I set up our on-call runbooks after a bad incident, and our time to resolve dropped by roughly half over the next two quarters.

Why this job: I've realised the part I enjoy most is the platform work, making other engineers faster and safer, and your posting is almost entirely that.

That's the short version. I'm happy to go deeper on the migration or the on-call work, whichever is more useful."

Three choices make it work without video. The opening names three parts, so the interviewer knows how long to listen and can take notes under each heading. The numbers are rounded ("about four months", "roughly half"), because a figure like 47.3 percent is hard to catch on a call. The close offers two places to go deeper, handing back control as eye contact would in a room. For more on this opener, see our guide to making "tell me about yourself" more than an introduction, and our list of common phone interview questions covers what tends to come next.

How to end the call and find out what happens next

When the interviewer asks for your questions, ask one about the work and then ask directly what the next stage is, who it is with, and when you should hear. Timelines differ: Amazon says it tries to respond within two business days, while USAJOBS says scheduling interviews may take time, and knowing the expected date tells you when a follow-up is reasonable.

Thank the interviewer by name, state your interest in one sentence, and send a thank-you email, which CMU recommends and Hillsdale lists alongside a handwritten note. If the line dropped during an answer or you realise you left out the result of a story, our view is that one short sentence in that email fixing it is helpful, while a second attempt at the whole answer is not.

A checklist for the day before and the last 15 minutes

The day before:

• Confirm with the recruiter who is calling, on which number or platform, and for how long.
• Identify which kind of phone interview it is and prepare for that call's focus, not a generic one.
• Rehearse your background answer and two stories aloud, timed, without looking at the page.
• For a technical screen, solve one problem in a plain editor while narrating every step.

The last 15 minutes:

• Go to the quiet room, close other apps or the laptop as the call type allows, and silence notifications.
• Test the headset and, on a meeting platform, join the test link or check your audio settings.
• Stand up for a minute and say your opening sentence out loud to warm up your voice.

Practise the voice-only version with Verve AI

Reading notes silently will not show whether your spoken answers run long; saying them out loud will. Verve AI's AI Mock Interview offers behavioral questions, custom questions and a LinkedIn job description option, and the camera is optional, so you can leave it off and rehearse the call as audio only. Your responses are transcribed and displayed on the transcription pad, so you can read back whether your answers had signposts or rambling openings, and afterwards you get "a detailed performance report with personalized feedback and scoring".

FAQ

How long is a phone interview?

There is no standard length; it depends on the kind of call. Amazon publishes its program manager phone screen as 60 minutes, Meta describes an initial technical screen of 5 minutes of introductions, 35 minutes of coding and 5 minutes of questions, and Google describes recruiter conversations only as shorter calls. Ask the recruiter when the call is booked, and leave some time free afterwards in case it overruns.

Is a phone interview easier than a video interview?

It is different rather than easier: you skip the camera, lighting and eye contact, but lose the interviewer's facial reactions. Signposting, shorter answers and explicit check-ins replace that feedback, and your voice carries more of the impression you make.

What should I do if a recruiter calls without warning?

CMU's advice is to let unknown calls go to voicemail when you have nothing scheduled, and to answer professionally when you do pick up. If you are not in a good place to talk, it is reasonable to thank the recruiter and propose a specific time later that day or the next. That gives you time to move somewhere quiet, find your notes and check which kind of call it will be.

Sources

• Amazon phone screening (Zoom or Amazon Chime, headset with microphone, computer with reliable internet and email, strong network coverage on mobile, resume and pen and paper, transcription on some Zoom interviews with consent, response within two business days): https://amazon.jobs/content/en/how-we-hire/phone-screening
• Amazon program manager phone screen (senior leader, 60 minutes, half behavioral on Leadership Principles and half functional; second Amazonian may shadow a remote interview): https://amazon.jobs/content/en/how-we-hire/program-manager-interview-prep
• Amazon SDE II coding expectations (Livecode, "syntactically correct code—no pseudo code", "think out loud"): https://amazon.jobs/content/en/how-we-hire/sde-ii-interview-prep
• Google recruiter conversations (one or two shorter calls over phone or video that "usually assess key skills you'll need for the role", location preferences): https://www.google.com/about/careers/applications/how-we-hire/
• Meta initial technical screen (video chat or in person with a Meta engineer, 5 minutes introductions, 35 minutes coding on two problems, 5 minutes questions, collaborative editor when remote, "can be as important as having the right answer", ask questions when stuck): https://www.metacareers.com/blog/preparing-for-your-software-engineering-interview-at-meta/
• Salesforce virtual technical screening (shared screen "so the interviewer can see how you decompose problems", quiet place, check phone and internet): https://trailhead.salesforce.com/content/learn/modules/strategies-for-successful-software-engineer-interviews/complete-the-virtual-technical-screening
• USAJOBS interview formats (panel, in person, video, phone; phone interview then in-person interview; scheduling may take time): https://usajobshelp.opm.gov/hc/en-us/articles/52846644688019-How-does-the-application-process-work
• OPM structured interviews (same questions and probes, "over the telephone", panel members rate individually then discuss, benchmarks): https://www.opm.gov/policy-data-oversight/assessment-and-selection/other-assessment-methods/structured-interviews/
• Carnegie Mellon telephone interview tips (voicemail greeting, "Hello, this is [your name]", let unscheduled unknown calls go to voicemail, smile "actually changes the tone of your voice", try standing, wait 1-2 seconds, call back if disconnected, notes for reminders but do not read, thank-you email): https://www.cmu.edu/career/documents/quick-tips/telephone-virtual-interview.pdf
• Stanford Oral Communication Program phone tips (voice to show enthusiasm, stand for projection or nerves, resume and notes in front of you, water, ask for a repeat, land line if possible): https://oralcommprogram.stanford.edu/mock-interviews/phonevideo-interview-tips
• Hillsdale College phone interview tips (no laptop because of typing and notifications, write thoughts down instead of interrupting, materials in front of you, thank-you note): https://www.hillsdale.edu/hillsdale-blog/career-services/10-phone-interview-tips/
• Verve AI Mock Interview (question banks including Behavioral Questions, Custom Questions and LinkedIn job description, camera optional, transcription pad, report wording): https://docs.vervecopilot.com/features/mock-interview