Phone screen interview questions: what recruiters and engineers ask, and how to answer

A phone screen is a short first interview that decides whether you move on to the full loop. A recruiter screen usually runs 15 to 30 minutes and checks your background, motivation, pay expectations and logistics. A technical phone screen, often 45 to 60 minutes with an engineer, checks that you can do the work. Both reward short, clear answers you have already said out loud.

What is a phone screen interview?

It is a filter. The company has more applicants than interview slots, so someone spends a short call confirming that you match the role on paper, that the basics line up, and that a longer interview is worth everyone's time. Despite the name, many screens now happen on a video call with the camera off or on, but the format stays the same: one person, one conversation, little time.

The bar is not "impress me." It is "give me no reason to stop here." Clear, specific and brief answers move you forward. Rambling, vague motivation or a mismatch on logistics are the usual reasons a screen ends the process.

Recruiter screen versus technical phone screen

• Who runs it. A recruiter or talent partner for the first, an engineer or hiring manager for the second.
• What they check. The recruiter checks fit, motivation, salary range, location, work authorization and timing. The engineer checks skills, usually with a coding problem or a set of concept questions.
• What they write down. The recruiter writes a short summary for the hiring manager. The engineer writes a hire or no-hire signal with notes on how you solved the problem.
• How to prepare. For the recruiter, your opener, your reasons and your logistics. For the engineer, two or three practice problems out loud in the language you will use.

Some companies combine them, or have the hiring manager run a screen that covers both. If the invitation does not say, ask the recruiter what the call will cover. It is a normal question.

Common recruiter screen questions

Walk me through your background

This is "tell me about yourself" with a little more chronology. Give the short map: what you do now, one result you are proud of, and why this role is the next step. About a minute. The recruiter has your resume and wants to hear how you connect it. The full method is in tell me about yourself interview practice.

Why are you looking?

Say what you are moving toward, not only what you are leaving. One honest sentence about the reason, then the part of this role that pulls you. Avoid criticizing your current employer, even if it is deserved. Why are you leaving your job has examples for layoffs, stalls and bad fits.

Why this company, or why this role?

Name one specific thing about the role or the product and connect it to your experience. A compliment about the company's culture is not a reason. Why do you want to work here goes deeper.

What are your salary expectations?

This one gets its own section below, because it is the question people most often answer badly.

Logistics questions

• When could you start? Know your notice period and any dates you cannot move.
• Are you authorized to work here, and will you need sponsorship? Answer plainly.
• Are you open to the location or the in-office days? Know your actual limits before the call.
• Are you interviewing elsewhere? A short, honest answer is fine: "Yes, I'm in early stages with a couple of companies." You do not have to name them.

How to answer the salary question without inventing a number

The worst answer is a figure you made up on the spot. Too low and it may anchor the offer. Too high without a reason and it can end the conversation. Do the research first, and prepare one of three honest answers.

1. Research before the call. Look for a range in the job posting, since some places require employers to publish one. Ask people you trust who work at a similar level. Note whether the range you find is base salary or total compensation.
2. Ask for their range first. It is reasonable to ask what the budgeted range is before you answer. Many recruiters will tell you.
3. Give a researched range. If you have done the work, state a range you can defend and say what it is based on.
4. Defer until you know the scope. If you genuinely do not know enough about the level, say so and offer to discuss it once you do.

Here are scripts for each. The bracketed parts are yours to fill from your own research. Do not fill them with a guess.

"Before I give a number, could you share the range budgeted for this role? That helps me see whether we're in the same place."

"Based on what I've seen for this level in [city or remote], I'm looking at [your researched range] in base salary. I'm flexible on how the total package is put together."

"I'd like to understand the level and scope first. If the role is what I think it is, I'm confident we can find a number that works. Can we come back to this after the next round?"

If you are asked about your current salary, know that in some places employers are not allowed to ask. Either way, you can steer back to what you are looking for: "I'd rather focus on the range for this role."

Common technical phone screen questions

• A coding problem in a shared editor, usually easier than an onsite problem but timed. Arrays, strings, hash maps and simple trees are common ground.
• Concept questions about your main language or stack: how memory is managed, what a closure is, how an index speeds up a query.
• A walk through a project on your resume: what you built, what was hard, what you would change.
• For senior roles, sometimes a short design question instead of, or after, the coding problem.

On a call without much video, the interviewer cannot see you thinking. Narrate more than you would in person: restate the problem, say the approach before you type, and name the complexity at the end. Live coding mock: narrate under a timer has a drill for exactly that.

Example: the first five minutes of a recruiter screen

An invented exchange. The candidate keeps each answer short and leaves room for the next question.

Recruiter: "Thanks for making time. Can you walk me through your background?" Candidate: "Sure. I'm a frontend engineer at a logistics company, mostly on the tools our dispatch team uses all day. Last year I rebuilt the scheduling screen so dispatchers stopped double-booking drivers, which had been the top support complaint. I'm looking for a role closer to the product's core, and this team owns the main customer app, which is why I applied." Recruiter: "Great. Why are you looking now?" Candidate: "My team is moving to maintenance work after a reorg. I've learned a lot there, but I want to keep building new things, and this role is mostly that."

Each answer is under thirty seconds. Nothing is negative about the current employer. The reason for leaving points straight at the role.

How to set up for a phone or audio-only call

• A quiet room with a door. Background noise is louder on a call than it sounds to you.
• A wired headset or earbuds you have tested on a real call. Speakerphone echoes.
• A charged phone with good signal, or a computer with the call app installed and the microphone tested.
• Notifications off on every device near you.
• One page of notes: the job description, your three stories as short titles, your salary research, and two questions to ask.
• Water within reach, and the recruiter's number saved in case the call drops.
• Confirm who calls whom, and the time zone.

Without faces, you lose the cues that tell you when to stop. Signpost instead: "I have two examples, I'll start with the shorter one." After a longer answer, check: "Does that cover it, or should I go deeper on one part?"

Questions to ask at the end of a phone screen

Ask about the next steps and the role, not about perks. Good choices: what the rest of the process looks like, what the team is working on this quarter, and what would make someone successful in the first few months. More options are in questions to ask the interviewer.

Common mistakes

• A three-minute answer to "walk me through your background." The recruiter needs the map, not the territory.
• A made-up salary figure. Research first, or ask for the range.
• Negative comments about a current or past employer.
• Not knowing which role you applied for, or which team.
• Taking the call somewhere loud, on a weak connection, or on speakerphone.
• Silence while solving a technical problem. On audio, silence sounds like being stuck.

A practice loop for phone screens

1. Say the opener on a timer. One minute. Present role, one proof, why this role. Stop.
2. Say the why-looking answer. Thirty seconds. One reason, then what you are moving toward.
3. Say your salary answer. Out loud, with your real research filled in. The first time is the awkward one, so make it a practice run.
4. Practice audio-only. Turn away from the screen or close your eyes, and answer as if nobody can see you. Notice where you trail off.
5. Write three lines. Which answer ran long, which word you repeated, and one change for next time.

Phone screen checklist

• I know which role and team this is, and who is calling.
• My one-minute opener is said out loud at least twice.
• My salary answer is based on research, or I will ask for the range.
• I know my notice period, start date limits and work authorization answer.
• My headset, signal and quiet room are tested.
• I have two questions to ask at the end.

Rehearse the screen on the Verbal surface

HIDEA AI is a desktop app for macOS and Windows, not a phone app, with four separate surfaces: Verbal, Live coding, System design and Project. The recruiter questions belong on Verbal, and the coding part of a technical screen belongs on Live coding. You speak or type every answer yourself.

A mock interview is verbal-only: the app asks questions out loud and listens, which is close to how an audio-only screen feels. Mocks run 20 or 30 minutes and are on Pro and Pro+. Fifteen session minutes a day is free, with no credit card. The setup guide covers the first run, and the pricing page lists what each plan includes.

If you are thinking about using a tool during a real screen, check the employer's rules first. Read is using an AI interview copilot cheating before you decide.

Where to go next

• Polish the opener: tell me about yourself interview practice.
• After the call: the thank-you email after an interview.
• If the screen is tomorrow: how to prepare for an interview in 24 hours.