The recruiter screen is the shortest round in most interview loops, and the easiest to underestimate. It's conversational, it's rarely technical, and it often feels like a formality. But it decides whether you get the rest of the loop, and it's where a lot of candidates lose momentum: a rambling background, a vague answer to "why us?", or a fumbled question about salary.
This guide covers what the screen is for, how long it lasts, what recruiters ask, and how to prepare in an evening.
What a recruiter screen is
A recruiter screen (or recruiter phone screen) is the first conversation in most hiring processes. A recruiter, usually not an engineer, calls to check whether it's worth the company spending engineering time on you. They're checking four things:
- Communication. Can you explain your background briefly and in plain language?
- Motivation. Do you have a real reason for wanting this role, beyond wanting a change?
- Alignment. Do your level, location, work authorisation, and timing match what the team needs?
- Expectations. Is there a chance your compensation range and theirs overlap?
The recruiter writes notes, and those notes often go to the hiring manager, who decides whether you move forward. So you're talking to two people: the recruiter on the call, and the hiring manager who'll read what the recruiter wrote. Clear, specific answers survive that summary. Vague ones don't.
How long a recruiter screen is
Usually 15 to 30 minutes, by phone or video. A typical shape:
| Part | Time |
|---|---|
| Introductions and the role | 2–5 min |
| Your background | 5–10 min |
| Motivation and fit | 3–5 min |
| Logistics and expectations | 3–5 min |
| Your questions | 3–5 min |
That's not long, so every answer needs to be reasonably short. A background that takes ten minutes leaves no room for anything else.
What recruiters ask
The questions are predictable. That's good news: you can prepare a clear answer to almost all of them.
"Tell me about yourself" or "Walk me through your background"
Almost always first. Aim for about 90 seconds: where you are now, two or three moves that explain how you got there, and why this role is the logical next step. End on the role, not on your history, so the conversation turns to why you fit.
A rough shape:
"I'm a backend engineer at a logistics company, where I've spent the last three years on the routing service, most recently leading its move to an event-driven design. Before that I was at an agency building client web apps, which is where I found I liked the infrastructure side more than the frontend. What drew me to this role is that it's the same kind of problem, high-volume event processing, but in payments, which is a domain I've wanted to work in."
We'll cover this question in more depth in a separate guide, because it's the one most worth rehearsing.
"Why this company?" and "Why now?"
The recruiter is listening for a reason that's specific to this role. "I'm looking for a new challenge" fits any job. "The posting talks about moving to event-driven processing, which is what I've spent the last year on, and I'd like to do it in a domain where correctness matters this much" fits this one. Use the job description; our guide to preparing from the job description covers how to read it for exactly this.
For "why now?", keep it forward-looking. You can be honest about why you're leaving without criticising your current employer: "I've learnt a lot there, and the next step I want isn't available on my team."
Questions about your CV
Expect questions about the moves on your CV: why you joined each place, why you left, and any gaps. Have a one-sentence answer for each. Gaps are common and rarely a problem if you explain them plainly.
A few technical checks
Some recruiters ask quick technical questions from a list the hiring team gave them: which languages you use day to day, the size of the systems you've worked on, whether you've used a particular technology. Answer in plain language and briefly. Save the detail for the technical rounds.
Logistics
- Where are you based? Are you open to the office, hybrid, or remote arrangement for this role?
- Do you need visa sponsorship?
- What's your notice period?
- Are you interviewing elsewhere, and how far along are you?
Have short, clear answers ready. On other processes, it's fine to say you're interviewing elsewhere and roughly where you are. It helps the recruiter plan the timeline and can speed things up.
"What are your salary expectations?"
The question that makes most people uncomfortable. You have two reasonable options:
- Give a researched range for the role and level, where you'd be happy at the bottom of it.
- Ask about the band first: "I'd like to understand the full package before I name a number. Could you share the range for this role?"
Both are fine. What matters is deciding which you'll do before the call, so you aren't improvising. If you give a range, base it on research for the role, level, and location, not on your current salary.
What to ask the recruiter
At the end you'll be asked if you have questions. Have two or three ready, and make them things a recruiter can actually answer:
- "What are the stages of the interview process, and what does each one cover?"
- "What's the team working on this year?"
- "How would you describe the level of this role relative to the team?"
- "What's the timeline from here?"
The first is the most useful question you can ask in the whole process. Most recruiters will tell you the rounds, and some will tell you what each focuses on, which turns the rest of your preparation from guesswork into a plan. Save deep technical questions for the engineers you'll meet later.
How to prepare
You can prepare well for a recruiter screen in an evening:
- Write your 90-second background as bullet points, not a script. It should end with why this role.
- Say it out loud several times, timing it. It will run long the first few times.
- Write one sentence for "why this company" that uses something specific from the posting.
- Prepare a one-sentence answer for each move on your CV, and any gaps.
- Decide your compensation approach: a researched range, or asking for the band first.
- Write down your logistics: notice period, location, work authorisation, other processes.
- Pick two or three questions for the recruiter.
The step people skip is saying it out loud. A background that reads well on paper can still come out as a three-minute ramble the first time you say it. Five out-loud attempts usually fix that.
On the call
- Be somewhere quiet with a good connection, and have the job description and your CV open.
- Keep answers short and let the recruiter ask follow-ups. A conversation goes better than a monologue.
- Be specific. "I led the migration of our payments service to a new database" beats "I've done a lot of backend work".
- Close well. Thank them, confirm the next steps, and ask when you should expect to hear back.
Recruiter screen vs interview: how it's different
People sometimes ask whether the recruiter screen is "a real interview". It is, but it's a different kind from the rounds that follow:
| Recruiter screen | Later interviews |
|---|---|
| Usually a recruiter, often not technical | Engineers, managers, sometimes product partners |
| 15–30 minutes | 45–60 minutes each |
| Background, motivation, logistics | Coding, design, depth, behavioural stories |
| Checks there's no reason to stop | Checks you can do the job at this level |
| Notes summarised for the hiring manager | Detailed written feedback from each interviewer |
The practical difference is that the screen rewards clarity over depth. A recruiter can't judge whether your caching strategy was right, but they can tell whether you explained what you built in two clear sentences. Pitch your answers accordingly: plain language, specific examples, and short enough to leave room for follow-ups.
It's also the stage where you learn the most about the rest of the process, so treat it as research as well as an interview. What you find out about the stages, the team, and the timeline shapes everything you prepare next.
After the screen
How long it takes to hear back varies a lot, from the same day to a couple of weeks. If the recruiter gave you a timeline, wait until it has passed, then send a short, polite follow-up. If you don't move forward, it's reasonable to ask whether they can share any feedback, though many companies don't.
If you do move forward, the next round is usually a technical screen. Depending on the role, that might be a live coding interview (see how to prepare for a live coding interview) or a take-home assignment.
Hardmode's recruiter screen round runs the call like a recruiter who has read the job description and your CV: it asks about your background, probes the parts of your CV that match (or don't), and follows up when an answer is vague. It's a 15–20 minute rehearsal of a conversation you'll have many times.