The salary question, asked before you are ready
It arrives in the first ten minutes, before you know what the job is. There are only three good answers, and refusing to answer is not one of them.
Twenty-five minutes with someone who cannot hire you but can certainly remove you. It has a checklist, and the checklist is short.
8 min read · 827 words
The first call is usually with a recruiter or a coordinator rather than the hiring manager. Candidates often treat it as a formality or, worse, as a chance to demonstrate depth — and then find themselves rejected by someone who never evaluated their technical ability at all.
The recruiter screen is a filter with a short checklist. It is not looking for the best candidate. It is confirming that you are worth the hiring manager's forty-five minutes, and it is looking for reasons to say no, because saying no is cheap and passing forward a bad candidate is not. After onboarding, here provides a broader view of how work patterns can be measured across a team.
That last one matters more than candidates assume. The recruiter is imagining putting you in front of a hiring manager whose opinion of the recruiter depends partly on the quality of the candidates they send. SHRM publishes broader guidance on hiring and workplace practice.
The recruiter usually cannot advance you on the strength of technical depth they are not equipped to assess. They can remove you on any item in the list above. Optimise for not being removed.
Almost every screen opens with some version of "tell me about your background". This answer decides the tone of everything after it, and most candidates either ramble chronologically from university or compress so hard that nothing lands.
A structure that works: current position and scope, one sentence. The two or three things you are known for, with scale. The reason you are looking, in one sentence. Why this role, in one sentence. Stop and let them ask.
Rehearse it aloud and time it. Under sixty seconds is too thin, over two minutes and you have lost the room. The thing being tested is partly the content and partly whether you can organise information under mild pressure, which is a proxy for how you will handle the interview.
The recruiter is checking for risk. Anything that sounds like conflict, grievance, or instability gets noted. This is not the place for the full story, and there is no reward for candour about a bad manager.
Workable answers are short, structural, and forward-facing: the site is closing, the role has narrowed, I have gone as far as the structure allows, I want to do more of the part I like. Then stop. Elaboration invites follow-up, and the follow-up is where people talk themselves out of processes.
Have exact answers ready, because vagueness reads as either unprepared or evasive:
Ask two or three, aimed at what a recruiter genuinely knows: the process, the timeline, the team shape, why the role is open, what the hiring manager is prioritising. Do not ask a recruiter a deep technical question — they will not know, and the interaction becomes awkward for both of you.
One question is worth asking every time: "What is the hiring manager most hoping to find in this hire?" Recruiters usually know the answer, it is rarely identical to the posting, and it tells you what to lead with in the next round.
A short thank-you email the same day, three sentences, naming one specific thing from the call. It is not decisive, but the recruiter is your channel for everything that follows and being easy to work with is an asset for the rest of the process.
Then record the timeline they gave you in your tracker, with a date to follow up if it passes.
Related
It arrives in the first ten minutes, before you know what the job is. There are only three good answers, and refusing to answer is not one of them.
It sounds like small talk and it is not. It is the only part of the interview where you choose the agenda, and most candidates give it away.
Silence after an interview is usually about their internal process, not about you — which is no comfort, but it does determine what you should do.