11 Phone Interview Questions With Sample Answers (2026)

The recruiter calls Wednesday at 2pm. Twenty minutes later they decide whether you move forward. That is the phone interview, and despite how short it is, it is where most candidates get filtered out. Not because they are unqualified, but because they treated the call like a casual chat instead of an interview.

The good news is that phone interviews are predictable. The same 10 to 12 questions show up across industries, and once you know what each one is testing for, you can prepare answers that get you through to the next round without sounding rehearsed.

What the Phone Screen Is Actually For

Phone interviews are screening calls, not in-depth conversations. The recruiter or hiring manager is checking three things: do your basic qualifications match the role, are your salary expectations and timing realistic, and do you come across as professional enough to send to the hiring team. That is it.

This means you do not need to convince them you are perfect. You just need to give them no reason to filter you out. Concise answers, clear motivation, and steady tone do most of the work.

11 Common Phone Interview Questions and Sample Answers

1. What do you know about our company?

They are checking whether you researched them or are mass-applying. Skim the homepage, the careers page, the last earnings call (if public), and the founder's recent LinkedIn posts. Then mention one specific thing that caught your attention.

"You shipped your AI summarization feature last month and the customer reaction looked strong. The fact that you went deep on accuracy instead of speed-to-market is what made me apply, because that matches how I prefer to build."

2. Why did you apply for this position?

They want to know if you are excited about the actual job or just the paycheck. Pick something specific to the role: a tech stack, a customer base, the team's recent work, or a clear growth path.

"Two reasons. First, your engineering team owns features end to end, which is the model I do my best work in. Second, the role would put me on infrastructure that serves enterprise clients, and I want to grow into that scale of system design."

3. Tell me about yourself.

Past, present, future, in 90 seconds. Skip the childhood. Skip the unrelated hobbies. Stick to the professional through-line that brought you to this conversation.

"I started in B2B sales out of college, moved into customer success after two years because I wanted more depth in the product, and have spent the last three years leading the CS team at a 200-person SaaS company. Now I'm looking for a senior CS role at a company where I can build playbooks from scratch instead of inheriting them, which is what drew me to this listing."

4. What are your salary expectations?

Research the range first using levels.fyi, Glassdoor, and Payscale. Give a range with the floor at what you would actually accept, not below.

"Based on the role and my experience level, I'm looking in the $130K to $150K range, with flexibility depending on equity and benefits. Does that fit the band you have for this role?"

That last question matters. It pushes them to confirm or recalibrate, which surfaces budget mismatches early.

5. What is your earliest start date?

Be honest about timing. Two weeks if you are working, immediately if you are not, and longer if you have a real reason (relocation, exam, family commitment).

"I would give my current employer two weeks' notice, so I could realistically start three weeks from an offer. I'm intentionally avoiding any earlier start because I want to leave my current team in a good place."

6. Why did you leave your last job?

Never bad-mouth your former employer, even if they deserve it. Frame it forward: what you learned, what you are looking for next.

"I'd been at the company for four years and had outgrown the role. The team is solid; there just was not a clear next step that matched where I want my career to go. I'm looking for a role with broader scope, which is why this one caught my attention."

7. What motivates you?

They know money is part of the answer. They want to hear what else is true. Be specific.

"Solving a problem nobody has cracked yet. The job I enjoyed most was a six-month project rebuilding our deployment pipeline. Nobody had documented why it was broken, so we essentially had to redesign from first principles. Going from a brittle process to one the team trusted was more satisfying than the bonus that came with it."

8. What are you most proud of?

This one is broader than the previous question. It does not have to be work-related, but if you choose something personal, make it specific and brief.

"I built a side project last year that helps small nonprofits track grant deadlines. It started as a tool for my mom's organization and now five other nonprofits use it. The fact that the thing I made on weekends is being used by real people every day is something I think about often."

9. Tell me about a problem you solved.

Use the STAR method: Situation, Task, Action, Result. Pick a problem relevant to the role and quantify the result.

"As CS lead, our renewal rate had dropped to 78 percent. I dug into the data and noticed half the churned accounts had not had a check-in in the last 90 days. I built a simple system that flagged accounts at 60 days without contact, and we wrapped a low-effort outreach playbook around it. Renewals climbed back to 91 percent within two quarters."

10. What can you bring to this role?

Pull from the job description and connect each requirement to a story you can tell. Avoid generic phrases like "I'm a hard worker."

"Three things specifically. I've shipped two production ML systems, which matches your tech stack. I've worked across product and engineering on cross-functional projects, which is the model your job description describes. And I've mentored junior engineers, which I noticed is part of the senior expectations here."

11. Do you have any questions for me?

Saying no is the worst possible answer. It signals disinterest and is one of the more common interview mistakes. Bring three questions, ask one or two.

Good ones for a phone screen:

What does the rest of the interview process look like, and what is the timeline?
What is the team working on right now that you are most excited about?
What separates someone who is great in this role from someone who is just good?

How to Prepare for a Phone Interview

Research the company. 30 minutes minimum. Homepage, recent news, the interviewer's LinkedIn.
Know who you are talking to. Look up the recruiter or hiring manager so you can ask informed questions about their background.
Have your resume in front of you. Open on your laptop. Reference specific bullets when answering questions about past roles.
Pick a quiet spot. Mute notifications, lock the door, and warn anyone in the house. Background noise tanks the impression instantly.
Pen and paper ready. Take notes on what they say. You will use these in your follow-up email and later interviews.
Test your signal. If you are on a VoIP call, run a 60-second test call ahead of time. Bad audio is the easiest way to lose the room.
Prepare your three questions. Specific, role-relevant, written down.

4 Tips for the Call Itself

Listen More Than You Think You Need To

You cannot read body language on a phone call, so verbal cues matter more. Pause before answering, even if just for a second, to make sure you understood the question. If anything was unclear, ask them to clarify before answering. That signals confidence, not weakness.

Slow Down Your Pace

Most people speak faster on the phone than they realize, especially when nervous. Aim for slightly slower than feels natural. The recruiter is taking notes; you want to give them time to capture what you said.

Stay Professional, Not Casual

Phone calls feel more conversational than video, which trips up candidates who get too loose. Keep it polite and measured. Do not interrupt. If you accidentally talk over them, apologize briefly and let them finish.

Dress for the Call (Yes, Really)

You will sound different in pajamas at the kitchen table than you will in business casual at a desk. The act of putting on real clothes and sitting up shifts your tone. Try it once and you will hear the difference.

The Follow-Up Email

Within 24 hours of the call, send a short thank-you note. If you have not heard back after 7 to 10 business days, send a check-in.

Sample check-in:

"Hi Adam, hope your week is going well. Following up on our conversation last week about the project manager role, I wanted to check where the process stands. I'm still very interested and happy to provide anything else that would be helpful. Thanks again for the time."

Final Thoughts

Phone interviews reward preparation more than personality. The candidates who consistently get to round two are not the most charismatic; they are the ones who treat the screening call like a real interview, with researched answers, specific questions, and a quiet room.

One thing the recruiter almost certainly has open during the call is your resume. If it is generic or buries the experience the role needs, no amount of phone-call performance will save you. Run your resume through ZapResume's free review before the next phone screen, so the document working alongside you is doing its job.