Hiring & Recruitment

Introduction

Most teams know their time to fill. Very few know which part of it is the problem. A 55-day average doesn't tell you whether the role sat in approval for two weeks, whether sourcing came up empty, or whether a strong candidate waited nine days for interview feedback.

This guide breaks time to fill into stages so you can see where your hiring days actually go. It includes a simple audit you can run on your last ten hires, a way to estimate what a slow fill costs, and specific fixes for the stages that stall IT roles most often. 

If you need the basic formula or industry benchmarks, our comparison of time to hire vs time to fill covers those in detail.

TL;DR

• A single time to fill number hides the real problem. Splitting it into stages shows where the days are lost.
• The federal government already uses a stage-based model with suggested days per step, and private teams can borrow the approach.
• Auditing your last ten hires by stage takes an afternoon and usually shows one or two stages causing most of the delay.
• In IT hiring, the slowest stages tend to be intake and approval, sourcing for niche skills, and offer or compliance steps.
• Put a daily cost on vacancy so delays become a business conversation, not just a recruiting complaint.

What the time to fill metric actually captures 

Time to fill counts the calendar days from when a role is opened to when a candidate accepts the offer. That's the short version, and it's enough for this guide.

What matters more is agreeing on the exact start and end events. Some teams start the clock when a hiring manager asks for headcount. 

Others start it when HR approves the requisition or when the job is posted. Some stop at offer acceptance, and others stop at the start date.

Pick one definition and write it down. If two recruiters measure differently, stage-level analysis falls apart, because you're comparing different things.

Time to fill by stage: borrowing the federal model 

The clearest public example of stage-based hiring measurement comes from the U.S. Office of Personnel Management. Its End-to-End Hiring Initiative sets an 80-day hiring standard and tracks the share of employees hired within that window. 

OPM notes that the days assigned to each step are suggestions, and agencies can shift them as long as the total stays within 80 days.

Here's how one agency, USDA's Farm and Foreign Agricultural Services, mapped that model:

You don't need to copy federal steps. The useful idea is the structure. Every stage has an owner and a time budget, so when hiring runs long, you can point to the stage that broke. 

Keep in mind that the federal model measures all the way to the start date, which is later than where most private teams stop the clock.

Even with a budget per stage, delays happen. OPM set the 80-day target, but federal agencies averaged 105.8 days at the 2016 and 2017 peak and 98.3 days in 2018. Having a model doesn't fix time to fill on its own. It shows you where to look.

How to audit your average time to fill 

You don't need new software for this. An ATS export or even a shared spreadsheet works.

Pull your last ten filled roles, ideally from the same job family, such as software engineering or data. Then record the date each role hit these milestones:

1. Headcount requested by the hiring manager
2. Requisition approved
3. Job posted or sent to recruiters and partners
4. First qualified candidate submitted to the hiring manager
5. First interview held with the eventual hire
6. Final interview completed
7. Offer extended
8. Offer accepted

Now calculate the days between each milestone and average them across the ten roles. The result will look something like this:

In most audits, one or two stages account for most of the delay. That's good news, because it means you can fix a specific problem instead of trying to speed up everything at once.

One tip from recruiters who run these audits often: look at the range, not just the average. If sourcing takes 4 days for some roles and 30 for others, the question isn't "why is sourcing slow?" It's "which roles are hard to source, and why?"

How to reduce time to fill for IT roles, stage by stage 

Tech hiring has its own pressure points. Skill sets are narrow, candidates often have multiple offers, and contract roles come with extra compliance steps. 

Here's where to focus once your audit shows the slow stage:

1. Intake and approval

A lot of delay happens before a single candidate is contacted. The fix is a 30-minute intake meeting between the recruiter and hiring manager on day one.

Settle four things in that meeting: the must-have skills, the nice-to-haves, the salary or bill rate range, and who has final say on the hire. When these are fuzzy, the search restarts halfway through. That's one of the most expensive mistakes in IT hiring, because the calendar keeps running.

It also helps to keep pre-approved job templates for roles you hire often, like Java developers or cloud engineers. Starting from a template cuts days out of the launch stage.

2. Sourcing

Sourcing is usually the longest stage for niche tech roles. A posted job for a Kubernetes specialist or a Salesforce architect may not get many qualified applicants no matter how well it's written.

A few things make a real difference:

• Go back to strong finalists from past searches. A candidate who came second six months ago may be available now.
• Keep a warm pipeline for roles you fill every quarter, even when nothing is open.
• Bring in a staffing partner early for hard-to-fill skills, rather than after the posting has been live for a month.

3. Screening and interviews

Once candidates arrive, the delay usually shifts to the hiring team. Shortlists sit in inboxes, and interviews get scheduled a week out.

Try blocking recurring interview slots on the hiring team's calendars while a role is open. Some teams run a single "interview day" where the candidate meets everyone in one session.

For a structured way to design those rounds, see our guide to IT staffing best practices.

4. Offer, compliance and acceptance

This last stretch gets less attention than it should. Offers wait on compensation approval, and contract hires wait on documentation, background checks or work authorization review.

Pre-approve salary or rate bands before interviews start, so the offer goes out within a day of the final interview. 

Start background checks and paperwork as soon as a verbal yes comes in, instead of waiting for every signature first. And keep your second-choice candidate warm until the start date. Offers do fall through.

Putting a price on the cost of vacancy

Recruiters often know time to fill is too long but struggle to get leadership to act. Putting a daily cost on an empty seat changes that conversation.

There's no universal number, but you can build a rough estimate for your own roles:

The numbers above are hypothetical, not a benchmark. Use your own finance team's estimate of what the role produces. Even a rough figure helps a hiring manager see why a nine-day wait for interview feedback isn't a small thing.

Labor market conditions add pressure too. The U.S. Bureau of Labor Statistics reported 7.3 million job openings in July 2026, according to its latest JOLTS release. 

With that many open roles competing for talent, strong tech candidates rarely wait around for slow processes.

When a staffing partner shortens time to fill (and when it won't) 

A staffing partner helps most in the sourcing stage, because they start with candidates who are already screened and available. 

For contract and contract-to-hire roles, they can also take on compliance and onboarding paperwork, which speeds up the final stage.

A partner won't fix slow internal stages. If requisitions sit in approval for two weeks or interview feedback takes ten days, you'll get great candidates faster and then lose them at the same bottleneck. Run your audit first so you know which problem you're paying to solve.

If you're comparing options, our review of the best IT staffing firms explains what to look for. 

It's also worth reading why IT contract staffing works as a business strategy, since a contract hire can fill the seat while a permanent decision takes longer.

Setting a time to fill target you can actually hit 

A useful time to fill target is built from your own stage data, not borrowed from a national average. Start with your audit, then set a time budget for each stage, the way OPM's model does. Give every stage an owner, and review the numbers monthly by job family.

Aim to improve the slowest stage first. Cutting a two-week approval delay to three days will do more for your time to fill than shaving a day off every other step. Once that stage is under control, the audit will show you the next one.

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

• Break time to fill into stages with a clear owner and time budget for each, so delays can be traced to a specific step.
• Audit your last ten hires by milestone. One or two stages usually cause most of the delay.
• For IT roles, focus on intake clarity, early sourcing for niche skills, blocked interview time and pre-approved offer ranges.
• Estimate a daily cost of vacancy with your finance team to make hiring delays a business priority.
• Use staffing partners to speed up sourcing and compliance, but fix slow internal approvals and feedback first.

FAQs

What is a good time to fill for IT roles?
It depends on the seniority and how niche the skill set is. Senior or specialized tech roles usually take longer than general roles. Track your own time to fill by job family over several quarters and aim to improve on that trend, rather than chasing a single industry number.

How do you calculate time to fill?
Count the calendar days from the date the role is opened to the date the candidate accepts the offer. For an average, add up the days for all hires in a period and divide by the number of hires. 

What causes a long time to fill?
The most common causes are unclear role requirements, slow requisition approval, a thin talent pool for niche skills, and slow feedback from hiring managers. Offer approvals and background checks can add days at the end. A stage-by-stage audit shows which of these applies to your team.

How can I reduce time to fill quickly?
Start with the slowest stage in your audit, since that's where you'll recover the most days. Quick wins include a day-one intake meeting, pre-approved salary ranges and blocked interview slots on hiring managers' calendars. For hard-to-fill roles, bringing in a staffing partner early also helps.

Does time to fill include onboarding?
Usually not. Most private employers stop the clock at offer acceptance. Some organizations, including federal agencies following OPM's model, measure through the start date, so check which definition a benchmark uses before comparing.

Is a shorter time to fill always better?
Not if speed comes at the cost of a bad hire. The goal is to remove waiting time, like delayed feedback or approvals, not to skip evaluation steps. Track quality of hire and early retention alongside time to fill so you know speed isn't hurting results.

Introduction

You don't need to write code to recruit engineers. You do need to know what the words mean, because a hiring manager who says "we need someone strong on Kubernetes and Terraform, ideally with SRE exposure" is describing a specific person, and you can't find that person by pattern-matching on keywords.

This is a working glossary of the technology terms that show up most in job descriptions, resumes, and screening calls. Each entry has a plain-English definition plus a short note on what it actually signals when you see it on a resume.

It's organized by category so you can jump to what you need. Nothing here requires a technical background to follow.

TL;DR

• Technology terms cluster into roles, languages, infrastructure, data, process, and security. Learning the clusters beats memorizing a long alphabetical list.
• The words that cause the most hiring mistakes are the ones that look similar, like Java and JavaScript, or DevOps and SRE.
• A tool name on a resume tells you less than the context around it. Two years of daily use and one weekend tutorial can read identically.
• Version and scale details matter more than the tool itself. React for a 5-person startup and React for a 200-engineer platform are different jobs.
• You don't have to fake expertise. Asking a candidate to explain something is a better screening move than pretending you already know it.

How To Use This Glossary 

Two ways to read this.

If you're new to technical recruiting, skim the role definitions first, then the process section. Those two give you enough to follow a conversation with a hiring manager.

If you're already sourcing and just hit a term you don't recognize, jump to the category and move on.

One caution before the lists start. A glossary tells you what a word means, not how much someone knows. "Experience with AWS" covers everything from spinning up one server to architecting a multi-region system. 

The follow-up question is always what matters, and there's a section at the end on how to ask it.

For broader context on where these skills sit in the job market, the BLS occupational outlook for computer and information technology is a reasonable baseline for role definitions and demand.

Roles And Job Titles 

Programming Languages And Frameworks 

A framework is a structure built on top of a language that handles common tasks so developers don't rebuild them. A library is a smaller collection of reusable code. 

The distinction rarely changes a sourcing decision, but confusing a framework with a language does.

Cloud And Infrastructure 

Cloud computing has a formal definition worth knowing, since the service model acronyms come directly from it. NIST Special Publication 800-145 defines cloud computing along with its three service models and four deployment models.

Data, Analytics, And AI 

How Software Actually Gets Built 

These terms come up in every hiring manager conversation, and knowing them makes you sound informed faster than knowing any language name.

If a hiring manager starts talking about delivery performance, they're often referring to a common set of measures. 

Google's DORA research defines four software delivery metrics covering speed and stability, and those four show up in engineering leadership conversations often enough to be worth recognizing.

Security Terms Worth Knowing

Security roles split into offensive (finding weaknesses), defensive (detecting and responding), and governance (policy and compliance). They attract different candidates and different rates, so it's worth clarifying which one a req actually needs.

Technology Terms People Mix Up 

This section prevents more bad submissions than any other list here.

Java and JavaScript. Different languages, unrelated origins, different jobs. A Java developer is generally not a JavaScript developer.

DevOps and SRE. DevOps is a set of practices connecting development and operations. SRE is a specific engineering discipline focused on reliability, typically with uptime targets and incident response responsibilities. A DevOps engineer and an SRE can both exist on one team doing different work.

AI and machine learning. ML is a subset of AI. "AI experience" on a resume usually means ML work or, increasingly, building on top of existing LLMs, which is a different skill from training models.

Data engineer, data scientist, and data analyst. The engineer builds pipelines, the scientist builds models, the analyst answers business questions with existing data. Submitting one for another is a common and avoidable miss.

API and SDK. An API is the interface. An SDK is a package of tools and libraries for building against a platform.

Front-end and full-stack. Many candidates describe themselves as full-stack when their backend experience is thin. Ask what they built on the server side and how recently.

Cloud certification and cloud experience. A certification proves someone studied. It doesn't prove they've run anything in production. Both matter, neither substitutes for the other.

Using These Terms In A Screening Call 

Knowing the vocabulary is step one. Using it without overreaching is step two.

Three questions that work regardless of how technical you are:

"Walk me through what you actually did with it." A candidate who used Kubernetes daily describes specific problems. One who touched it once describes what it is. You don't need to evaluate the answer technically to hear the difference.

"How big was the system and how big was the team?" Scale context changes everything. Same tool, very different job.

"What part of this stack would you not want to work on again?" Honest candidates answer specifically, and the answer usually tells you where their real depth is.

And when you don't know something, say so and ask. Candidates respond better to a recruiter who asks a clear question than one who bluffs through a term they've misread. 

If you're building out the broader process around these conversations, Consultadd's guide to technical recruitment covers sourcing and screening structure, and the candidate vetting sequence covers what happens after the screen.

For candidates on the other side of this conversation, the 2026 coding interview playbook covers what these terms look like when they show up in technical rounds.

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

• Technology terms are easier to learn in clusters, by role, language, infrastructure, data, process, and security, than as a flat alphabetical list.
• The most expensive confusions are between similar-sounding terms: Java and JavaScript, DevOps and SRE, data engineer and data scientist.
• A tool name on a resume carries no information about depth. Scale, team size, and recency do.
• Process vocabulary like sprint, pull request, and CI/CD buys you more credibility with hiring managers than memorizing framework names.
• Asking a candidate to explain something you don't know is a stronger screening move than bluffing, and it usually produces better information.

FAQs

What are the most important technology terms for a non-technical recruiter to learn first?
Start with role definitions and process vocabulary. Knowing the difference between front-end, back-end, DevOps, and data roles, plus terms like sprint, pull request, and CI/CD, covers most hiring manager conversations. Language and framework names can be looked up as they come up.

Is Java the same as JavaScript?
No. They are separate languages with different uses, different ecosystems, and different developer communities. The similar name is a historical marketing decision, and treating them as related is one of the most common sourcing errors in tech recruiting.

What's the difference between DevOps and SRE?
DevOps describes practices that connect software development and operations, usually with heavy automation. SRE is a specific engineering role focused on system reliability, often with defined uptime targets and on-call incident response. Some companies use the titles loosely, so confirm the actual responsibilities with the hiring manager.

Do candidates need cloud certifications?
It depends on the role and the client. Certifications demonstrate structured knowledge and sometimes satisfy a client or partner requirement, but they don't demonstrate production experience. Treat them as a supporting signal rather than a qualification on their own.

How do I tell whether a candidate really knows a technology?
Ask what they built with it, how large the system was, and what went wrong. Depth shows up in specific problems and specific trade-offs. Surface familiarity tends to produce textbook definitions instead of stories.

How often do these technology terms change?
Core concepts like APIs, containers, and version control stay stable for years. Specific tools and frameworks shift faster, particularly in front-end and AI work. Reviewing the tool names in your active job descriptions every six months is usually enough to stay current.

Introduction

Pre-employment screening is the part of hiring where a mistake costs you twice. Run too little and you find out about a problem after someone has system access. Run it carelessly and you end up on the wrong side of a federal law that comes with its own private right of action.

The good news is that the rules are clearer than most people assume. There's a required sequence, there's a required set of notices, and once your process follows both, screening becomes an operational problem rather than a legal one.

This guide covers how to decide what to check, the federal steps that apply when a third party runs your reports, realistic turnaround times, and the points where hiring teams lose days without noticing.

If you're building the wider hiring process rather than the screening piece specifically, Consultadd's guide to the candidate vetting sequence that cuts bad hires covers references, skills validation, and where teams cut corners.

TL;DR

• Pre-employment screening means verified checks run before someone starts, usually through a third-party consumer reporting agency, which triggers specific legal obligations.
• The FCRA requires a standalone written disclosure and the candidate's authorization before you order any report.
• If anything in a report might cost someone the job, you owe them a pre-adverse action notice with a copy of the report and a summary of their rights, plus time to respond.
• Screening depth should follow the risk of the role. Running executive-level checks on every hire adds days and money without adding safety.
• Most screening delays come from candidate data entry errors and manual court records, not from the provider being slow.

What Pre-Employment Screening Covers 

Pre-employment screening is the verification layer that sits between an offer and a start date. Interviews tell you what someone says about themselves. Screening confirms the parts that can be checked against records.

A typical program pulls from a handful of check types:

• Identity and Social Security trace, which establishes name history and addresses to search
• Criminal history searches at county, state, and federal levels
• Employment verification with previous employers
• Education and credential verification
• Motor vehicle records, for roles that involve driving
• Credit history, only where the role genuinely justifies it and state law allows it
• Drug testing, where applicable to the role and jurisdiction

The important distinction is who runs the check. When you use a third-party company to compile background information, the report becomes a consumer report and the Fair Credit Reporting Act applies. 

Googling a candidate yourself sits outside the FCRA, but still sits squarely inside anti-discrimination law.

Reference calls are a separate exercise with a different purpose. They gather judgment rather than records, which is why they need different questions. 

Consultadd has a breakdown of reference check questions that surface something useful if that part of your process has gone generic.

Match The Checks To The Role, Not The Company 

One screening package applied to every position is the most common design mistake. It over-screens junior roles, under-screens sensitive ones, and gives you no defensible logic if a candidate challenges a decision.

Write the policy by tier instead, and document why each tier gets what it gets.

Two rules keep the policy defensible. Apply each tier consistently to everyone in it, and write down the business reason for each check before you need to explain it.

Credit checks deserve particular care. 

Several states restrict employment credit checks to specific job categories, and the EEOC and FTC joint guidance for employers advises reviewing state and municipal rules on top of federal law, because many localities regulate what you can consider and when you can ask.

The Legal Steps You Cannot Skip

This is the section worth printing. When a third party runs your reports, the sequence below is not optional.

Before you order the report

You need a written disclosure telling the candidate you may obtain a background report for employment purposes, and you need their written authorization.

The disclosure has to be a standalone document. The FTC's guidance for employers is specific that this notice should be clear and not buried inside other paperwork. 

Burying it in the job application, or bolting a liability waiver onto it, is one of the most litigated FCRA mistakes there is. Keep the document to what it is: a plain notice and a signature line.

After the report comes back

If something in the report might cause you not to hire the person, a two-step process applies.

One more thing the same guidance covers: dispose of background reports securely once you're done with them. Shredding for paper, proper deletion for files.

Candidates have their own set of rights here, laid out in the EEOC and FTC guidance written for applicants. It's worth reading the applicant version too, because it tells you exactly what a well-informed candidate will expect from you.

How Long Screening Takes And What Slows It Down 

Most hiring teams budget two days for screening and then lose a week. Here's where the time actually goes.

The single biggest controllable delay is candidate data entry. A typo in a Social Security number, a missing former address, an employer name without the legal entity. Every one of those bounces the file back and restarts a queue.

Fixing that is unglamorous: a clear instruction email, a named person the candidate can ask questions of, and a check on the submitted form before it goes to the provider.

Sequencing helps too. Order everything in parallel rather than waiting for the criminal search to clear before starting employment verification. And start the process the day the offer is accepted, not the day before the intended start date. 

If your overall hiring timeline keeps slipping for reasons like this, Consultadd's piece on why hiring processes take longer than they should covers the other usual culprits.

Where Screening Budgets Get Wasted 

Screening costs scale with scope, and scope is where the waste happens.

Running a seven-year, multi-county criminal search plus credit plus education on an entry-level role costs more and takes longer than a tiered approach, without making the hire any safer. That's money and days spent on a risk the role doesn't carry.

Three other patterns worth checking in your own process:

Duplicate screening. Contractors placed through a staffing partner have usually already been screened. Running the same package again is a second invoice for the same information. Ask what your partner already ran and what documentation they can share.

Re-screening on rehire without a policy. Some companies re-run everything for a boomerang employee who left four months ago. Others never re-screen anyone. Neither is a decision, they're both defaults.

Paying for speed you don't use. Expedited processing is worth it when a start date is fixed. It's wasted when the hiring manager takes three days to review results anyway.

The Candidate Experience Nobody Designs 

Screening is often the last impression a candidate has before day one, and it's usually the worst-designed part of the process.

They've resigned from their jobs. They're being asked for a Social Security number, addresses going back seven years, and consent to a criminal search, frequently by an unfamiliar company with no explanation attached. Then they hear nothing for six days.

Three small fixes handle most of it:

• Tell them in advance what will be checked, who the provider is, and roughly how long it takes
• Give them a named contact for questions, not a no-reply address
• Message them proactively when something is taking longer than expected

Candidates who feel informed complete forms faster and accurately, which shortens your timeline. The courtesy and the efficiency point in the same direction here.

Screening Contractors And Visa Holders

Two groups get treated as exceptions, and both deserve the same rigor as everyone else.

1. Contractors

Short engagements often get a lighter screen on the assumption that less time means less risk. 

That logic doesn't hold when a three-month contractor has the same repository and production access as a full-time engineer. Screen by access level and role risk, not employment type.

2. Visa holders. 

Work authorization verification is separate from background screening and legally mandatory for everyone. Every US employer must complete Form I-9 for each new hire, regardless of citizenship. 

That requirement applies uniformly, and applying extra scrutiny to candidates based on perceived national origin creates discrimination exposure of its own.

If your team handles a mix of citizens, visa holders, and contractors, Consultadd's guide to work authorization requirements for new hires breaks down what documentation each category needs.

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

• Pre-employment screening is the verified layer of hiring, and using a third-party provider brings FCRA obligations along with it.
• A standalone written disclosure and the candidate's authorization come before any report is ordered. No exceptions, no bundling into the application.
• The pre-adverse action step exists because reports contain errors. Send the report, wait a reasonable period, then finalize.
• Tier your screening policy by role risk and write down the reasoning, so the process is consistent and explainable.
• Most delays trace back to candidate data errors and manual court records, both of which you can plan around.

FAQs

What is the difference between pre-employment screening and a background check?
A background check is one component of pre-employment screening. Screening is the broader set of verifications run before someone starts, which can include identity, criminal history, employment, education, driving records, and testing. Background check usually refers specifically to the criminal and records portion.

Do I need the candidate's permission to run a pre-employment screening?
Yes, when a third-party consumer reporting agency runs it. The FCRA requires a clear written disclosure in a standalone document and the candidate's written authorization before you order any report. Skipping or bundling that disclosure is a common source of litigation.

When in the hiring process should screening happen?
Most employers screen after extending a conditional offer, which keeps the cost down and avoids screening candidates who won't reach that stage. Some state and local laws also restrict when you can ask about criminal history, so confirm the rules for each jurisdiction you hire in.

What happens if something comes back on a report?
You send a pre-adverse action notice with a copy of the report and a summary of the candidate's FCRA rights, then give them reasonable time to respond or dispute it. If you still decide not to hire, you send a final adverse action notice with the reporting company's details and the candidate's dispute rights.

How long should a pre-employment screening take?
A standard package usually completes in two to five business days. Education verification, international records, and counties requiring manual court retrieval can push it to a week or more, so build that into the offer-to-start timeline rather than discovering it late.

Can a staffing partner handle screening for us?
Yes, and for contract placements the partner typically screens before submitting candidates. Ask specifically which checks are included, what documentation they can share, and who holds compliance responsibility, since that division should be written into the agreement rather than assumed.

Introduction 

Most teams do not have a hiring problem. They have a candidate sourcing problem that only looks like a hiring problem once the req has been open for six weeks.

The symptoms are recognizable. Applications come in, the pile is large, and almost none of it is submittable. 

Meanwhile SHRM's 2026 benchmarking data puts median time to fill at 39 calendar days for nonexecutive roles and 45 days for executive roles, and median requisitions per recruiter climbed to 25 in 2026 from 20 the year before. 

More reqs, same hours, and a pipeline built out of whoever happened to apply.

This guide covers the sourcing stage specifically: finding and engaging people before they become applicants. Screening, interviewing, and offer strategy sit downstream and are covered elsewhere.

TL;DR

• Candidate sourcing is the proactive search for talent that has not applied. It ends the moment someone enters your screening process.
• Job boards generate roughly 90% of applications but only about 50% of hires, which is why application volume is a misleading health signal.
• Outbound sourced candidates convert to hires at around five times the rate of inbound applicants, according to Gem's 2026 analysis of 165 million applications.
• Your existing ATS is the highest-yield channel most teams ignore. Rediscovered candidates accounted for 46% of sourced hires in 2026, up from 26% in 2021.
• Track source-to-submittal and response rate by channel. Volume metrics tell you almost nothing useful.

What candidate sourcing actually is, and where it ends 

Candidate sourcing is the work of identifying and contacting qualified people who have not applied to your role. It produces conversations, not hires.

That boundary matters more than it sounds. When sourcing and recruiting get treated as one blurred activity, the sourcing work quietly gets deprioritized every time an interview needs scheduling. Reqs then run on inbound applications by default.

Sourcing vs recruiting

One practical test: if you stopped posting jobs entirely tomorrow, could you still fill a req? If the answer is no, you do not have a sourcing function. You have a job board subscription.

Why the math favors outbound sourcing 

The case for sourcing is not philosophical. It comes down to pool size and conversion.

LinkedIn's research across 18,000 professionals in 26 countries found that about 70% of the global workforce qualifies as passive talent, and roughly 45% of those people are open to a recruiter's message if the approach is right. Only about 15% are fully disengaged from recruiter outreach.

So if your pipeline depends entirely on applicants, you are competing with everyone else for the same 30% slice.

The conversion data points in the same direction. 

Gem's 2026 analysis found that outbound sourced candidates convert to hires at five times the rate of inbound applicants, and that job boards produce roughly 90% of applications but only about 50% of hires.

That gap is the whole argument. Job boards are a volume channel masquerading as a quality channel, and volume is what burns recruiter hours.

Demand context helps here too. The U.S. Bureau of Labor Statistics reported 7.4 million job openings and 5.3 million hires in June 2026. There is no shortage of open seats. The constraint is reaching the right people before someone else does.

The candidate sourcing channels that carry real weight 

Channel choice should follow role type, not habit. Here is how the main options compare in practice.

1. Your own ATS is the most underused channel

Almost every team has thousands of previously screened candidates sitting in a database, and almost nobody searches it first.

Rediscovered talent, meaning candidates already in the ATS who get re-engaged for a new role, accounted for 46% of sourced hires in 2026, up from 26% in 2021.

These people already passed a screen once. They already know your company name. The outreach is warmer, the response rate is better, and the cost is effectively zero.

The barrier is usually data hygiene, not strategy. If your ATS records have no skill tags, no reason-for-rejection field, and no last-contacted date, rediscovery is guesswork. Fixing that is a two-week project that pays for years.

2. Referrals still outperform, and it is not close

SHRM research indicates referred candidates are hired roughly 55% faster than candidates from other channels, with better retention.

A referred passive candidate has already had the awkward questions answered by someone they trust. Is the manager decent? Is the technical work real? That conversation happened before you ever entered the picture.

Referral programs go quiet for boring reasons. The bonus is too small, the process is a form nobody can find, or employees never hear what happened to the person they referred. Fix those three things before buying another sourcing tool.

3. Where technical candidates actually live

For engineering roles, resumes are a weak signal and public work is a strong one. GitHub contribution history, Stack Overflow answers, conference talks, and open source maintainership show what someone can do rather than what they claim.

This is slow sourcing. It does not scale to twenty reqs. For a hard cloud or DevOps search where the shortlist is ten people nationally, it is the only method that works. 

Our technical recruitment guide covers how to evaluate what you find there.

How to write outreach people answer

Sourcing generates a list. Outreach turns the list into a pipeline, and this is where most sourcing effort dies.

Response rate benchmarks make the personalization argument for you. Personalized recruiter InMails see roughly 18% to 25% response rates, against 5% to 8% for template messages.

Length matters too. LinkedIn's own data shows messages under 400 characters get response rates about 22% above the global average, with the best performance from messages in the 50 to 70 word range.

So the highest-performing recruiter message is short, specific, and obviously written by a person who read the profile. Three things to cut immediately:

• The pasted job description. Nobody reads it in the first message.
• "I came across your profile and was impressed." Everyone writes this. It signals a template.
• Four paragraphs about your company's mission before you say what the role is.

What to include instead: one concrete detail from their actual background, what the role is in one line, why you thought of them specifically, and a low-commitment question.

Follow up two or three times, spaced several days apart. A single message is a coin flip on whether they saw it at all.

The candidate sourcing metrics worth tracking 

Most sourcing dashboards measure activity. Activity is not yield.

Two diagnostic patterns are worth memorizing. A healthy time to hire paired with a bloated time to fill usually means sourcing is the bottleneck. Both numbers high usually means the evaluation process is. 

Our breakdown of time to hire benchmarks and the fixes that move them goes deeper on separating those two.

One more number worth noting: only about 20% of organizations measure quality of hire at all. If nobody checks which sourcing channel produced people who were still performing at month six, channel budgets get set on gut feel indefinitely.

Building a sourcing function versus buying pipeline 

There is a real decision here, and the right answer changes by role type.

Building in-house makes sense when you hire the same profiles repeatedly, when the employer brand is a genuine asset, and when your reqs are permanent roles you want to own long term. The investment compounds. A well-maintained talent pool gets cheaper every quarter.

Buying pipeline makes sense when the need is urgent, when the skill is outside your team's search competence, or when the work is project-bound. 

SHRM's 2026 data shows median cost per hire at $1,300 for nonexecutive roles and $15,000 for executive roles, with executive cost per hire up 42% in a single year. For the hard searches, the build-versus-buy math is closer than people assume.

Most teams end up running both, and that is usually correct. Own sourcing for your core recurring roles. Use a partner bench for urgent contract starts and specialist skills you touch twice a year. 

If you are evaluating that second path, our guide to IT staffing models lays out where each one fits.

A 30-day plan to fix weak candidate sourcing 

If sourcing is currently the weak link, this sequence works and does not require a new budget.

Compare response rate and source-to-submittal by channel. Move hours away from the worst performer.

Do not try to add channels in month one. Most teams already run more channels than they measure, and adding a sixth underperforming source makes the picture harder to read, not better.

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

• Candidate sourcing is proactive outreach to people who have not applied, and it ends where screening begins. Treating it as a distinct function is what keeps it from getting deprioritized.
• Application volume is a vanity metric. Job boards produce most applications and only about half of hires.
• Start channel improvement inside your own ATS, since rediscovered candidates now drive nearly half of sourced hires.
• Short, specific outreach under 70 words outperforms templates by a wide margin. Send follow-ups.
• Measure response rate and source-to-submittal by channel, not messages sent. Reallocate hours based on what those two numbers say.

FAQs

What is the difference between candidate sourcing and recruiting?
Sourcing is the proactive search for people who have not applied, and it produces engaged candidates. Recruiting takes over once someone is interested and covers screening, interviewing, and closing. Sourcing is measured by response and submittal rates, recruiting by offer acceptance and hires.

How do you source candidates with no budget?
Start with your ATS and your referral program, since both are already paid for and both produce strong conversion. Add free technical communities like GitHub or Stack Overflow for engineering roles. Budget buys reach, but it does not fix weak targeting or generic outreach.

What is a good response rate for candidate outreach?
Personalized recruiter messages generally land in the 18% to 25% range, while template messages run closer to 5% to 8%. Rates vary widely by industry, and saturated tech markets sit lower. Track your own baseline by channel rather than chasing a national average.

How many candidates should be in a pipeline per open role?
It depends on your submittal-to-hire ratio, so work backward from your own data. If roughly one in four submittals converts, you need enough engaged candidates to produce four solid submittals. Pipeline coverage is more useful as a trend line than as a fixed target.

Are passive candidates really better than active applicants?
They are not inherently better, but they are less contested and convert at a higher rate once engaged. Active candidates can be excellent and move faster. The practical argument for passive sourcing is pool size, since around 70% of the workforce is not actively looking at any given time.

Should we build a sourcing team or use a staffing partner?
Build in-house for roles you hire repeatedly, where the investment in a talent pool compounds over time. Use a partner for urgent contract starts, niche skills, or capacity spikes your team cannot absorb. Most organizations run both and assign each channel to the role types it fits.

Introduction 

Ask ten hiring managers to describe their recruitment and selection process and most will give you a list of stages. Post the role, screen resumes, phone screen, interviews, offer.

That's a workflow. It isn't a process, and the distinction shows up the moment someone asks why a candidate was rejected and nobody can answer with anything more specific than "not a fit."

Recruitment and selection are two separate disciplines that got merged into one phrase. 

Recruitment is about attracting a pool. Selection is about choosing from it, defensibly, using methods that actually predict whether someone will do the job well. Most teams are competent at the first and improvising at the second.

This covers the second half, since that's where the money and the legal exposure both sit.

This is general information about hiring practice, not legal advice. Employment law varies by jurisdiction, so check specific obligations with counsel.

TL;DR

• Recruitment attracts candidates; selection chooses among them. Running both as one undifferentiated funnel is why hiring decisions become hard to explain.
• Under federal guidance, a selection procedure is almost anything you use to make a hiring decision, including a casual interview or an experience requirement.
• If a selection method disproportionately excludes a protected group, the employer has to show it's job-related and consistent with business necessity.
• The four-fifths rule is the standard federal starting point for spotting adverse impact, and it's simple enough to check yourself.
• Structured methods beat unstructured ones on both prediction and defensibility, which is unusual. Most tradeoffs don't point the same direction.

Recruitment and selection are two different jobs 

They have different goals, different failure modes, and different people are usually good at them.

The practical consequence: expanding your pool won't fix a broken selection process, and it often makes it worse. More candidates through a process with no consistent criteria just means more inconsistent decisions.

If your problem is genuinely on the recruitment side, Consultadd's hiring and recruiting strategies playbook covers sourcing and pipeline building in depth. 

This piece assumes you have candidates and the question is how you pick.

Why the split matters

Because the two halves are held to different standards.

Nobody audits your sourcing channels. Plenty of people can audit your selection decisions, including candidates, regulators, and your own leadership when a senior hire fails at month four.

Selection is also where most of the value is created. A recruiter who doubles your applicant pool has helped. An assessment process that reliably distinguishes the top quartile has changed your team's output for years.

And selection is the half that's usually undocumented. Teams keep detailed records of where candidates came from and almost none of why they were rejected.

What actually counts as a selection procedure 

This is the part that surprises people, and it's worth reading carefully.

The Uniform Guidelines on Employee Selection Procedures, adopted in 1978 by the EEOC, the Department of Labor, the Department of Justice, and the Civil Service Commission, define a selection procedure broadly. It isn't just formal tests. 

The guidelines cover job requirements like physical, educational, and experience criteria, plus evaluation through application forms, interviews, performance tests, written tests, and performance in training or probationary periods.

Read that again. An informal interview is a selection procedure. So is "must have a bachelor's degree." So is "five years minimum experience."

The EEOC's guidance on employment tests and selection procedures makes the consequence clear: employers can face liability not only for intentional discrimination, but for using apparently neutral procedures that disproportionately exclude a protected group, unless they can justify them.

So the requirement to be job-related doesn't apply only to a personality assessment you bought. It applies to the degree requirement someone copied from an old job description in 2019 and nobody has questioned since.

Choosing methods that predict performance

Different selection methods answer different questions, and using the wrong one is how teams end up with candidates who interview beautifully and can't do the work.

Two things hold consistently in the research literature. 

• Structured approaches outperform unstructured ones at predicting job performance. 
• Methods that sample actual work outperform methods that ask people to describe their work.

The unusual part is that structure improves defensibility at the same time. Most hiring tradeoffs force a choice between rigour and speed. This one doesn't, which is why it's the single highest-return change most teams can make.

For how these methods sequence within a technical hiring cycle specifically, Consultadd's guide to how technical recruitment works stage by stage walks through the assessment stages in order.

Keeping the process defensible 

Defensibility isn't a separate compliance exercise bolted onto the end. It's mostly a byproduct of running a consistent process.

Three things do the work:

1. Start from job analysis. 

• Every criterion should trace to something the job actually requires. 
• If you can't explain why a requirement predicts performance in this role, it shouldn't be filtering anyone out. 
• This is also the cheapest fix available, since it costs a conversation with the hiring manager.

2. Check for adverse impact. 

• The Uniform Guidelines describe the four-fifths rule: a selection rate for any race, sex, or ethnic group that falls below four-fifths, or 80%, of the rate for the highest-scoring group will generally be regarded by federal enforcement agencies as evidence of adverse impact. 
• Rates above that generally won't be.
• Running that check is arithmetic. Divide selected by applied for each group, find the highest rate, and compare the others against 80% of it. 
• The guidelines note that smaller differences can still constitute adverse impact where they're significant in statistical and practical terms, and that larger gaps may not where the numbers are small and not statistically significant. 
• So treat it as a flag to investigate, not a verdict.
• The guidelines also suggest adverse impact determinations be made at least annually for each group making up at least 2% of the relevant labor force or applicable workforce.

3. Know what happens if you find impact. 

• If a procedure disproportionately excludes a protected group, the employer needs to show it's job-related and consistent with business necessity. 
• Even then, a challenger can argue a less discriminatory alternative exists that would predict performance equally well.

Worth noting: the guidelines don't require validity studies where no adverse impact results. The obligation is triggered by impact, not by using a test.

The documentation most teams skip

Where the total selection process shows adverse impact, the guidelines indicate employers should keep records showing which components are producing it. 

That's impossible to do retroactively if you never recorded stage-level outcomes.

None of this is heavy. It's a scorecard and a spreadsheet. The reason teams skip it isn't cost, it's that documentation feels like overhead until the first time someone asks a question you can't answer.

Where processes break 

A few patterns recur, drawn from watching hiring cycles go sideways: 

1. Criteria written after meeting candidates. 

• The requirements quietly reshape themselves around whoever the hiring manager liked. 
• This is the most common failure and the hardest to see from inside.

2. Interviewers scoring different things. 

• Five interviewers, no rubric, five private definitions of a good answer. 
• The debrief becomes a negotiation between confident opinions rather than a comparison of evidence.

3. Requirements nobody can justify. 

• Degree minimums, arbitrary years of experience, and tool-specific demands that were copied forward. 
• Each one narrows the pool and each one has to be defensible.

4. Speed collapsing rigour. 

• Under pressure, teams skip the structured parts first because they feel slow. 

Consultadd's breakdown of where IT recruitment strategies break down covers the speed pressure side of this in more detail.

5. Treating selection as HR's problem. 

• The hiring manager owns the decision and usually owns the inconsistency too. 
• Process fixes that don't involve them don't hold.

For teams hiring technical contract talent where the selection burden partly shifts to a staffing partner, the eight stages of the IT staffing process shows where vetting responsibility sits at each handoff.

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

• Treat recruitment and selection as two disciplines. Fixing your pipeline won't fix inconsistent decisions.
• Federal guidance treats interviews, experience requirements, and education minimums as selection procedures, so each one needs a job-related justification.
• Structure improves both prediction and defensibility at once, which makes rubrics and consistent questions the highest-return change available.
• The four-fifths rule is a simple arithmetic check you can run on your own data as an early warning, not a final verdict.
• Record criteria, scores, and rejection reasons as you go. Stage-level data can't be reconstructed later.

FAQs

What is the difference between recruitment and selection?
Recruitment is the work of attracting and building a pool of qualified applicants. Selection is the work of assessing that pool and choosing who to hire. Recruitment is measured by pipeline quality and volume; selection is measured by whether the people you choose succeed in the role.

What are the main stages of the recruitment and selection process?
Recruitment typically covers workforce planning, job analysis, job description, sourcing, and application. Selection covers screening, assessment, interviewing, reference and background checks, and the offer decision. The stages matter less than whether each one applies consistent, job-related criteria.

What is a selection procedure under EEOC guidance?
The Uniform Guidelines define it broadly as measures used as a basis for an employment decision. That includes formal tests but also interviews, application form reviews, work samples, and physical, educational, or experience requirements. Informal interviews are covered too.

What is the four-fifths rule?
It's the federal starting point for identifying adverse impact. If a group's selection rate is less than 80% of the rate for the highest group, federal enforcement agencies will generally regard that as evidence of adverse impact. The guidelines note smaller gaps can still matter and larger gaps may not where numbers are small.

Are structured interviews better than unstructured ones?
Yes, on both counts that matter. Structured interviews, where every candidate gets the same questions scored against a defined rubric, predict job performance more reliably and produce decisions that are far easier to explain and defend. Unstructured conversations are better used to sell the role than to score candidates.

How do we make our recruitment and selection process more defensible?
Start from a job analysis so every criterion traces to a real requirement, use the same questions and scoring across candidates, record the reason for each rejection against a specific criterion, and run periodic adverse impact checks on your stage-level data. Most of the defensibility comes free with consistency.

Introduction 

Most advice about recruitment in IT stops at the strategy level. Hire for skills, build a pipeline, move faster. All true, and none of it tells you what to do on Monday morning when a req lands in your queue.

This is the operational version. Six stages, what each one should produce, how long it should take, and what to measure when it doesn't work.

One number frames the whole thing. In July 2026, US employers held 7.3 million open jobs but made only 5.1 million hires, and the hires rate sat at 3.2 percent, according to BLS Job Openings and Labor Turnover data. 

Openings are plentiful. Actual hiring is slow. That gap is a process problem more than a demand problem, and process problems are fixable.

If you want the strategic context first, our breakdown of what's broken and what's working in IT recruitment covers the market conditions behind these numbers.

TL;DR

• A weak intake meeting is the single most expensive failure in the process, because every later stage inherits its ambiguity.
• Interview counts per hire have climbed sharply, which means added rounds now cost you candidates rather than better decisions.
• AI screening tools became a compliance question in 2026, with Illinois HB 3773 effective January 1 and NYC enforcement tightening.
• Measure elapsed days per stage alongside conversion per stage, or you'll optimize the wrong thing.
• Offers that sit open for days lose candidates. Speed at the close matters more than most teams account for.

The six stages and what each should produce 

Durations are targets, not promises. Senior and specialized roles run longer. But if a stage consistently doubles its target, that's where your process is leaking.

Intake: the stage everyone rushes 

Skipping a proper intake meeting is the most common and most expensive mistake in technical hiring. Everything downstream inherits whatever ambiguity survives this conversation.

A useful intake produces three artifacts:

1. A separated requirements list. 

Must-haves and nice-to-haves in two columns, not one paragraph. Padding a job description with every desirable attribute discourages qualified people from applying and gives the recruiter no way to prioritize. If the list of must-haves runs past five items, the role is probably two roles.

2. An agreed compensation range. 

Not "competitive." An actual number, confirmed with whoever approves it. Discovering a budget ceiling at offer stage wastes six weeks of everyone's time.

3. A scorecard. 

What does a strong answer look like for each must-have, and who on the panel assesses which one. Without this, interviewers default to gut feel, and gut feel is where both bias and inconsistency enter.

One question worth asking the hiring manager directly: name someone currently on the team who'd be a strong fit for this role. Then look at that person's actual background. It's usually different from the job description, and the difference tells you what the role really needs.

Sourcing and outreach 

Two channels do most of the work in technical hiring: direct outreach and referrals. Job boards contribute volume, and volume has become a liability rather than an asset.

On outreach response rates, LinkedIn Talent Solutions data puts personalized messages in the 18 to 25 percent range against 5 to 8 percent for templates. That gap is the entire argument for spending three minutes per message instead of thirty seconds.

What personalization actually means: reference something specific and recent from their work. A repository, a talk, a system they built. Not their job title and years of experience, which is what templates do and what candidates recognize instantly.

A practical benchmark for the first week: a first shortlist submitted within seven days of intake. If that slips, the usual cause is an unclear must-have list, which sends you back to stage one.

For roles that are genuinely hard to fill in the open market, a specialized partner with an existing bench often beats building a pipeline from zero. 

Our guide to evaluating IT staffing firms covers what to ask before signing one, and IT contract staffing as a strategy explains when contract structures make a hard req easier to fill.

Screening, and the 2026 AI hiring rules 

This stage changed legally in 2026, and a lot of teams haven't caught up.

If your ATS ranks or scores candidates, if a tool filters resumes automatically, or if a video interview platform analyzes responses, you may be running what the law calls an automated employment decision tool. That triggers obligations in a growing number of jurisdictions.

Two things make this more urgent than it looks: 

First, a human making the final call doesn't necessarily take you outside scope. A resume-ranking score a recruiter relies on is generally treated as covered. 

Second, enforcement is tightening. 

A December 2025 New York State Comptroller audit of DCWP's enforcement of Local Law 144 found weaknesses in complaint handling and recommended a shift toward proactive investigation, which the agency accepted.

The practical first step is boring and useful: inventory every tool in your hiring stack and write down what each one actually scores. Most teams can't answer that question about their own ATS. 

NYC's DCWP page on automated employment decision tools sets out the audit and notice mechanics if you hire there.

This is general information, not legal advice. If AI sits anywhere in your screening path, run the inventory past counsel.

The interview loop 

Here's the uncomfortable finding from 2026 benchmark data. Ashby's analysis found technical interviews per hire rose 52 percent since 2021, reaching roughly 17.6, while business interviews rose 36 percent to 11.7. Gem's data puts the overall figure near 13 interviews per hire, up 42 percent in three years.

Teams added rounds to handle rising applicant volume. The result is more recruiter and interviewer hours per hire, not better hires.

Meanwhile Talent Board found 57 percent of candidates have abandoned a process for being too slow. So the added rounds are costing you the people they were meant to evaluate.

Three fixes that work:

1. Cap the loop before you start. 

Decide the number of rounds at intake and treat adding one as a decision requiring a reason, not a default.

2. Make the technical assessment resemble the job. 

A take-home that mirrors a real task, time-boxed to two hours, tells you more than an algorithmic puzzle and annoys candidates less. If you use a live exercise, make it collaborative rather than adversarial.

3. Schedule the loop as a block. 

Pre-booked panel slots on one or two days beat scheduling each round after the previous one clears. Scheduling latency, not evaluation time, is where most of the elapsed days go.

Watch the reschedule rate too. Candidate.fyi's 2025 data found 14 percent of interviews were rescheduled and 18 percent of scheduling signals needed human intervention. Neither shows up in standard funnel reporting, and both consume days.

Offer, close, and what to measure 

Offer acceptance across roles and industries sat around 82 percent in Gem's 2026 benchmarks, the highest since 2021. Technical roles run lower.

The strongest predictor of a close is how long the offer sits open. Two days versus six is a meaningful gap, and it's an early warning signal most teams don't track. If an offer is still unsigned after 72 hours, that's information, not patience.

Call the candidate before the written offer arrives. Verbal first, with the number said out loud, gives you the chance to hear hesitation and address it before it hardens into a counteroffer conversation elsewhere.

The metrics worth tracking

Treat these as reference points, not targets. Published benchmarks define stages differently, so your own trend line over two quarters is more useful than any single industry figure.

The one instruction that matters most: measure elapsed days per stage alongside conversion per stage. 

A candidate who would have passed your loop but dropped out in week three shows up in your dashboard as a screening loss. The actual cause was delay. Fix the wrong thing and the number won't move.

For where demand is concentrated right now and which skills are hardest to source, our review of IT staffing trends and what's changing in tech hiring has the current picture.

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

• Recruitment in IT breaks down into six stages, and a weak intake meeting contaminates all five that follow.
• Personalized outreach converts at roughly three to four times the rate of templated messages.
• AI screening tools carry real compliance obligations as of 2026, and a human making the final call does not automatically exempt you.
• Interview counts per hire have risen sharply without improving outcomes, so cap the loop deliberately.
• Track days per stage alongside conversion per stage, since latency often masquerades as a screening problem.

FAQs

What is the IT recruitment process?

It runs from intake through onboarding: defining the role with the hiring manager, sourcing and outreach, screening, a technical interview loop, offer and close, then handoff to onboarding. Each stage should produce a specific output, and the intake stage determines the quality of everything after it.

How long should it take to fill a technical role?

SHRM's benchmarking data puts the US median time to fill at roughly 44 days across roles, with engineering positions running closer to 62 days. Specialized and senior technical roles take longer. What matters more than the absolute number is where in your own process the days accumulate.

How many interview rounds should a technical role have?

Fewer than most teams currently run. Benchmark data shows technical interviews per hire climbed more than 50 percent since 2021 without a corresponding improvement in hiring outcomes, while more than half of candidates have abandoned a process for being too slow. Decide the number at intake and treat adding a round as an exception.

Do AI screening tools create legal risk in 2026?

Yes, in a growing number of jurisdictions. NYC Local Law 144 requires an annual independent bias audit, a public summary, and advance candidate notice. Illinois HB 3773 took effect January 1, 2026 and makes discriminatory effect from AI in employment decisions a Human Rights Act violation. Colorado's requirements for employment AI began June 30, 2026.

What recruiting metrics matter most for IT hiring?

Start with three: outreach response rate, time to fill, and offer acceptance rate. Those cover sourcing quality, process speed, and close quality. Add application-to-interview and interview-to-offer conversion once the first three are stable, and always track elapsed days per stage alongside them.

Should we build an internal recruiting function or use a staffing partner?

Internal teams work well for steady, repeatable hiring where institutional knowledge compounds. Staffing partners add the most value on hard-to-fill niche roles and when speed matters more than cost per hire. Most organizations doing this well run both, with a clear rule about which reqs go where.