ChannelPulse
The recruiter screen
Thirty-five minutes, no technical questions, and the highest ratio of consequence to difficulty anywhere in the loop. This is where the level you will be interviewed at gets set, and where one sentence about salary can cap an offer you have not yet earned. The lesson covers what the recruiter is actually collecting, how to answer the compensation question without lying or anchoring yourself, and what to ask.
What you'll be able to do
- Identify what a recruiter is collecting and why they need a number
- Answer the salary expectations question without anchoring yourself low
- Recognise the four things that go wrong when candidates talk numbers too early
- Use the screen to set level, timeline and format in your favour
Before this: the-anatomy-of-a-loop
The recruiter screen is the round candidates prepare least for and the round with the longest reach. Nothing technical happens. And yet the number you say out loud in minute twenty can still be sitting in an internal system four rounds later, quietly deciding what your written offer is allowed to contain.
The whole video is about negotiation and the back half belongs to a later lesson. The five chapters below are the ones that happen at this stage — before you have an offer, sometimes before you have applied — and the third and fourth are the exact moment this lesson is about. Watch those two twice.
Jump to the part you need
What the recruiter is collecting
Recruiters are not gatekeepers in the adversarial sense; their incentive is to fill the role with someone who accepts. But they are collecting four things, and it helps to know which question maps to which.
| They ask | They are collecting |
|---|---|
| Tell me about your current role and scope | Level. Team size, system ownership, blast radius. This becomes your target level |
| Why are you looking? | Close risk. Whether you will still be interested in six weeks |
| What are you looking for in your next role? | Team match input, and a second read on level |
| What are your compensation expectations? | A number for finance, and an early read on whether you are affordable |
| What is your timeline? | Urgency and competition. Whether they need to move fast |
The fifth one matters more than it looks. Recruiters explain compensation structure at this stage partly to be helpful and partly because they need as firm a number as possible to take to finance. That is a legitimate need. It is also the point at which your leverage is at its absolute lowest, because they have no evidence yet that they want you.
The compensation question
There is a version of this question that is friendly, casual, and asked in the last five minutes: so that we're not wasting each other's time, what sort of range are you thinking?
The principle is simple to state and hard to do: stay ambiguous until they tell you that you are moving to offers. Not evasive, not coy — ambiguous, with a reason attached that a reasonable person accepts.
Three answers, in descending order of how much they protect you.
Defer with a reason. "I'd rather learn more about the level and scope before putting a number on it — what's the band for this role?" This is the strongest move and it is not rude, because you have asked a question back that they can usually answer. In the United States, many jurisdictions now require the range to be disclosed anyway, and asking makes you look prepared rather than difficult.
Give a market range, not your range. "For a senior engineer at this level in this market I'd expect total compensation in the 300 to 360 band — but the mix of base, equity and bonus matters more to me than the headline." The range is about the role, sourced from public data, and the second half moves the conversation onto structure, where you have room later.
Give a number as a floor, if forced. Sometimes the recruiter genuinely cannot progress without one. Then the number you say is a floor and must be phrased as one: "I'd need to be above X to consider a move." Never say your current compensation in response to this question unless you are legally required to and never volunteer it. Which is worth stating flatly:
There is one important exception in the other direction. If you are returning to a company you worked at before, your historical compensation there is on file and at some companies — Meta notably — it is weighted more heavily than the standard band. In that specific case the number is already known and pretending otherwise is pointless.
The four things that go wrong
The failure modes at this stage are well documented and none of them require bad luck.
Talking numbers too soon. Covered above, and the most common by a wide margin.
Inconsistent storytelling. If your reason for leaving changes between the recruiter screen and the hiring manager round, or your stated expectation drifts by fifty thousand between two calls, the recruiter loses the ability to advocate for you internally — because their pitch to finance is a narrative, and it has to hold. Pick a story pegged to something checkable and keep it identical.
Negotiating with the hiring manager. Do not. The hiring manager is the person who has to champion you internally, and the moment compensation enters that relationship you have spent goodwill you need elsewhere. All money conversations belong with the recruiter, who is the one who can actually go to finance.
Accepting too quickly. This applies later in the process but the habit is formed here. Enthusiasm is good; immediacy is a signal that you were not weighing anything.
Use the screen for your own purposes
You have a recruiter on the phone whose job includes making you successful. Four things worth extracting before the call ends:
- The level you are being considered for, in their words, and whether the loop is a generalist loop or team-specific. This determines which rubric the onsite scores you against.
- The exact round structure — how many rounds, which are coding, whether there is a system design round, whether there is a take-home, and how long the whole thing runs.
- The timeline, including how long after the onsite a decision usually takes. You will want this later, because following up before the stated window closes reads as anxiety and following up after it closes is entirely reasonable.
- Who your interviewers will be, if they will say. Many recruiters will, and knowing that one round is with a staff engineer on the infrastructure team is worth an hour of targeted preparation.
What to carry into the next lesson
The recruiter screen decides which loop you get and what it is scored against. The next round decides whether a specific person wants you on their specific team, which is a different question and is answered by different behaviour: the hiring manager round.