You did the work and the phone rang. The first call is usually twenty to thirty minutes with a recruiter rather than the hiring manager, and candidates routinely underprepare for it because it feels like a formality.

It is not. A recruiter screen is a filter, and a fair number of qualified people fail it for entirely avoidable reasons.

What the screen is actually for

The recruiter is answering four questions, in roughly this order:

  • Are you real? Does your experience match what your resume claims, in your own words?
  • Are you interested? Do you know what this company does and why you applied here specifically?
  • Do the logistics work? Salary range, location and working pattern, notice period, work authorization, start date.
  • Can you communicate? They are imagining you in front of the hiring manager. If you ramble for six minutes on the first question, they will hesitate to pass you along.

Notice that deep technical evaluation is not on the list. Do not try to prove everything in the screen — prove that you are worth a longer conversation.

Fifteen minutes of preparation

Before the call: reread the job description, reread the resume version you actually sent them, and have three things in front of you — your two-sentence summary of what the company does, your salary range, and two questions to ask.

Have the posting open during the call. Recruiters expect it, and referring to a specific line in it is a positive signal, not a negative one.

The opening answer

"Tell me about yourself" is the most predictable question in hiring and the most commonly fumbled. Answer it in about ninety seconds, structured in three beats: where you are now and what you own, one or two relevant highlights with a result attached, and why this role is the logical next step.

That last beat is what most people omit, and it is the one that transitions the conversation. Do not start with where you went to university and walk forward chronologically. Start with the present, go backwards only for what is relevant, and land on them.

Handling the salary question

It will come up, usually early, and dodging it entirely tends to annoy recruiters who have a band to work within. The most useful answer is a researched range with a reason attached: "Based on what I have seen for this scope in this market, I am looking at X to Y, and I am flexible depending on the full package."

If you would rather not go first, it is entirely reasonable to ask what range is budgeted for the role — many recruiters will tell you, and in a number of places they are required to. Do the salary research before the call rather than improvising a number under pressure. A range you can justify is much harder to negotiate down later.

Have two questions ready

Recruiters can rarely go deep on the technical work, so ask them what they actually know: why the role is open, what the interview process looks like and how many stages, what the team's structure is, what the timeline is. "Why is this role open?" is particularly valuable — a new role, a backfill, and a rebuild after a departure are three very different jobs.

Close the call properly

In the last two minutes, do two things. Say plainly that you are interested and why, in one sentence. Then confirm the next step and the timing: what happens next, and when should you expect to hear.

That second question does more work than it looks like. It gives you a date, which means your follow-up is no longer guesswork — if they said "by the end of next week" and next week ends, you have an obvious, entirely appropriate reason to check in.

After the call

Send a short thank-you the same day: three sentences, one of which references something specific from the conversation. Then log the stated timeline in your tracker with the follow-up date set.

The common failure

It is almost never technical. It is answering the first question for six minutes, being unable to say what the company does, having no number when salary comes up, or sounding indifferent about a role you actually want. All four are solved by fifteen minutes of preparation, which is a very good return on a call that decides whether the rest of the process happens.