Vet Potential Candidates Fast: A Recruiter's Checklist

Table of Contents

Introduction

Every recruiter has had this happen. The resume matched the job description line for line, the candidate sounded sharp on the phone, and the client's first technical interview fell apart in ten minutes.

The fix is learning to vet potential candidates earlier, on the first call and before the submittal, not after the client has spent an hour on them.

This guide is a working checklist for that stage: what to confirm in a 15-minute screen, how to test resume claims, what to ask about availability and work authorization, and when a red flag should stop a submittal.

If you want the broader picture first, start with what vetting a candidate means and how it differs from screening.

TL;DR

Vet potential candidates before the first submittal, because every weak candidate a client interviews costs you credibility on the next req.
A 15-minute screening call should confirm skills, project depth, availability, rate and work authorization.
Test resume claims by asking candidates to walk through one real project in detail, including their own part in it.
Score every candidate the same way, so your submittal decisions don't depend on how the call felt.
Pause the submittal when answers conflict with the resume, dates don't line up, or the candidate won't commit to a start date.

Why recruiters vet potential candidates before the first submittal

Clients judge a vendor on its first few submittals. Send two strong candidates and your next profiles get opened quickly. Send two who can't explain their own resumes and your submittals start sitting in the queue.

Early vetting also protects your time. A candidate who drops out at the offer stage, or turns out to need sponsorship the client can't offer, has already cost you sourcing hours, prep calls and interview coordination.

Most of those problems can be caught in the first conversation if you ask the right questions.

What to cover in the first screening call

The first call isn't an interview. It's a check on whether this person is worth a client's time. Keep it to 15 or 20 minutes and cover the same ground with everyone.

The core checks

Check	Question to ask	A weak answer sounds like
Core skills	"Which of the required skills have you used in the last two years, and on what project?"	Lists tools without naming a project
Project depth	"What was your specific part in that project?"	Talks only about what "we" or "the team" did
Role fit	"What would you want to do more of, and less of, in your next role?"	Describes a very different role from the one on offer
Availability	"If an offer came this week, when could you start?"	"It depends" with no clear notice period
Rate or salary	"What rate are you targeting for this kind of contract?"	A number far outside the client's range, with no flexibility
Other processes	"Are you interviewing anywhere else right now?"	Several late-stage offers they won't discuss
Work authorization	"Are you authorized to work in the U.S., and will you need sponsorship now or later?"	Vague or changing answers

Write the answers down while you talk. You'll need them for the scorecard and for the client write-up.

Questions to keep out of the call

Vetting should stick to what the job requires. The U.S. Equal Employment Opportunity Commission's guidance on prohibited employment policies and practices advises limiting pre-employment questions to information needed to judge whether someone is qualified.

In practice, don't ask about age, religion, marital status, family plans, national origin or disability.

Ask whether the candidate is authorized to work and needs sponsorship, not where they're from or what their citizenship is.

How to test resume claims without a full technical interview

You don't need to be an engineer to spot a padded resume. You need a few questions that are hard to answer with rehearsed lines.

The one-project walkthrough

Pick the most relevant project on the resume and ask the candidate to walk you through it. Listen for these details:

What the system or product did, in plain terms
How big the team was and who they reported to
Which parts they built or owned themselves
One problem that went wrong and how they fixed it
The tools and versions they used, and why those were chosen

Candidates who did the work can usually answer all five without hesitating. Candidates who borrowed the project from a colleague's resume tend to stay general and repeat the job description back to you.

Check dates and titles against each other

Look for overlapping contracts, very short stints on long projects, or a title that jumps two levels between roles. None of these is a problem on its own. Ask about them directly and see whether the explanation makes sense.

If something still feels off, such as a voice that doesn't match an earlier call or a LinkedIn profile created last month, our guide to identifying and preventing fake candidates covers ID and video verification in more depth.

Availability, intent and rate alignment

Skills get most of the attention during vetting, but availability and intent cause more failed placements. A strong candidate who takes a counteroffer is still a failed submittal.

Ask these before you submit:

Why are you looking? "My contract ends in three weeks" is a clear reason. "Just seeing what's out there" usually means a low chance of closing.
What would make you stay where you are? This tells you how likely a counteroffer is to work.
Have you been submitted to this client by anyone else? Get written right-to-represent before you send the profile, so you avoid duplicate-submission disputes.
Is the rate you gave firm? Confirm it again right before the submittal, not only at the offer stage.

Work authorization and checks at the shortlist stage

Confirm work authorization early, but handle the documents at the right point in the process.

At the screening stage, ask whether the candidate is authorized to work in the U.S. and whether they'll need sponsorship.

Before start, the employer of record completes Form I-9 to verify identity and work authorization, as explained in USCIS's Form I-9 guidance.

If your desk places a mix of visa holders and citizens, our breakdown of work authorization requirements explains what each category involves.

Background checks run through a screening company come with their own rules. The FTC's guide to background checks for employers explains the disclosure and written-permission requirements.

Reference calls fit here too, and they work best with specific questions, not "would you rehire them?" Our guide on reference check questions has examples.

A simple scorecard for potential candidates

A scorecard stops you from submitting someone just because the call went well. Score each area from 1 to 3 right after the call, while your notes are fresh.

Area	1 (weak)	2 (acceptable)	3 (strong)
Must-have skills	Missing one or more	All present, some dated	All used recently on real projects
Project depth	General answers only	Clear on most details	Explains own work, problems and choices
Availability	No clear start date	Start date within client's window	Available on or before the target date
Rate fit	Outside the range	At the top of the range	Comfortably inside the range
Intent	Browsing, several offers	Active search, some options	Clear reason to move, committed to this role
Work authorization	Unclear or conflicting	Confirmed, needs checking	Confirmed and matches client requirements

A workable rule: submit candidates who score 14 or higher out of 18 with no 1s in must-have skills or work authorization. Adjust the threshold for your clients, but use the same one for every candidate on the same req.

Red flags that should pause a submittal

One red flag doesn't always mean rejection. It means you ask one more question before the profile goes to the client.

Red flag	What it might mean	What to do
Answers don't match the resume	Padded or borrowed experience	Run a second call focused on one project
Can't name their own contribution	Worked near the skill, not with it	Ask for a specific task they owned end to end
Dates overlap or don't add up	Rounded dates, or hidden short stints	Ask directly and note the explanation
Avoids the start date question	Waiting on another offer	Confirm notice period in writing before submittal
Rate keeps moving	Using your offer for leverage elsewhere	Agree the rate in writing, or hold the submittal
Camera off or refuses video	Could be personal preference, or an identity issue	Require a short video call before submittal
Already submitted by another vendor	Duplicate submission risk	Don't submit without written right-to-represent

When to stop vetting and submit

Vetting has a cost too. Every extra round slows your submittal, and on a competitive req the first strong profile often gets the interview.

Stop when you have confirmed the must-have skills through a real project, the start date and rate fit the client's range, work authorization matches the requirement, and you have written right-to-represent.

That's enough to vet potential candidates well at the submittal stage. The client's own interviews and the final background checks cover the rest.

If you'd rather receive candidates who already pass these checks, here's what pre-vetted candidates should mean and how to tell whether a vendor's vetting is real.

Start Strong With Consultadd

With 15 years in business and 5,000+ successful staffing engagements, we don't just fill roles, we build reliability into your process. We've supported 65 staffing companies in the past year alone and maintain MSAs with industry leaders like Robert Half and TEKsystems.

Here's what working with Consultadd looks like:

Talent sourced in under 24 hours
Ready-to-deploy candidates, vetted for experience and compliance
Lower turnover risk: we match long-term goals, not just short-term needs
Seamless compliance: visa, documentation, onboarding? Handled.
Dedicated 1:1 account managers for responsive, personalized support
Top 100 candidate matches delivered in the past year
Strong partnerships with universities to tap into fresh, committed talent
Post-placement support so your investment grows beyond day one

For candidates, your next opportunity is more than just a job title, it's a chance to build skills, gain experience, and move your career forward. At Consultadd, we connect technology professionals with projects and employers that align with their goals, whether they're looking for contract, contract-to-hire, or long-term opportunities.

The tech job market moves fast, but the right guidance can make all the difference. Ready to take the next step in your career journey? Explore Opportunities >>

Key takeaways

Vetting potential candidates before submittal protects your standing with the client on every future req.
A short, consistent screening call covering skills, project depth, availability, rate and work authorization catches most problems early.
A one-project walkthrough is the fastest way to test resume claims without a full technical interview.
Score every candidate on the same criteria and set a clear submittal threshold.
Treat red flags as a reason for one more question, and get written right-to-represent before any profile goes out.

FAQs

How do you vet a potential candidate quickly?

Run a 15 to 20 minute screening call with the same questions for every candidate. Confirm must-have skills through one real project, then check start date, rate, other processes and work authorization. Score the call right away so you can compare candidates fairly.

What questions should you ask when screening a candidate?

Ask which required skills they've used recently and on what project, what their own part was, when they could start, what rate they're targeting, and whether they're authorized to work and need sponsorship. Keep every question tied to the job's requirements.

What questions are illegal to ask during candidate screening?

Avoid questions about age, religion, marital status, pregnancy or family plans, national origin and disability. The EEOC advises keeping pre-employment questions to what's needed to judge whether someone is qualified. State and local laws may add limits, such as salary history bans, so check the rules where you hire.

How can recruiters tell if a resume is exaggerated?

Ask the candidate to walk through one project in detail, including team size, their own tasks and a problem they solved. People who did the work give specific answers without much hesitation. Vague "we did" answers and dates that don't add up are signs to dig deeper.

Should recruiters check references before submitting a candidate?

For most contract roles, references come after the client shows interest, but it helps to confirm the candidate can provide them early. For senior roles or new clients, a quick reference call before submittal can be worth the time. Use specific questions about past projects, not generic ones.

How long should candidate vetting take before a submittal?

For most contract tech roles, the recruiter's part can be done within a day: one screening call, a short follow-up if needed, and right-to-represent in writing. Background checks and I-9 verification come later, closer to the offer and start date.