Recruiter Screening Call: What to Say and Avoid

The recruiter screening call is the gate almost every IT job passes through, and freshers routinely underestimate it. It feels informal — a friendly ten-minute chat — so people wing it, and then quietly never hear back. The call is short precisely because it is a filter: the recruiter is confirming you match the role, are actually available, and can hold a clear conversation before they spend a senior engineer's time on you. Handle it well and you advance; fumble it and the strongest technical skills never get a chance to show. This guide covers exactly what to say, what to avoid, and how to prepare in fifteen minutes.

What the call is actually for

A screening call is not a technical interview. The recruiter usually is not the person who will judge your code. Their job is to answer three questions on the company's behalf: does this candidate genuinely match the requirements, are they available on a workable timeline and budget, and can they communicate like someone we could put in front of a client or team. Everything they ask maps to one of those three. Once you see the call through that lens, your answers get sharper — you are giving evidence for "yes, match; yes, available; yes, clear communicator."

What recruiters ask, and how to answer

The questions are predictable. Prepare a crisp answer for each:

Typical screening questions
- "Tell me a bit about yourself"        -> 30-second focused intro
- "Walk me through your key skills"      -> match them to the JD
- "Tell me about a project you built"    -> one project, 2-3 sentences
- "What is your notice period / status?" -> honest and specific
- "What are your salary expectations?"   -> researched, realistic range
- "Preferred location? Open to office?"  -> clear yes/no
- "Why are you interested in this role?"  -> a genuine, specific reason

For the introduction, keep it to thirty seconds: who you are, your core stack, and what you are looking for — not your life story. For skills, explicitly mirror the job description's language so the recruiter can tick their boxes. For your project, name what you built, the tech, and the outcome in two or three sentences; this is the fresher's strongest card, so have it ready.

Notice period and availability

Be honest and specific. If you are a fresher available immediately, say so — it is an advantage. If you are serving notice, state the real last working day or notice length. Vagueness here reads as either disorganization or hiding something, and it slows the process. Recruiters plan around this number, so giving a straight answer builds trust immediately.

Handling the salary question

This is where freshers stumble most. Two failure modes: quoting an inflated number pulled from a random online figure, or dodging entirely with "as per company standards," which frustrates the recruiter who needs a workable range. The better move is to give a researched, realistic range. Before the call, check current market rates for the role on the job portals so your number is grounded rather than aspirational. If you genuinely do not know the band as a fresher, it is fine to say you are open and ask what range the role sits in — that keeps the conversation productive without either lowballing yourself or pricing yourself out silently.

Salary answer patterns
GOOD (researched):  "Based on what I've seen for this role, I'm looking at
                     roughly X to Y; I'm flexible for the right opportunity."
GOOD (fresher):     "I'm open on numbers — could you share the range for
                     this role so I can tell you if it works?"
WEAK:               "As per company standards." (dodges, frustrates)
WEAK:               A single inflated number with no basis.

Showing genuine interest

Recruiters can tell the difference between "I applied to two hundred jobs and cannot remember this one" and "I looked at this role and here is why it fits." A specific reason — the technology, the type of product, the chance to grow in a particular area — signals you will actually take the offer if extended, which matters to a recruiter judged on candidates who stick. Spend thirty seconds before the call recalling what the role was and why you applied.

What to avoid

Several answers quietly end candidacies. Do not:

• Ramble. If you cannot answer a simple question in under a minute, the recruiter worries about client calls. Be crisp.
• Badmouth an employer. Complaining about a current or former company, college or manager reads as a future risk. Keep reasons for leaving neutral and forward-looking.
• Quote an unrealistic salary with no basis, or refuse to engage on numbers at all.
• Sound unsure whether you want the job. Lukewarm interest gets deprioritized in favour of eager candidates.
• Fail to describe your own project or skills. If you cannot summarize what is on your own resume, it undermines everything.

A fifteen-minute preparation routine

You do not need hours. Before any screening call, run this:

Pre-call prep (15 minutes)
[ ] Re-read the job description; note the exact skills they want
[ ] Rehearse a 30-second introduction out loud
[ ] Prepare a 2-3 sentence summary of your best project
[ ] Confirm your notice period / availability in one line
[ ] Research a realistic salary range on job portals
[ ] Note one genuine reason you want this specific role
[ ] Find a quiet spot with good signal; keep your resume open

Saying your introduction and project summary out loud once, rather than only reading them, is what makes them come out smoothly on the call. Speaking is a separate skill from knowing.

After the call

If the recruiter says they will get back to you and a reasonable window passes with silence, a single polite follow-up is appropriate — the timing and wording of which are covered in the job application follow-up etiquette guide. Also make sure the profile they found you through is clean and keyword-matched in the first place, which the Naukri profile optimization guide walks through.

The bottom line

Treat the screening call as the decisive filter it is, not a casual chat. Be crisp about your skills and project, honest about availability, grounded on salary, and clearly interested in the role. Avoid rambling, negativity and vague numbers. Fifteen minutes of preparation and one out-loud rehearsal put you ahead of most freshers, who walk in cold. If you want to practise these answers under realistic pressure, a CodeBegun readiness session can help you sharpen them before the calls that count.