The Perfect Screening Call Script (AI-Generated in 10 Seconds)

A screening call is the most underrated step in the hiring process. Done well, it saves everyone time — you qualify or disqualify candidates in 15 minutes instead of wasting a hiring manager’s hour on someone who wants 40% more than the budget allows. Done poorly, it’s an awkward phone call where you ask generic questions and learn nothing useful.

The difference? A structured script.

Most recruiters wing their screening calls. They open the candidate’s profile, glance at the job description, and improvise. That works when you’re doing 2-3 calls a week. When you’re doing 3-5 per day, improvisation leads to inconsistency, missed questions, and bad hiring decisions.

Anatomy of a Perfect Screening Script

A great screening script has six distinct sections. Each one serves a specific purpose, and skipping any of them leaves gaps that surface later in the process.

1. Company Introduction (2 minutes)

This is your elevator pitch for the company and role. It needs to be:

Short — under 2 minutes. Candidates zone out after that.
Simple — avoid industry jargon and internal terminology.
Spoken, not written — this isn’t a job posting. It should sound natural when you say it aloud.
Honest — don’t oversell. Candidates can tell when you’re reading marketing copy.

A good company intro answers three questions:

What does the company do? (One sentence)
Why is this role open? (Growth, new project, backfill)
What will the person actually do day-to-day?

Bad example: “We’re a leading provider of enterprise SaaS solutions leveraging cutting-edge AI/ML capabilities to transform the B2B landscape…”

Good example: “The company builds software that helps online stores manage their inventory. They’ve grown from 50 to 200 people in the last year, and they need a senior backend developer to lead a new team working on the payments system.”

2. Must-Ask Questions (3 minutes)

These are the deal-breakers. If any answer is a mismatch, you save everyone time by finding out now:

Salary expectations: “What’s your expected salary range for your next role?”
Location/remote: “This role is [hybrid in Berlin / fully remote / on-site]. Does that work for you?”
Availability: “When would you be able to start? Do you have a notice period?”
Visa/work authorization: “Are you authorized to work in [country]?” (Only where legally appropriate)
Other processes: “Are you currently interviewing elsewhere? At what stage?”

Ask these early. There’s no point spending 15 minutes on technical deep-dive only to discover the candidate expects double the budget.

3. Role-Specific Deep Dive (5 minutes)

These questions verify that the candidate’s experience matches the job requirements. They should be derived directly from the JD’s must-have requirements.

For a technical role, this might include:

Experience with specific technologies
Scale of systems they’ve worked on
Team size and leadership experience
Domain-specific knowledge

For a non-technical role:

Relevant industry experience
Key skills demonstrated in previous roles
Management or leadership scope
Metrics they’ve owned or improved

The key is to ask about specific experience, not hypotheticals. “Tell me about a time when…” is better than “How would you handle…“

4. Candidate-Specific Questions (3 minutes)

This is where most screening calls fail. Generic scripts ask the same questions to every candidate. A great script includes questions tailored to this specific candidate’s profile:

Gaps in the scorecard — if the JD requires Kubernetes experience and it’s not on the candidate’s CV, ask about it directly
Career transitions — if the candidate switched industries, ask why and what they learned
Unusual patterns — short tenures, long gaps, overqualification — address them directly but respectfully
Specific achievements — “I noticed you mention reducing deployment time by 70% at your last role. Can you walk me through that?”

These questions show the candidate you’ve actually reviewed their profile. That alone differentiates you from 90% of recruiters.

5. Good/Bad Answer Signals

For each question, your script should include signals that indicate a strong or weak answer. This keeps your evaluation consistent across candidates and helps junior recruiters make better judgments.

Example question: “Tell me about your experience with microservices architecture.”

Good signals: Mentions specific services they owned, can discuss trade-offs (monolith vs. micro), talks about monitoring/observability, references specific tools (Kubernetes, Docker, service mesh)

Bad signals: Vague answers (“I’ve worked with microservices”), can’t explain basic concepts, only knows the buzzwords without depth, describes a monolith as microservices

6. Wrap-Up and Next Steps (2 minutes)

End every screening call the same way:

Candidate questions — “Do you have any questions about the role or the company?”
Timeline — “Here’s what happens next: I’ll share your profile with the hiring team, and you should hear back within [X] days.”
Thank you — “Thanks for your time today, [Name]. I’ll be in touch soon.”

Never end a call without setting expectations for next steps. Ghosting candidates after a screening call is the fastest way to destroy your reputation as a recruiter.

Complete Example: Senior React Developer

Here’s a full screening script for a Senior React Developer position at a fintech startup:

Company Introduction

“Hi [Name], thanks for taking the time to chat. Let me give you a quick overview of the company and the role.

The company is called PayFlow — they’re a fintech startup based in Berlin, about 120 people. They build payment processing tools for e-commerce businesses in Europe. Think of it as the infrastructure that sits between online shops and banks.

They’ve been growing fast — doubled the engineering team in the last year — and now they need a Senior React Developer to join the frontend platform team. This team is responsible for the merchant dashboard — that’s what PayFlow’s customers use to manage their payments, view analytics, and configure their settings.

The day-to-day is roughly 70% coding, 20% code review and mentoring, and 10% planning and architecture discussions. The team is 6 people, fully remote across Europe.”

Must-Ask Questions

Salary: “What salary range are you targeting for your next role?”
Location: “The team is fully remote but needs overlap with CET business hours. You’re based in [city] — would that work for you?”
Start date: “When could you start? Do you have a notice period?”
Other processes: “Are you interviewing anywhere else right now? Anything close to an offer?”

Role-Specific Deep Dive

“How many years have you been working with React professionally? Which versions have you worked with?”
- Good: 4+ years, experience with hooks and modern React (18+), mentions migration from class components
- Bad: Less than 2 years, only class components, no hooks experience
“Have you worked with TypeScript in a React codebase? How strict was the config?”
- Good: Yes, strict mode, can discuss type patterns for React (generics, discriminated unions)
- Bad: No TypeScript, or only “a little bit,” or JavaScript-only background
“Tell me about the most complex frontend feature you’ve built. What made it complex?”
- Good: Specific example with technical depth — state management challenges, performance optimization, real-time data
- Bad: Vague answer, can’t articulate what was complex, describes basic CRUD
“Have you worked with any state management libraries? Which ones, and what’s your preference?”
- Good: Experience with 2+ (Redux, Zustand, Jotai), has opinions about trade-offs, mentions when global state is vs. isn’t appropriate
- Bad: Only Redux, can’t explain why, no opinion on alternatives
“This team owns a design system used by 3 other teams. Have you built or maintained a component library before?”
- Good: Yes, discusses API design, versioning, documentation, accessibility
- Bad: No experience, or only consumed design systems without contributing

Candidate-Specific Questions

(These would be generated based on the specific candidate’s profile and scorecard gaps)

“I see you’ve been at your current company for 4 years — what’s motivating the change now?”
“Your CV mentions Redux but not any modern alternatives. Have you explored Zustand or Jotai?”
“I noticed your experience is mostly in B2C products. This role is B2B — the UX patterns are quite different. How do you see that transition?”

Wrap-Up

“Those are all my questions. Do you have any questions about PayFlow or the role?”

[Answer candidate questions]

“Great. Here’s what happens next: I’ll share a summary with the hiring team this week. If they’d like to proceed, the next step is a technical interview — a 90-minute pair programming session. You should hear from me within 3 business days either way.”

“Thanks for your time today, [Name]. Talk soon.”

Tips for Non-Native English Speakers

If English isn’t your first language, screening calls can feel stressful. Here are practical tips:

Use simple sentence structures. Instead of “I was wondering whether you might be able to tell me about your experience with…” just say “Tell me about your experience with…”

Prepare your intro word-for-word. The company introduction is the one part where you’re doing most of the talking. Write it out and practice it aloud until it sounds natural.

It’s okay to ask candidates to repeat. “Sorry, could you say that again?” is perfectly professional. It’s better than pretending you understood.

Don’t apologize for your English. It undermines your authority. You’re the one conducting the interview — own it.

Use the script as a safety net. Having questions written down means you never freeze or lose your train of thought. Even native speakers benefit from this.

Post-Call Notes Template

Immediately after the call (within 5 minutes while it’s fresh), record:

Overall impression: Strong / Maybe / Weak
Salary match: Yes / Negotiate / No
Availability: Date or notice period
Technical depth: Exceeded / Met / Below expectations
Key strengths: 2-3 bullet points
Concerns: Anything that needs clarification in the next round
Recommendation: Advance / Reject / Hold
Notes: Anything memorable or important for the hiring manager

This takes 2 minutes and saves 10 minutes later when you need to brief the hiring manager or compare candidates.

Why AI-Generated Scripts Win

Manually writing a screening script takes 15-20 minutes. You need to read the JD, identify key requirements, think of good questions, consider the specific candidate’s background, and format everything clearly.

AI-generated scripts take 10 seconds — and they’re better, because:

They cross-reference the JD requirements with the candidate’s actual profile
They identify gaps and generate targeted questions automatically
They include good/bad answer signals based on the role requirements
They’re consistent — every candidate gets an equally thorough evaluation
They’re always up to date with the latest JD changes

The recruiter’s job shifts from writing questions to reviewing and personalizing an already-excellent script. That’s a 95% time reduction on prep with better outcomes.

Want screening scripts generated in 10 seconds? Try Inga CRM free — one-click screening prep that cross-references the job description with each candidate’s profile.