# What Recruiters Actually Score on the Phone Screen

Source: https://www.techinterview.org/post/3233477387/recruiter-phone-screen/
Updated: 2026-09-05 · techinterview.org

The recruiter phone screen is not a technical test. It's a filter with maybe four or five yes/no boxes: do you actually want this role, does your background match the level, are your comp expectations inside their band, and can you communicate clearly. Get the compensation number aligned and give a tight two-minute background pitch, and you pass. The most common reasons for a reject here are salary mismatch or a vague "why are you looking," not anything you'd study for.

A recruiter screen runs 20 to 30 minutes, and the person on the other end is usually not an engineer. That trips up a lot of strong candidates, because they prepare for a technical conversation and get a logistics conversation instead. The recruiter's job is not to assess whether your binary search is correct. It's to decide, fast, whether pushing you into an expensive interview loop is a good bet for the team and a defensible use of the hiring manager's time.

Every full loop costs the company real money: four to six engineers pulled off work for an hour each, a hiring manager's debrief, coordinator time. The recruiter is the gate that keeps that pipeline from filling with people who will bail over comp, who are targeting a level they can't clear, or who can't explain what they do. So the screen is scored against a short internal checklist, and the checklist is more predictable than the interview it protects.

## The scorecard is shorter than you think

After the call the recruiter types a few lines into an ATS like Greenhouse or Ashby and marks you advance or reject. What they're filling in is roughly this: interest and motivation, level and background fit, compensation alignment, timeline, and communication. That's the whole thing. There's occasionally a light technical gut-check, but it rarely decides the outcome on its own.

| What the recruiter scores | The question that measures it | What passes | What fails |
| --- | --- | --- | --- |
| Interest / motivation | "Why are you looking?" / "Why this company?" | One concrete, specific reason tied to the role | "I'm just exploring" or a generic answer that fits any job |
| Level & background fit | "Walk me through your background." | A 2-minute pitch matching the seniority on the req | Rambling, or scope that's clearly a level off |
| Compensation alignment | "What are your expectations?" | A number or range inside the role's band | A figure well above the band, or refusing to engage at all |
| Timeline & logistics | "When could you start? Other processes going?" | Clear availability, upfront about competing offers | No sense of timeline, or a hard constraint they didn't flag |
| Work authorization | "Are you authorized to work here? Need sponsorship now or later?" | Clear, upfront status | Surprising them with a sponsorship need late in the process |
| Communication | The whole call | Clear, concise, answers the question asked | Long tangents, defensive tone, talking over them |

## "Why are you looking?" is the real first question

This one sounds like small talk and it isn't. The recruiter is checking whether you have a reason that survives contact with a hiring manager. "I want to work on payments infrastructure at scale, and that's what this team owns" is a pass. "I'm open to new things" is a soft reject, because it tells them you'll be just as open to the counteroffer your current employer makes in week three.

Say one specific thing the role offers that your current job doesn't. You don't have to trash your current employer, and you shouldn't. Recruiters clock bitterness immediately and read it as risk. Keep it forward-looking: what you want to build next, and why this team is a plausible place to do it.

If you're not currently employed, the same rule holds, just aimed at a different worry. Coming off a gap, name it plainly and point forward ("I took two years for caregiving, I've been rebuilding with a returnship project, and I'm targeting backend roles again") so the recruiter reads intent rather than a hole. Changing careers or coming out of school, lead with the pull toward the work, not the push away from it, and tie a transferable win to what this team needs.

## The background pitch: two minutes, not ten

When they say "walk me through your background," they are not asking for your resume read aloud in reverse chronological order. They want a compressed narrative that lands you at the right level. Lead with what you do now, anchor it with one result that has a number attached, and connect it to why this role is the next step. Ninety seconds to two minutes. Then stop and let them steer.

The number matters more than people expect. "I led the migration off a monolith" is forgettable. "I led the migration off a monolith for a service doing 40k requests a second, and cut p99 latency (the slowest 1% of requests) by half" tells a non-engineer recruiter that you operate at a level they can sell to the hiring manager. You don't need production metrics for this to work: an internship that "cut the team's build time from 12 minutes to 4," or a measurable win from a prior career ("ran a warehouse that shipped 30% more orders after I redid the picking flow") gives the recruiter a concrete number to repeat. If you're prepping this, the same present/past/future structure that works for the [STAR answer builder](/star-method-answer-builder/) works here, just compressed and without the situation-heavy setup.

If your background is genuinely a level off from the req (the internal job requisition, which lists the target level and band), the screen is where that surfaces. A recruiter for a staff role who hears entirely feature-level work with no cross-team scope will note the mismatch and route you to a lower posting, or pass. That's not a failure of the call; it's the call doing its job. The recruiter isn't judging your engineering here either. That comes later, in the [hiring-manager and technical screens](/post/3233474693/hiring-manager-vs-technical-screen/), which is a different conversation with different stakes.

## Compensation is where most screens actually die

In practice, comp misalignment is one of the most common reasons a screen ends in a reject, and it's the one candidates least expect. A recruiter can love everything about you and still reject you in the ATS because your number is 30% over the band and they don't want to run a five-round loop that ends in a declined offer. So handle this part deliberately.

You'll usually get some version of "what are your compensation expectations?" You have a few defensible moves. You can ask for their range first: "Do you have a band budgeted for this role? I want to make sure we're in the same ballpark before we both invest time." Plenty of recruiters will share it, especially in states with pay-transparency laws where the range is on the posting anyway. If they push you for a number, give a range whose bottom is a figure you'd actually accept, and make sure the range is grounded in real market data for the level and location, not a wish.

Do the homework before the call. Know the total-comp picture beyond base: bonus target and equity too, because at most tech and AI companies the equity is a large part of the offer and the recruiter is thinking in total-comp terms. A [total comp calculator](/total-comp-calculator/) is useful here so you're quoting a coherent total rather than a base number that reads as either naive or lowball. The heavy lifting on the actual number comes later; for a deeper treatment of how to hold your ground once an offer exists, the [salary negotiation](/post/3233474669/salary-negotiation-2026/) playbook covers the offer stage. On the screen, the only goal is to confirm you're in the same universe so the loop can proceed.

> Giving a specific number too early can cap you. Refusing to give any signal at all reads as difficult and gets you passed over for someone easier to place. A researched range threads it.

## The red flags recruiters are trained to catch

Recruiters run dozens of these calls a week, so they pattern-match on a handful of tells that correlate with a loop going badly. None of these are about your engineering ability. They're about whether you're a safe bet to put in front of the team.

- Trashing your current or former employer. Reads as: this person will talk about us that way next.

- Comp expectations far outside the band with no flexibility. Reads as: guaranteed declined offer.

- Can't explain what they personally did versus what "the team" did. Reads as: level inflation on the resume.

- Vague on why they're leaving or why this company. Reads as: flight risk, or just shopping.

- Interrupting, talking for ten minutes straight, or getting defensive at a normal question. Reads as: the interviewers will have a bad time.

The communication one is underrated. A phone screen is a live demo of what you're like to talk to for an hour. Answer the question they actually asked, keep answers tight, and let them drive. If you find yourself three minutes into an answer, wrap it.

## The light technical check, when it happens

Some screens include a small technical filter, especially at larger companies routing high volume. It's usually resume verification more than assessment: "the posting is heavy Go, how much have you written?" or "have you owned anything in production on Kubernetes?" Occasionally a non-engineer recruiter reads a scripted question off a sheet, sometimes a basic Big-O prompt (the standard shorthand for an algorithm's efficiency), and writes down whether your answer matches an expected keyword. Answer plainly and don't over-engineer it. This is verifying that your resume is real, not testing depth, and a [resume checker](/resume-checker/) catches the level-inflation gaps a recruiter probes for. Depth is what the actual loop is for, and that's where a [study plan generator](/study-plan/) and pattern practice earn their keep, not here.

## Timeline talk, and how to use it

Near the end they'll ask about your timeline and whether you have other processes going. Be straight and specific. If you're interviewing elsewhere and have an onsite next week, say so. It doesn't make you look disloyal; it makes you look in-demand and gives the recruiter a reason to move faster. Recruiters chase candidates with competing timelines because those are the ones about to disappear.

Work authorization surfaces here too, and it's not a place to be vague. If you need visa sponsorship now, or will when a current status expires, say so plainly and give the timing. A recruiter who learns about it at the offer stage feels blindsided, and some companies simply don't sponsor for certain roles. Naming it early costs you nothing with the ones that do and saves a wasted loop with the ones that don't.

This is also your window to ask about the process itself: how many rounds, what each one covers, who you'd talk to, and the realistic calendar. A recruiter who can't describe their own loop cleanly is a small yellow flag about how organized the process will be. And knowing the shape of the loop lets you prep the right things, which is the entire point of the [interview prep](/category/interview-prep/) that comes after this call.

Treat the screen as what it is: a cheap, fast compatibility check that you pass by being clear, being researched on comp, and having one real reason you're on the phone. Nail those three and you're through to the part where your engineering actually gets tested. Miss the comp number and it won't matter how good your engineering is, because you'll never get to show it.