Type something to search...
What the recruiter is actually screening for

What the recruiter is actually screening for

The first call in a hiring process is usually 30 minutes with a recruiter, and most candidates treat it as scheduling with extra steps. Here’s what the recruiter was actually asked to check, what the standard questions are really asking, and how to handle the comp question.


The round people prepare for last

Ask someone how their interview prep is going and they’ll tell you about the hiring manager conversation. They’ve got their project stories lined up and they’ve read the engineering blog.

Then a recruiter emails to set up a 30-minute intro call, and that one gets handled in whatever gap exists on Thursday afternoon, with no preparation at all, because it isn’t a real interview. It’s just an intro.

It is a real interview. It’s the one that decides whether the conversation you prepared for ever gets scheduled. We’ve written before about how candidates spend hours on applications and minutes on preparation, and this is where that imbalance costs the most, because it’s the cheapest round to prepare for and the earliest one you can lose.

When you lose it, you rarely find out. The thread goes quiet, and there’s no feedback, because from the recruiter’s side nothing dramatic happened. They talked to a handful of people that week, some matched what the hiring manager had described, and those are the ones they passed along.

The recruiter is working from a list you can reconstruct

Before the job went live, the recruiter sat down with the hiring manager for a short intake conversation. That meeting produced a handful of notes: the two or three things this person has to have done before, the salary band that got approved, and the constraints on who can be hired at all.

Those notes are what the recruiter is holding during your call. They aren’t evaluating your depth the way the hiring manager will. They’re checking boxes and writing something they can paste into an email that starts “I think you’ll want to talk to this one.”

So your job on the call is to make that email easy to write. Say the things that map to the notes, in language close enough to the posting that the recruiter recognizes it. If the posting is built around a migration off a legacy system and you’ve done one, that belongs in your first two minutes, not on minute 19 of a chronological walk through your career.

The posting is the closest thing you get to seeing those intake notes, so read it again the morning of the call. It also helps to know what happens to your application between clicking submit and this phone ringing.

What the standard questions are really asking

The questions are predictable. What they’re checking is less obvious.

“Tell me about yourself” is not an invitation to narrate your resume from the top. The recruiter is checking whether you can describe your own work clearly and whether your background matches the role. Two minutes, ending on why this job is the sensible next thing. Spend those two minutes on a job you held six years ago and you’ve told them you can’t prioritize.

“Why are you looking?” is checking for risk. Recruiters have watched offers fall apart because a candidate was working one for leverage elsewhere, or was leaving a situation in a way that suggested the same thing would happen again in a year. There’s a good answer to this even when the true answer is bad. Be brief, be neutral about your current employer, and put the weight on what you’re moving toward.

“Walk me through your background” is checking for gaps and short stints the hiring manager will ask about, so the recruiter can get ahead of them. If you have a nine-month gap, name it in one sentence and keep going. Explaining it before you’re asked removes it as a question later.

“What are you looking for in your next role?” is checking fit against a job that already exists and can’t be redesigned. Candidates hurt themselves here by describing an ideal role that isn’t this one. If you want to lead a team and this is an individual contributor job, you’ll find out faster by saying so than by getting three rounds in.

The compensation question

It usually arrives near the end, phrased as “what are your salary expectations?”, and most people handle it badly in one of two directions. They name a number below what the role was budgeted for, which becomes the ceiling for every conversation afterward, or they refuse to engage at all, which reads as difficult and sometimes ends the call.

There’s a third option and it’s not complicated. Ask first. “Before I give you a number, what’s the range approved for the role?” is a normal question, and the recruiter usually knows the answer because the band was set at that same intake meeting. If they give you a range, you say whether it works, and you’re done in 20 seconds.

If they want your number first, give a range rather than a point. Put the bottom of it at a figure you would genuinely accept, say what it’s based on, and add that you’d want to see the whole package before getting more specific. That’s a real answer, so it doesn’t read as evasive, and it hasn’t pinned you to one number.

What you want to avoid is being surprised by the question. Decide your range before the call, not during it.

The logistics that quietly end things

Somewhere in the call the recruiter will confirm a short set of practical facts: when you could start, whether you need visa sponsorship, where you live and whether you can be in the office on the days the team is, and whether you’re in other processes.

None of these are trick questions and none are the interesting part of the call. They matter because they’re the things that kill an offer at week seven instead of week one. Answer them directly. If sponsorship is a hard no at that company, you want that in the first 30 minutes rather than after a take-home.

The one worth thinking about in advance is “are you interviewing elsewhere?” You don’t owe anyone a list of company names. “Yes, a couple of other processes, one fairly far along” is enough, and it’s useful to them, because it changes how fast they move.

The recruiter knows things nobody else will tell you

This is the part most candidates leave on the table. A recruiter has context the hiring manager won’t volunteer and your friend at the company doesn’t have. They talk to that manager weekly and they’ve watched other candidates go through this exact process. Ask them.

Why is the role open? A backfill and a new headcount are different jobs, and if it’s a backfill, asking what happened to the last person is fair.

How long has it been open, and is anyone at the final stages? That tells you whether you’re early or catching the end of a search.

Who would this person report to, and how big is the team? You want the manager’s name before the next round so you can prepare for a specific human.

What does the process look like from here? Get the number of rounds, the format of each, and who’s in them. Preparing for a system design round you didn’t know was coming is impossible.

What does the hiring manager care most about? Recruiters answer this one surprisingly often and surprisingly specifically, and it’s the most useful thing you can carry forward.

Ask three or four of these, not all of them. It’s a 30-minute call and they have a script to get through.

Closing the call

In the last minute, say plainly that you want to move forward. Recruiters track interest, and lukewarm candidates get deprioritized when a hiring manager’s calendar is tight. Then confirm what happens next: who’s contacting you, in what form, and by roughly which day.

Then write it down while it’s fresh: the manager’s name, the process shape, the range, and why the role is open. That’s the source material for the next round, and it’s already stale by Friday if it only lives in your memory. A short follow-up note the same day is worth sending too, for the same reason it’s worth sending after any interview: it’s low effort and almost nobody does it.

The recruiter screen rewards 20 minutes of preparation more than any other round, because so few people give it any. Read the posting again, know your range, pick your questions, and treat it like the interview it is.

That’s the part JobHawk makes easier. It tracks where each application actually stands, so you know which conversations are live, and interview prep is in the Essential plan at $15 a month rather than something you buy separately once you’re already nervous.

Try JobHawk free →

Related Posts

Interview prep doesn't have to cost $5,000

Interview prep doesn't have to cost $5,000

Interview bootcamps charge $5,000 to $12,000. Career coaches charge $150 an hour. Here's what they actually teach, and how much of it you can get for $15 a month.The interview prep market

read more
You spend hours applying and minutes preparing for the interview. That ratio is backwards.

You spend hours applying and minutes preparing for the interview. That ratio is backwards.

Most job seekers spend an hour applying and fifteen minutes prepping for the interview. The prep is where offers are won.You spend hours applying and minutes preparing for the interview. Th

read more
The 10-minute post-interview habit most candidates skip

The 10-minute post-interview habit most candidates skip

Most candidates skip the thank you note or send something generic. Here's how to write one in 10 minutes that references your actual conversation and keeps you top of mind.The email nobody

read more
The STAR method is table stakes. Here's what interviewers actually look for.

The STAR method is table stakes. Here's what interviewers actually look for.

Everyone knows STAR. Most candidates still bomb behavioral questions. The framework is the starting point, not the finish line.STAR is everywhere, and it's not enough If you've done any i

read more
A job search tool that actually helps you prepare for interviews

A job search tool that actually helps you prepare for interviews

Every job search tool helps you apply. JobHawk is the first one that helps you prepare for the interview.A job search tool that actually helps you prepare for interviews There's a pattern

read more