How to Prepare for a Phone Interview: Checklist & Answers

By Codinn · Written October 21, 2026

To prepare for a phone interview, confirm the call details, match three job requirements to examples from your experience, rehearse a short introduction, and test your audio in a quiet place. Keep your resume, the job description, brief notes, and questions within reach.

If the interview is today, start with the 30-minute preparation plan. If you have more time, work through the examples below and finish with the copyable prep sheet.

This guide is for US job seekers, including college students, recent graduates, junior developers, and people returning to the market after a layoff. The sample answers are fictional teaching examples, not recruiter-approved scripts or guarantees of an offer. Replace every detail with something true about your experience.

On this page

• Know which kind of phone interview you have
• Your 30-minute preparation plan
• Research the role and choose your evidence
• Seven phone interview questions and sample answers
• Copyable phone interview prep sheet
• Phone interview checklist
• Handle a late call, bad connection, or unexpected question
• Follow up after the call
• Frequently asked questions
• Sources and further practice

Know which kind of phone interview you have

A phone interview describes the communication channel, not necessarily the assessment. Before preparing, check the invitation for the interviewer's role, the scheduled duration, and any instructions about coding or screen sharing.

Interview type	What to prepare	What to confirm
Recruiter phone screen	A concise background summary, relevant experience, interest in the role, and practical availability	Who calls whom, the time zone, and the next hiring stage
Hiring-manager conversation	Project decisions, collaboration examples, and questions about the team's work	Whether the conversation includes a detailed project walkthrough
Technical phone interview	Relevant fundamentals, problem-solving practice, and an explanation of your approach	Whether you need a laptop, coding environment, or shared document

CareerOneStop distinguishes initial screening from behavioral interviews and skill demonstrations. Do not assume that every call is only an informal introduction.

If the invitation is unclear, send:

Thanks for arranging the interview. Could you confirm whether this will be a recruiter conversation or a technical assessment, and whether I need anything besides my phone?

Use the calendar invitation to check the conversion between your local time and the interviewer's time zone. For a US employer, confirm whether the meeting time is Eastern, Central, Mountain, Pacific, or another specified zone; do not guess from the company's headquarters.

Your 30-minute phone interview preparation plan

This is a suggested preparation schedule, not a claim that every interview can be prepared for in half an hour. A coding assessment or unfamiliar role may need substantially more practice.

Time	Action	What you should have when you finish
Minutes 0–5	Open the invitation, resume, and job posting. Confirm the format and call details.	The correct number or meeting link, contact name, time zone, and backup contact
Minutes 5–12	Pick three important requirements and connect each to a real example.	Three short evidence notes, including your individual contribution
Minutes 12–20	Say your introduction and two project or teamwork answers aloud.	Answers you can explain without reading paragraphs
Minutes 20–25	Choose questions and prepare for availability and compensation discussions.	Two role-specific questions and accurate logistical details
Minutes 25–30	Test your setup and put your prep sheet within reach.	A charged phone, working microphone, quiet setting, and water

Only have five minutes? Check the call details, write one sentence about your relevant experience, choose one example you can explain, prepare one question, and test your connection. Do not spend the whole window researching interview tips.

Have a full day? Add a practice call with someone who has not seen your resume. Ask them which parts were unclear, where you rambled, and what evidence they remember. Revise those answers rather than memorizing more scripts.

Research the role and choose your evidence

Build a requirement-to-example map

Open the actual job posting, not a generic description of the occupation. Select three responsibilities you understand well enough to discuss. For each, write what you did, how you did it, and what happened.

For a junior frontend developer, a practice map might look like this:

Requirement in the posting	Evidence you could use, if true	Detail to be ready to explain
Build accessible interfaces	A class project with keyboard-accessible forms	How you labeled inputs and tested the keyboard flow
Work with APIs	A portfolio application that fetches search results	How you handled loading, an empty response, and a failed request
Collaborate with other developers	A group assignment, internship, or open-source contribution	Your part of the work and how feedback changed it

If you do not have paid experience, coursework, part-time work, volunteer work, and personal projects can provide relevant examples. Be clear about the setting. A class prototype is not a production system, and a team result is not automatically your individual achievement.

Research enough to ask a real question

Read the employer's product or service page and the specific job description. If you use recent news, verify it against the company's own announcement before mentioning it. Write down one connection between the work and your interests.

Replace “I love your innovative culture” with something you can discuss: “The posting mentions improving the account setup flow. How does the team decide which onboarding problems to tackle first?”

Explain technical work without assuming technical knowledge

For a recruiter conversation, start with the problem and your contribution before naming tools. For a technical interviewer, be ready to go deeper into trade-offs, testing, and limitations.

Instead of listing “React, JavaScript, REST, Git,” try: “I built the search interface, connected it to an API, and made sure users could recover from failed requests.” Then explain the implementation if asked.

Seven phone interview questions and sample answers

These are seven useful questions to rehearse, not a universal ranking of the most common questions. Interviewers can ask different questions depending on the role and hiring stage.

1. Tell me about yourself

Use a simple sequence: your current focus, one relevant example, and why this opportunity makes sense. Aim for roughly a minute as a practice target, not a strict rule.

Recent-graduate example:

I recently completed my computer science degree, and I've been focusing on frontend development. In my capstone project, I owned the search and filtering interface for a campus events application. I worked on the React components, handled failed API requests, and tested the keyboard navigation. I'm looking for a junior role where I can contribute to a product while getting better at testing and code review. This opening stood out because it combines UI work with support from a larger engineering team.

Why this is useful: it gives the interviewer an understandable starting point and a specific project to ask about. Do not add an improvement percentage unless you measured it and can explain the method.

2. Why are you interested in this role?

Connect a responsibility in the posting to work you want to do. Mention something specific about the employer without pretending you have used a product you have never tried.

Example:

The role describes improving customer-facing forms and working with designers. That's work I enjoyed in my internship, especially turning feedback into clearer validation messages. I also noticed your team supports small-business customers. I'd like to understand how their feedback reaches engineering and contribute to making those workflows easier to use.

Avoid making the whole answer about needing any job. The interviewer needs to understand the match, not a declaration that this is your only acceptable employer.

3. What experience do you have that matches the job?

Choose one requirement and make the connection explicit. If your experience is adjacent rather than exact, say so.

Career-transition example:

I haven't worked on a large production React application yet. My closest experience is a volunteer scheduling tool where I built the sign-up flow and handled validation. In my previous support role, I also investigated user reports and wrote reproducible bug descriptions. Those experiences connect to the UI development and troubleshooting responsibilities in this posting, although I'd need to learn your production workflow.

This is more useful than claiming expertise in every listed technology. Be ready for a follow-up about the code, decisions, and help you received.

4. Tell me about a challenge or mistake

For a behavioral answer, use Situation, Task, Action, Result (STAR) as an organizing framework. Keep the setup short and spend more time on what you actually did. Yale's interview preparation resources include behavioral interview guidance and accomplishment-story practice.

Junior-developer example:

In a group project, our demo failed when the API returned an empty list. I was responsible for the results component, and I'd only tested it with populated data. I added an explicit empty state, wrote down cases for loading and failed requests, and asked a teammate to review the flow. The next demo handled those cases correctly. Since then, I check missing and unsuccessful responses before calling a feature complete.

Explain a real result, even if it is qualitative. Do not turn every mistake into an implausible success story or blame teammates for your part of the problem.

5. Why are you leaving, or why did your last role end?

Give a brief, accurate explanation, then return to the work you are seeking. You do not need to manufacture a positive reason for a layoff.

Layoff example, only if accurate:

My role ended during a team reduction. Since then, I've been maintaining a small React project and reviewing the areas I want to strengthen, particularly testing. I'm now looking for a frontend position where I can contribute to an established product and work closely with other engineers.

If you are still employed, focus on what you want next rather than criticizing your manager. If you took time away for personal reasons, decide in advance how much you are comfortable sharing and keep your explanation truthful.

6. What are your salary expectations, and when can you start?

Prepare these as two separate answers. For compensation, understand whether the discussion concerns annual base salary, hourly pay, or a package that includes other compensation. Research the role, location, level, and employer's posted range rather than borrowing a number from an unrelated job.

Compensation conversation starter:

Could you share the budgeted base salary range for this position? I'd like to understand the level and responsibilities before narrowing down expectations. I'd also want to consider the full package and work arrangement.

The interviewer may still ask for your range. Decide beforehand what you can reasonably discuss, and distinguish a target from a firm minimum. This is a preparation approach, not compensation or legal advice.

Availability example:

I could start two weeks after accepting an offer. I'm available for the next interview stage on Tuesday or Thursday afternoon, Eastern Time.

Use a start date you can actually meet. Answer work-authorization questions accurately if they arise; for individual immigration questions, seek qualified guidance rather than relying on an interview script.

7. What questions do you have for us?

Choose two questions that help you evaluate the job. A recruiter may not know detailed architecture decisions, so match the question to the person.

For a recruiter:

• What are the remaining interview stages, and what does each assess?
• Is this role tied to a particular office, time zone, or work schedule?

For a hiring manager:

• What would a successful first three months look like for someone at this level?
• How do junior developers receive feedback on their code?
• What problem would you want this person to help solve first?

Listen for information that affects your own decision. An interview is also a chance to understand whether the role fits your needs.

Copyable phone interview prep sheet

Copy this template into your notes and replace the prompts. Keep it short enough to scan without losing the conversation. It requires no account, email address, or AI subscription.

PHONE INTERVIEW PREP SHEET

Company / role:
Interviewer / role:
Date / time / time zone:
Who calls whom / phone number or link:
Backup contact / agreed reconnection plan:

MY INTRODUCTION — bullet prompts, not a script
Current focus:
One relevant example:
Why this role:

THREE REQUIREMENTS → MY EVIDENCE
1. Requirement / example / my contribution:
2. Requirement / example / my contribution:
3. Requirement / example / my contribution:

TWO STORIES TO PRACTICE
Problem / action I took / result / lesson:
Teamwork / action I took / result / lesson:

PRACTICAL DETAILS
Possible start date:
Work location / schedule questions:
Compensation questions / researched range:

QUESTIONS FOR THE INTERVIEWER
1.
2.

AFTER THE CALL
What I learned:
What I need to clarify:
Next step / expected timeline:

Prepare notes from information you are entitled to share. Exclude customer data, private code, and confidential details from a former employer.

Phone interview checklist

The day before

• Confirm the date, time zone, interview format, and who initiates the call.
• Save the job posting and the version of your resume you submitted.
• Prepare your introduction, three evidence notes, and two questions.
• Test a call from the place where you plan to interview.
• Rehearse at least one answer without looking at your notes.
• Ask the recruiting contact in advance about any access arrangements you need.

Before the call

• Charge your phone and test the microphone or headset you will use.
• Silence distracting notifications without blocking the interviewer's call. Check unknown-caller settings and any call-filtering app.
• Close noisy applications and tell other people nearby that you need quiet.
• Place your resume, job posting, notes, pen, and water within reach.
• Leave a buffer around the scheduled slot rather than booking another commitment immediately afterward.

Yale's phone interview guidance recommends a quiet location, concise note prompts, and clear speech. If a private room is difficult to find, ask your college career center or local library whether a suitable room is available; availability and booking rules vary.

During the call

• Answer with your name and confirm that you are speaking with the expected person.
• Let the interviewer finish before answering. A short pause is fine.
• Ask for clarification rather than guessing what a vague question means.
• Use notes as prompts, not text to read aloud.
• Ask about the next step and expected timeline before ending.

Handle a late call, bad connection, or unexpected question

The interviewer has not called

Check the time zone, missed calls, voicemail, and invitation instructions first. If the call is late and you have no update, use the existing recruiting email thread to check in politely. For example:

Hi Jordan, I'm available for our scheduled interview and wanted to confirm that the time still works. You can reach me at the number in our invitation. Please let me know if we need to adjust the schedule.

There is no universal waiting period. Follow any employer instructions, avoid repeated messages, and explain your availability if you cannot keep waiting.

You cannot hear the interviewer

Say so promptly: “The audio is breaking up, and I want to make sure I answer your question correctly. Could you repeat the last part?” If necessary, propose using the backup number or rescheduling. Do not pretend to understand and answer a different question.

You receive an unexpected screening call

If you are driving, working, or somewhere unsuitable, ask to schedule a focused conversation. Offer a couple of alternatives instead of trying to interview while distracted.

You do not know a technical answer

State what you know, identify the gap, and explain how you would investigate. For example: “I haven't used that library. I've handled a similar requirement with native browser APIs; could I explain that approach?” Do not claim experience you cannot discuss.

You want to use AI to prepare

Before the interview, you can ask a tool to play an interviewer or point out unclear parts of an answer. Use redacted, nonconfidential information and check any factual suggestions. A practice prompt is:

Ask me one junior frontend recruiter-screen question at a time. After I answer, identify one vague claim and ask for evidence. Do not invent achievements or rewrite my background.

Follow the employer's rules during the actual assessment. Do not secretly outsource answers, record the conversation, or send the interviewer's words to another service without the necessary permission. You should be able to explain every example yourself.

Follow up after the call

Write down what you learned while it is fresh: the work, the hiring stages, any preparation instructions, and the expected timeline. If appropriate, send a short thank-you message later that day or the next business day; treat this as a courtesy, not a hiring shortcut.

Adaptable thank-you email:

Subject: Thank you — Junior Frontend Developer conversation

Hi Jordan,

Thank you for speaking with me today about the frontend opening. I appreciated learning how the team approaches accessibility reviews. The opportunity to improve customer-facing forms connects with the project experience we discussed.

I'm interested in continuing the conversation. Please let me know if you need anything else from me before the next stage.

Best, Alex

Replace the role, names, and conversation detail. If you do not hear back, use the timeline you were given to decide when to send a brief follow-up. Continue your broader job search rather than treating one call as an offer.

Frequently asked questions

How long does a phone interview take?

Use the duration in your invitation as your planning baseline, and ask if it is missing. Recruiter screens and technical interviews are different formats, so there is no single reliable duration for every phone interview. Leave time for setup and possible delays, and ask before the call if you have a firm end time.

How do I prepare for a phone interview with no experience?

Choose examples from school, volunteer work, part-time jobs, or personal projects that demonstrate the requirements in the posting. Explain your own contribution, a problem you handled, and what you learned. Be direct about the limits of your experience rather than presenting a practice project as paid employment.

Can I use notes during a phone interview?

Brief notes can help in a recruiter conversation. Keep the job description, resume, questions, and a few example prompts nearby, but avoid reading full answers. For an assessment, follow the employer's instructions about permitted materials and ask beforehand if the rules are unclear.

What should I wear to a phone interview?

For an audio-only call, choose something comfortable that helps you focus. If the invitation includes video or the format might change, confirm the requirements and prepare accordingly. Your preparation should not depend on buying a new outfit for a call where you will not be seen.

How is an internship phone interview different?

Focus on relevant coursework, projects, availability, and what you can contribute while learning. Ask whether there will be a separate technical assessment. The word “internship” does not establish the duration or guarantee that the interview is informal; confirm the schedule with the recruiter.

Sources and further practice

The examples and preparation schedule above were created for this guide. These US career resources provide additional context; they do not endorse Codinn or the sample answers:

• Yale Office of Career Strategy: phone and video interview preparation.
• Yale Office of Career Strategy: interview preparation and interview types.
• CareerOneStop: screening, behavioral, and skill-demonstration interviews, sponsored by the US Department of Labor.

If your next round includes frontend coding, continue with JavaScript output-prediction interview practice or React coding interview questions. These are technical practice resources, not substitutes for researching the employer or preparing your own experience examples.

Your next action: fill in the prep sheet for one actual job posting, then say your introduction aloud without reading it.