How to prepare for a phone interview: what the screen is checking, what to do before, during and after the call, the first lines to say, common phone screen questions with short sample answers, and how AI can help you practice.
The best phone interview tips are simple: prepare as you would for an in-person interview, take the call in a quiet room with your resume and notes in front of you, and speak a little slower and warmer than feels normal, because your voice is all they get. Have a short opening ready, answer each question and stop, and ask what happens next before you hang up.
A phone interview is usually the first round, a short screen to check that you fit the basics before the employer spends more time on you. The UK National Careers Service says a phone interview "usually takes place in the early stages of applying for a job" (NCS, phone interview tips). Clemson's career center says employers use it to screen candidates and judge communication skills, professionalism and fit (Clemson Center for Career and Professional Development).
Below: a checklist for before, during and after the call, a script for the first 30 seconds, common phone screen questions with short sample answers, and how AI can help you prepare (mock calls, answer drafts, timing) without making you sound scripted.
Key takeaways
On this page
Most phone screens are run by a recruiter or someone in HR, not the hiring manager. They are trying to answer a few plain questions:
India angle: many freshers get a short call from HR (often called a telephonic round) before a campus or off-campus interview. The same checklist works. Keep your college, branch, graduation year and one project ready to say in a sentence each.
This is how to prepare for a phone interview, step by step. The items come from the career services listed at the end of the page, plus a few practical steps of our own (marked "practical").
| When | Do this | Why |
|---|---|---|
| When you are invited | Write down the date, time, time zone, the caller's name, the company and the role. Check they have the right number for you. | NCS lists exactly these details. The role matters if you have more than one interview lined up. |
| Same day | Ask who calls whom, and what happens if the line drops. | FGCU suggests confirming who calls back if you get disconnected. MIT CAPD suggests keeping the interviewer's number as a backup. |
| Days before | Read the job description and your resume side by side. Pick three to five stories that prove what they ask for. | NCS: prepare as you would for a face-to-face interview, and use the STAR method to plan answers. |
| Days before | Write 2 or 3 questions to ask them. | NCS suggests questions like what training there is and what an average day looks like. |
| Days before | Do one mock call out loud, or record yourself and play it back. | NCS: listen for a clear voice, a calm pace and whether you sound keen. |
| The day | Charge your phone. Find a quiet room. Put your resume, notes, questions, a pen and paper in front of you. | NCS and FGCU both list these. Your notes are the one advantage a phone call gives you. |
| 10 minutes before | Be ready and settled. Drink some water. Say your opening once out loud. | NCS suggests being ready 10 minutes early to settle yourself. |
| During | Use the interviewer's name. Pause briefly before you answer. Ask them to repeat a question you did not catch. Say so if the line is bad. | FGCU (names build rapport) and NCS (leave a small gap so you do not talk over them). |
| During | Keep an eye on a clock. | FGCU: respect the time the interviewer set. |
| End of call | Thank them and ask when you can expect to hear back. | NCS says it is fine to ask about the timeline. |
| Within the hour | Write down every question they asked and how you answered. Note two things that went well and one to fix. | NCS suggests reflecting on 2 or 3 things that went well and what to do better. |
| Same day | Send a short thank-you email that repeats one strong point. | Practical. The thank-you email after interview tool writes one. |
Want the general version for any round? The interview preparation checklist breaks it down by how much time you have left.
The first half minute sets the tone. Phone screens often start with small talk and then "tell me about yourself" straight away. Have both ready. This is a sample; swap in your own words.
Answering: "Hello, this is Priya speaking."
They introduce themselves: "Hi Daniel, thanks for calling. Yes, it's a good time. Can you hear me clearly?"
They explain the call: "That sounds great. I have the job description in front of me, and I'm looking forward to it."
"So, tell me about yourself": "Sure. I'm a customer support specialist with three years at a software company, where I work the busiest support queue on our team. Two things I'm proud of: I rewrote our help articles so fewer people needed to call, and I trained four new hires. I'm looking for a role where I can do more of the training side, which is why this one caught my eye."
Why it works: you confirm they can hear you (FGCU notes most interviewees do not speak loudly enough and suggests asking this at the start), you sound ready, and your opening is under a minute with one clear reason you want the job. Build your own with the tell me about yourself guide.
If the call comes at a bad time (an unscheduled recruiter call): "Thanks for calling. I'm not somewhere I can talk properly right now. Could we do this at 4 today or 10 tomorrow?" Taking the call in a noisy street is worse than moving it.
On the phone, your voice carries everything your face and posture would. FGCU's phone interview page gives a short list: tone, pitch, volume, tempo, clarity, hesitation, pauses and language. In practice that means:
If your mind goes blank mid-answer, a bridging line buys time. The mind went blank phrases tool has a few to practice.
Phone screen questions are mostly about fit and logistics. These samples are written for this page to show the shape of a good answer. They are not real candidates' answers; change every detail to match you.
| Question | What they check | Short sample answer |
|---|---|---|
| Tell me about yourself. | Can you summarize clearly? | "I'm a final-year computer science student. I built a library booking app with two classmates that our college now uses, and I've done a summer internship in testing. I'm applying because this role mixes testing and development." |
| Why are you interested in this role? | Did you read the job post? | "The post mentions owning onboarding for new clients. I did that informally in my last job and enjoyed it most, so a role built around it fits." |
| Why are you leaving your current job? | Any red flags? | "I've learned a lot, but the team is small and there's no path into analytics there. This role has one." |
| Walk me through your resume. | Does the story hang together? | Start at the most relevant job, not the oldest. One line per role, then stop and let them pick what to ask about. |
| What are your salary expectations? | Are you in budget? | "I'd like to understand the role better first. Could you share the range budgeted for it?" If pressed, give a researched range: "[low] to [high], depending on the full package." |
| When could you start? | Notice period, availability. | "My notice period is four weeks, so I could start four weeks after an offer." |
| Are you authorized to work here? Will you need sponsorship? | A basic filter. | Answer plainly and truthfully. Guessing here causes trouble later. |
| Tell me about a time you solved a problem. | A first look at how you work. | Use STAR in under two minutes: the situation in one line, your task, what you did, and the result you can name. |
| Do you have any questions for me? | Interest. | "What does success look like in the first three months?" and "What are the next steps after this call?" |
More of these, with frames for each, are in the common HR interview questions guide. For the pay question, the salary expectations answer generator writes both versions: the first answer that asks for their range, and the one to use if they push for a number.
| Mistake | The fix |
|---|---|
| Taking the call on the move, with traffic or a bad signal. | Move the call, or go somewhere quiet. FGCU says to make sure the signal is stable. |
| Reading answers word for word from notes. | Notes hold keywords and numbers only. Full sentences make you sound like you are reading. |
| Long answers that wander. | Answer, give one example, stop. Silence after you finish is their turn, not a gap to fill. |
| Typing loudly while they talk. | Write notes with a pen, or type only short words after they finish. |
| Not knowing who called. | Write the name down when they introduce themselves and use it once or twice. |
| Hanging up without the next step. | Ask: "What are the next steps, and when should I expect to hear back?" |
AI is most useful before the call. MIT's career office has a page on using AI for interview prep, and its advice fits phone screens well (MIT CAPD, Using AI for interview prep):
MIT also lists what not to do. "The biggest trap: memorizing answers word-for-word." Check any company facts the AI gives you, because they can be out of date. And AI "cannot help with fine-tuning your delivery", so pair it with a real mock interview with a person. MIT also warns you to think about what personal data you upload with your resume.
One free way to do the practice part: the AI mock interview reads questions for your role out loud, asks follow-ups on what you said, and reports pace, filler words, pauses, answer length and STAR structure. It runs in the browser and does not store recordings.
ClapAssist is a desktop app for Mac and Windows. It listens to the call audio playing on your computer and shows a suggested answer drawn from your resume and the job description. That means it can only hear a call that runs on your computer, such as a Zoom, Google Meet or Microsoft Teams call. It does not help with a call you take on your mobile phone. For a true phone call, use it to prepare instead.
Some employers do not allow AI help during interviews or assessments. Check the employer's rules before using any live help, and when in doubt, ask. Live call audio and screenshots are never stored; your resume, notes, the written recap and the interview transcript are saved to your account (you can switch transcripts off in Settings and delete them any time).
Outside pages that back the advice above, opened and checked on the date shown.
ClapAssist is a desktop app for Mac and Windows. During a Zoom, Google Meet or Teams call on your computer, it shows a suggested answer from your resume. It does not work on a call taken on a mobile phone. Some employers do not allow AI help in interviews, so check first.
Prepare as you would for an in-person interview, take the call in a quiet room with your resume and notes in front of you, confirm they can hear you, speak a little slower than normal, answer each question and stop, and ask about next steps before the call ends.
It varies by employer, so ask when the call is booked. Many screens are short first-round calls. Keep an eye on a clock during the call and respect the time the interviewer set, as Florida Gulf Coast University suggests.
Yes. The UK National Careers Service suggests having your CV, application and prompt cards in front of you. Keep notes to keywords and numbers so you do not sound like you are reading.
Use it to predict likely questions from the job description, narrow them to what a short call would cover, shape your stories into STAR, and run a mock call with feedback. Say answers in your own words rather than memorizing them, check any company facts, and practice once with a real person too.
No. ClapAssist is a desktop app for Mac and Windows and only hears call audio playing on that computer, such as a Zoom, Meet or Teams call. For a call on your mobile, use AI tools to prepare beforehand. Some employers do not allow AI help during interviews, so check their rules first.
Thank them for their time, say in one line why you are interested, and ask what the next steps are and when you can expect to hear back. Then send a short thank-you email the same day.
ClapAssist hears the call from your own computer, so it works with any interview that plays through your speakers or headphones: the apps above, a call in a browser tab, a coding round shared on a video call, or a phone call taken on your laptop. No bot joins the meeting and nothing is installed on the interviewer's side. It is not built for locked-down test sites like HackerRank or CoderPad.
ClapAssist gives every account 10 free interview minutes, once, with no card. Test it on a practice call on your computer first.