The Recruiter Phone Screen: What to Say in the First Call

The first call in any tech loop is with a recruiter, not an engineer. It's 20 to 30 minutes, it sounds casual, and candidates treat it as a box to check on the way to "the real interviews."

That's a mistake. The recruiter screen is the gate. They decide whether you advance, and one question on this call quietly sets the ceiling on your eventual offer. Treat it as the high-stakes conversation it is.

What the Recruiter Is Actually Doing

The recruiter has three jobs on this call, and knowing them lets you give them what they need:

Confirm you're real and interested - that your resume isn't fiction and you'd actually take the job
Screen for obvious misfits - comp expectations wildly off, can't legally work here, notice period too long, location mismatch
Sell you on the role - good recruiters are recruiting you, not just filtering

They are not evaluating your code. They're evaluating whether it's worth an engineer's hour to talk to you. Make that an easy yes.

The Opener: "Tell Me About Yourself"

This is almost always the first real question, and it's not an invitation to recite your life story. The recruiter wants a 60-to-90-second narrative that answers: who are you, why are you a fit, why are you here.

A clean structure:

"I'm a backend engineer with about five years of experience, mostly in Go and distributed systems. At my current company I own the payments service that handles about 2 million transactions a day. I'm looking to move because I want to work on infrastructure at larger scale, and that's exactly what this role looked like from the description."

Three beats: what you do now (with a concrete number), one credible highlight, and a forward-looking reason you're talking to them. Practice it out loud until it's smooth but not robotic. This sets the tone for the whole call.

The Salary Question: Where Money Is Won or Lost

At some point the recruiter asks about compensation. How you answer can cost or save you tens of thousands of dollars. There are two schools, and which you use depends on your situation.

Option A - Deflect to their range (usually best):

"I'd rather understand the full scope and level first - I'm flexible for the right role. Do you have a band for this position you can share?"

In many places, salary-range transparency laws mean they have to tell you if you ask. Get their number first. The first party to name a number anchors the negotiation - let it be them.

Option B - Give a range, anchored high:
If they push and you must answer, give a researched range with your target near the bottom:

"Based on the market for this level, I'm targeting something in the $190k to $220k total comp range."

Never give a single number, and never quote your current salary as your expectation - that caps you at your old job's pay. If asked directly what you currently make, you can decline (illegal to require in many jurisdictions) and pivot to expectations:

"I'd prefer to focus on the market rate for this role rather than my current comp."

The mistake to avoid above all: blurting out a low number to seem reasonable. You can't negotiate up from an anchor you set yourself.

Questions That Get You Advanced

Recruiters advance candidates who seem genuinely interested and easy to work with. The questions you ask signal both. Have a few ready:

"What does the interview process look like end to end, and how should I prep for each stage?" (shows you're serious, gets you the playbook)
"What's the team I'd be joining, and what are they working on right now?"
"What's the timeline you're working against?"
"Is this a backfill or a new role?" (tells you about team health)

That first question is the most valuable thing you can ask on the entire call. Recruiters will often tell you exactly what each round covers and what the interviewers look for. Free intel - take notes.

Logistics That Quietly Disqualify People

These rarely come up in prep but routinely sink candidates on the recruiter screen:

Work authorization - be ready to state your status clearly and without apology
Location / remote / relocation - know your real constraints and say them
Notice period - "two weeks" or "a month" is fine; "I can start tomorrow" can read as a red flag, "three months" can stall you out of a fast loop
Other processes - if you're interviewing elsewhere, a light mention ("I'm in a couple of other conversations") creates healthy urgency without bluffing

How to Close the Call

End with intent and clarity:

"This sounds like a strong fit, and I'm excited about it. What are the next steps, and is there anything specific I should prepare for the technical round?"

Then send a short thank-you email within a few hours. Two lines is enough. It keeps you top of mind while the recruiter is deciding who to push forward.

The Mindset Shift

Stop thinking of the recruiter as a gatekeeper to get past and start thinking of them as your inside advocate. A recruiter who likes you will coach you, flag your application internally, push your comp with the hiring manager, and tell you what the interviewers want to hear. You earn that by being prepared, easy, and clear about what you want.

The phone screen isn't the warm-up. It's the first round - and the one that decides whether the rest happen.

Run the recruiter screen with the same intent you'd bring to a coding round: a tight intro, a disciplined answer on comp, sharp questions, clean logistics.

Want to walk in already knowing the market band so the salary question is a layup? gitGood's compensation explorer gives you real comp data by company and level - and our interview prep tracks get you ready for everything the recruiter says comes next.