Why Tech Roles Stay Open: Where the Hiring Days Really Go
Technical roles take a median 75 days to fill. We break down each hiring stage to show where time goes and why most delays come from inside the process.
Key Takeaways
Technical roles take a median of about 75 days to fill, versus about 60 for business roles, according to Ashby's 2026 Talent Trends data covering 93,000 jobs.
The interview loop itself, first interview to last, runs a median 17.9 days for technical roles. That's less than a quarter of the total.
Interviews per hire climbed from 14 to 20 between 2021 and 2024 in Gem's benchmark data, while average time to hire rose 24 percent.
About one in four offers to sourced technical candidates gets declined, which sends the search back toward the start.
The biggest gaps between fast and slow hiring teams show up in waiting states: feedback, scheduling, and offer approvals.
What does a stalled tech role look like?
A stalled role usually looks busy. There are candidates in the pipeline, interviews on calendars, and a weekly sync where someone says the market is tough. What's missing is movement. The same three finalists sit in "debrief pending" for a week, and the req quietly crosses the 90 day mark.
If you're living it, the symptoms are familiar. The hiring manager says there aren't enough good candidates. The recruiter says candidates keep dropping out. Both are right, and neither is describing the cause.
Here are the signs that show up most often:
Scorecards arrive two or three days after the interview, and some never arrive at all
The panel disagrees at debrief about what the role actually needs
A strong finalist accepts another offer while yours is waiting on a comp approval
The job description has been rewritten at least once since the req opened
Nobody can say, with a date, when the last candidate moved stages
That last one matters most. When nobody owns the clock, the clock runs.
Where do the days go in a 75 day technical hire?
Most of a technical hire's calendar time sits outside the interviews. The interview loop takes a median 17.9 days and outreach to first interview takes about six, which accounts for roughly 24 of 75 days. The remaining 50 or so are spent before the first conversation, after the last one, or restarting when a finalist walks.
Some of that is real sourcing effort, especially for senior roles. Ashby's data shows senior roles take 37 percent longer to fill than junior ones, and nobody finds a strong staff engineer in a week. But a lot of it is waiting. Waiting on scorecards, and waiting on a VP to sign off on an offer that's $8,000 over band.
Stage | What happens | What the data shows | Who owns the wait |
|---|---|---|---|
Intake and approval | Req written, comp band set, interview plan agreed | Rarely tracked. Counted in time to fill but not in time to hire | Hiring manager, finance |
Outreach to first interview | Sourcing, replies, recruiter screens | 5.8 median days for software engineering roles (Pin) | Recruiter |
Interview loop | Technical screens, panels, onsite | 17.9 median days for technical roles (Ashby) | Interviewers, coordinator |
Feedback and debrief | Scorecards submitted, decision made | Roughly 30 percent of scorecards aren't in within 24 hours (Ashby) | Interview panel |
Offer approval and close | Comp sign-off, negotiation, acceptance | Slowest teams add 4.7 days on approvals alone versus the fastest (Ashby) | Finance, leadership |
Restart | Finalist declines or withdraws | 76 percent offer acceptance for sourced tech candidates (Ashby) | Everyone |
Look at the right column. Only one row belongs mostly to the recruiter. The rest belong to people whose main job isn't hiring.
Why does a role stall before sourcing even starts?
Roles stall at intake when the hiring manager, the panel, and finance haven't agreed on what the job is. The req opens anyway, sourcing starts against a vague target, and the first two weeks of candidates get rejected for reasons nobody wrote down. That's calendar time spent discovering the requirements.
The pattern is common enough to have a name inside most recruiting teams: the moving target. A role opens as "senior backend engineer," then after four screens becomes "senior backend engineer who has also run Kafka in production," then after the first onsite picks up a management expectation. Each revision quietly resets the search.
Comp is the other intake problem. If the band was set from last year's data or from a local market that no longer reflects what the role pays, you'll find out at the offer stage. Late.
Why does feedback lag cost more time than scheduling?
Scheduling delays are measured in hours, while feedback delays are measured in days. Ashby's data puts manual scheduling at a median of 5 hours to confirm an interview. Feedback is slower: only 66 to 70 percent of scorecards get submitted within 24 hours, so a single missing scorecard can hold a whole debrief for most of a week.
Here's how it compounds. A candidate finishes an onsite on Tuesday. Two of four interviewers submit that night. One submits Thursday. The fourth is traveling and submits the following Monday. Debrief happens Wednesday. That's eight days of silence for a candidate who is almost certainly talking to someone else.
Loops have also gotten longer. Gem's recruiting benchmarks show interviews per hire rising from 14 in 2021 to 20 in 2024. Every added round is another scorecard to chase and another chance for one person's calendar to become the bottleneck.
Why do finalists walk away late in the process?
Finalists usually leave because the process gave them a reason to doubt the company, or because a faster offer arrived first. In the 2024 Monster Work Watch report, 47 percent of job seekers who withdrew cited poor communication, and 36 percent said they'd been asked to jump through too many hoops.
The expensive part is when it happens. Ashby's funnel data shows about 95 percent of candidates who clear the onsite move forward, and about 81 percent move through the offer stage. So by the time someone reaches an offer, you've already spent the full loop on them. Losing that person costs you the most of anyone in the pipeline.
There's also a perception gap worth knowing about. In a Sterling survey of more than 3,700 job seekers and 1,200 HR professionals, 78 percent of candidates said they'd drop out or consider dropping out of a lengthy or complex process. Only 9 percent of HR respondents thought candidates would find their own process complicated.
Most teams think their process is fine. Most candidates disagree.
What do teams that fill tech roles faster do differently?
Faster teams manage hiring time the way they'd manage a sprint, with owners and deadlines for each handoff. They lock the role definition before sourcing and pre-approve the offer range so a finalist never waits on finance. None of it requires new tools. It requires someone to own each step between one stage and the next.
In practice, the teams that move well tend to share a few habits:
A written intake. Must-haves, nice-to-haves, the comp range, and the interview plan, agreed and signed off before the first outreach goes out.
A 24 hour feedback rule. Scorecards due the same day or the next morning, with the recruiter empowered to chase.
A shorter loop. Every interview maps to a specific competency on the scorecard. If two rounds test the same thing, one goes.
Pre-approved offers. The band and the flex are cleared before the onsite, so an offer can go out within a day of the debrief.
A named clock owner. One person who can tell you, for every active candidate, how many days since they last heard from you.
Referrals help too. Ashby's data shows 52 percent of referred candidates pass initial screens, compared with 35 percent overall, which means fewer screens spent per hire.
How can you tell a tech role is stalling early?
The earliest warning signs show up in the first three weeks, well before a role hits the 90 day mark. Watch for requirement changes after sourcing starts, scorecards arriving more than a day late, and candidates going more than five business days without an update. Any one of these predicts a long fill.
Here are the leading indicators worth tracking on every open technical req:
Days from req approval to first outreach. More than a week usually means intake wasn't finished.
Rejection reasons in the first ten screens. If they're inconsistent, the role isn't defined yet.
Median hours from interview to scorecard. Over 24 is a problem. Over 48 is a pattern.
Days since last candidate touch. Tracked per candidate, not per req.
Offer approval time. If it's measured in days, a competitor's offer will beat yours.
Late stage withdrawals. Two finalists lost in a row is a process signal worth investigating.
None of these require an applicant tracking system upgrade. Most teams can pull them from calendars and email in an afternoon. The hard part is looking.
If you'd rather have someone else do the looking, International Digital Partners runs a free Hiring Process Assessment for U.S. technology teams with open roles. It starts with a 30 minute call, no questionnaire, and Eric Swiezynski, IDP's President, runs it personally. Within one week you get a written report: a one-page map of your process from intake through offer, the bottlenecks in plain language, and a prioritized list of what to fix first. The report is yours to use whether or not IDP is part of the answer.
Sources
More Articles
AI Gave the World More Code. Now the World Needs More Reviewers.
High-AI teams merge 98% more pull requests, yet review time is up 91% and 31% of an engineer's day is invisible work. Here is where delivery stalls.
Nearshore Teams Are Outpacing US Shops on AI Coding Tools
Nearshore teams already work async and document everything. That habit, not geography, is why they adopt AI coding tools faster than most U.S. shops.
Nearshore vs. Offshore Cost Comparison: The Real Numbers
Offshore developer rates undercut nearshore by 40 to 70 percent on paper. Attrition, lost overlap, and rework close most of that gap in practice.