What a recruiter screen is really checking

Five things on a short list
A recruiter screen looks like a conversation and functions like a checklist. In twenty to thirty minutes, most recruiters are confirming five things: work authorization and location, pay expectations, notice period, and whether the story you tell about your background actually matches the requisition in front of them. Everything you say gets filtered down to a few lines in an applicant tracking note afterward. Knowing the checklist in advance isn't about gaming it, it's about not wasting the recruiter's short window on things that were never in question.
Authorization and location come first, and they're binary
These questions get asked early because they can end the call in either direction before either of you spends more time. Work authorization gets checked here the same way it's checked on the application form itself: a straightforward statement of your status, not a story. If a posting requires onsite presence in a specific city and you're elsewhere, the recruiter is confirming that gap exists and deciding, on the spot, whether it's a dealbreaker or something workable. Answer plainly. Vague or evasive answers here read as a red flag even when the honest answer would have been fine.
Pay expectations: the question everyone dreads
Most recruiter screens ask for a number, and most candidates are unsure whether to give one. The safer move, when the recruiter opens with "what are your salary expectations," is to redirect once before answering: "I'd rather understand the full scope of the role first. What range is budgeted for this position?" Recruiters ask this question dozens of times a week, and a version of that redirect won't surprise or offend anyone. If they push back and ask again, that's your signal to answer, and the way to do it without boxing yourself in is a range anchored slightly above your real target: "Based on what I'm seeing for roles at this level, I'd expect somewhere in the X to Y range, though I'm flexible depending on the full package." A range with the bottom already at your real number gives you room to move up without contradicting yourself later, and it keeps the door open for a fuller conversation about the range once you're further along.
Notice period and timeline
Recruiters are staffing a pipeline against a deadline, and your timeline either fits it or doesn't. Be specific and honest: two weeks, a month, whatever your actual notice requirement is. If you're not currently employed, say so plainly rather than hedging around it. A mismatch here is rarely disqualifying by itself, but a vague answer makes the recruiter's own planning harder, and recruiters remember candidates who make their job easier.
The story match
This is the part candidates underestimate. The recruiter is holding a requisition with specific language on it, and your job in this call is to connect your background to that language directly, not to recap your resume in general terms. If the req says the role owns a defined book of accounts and your last two roles had you sharing a book across a team, say so and explain the shift plainly rather than hoping it doesn't come up: "My last two roles were on a shared book, and part of what draws me to this one is owning a defined set of accounts outright." Recruiters are trained to listen for exactly this kind of gap, and naming it yourself, with a reason, reads far better than having it surface as a question you visibly weren't ready for. The same applies to a location mismatch. If the req lists a specific city and you're currently somewhere else, don't wait for the recruiter to raise it: "I saw this role is based in [city]. I'm currently in [your location], and here's how I'd approach the transition." Naming the gap yourself, with a plan attached, reads as someone who read the posting carefully. Letting it surface as a question you seem unprepared for reads as someone who applied broadly without much thought, even when that isn't actually true.
The call runs both directions
The recruiter is checking a list, but you should be too. This is your best chance before an onsite loop to ask a few plain questions that shape whether you want to keep going: how many rounds are left, roughly how long the process usually takes end to end, and who you'd actually be meeting. "Can you walk me through what the rest of the process looks like, and roughly how long it typically takes?" is a normal, expected question, and the answer tells you whether to plan around two weeks or two months.
It's also worth asking why the role is open, plainly: "Is this a new position, or is it a backfill?" A recruiter who answers this smoothly and specifically is describing a role the company has thought through. One who hesitates, or gives a vague answer about "restructuring," isn't necessarily hiding something, but it's worth listening for in later rounds, especially from the hiring manager directly.
Ask about team size and reporting line too, even briefly: "How big is the team this role sits on, and who does it report to?" This is a low stakes question at this stage, easy for any recruiter to answer, and it gives you a baseline to check against what you hear later in the loop, the same way you'd check any other detail for consistency across the process. None of this needs to feel adversarial. A recruiter who's good at the job expects a few questions back and treats them as a normal part of a two way conversation, not an inconvenience.
What gets written down after you hang up
After most screens, the recruiter writes a short note that follows you through the rest of the loop: authorized or not, location fit, pay range discussed, notice period, and a one line summary of fit against the req. That note is often the only thing a hiring manager reads before your first real interview. It's worth treating the call accordingly: clear, specific answers to the five things above matter more here than in almost any other part of the process, because this is the one conversation that gets reduced to bullet points read by someone who wasn't on the call.
Prepare for this call the same way you'd prepare for the interview itself: reread the posting right before you pick up the phone, and have your notice period and a pay range decided in advance, not worked out live.
iapplyai.app drafts a pay range and a fit summary for each posting before you ever get the recruiter call, scored against your real resume, so you're not doing that math out loud for the first time on someone else's clock.



