The first conversation with a recruiter is a filter, not a deep evaluation. It runs 20 to 30 minutes, usually by phone or video, and the person on the other end (an internal recruiter or an agency recruiter) works from a concrete checklist: confirm the background matches the posting, confirm the terms are compatible, and confirm the conversation flows. Candidates who understand that objective arrive with an advantage, because they prepare for what is being evaluated now instead of what gets evaluated later.
This guide explains what the recruiter is watching for on that first call, which questions repeat and how to answer them briefly, what does not need proving yet, and how to close the conversation in a way that moves it to the next stage.
In this guide
What the screen decides
In most hiring processes, the recruiting team talks to the candidate before the hiring manager does. Their task is narrowing a list of 30 or 40 applications down to the four or five worth the team's time. That is why the conversation is short, follows a similar script with everyone, and centers on verifiable facts.
It helps to be clear about what the call decides. It does not decide the hire; it decides whether the candidate advances. Recruiters rarely have the technical background to judge the quality of the work, and they are not trying to. What they can judge is whether the terms line up, whether the resume matches what the person describes, and whether the communication is clear. That is the bar, and preparing for a different one wastes the time.
What the recruiter evaluates in 20 minutes
Behind the questions sit five boxes the recruiter needs to check before passing the profile along. Almost the entire call orbits them:
- Basic fit. That the experience, education, and tools in the posting show up somewhere in the background, even partially. What the resume says gets checked against what the person says.
- Availability. Possible start date, work arrangement (onsite, hybrid, remote), schedule, and where applicable, willingness to travel or relocate.
- Compensation expectations. That the number falls inside the range for the position. This is the question that eliminates the most candidates at this stage, and there is a dedicated guide on answering the salary expectations question.
- Motivation. Why this role and why now. The recruiter is trying to screen out mass applications and people who will drop out halfway through.
- Communication. Clarity, concision, and tone. It is never asked directly and it gets evaluated the whole call.
A candidate can clear four boxes and still be cut on the fifth. Expectations 40% above the range, or availability incompatible with the work arrangement, end the conversation regardless of how strong the background is.
The most common questions, with model answers
The screening script varies little between companies. These seven questions come up on almost every call, and the answers below are built to run 30 to 60 seconds, which is what the format accommodates.
"Tell me a little about yourself"
The standard opener, asking for a 45-second introduction rather than a biography. Structure: what you do now, what led there, what you are looking for. "I'm an accounts payable analyst at a food distributor, three years in the role. Before that I spent two years at a public accounting firm. I'm looking for a position with higher transaction volume and a larger team, which is what caught my attention in this posting." The full version, with variants by experience level, is in the guide on how to answer "tell me about yourself".
"Why are you interested in this position?"
This needs one concrete detail about the company or the role, connected to your own background. "I come from a heavily regulated industry, and the posting mentions the team is implementing a new ERP; I was part of a similar migration and I'd like to repeat that at a larger scale."
"What's prompting you to look for a change?"
Short, honest, and without complaints. "I completed a three-year cycle and the role doesn't have a next step; I'm looking for more ownership over results." A long explanation, and especially criticism of the current employer, costs more at this stage than at any other.
"What's your availability to start?"
Answer with a date or a concrete window. "I need to give two weeks' notice, so I could start the first week of next month." If there are conditions such as scheduled time off or a pending bonus, mention them now rather than at the offer.
"What are your salary expectations?"
With a range researched before the call and a note about flexibility. "Based on what I'm seeing in the market for this role, my expectation is between X and Y, with flexibility depending on the full package." Deflecting does not work: the recruiter needs the number to move the profile forward. In the states and cities with pay transparency laws, the posted range is the best anchor available.
"Are you interviewing anywhere else?"
The honest, neutral answer is the best one. "I'm in early-stage conversations with two other companies. This role interests me in particular because of the type of work." No names are needed, and inventing offers to create pressure rarely survives contact with a real timeline.
"Do you have any questions for us?"
One or two short questions about the process are enough: how many stages there are, who the next interview would be with, when they expect to fill the role. Questions about the team and the challenges of the job pay off more in the second interview, where the person who can answer them will be present.
What does not need proving yet
A frequent mistake is treating the screen like a technical interview. The recruiter is not going to evaluate depth of knowledge, code quality, or judgment on a case. When a candidate goes long on technical detail, the call stretches, the recruiter loses the thread of their list, and the overall impression gets worse.
What is worth saving for later stages:
- Detailed technical explanations of past projects. At this stage, naming the project, the role, and the result in one sentence is enough.
- Questions about team structure, internal tooling, or working methodology. Those are for the hiring manager.
- Fine-grained salary negotiation. The screen only verifies the range is compatible; negotiation belongs to the offer.
- Long situation-action-result stories. Those are for the behavioral interview, not for a 20-minute call.
The practical rule for a screen: every answer under one minute. If the recruiter wants more detail, they will ask. If they do not ask, it is because they already have what that box required.
Closing the call and practicing the format
The last two minutes set the impression that stays. An orderly close has three parts: confirm interest, ask about next steps, and thank them without overdoing it. "I'm interested in moving forward. What would the next steps be, and on what timeline?" is enough and leaves the recruiter with a concrete action. Afterward, write down what was left open: which questions were hard, what company detail was missing, what the recruiter said about the next stage. That record is the starting point for preparing the second interview.
The screen has a very defined shape: short questions, short answers, fast pace. Anyone unaccustomed to it tends either to run long or to freeze on the compensation question. One round of practice out loud with the seven questions in this guide, timing each answer, corrects most of that.
The interview simulator rehearses exactly this kind of conversation: it asks screening questions for the role given, probes when an answer stays vague, and returns an observation on clarity and length. Two or three rounds are enough for salary expectations and availability to come out without hesitation.
Common mistakes on a recruiter screen
| Avoid | Better |
|---|---|
| Taking the call outdoors or without rereading the posting | Scheduling a time, keeping the resume and posting visible, quiet room |
| Answering compensation with "whatever you're offering" or an unresearched number | A researched range, with flexibility stated |
| Explaining a technical project in detail for five minutes | Project, role, and result in one sentence; offer to expand at the next stage |
| Criticizing the current employer when explaining the change | Reason for leaving in one sentence, framed around what you are looking for |
| Giving an availability date that cannot be honored | A realistic date, notice period and commitments included |
| Asking nothing at the end | One or two questions about the process and the timeline |
The mistakes in that table share something: none of them has anything to do with professional quality. They are format mistakes, which is why preparation fixes them and more experience does not.
Frequently asked questions
How long does an HR screening interview last?
Twenty to thirty minutes in most processes. Under ten usually means one condition (compensation, availability, work arrangement) did not line up; over forty usually means the recruiter found something interesting and is digging. Preparation should target the short format.
What does a recruiter ask in a screening call?
The usual script covers a brief introduction, interest in the role, reason for the change, availability, salary expectations, whether other processes are underway, and whether the candidate has questions. It may add one or two questions about the resume to verify what it claims.
Do you have to give salary expectations on the first call?
Yes, and the number should be ready. The recruiter has to confirm the range is compatible before moving the profile forward, and deflecting usually leaves the application on hold. A researched range with flexibility on the full package is the answer that works best.
What happens after the HR screening interview?
If the profile advances, the next stage is usually an interview with the hiring manager or the team, sometimes preceded by a test or a case exercise. One to two weeks is the common timeline; a short email asking about status after that is reasonable.
Should an HR screen be prepared the same way as a technical interview?
No. The screen evaluates terms, basic fit, and communication, not depth of knowledge. Preparing one-minute answers to the seven usual questions, and having your own numbers ready, pays off more than reviewing technical material.