The Sourcing Budget Answer That Isn't

A 350-person SaaS company adds two job board subscriptions in Q1 after engineering reqs keep aging past sixty days. Applications for technical roles triple over the prior quarter. Three months later, the Director of Engineering is still asking when the slate will be ready, and the VP TA is explaining why a pipeline with three hundred applications hasn't produced five qualified candidates for a hiring manager review.

This is not a sourcing problem. It's a screening bottleneck, and more applications make it worse, not better.

What the Application Numbers Are Actually Telling You

The volume is not the issue. Greenhouse's 2026 Hiring Benchmarks analyzed more than 640 million applications across 6,000 companies and found that applications per open role grew 111 percent between 2022 and 2025, from 116 to 244 per job. Time-to-fill over the same period grew 37 percent, from 43 days to nearly 60. More candidates are entering the pipeline. Fewer are getting through it faster.

For technology and engineering roles specifically, the disconnect is sharper. iCIMS data from early 2025 shows 68 applicants per tech opening, versus 34 for the overall labor market. Applications for tech positions grew 28 percent year over year. Actual hires in the same period dropped 3 percent. Every new sourcing channel added more applicants to a pipeline that was already failing to convert.

The instinct when reqs age is to blame sourcing. Not enough reach, wrong job boards, passive candidate pool isn't activated. That instinct is understandable and usually wrong. The candidates are there. The problem is what happens after they apply.

Tech Candidates Don't Wait

The technology and SaaS sector has the highest candidate withdrawal rate of any industry. Starred's 2026 Hiring Benchmarks Report, drawing on 2.5 million hiring experiences, puts the tech withdrawal rate at 13.5 percent, the highest across all sectors studied. When withdrawn candidates were asked why they left the process, the leading reasons were communication gaps and slow timelines.

Not compensation. Not culture. Not the role itself. Speed and communication.

A software engineer who applies to a mid-market role on a Tuesday and hears nothing structured until a recruiter phone screen ten days later has already been through two or three conversations elsewhere. The pipeline didn't lose that candidate to a competitor's sourcing team. It lost them to its own latency.

Where the Pipeline Actually Breaks

For most mid-market tech companies, the recruiting workflow follows a predictable shape: a candidate applies, their resume enters an ATS queue, a recruiter reviews that queue when capacity allows, and a phone screen gets scheduled somewhere in week two or three. The first structured touchpoint happens two to three weeks after the application.

That interval is where tech candidates drop. Not because they weren't interested. Because they got a faster signal from somewhere else, and the process had created space for alternatives to become more attractive.

Widening the sourcing funnel doesn't solve this. It produces more applications into the same queue, reviewed by the same number of recruiters, on the same timeline. The pipeline leaks at the same stage. It just leaks more volume.

Why Recruiter Capacity Isn't the Root Cause Either

It would be convenient to frame this as a headcount problem. Add more recruiters, reduce the queue, speed up the screen. That logic works until the next wave of applications arrives, and the queue is back. The structural issue is that the first structured evaluation step requires recruiter time, and recruiter time is finite.

The gap between application and recruiter review is a capacity constraint, not a failure of effort. Recruiters working a fifteen-req load cannot respond to every application within 48 hours. That's arithmetic. The question worth asking is whether the first evaluation step has to require a recruiter at all.

Closing the Gap Between Application and Qualified Slate

A structured first-touch that operates asynchronously changes the conversion math. When a screening conversation happens within hours of the application, collects responses against the criteria the recruiter and hiring manager set, and flags the qualified candidates, the recruiter's time shifts from reviewing the full queue to reviewing the right candidates.

Sia, Eximius's screening agent, handles that structured first-touch across chat, voice, or video. The recruiter doesn't receive 244 resumes. They receive a ranked slate of candidates who have already answered the relevant questions, with their responses scored against the criteria the team defined. The time between application and first qualified human review drops from days to hours.

The hiring manager's slate arrives faster. The candidates who reach that slate have been through a structured evaluation, not just a resume filter. The candidates who would have withdrawn waiting for a callback have already had a structured response from the process.

The recruiter still owns the slate, the decision, and the close. Sia handles the structured first-touch that currently sits in the queue waiting for capacity.

The Right Diagnostic Before the Next Sourcing Investment

If your engineering reqs are aging and the reflex is to add sourcing budget, the first question to answer is: what is your average time from application to first structured evaluation? If it's more than three days, the sourcing supply is not the constraint. More applications will make the aging worse, not better, because they deepen the queue without closing the conversion gap.

The fix is shortening the interval between the moment a qualified candidate enters the pipeline and the moment they receive a structured signal that the process is moving. That's a screening infrastructure question, not a sourcing spend question, and it doesn't require adding headcount.

Want to see what structured screening looks like on your current req volume? Book a pilot and we'll run your next role through the Eximius workflow.