A recruiter screen runs 25 to 30 minutes, and by the end of it someone has typed two or three sentences about you into Greenhouse or Ashby that the hiring manager reads before deciding whether to book five engineers for your loop. Most candidates treat the call as a formality and spend it being pleasant. The people who walk away with the strongest offers treat it as the first round of negotiation, because that’s what it is.
The recruiter is not scoring your algorithms. On this one call they’re doing three separate jobs: confirming you’re real and roughly the level the req was written for, checking that your pay expectations land inside the band before anyone burns interviewer time, and reading how likely you are to actually sign if an offer shows up. Almost every question they ask feeds one of those three.
What the recruiter is actually writing down
Recruiter notes are short and blunt. They land in the applicant tracking system as a quick verdict the hiring team skims later: “Strong background, L5 scope, comp expectations ~10% over band, flight risk low, move fast.” That single line shapes your offer more than most of what happens in the technical rounds, and you never see it. Here’s how the friendly questions map to what’s being recorded.
| What they ask | What they’re recording |
|---|---|
| “Walk me through your background” | Level and scope: does what you say match the resume, and does it match the req |
| “What are you looking for next?” | Fit and flight risk: will this job hold you, or will you leave in a year |
| “What are your salary expectations?” | Comp alignment: can they afford you before scheduling the loop |
| “Why are you leaving your current role?” | Red-flag scan: running from something, or moving toward something |
| “What does your timeline look like?” | Urgency: competing offers, and how high to prioritize your scheduling |
The salary question is the whole ballgame
This is the one exchange where a bad thirty seconds costs you real money, and it’s the one most people fumble by answering too fast and too specifically. When the recruiter asks what you’re looking for, the right first move is to ask them for the band. “What range is budgeted for this level?” is a normal question, and most recruiters have that number in front of them. In states with pay transparency rules, including California, Colorado, New York, Washington, and Illinois, the range is often already in the posting, so you can open with “the posting listed 190 to 240, can you confirm that’s the band for the senior level?” and let them talk first.
If they push the question back to you, give a range, never a single figure, and set the bottom of that range at a number you’d genuinely accept. Say 185 as your floor and the recruiter hears 185 as the number they can close you at. Say 210 to 240 tied to market data and you’ve anchored the conversation where you want it. Don’t volunteer your current salary. In much of the country they’re not allowed to ask, and even where they can, you’re under no obligation to answer a question that only helps them lowball a raise.
The reason this matters so early is mechanical. If your expectation lands far above the band, the recruiter closes the file and moves on, and you never learn you were 15 thousand apart on a job you’d have taken. If it lands well below, they book the loop and later extend an offer anchored to your low number, and you leave 30 or 40 thousand behind without knowing it. Getting the band on the table first protects you from both.
How they slot you into a level
Titles are close to meaningless across companies, so recruiters ignore them and listen for scope. “Senior engineer” at a 40-person startup might map to L4 at Google or E4 at Meta, while a staff title at a no-name shop can land as a mid-level offer. What they’re calibrating is the size of what you owned: the systems you were responsible for, whether you drove projects or worked tickets, how many engineers your decisions touched. That mapping decides your level, and one level is often 40 to 80 thousand a year in total comp.
So when you walk through your background, talk in scope, not in titles. “I owned the billing service end to end, including the on-call rotation and a rewrite that cut invoice errors by a third” tells the recruiter more than “I was a senior engineer for three years.” Say “we” and they can’t score you, because they can’t tell which part of the work was yours. Say “I designed, I decided, I shipped” and you give them a reason to write down the higher level.
The red flags that get you quietly cut
Some of these end the call without you ever hearing why. Trashing your current employer sits near the top; even when the complaints are fair, the recruiter reads it as how you’ll talk about them in a year. Being vague about what you personally did is another, because a candidate who only speaks in “the team” can’t be calibrated and defaults to the lower level. A resume that falls apart on the first follow-up question is fatal, so don’t list a technology you touched once and can’t discuss under mild pressure.
Comp is a red flag in both directions. Plant a number so far above the band that scheduling would be a waste, signal zero flexibility, and the file closes. A string of sub-one-year stints with no explanation reads as flight risk, so if your history looks jumpy, have a plain two-sentence story ready before they ask for it.
What to ask before you hang up
The last few minutes are usually yours, and good questions here do double duty: they get you real information and they signal you’re serious. Worth asking:
- How many rounds are in the loop, and what does each one cover?
- What’s the band for the level you’re considering me for?
- Who’s the hiring manager, and what is the team building right now?
- What’s the timeline, and are there other candidates far along in the process?
The answers tell you how to prep, whether the money is even close, and how much the calendar works in your favor. A recruiter racing three other people to a close is a different negotiation than one who’s been sitting on an open req for two months.
Keep one thing in mind about the person on the other end of the call. The recruiter is the only participant in the whole process whose incentive is to get you hired and to close you at a number you’ll sign, which makes them the closest thing to an ally you have, right up until you’re negotiating the offer against them. Be warm and specific, and remember that the two sentences they type when they hang up follow you into every round after.
Practice the behavioral round:
