If you've hired a senior engineer at a growing technology company in the last three years, you already know the number. From role opening to signed offer, the typical cycle is 60 to 100 days. The 2024 LinkedIn Talent Solutions benchmark put it at 68 days globally for software engineers. Our own tracking across Canadian and US scale-ups puts senior roles consistently in the 80–110 day range. Staff-level roles routinely cross 120.
This is not a small number. For a Series B startup hiring a Staff ML Engineer on a $200K base, the fully loaded cost of that vacancy — lost shipping velocity, delayed roadmap commitments, burnt hiring-manager cycles — is roughly $4,000 per day. Three months unfilled: half a million dollars in real but invisible cost.
So where does the time actually go?
The 90 days, broken down
In most hiring funnels we've mapped, the calendar looks something like this:
- Days 1–10: Role scoping and JD. Usually longer than it should be, because the hiring manager and the recruiter aren't yet on the same page about what "senior" means in this role.
- Days 10–30: Sourcing and initial outreach. Recruiter picks up the role, starts an outreach sequence, waits for responses.
- Days 30–50: First interviews. A handful of responders go through an initial screen. Most are rejected. A few go to the hiring manager.
- Days 50–75: On-site interviews. Calendar coordination is painful. The hiring manager is senior and over-scheduled. Candidates are in other processes.
- Days 75–95: Offer and negotiation. Candidate needs to see the full package. References check out. An offer is made. Counter-offers happen.
- Days 95+: Notice period. Usually 4 weeks. Sometimes 8.
The problem is that most of the time savings opportunities are in the first 30 days — where almost nothing is measured.
The four compressors
Across the engagements we run, four specific interventions consistently compress senior tech hires from 90 days to 30.
1. Kill the JD, write the brief
Job descriptions are a legacy artifact. They're written to satisfy HR compliance and SEO indexing, not to help a recruiter find the right candidate. A "brief" is different: it documents the role and the context. What is this team shipping in the next six months? Who is this person replacing, or what gap are they filling? What's the first 90-day project? What's non-negotiable, and what's genuinely flexible?
A good brief cuts sourcing time by roughly half, because the recruiter stops chasing keyword matches and starts finding people who could actually do the work. Writing a proper brief takes 90 minutes. Most teams skip this step and pay for it in week 8.
2. Source in parallel, not sequence
Most recruiters run sourcing sequentially: pick 10 names, reach out, wait, assess responses, pick 10 more. This makes sense if you're one person running a single search. It makes no sense if the organization has leverage.
We source in parallel batches of 40–60, with structured outreach that tracks response rates per segment. The first week should produce 200+ touchpoints, not 30. Yes, most go unanswered. The point is that by week 2 you have a response pool large enough to move to assessment — not a lonely pipeline of 3 people "still waiting to hear back."
Parallel sourcing requires platform support. Without it, the recruiter is drowning in a spreadsheet. This is where the AI-native platforms win: they compress the mechanical load of parallel outreach so the human recruiter can focus on the qualified responses.
3. Assess before introducing
The "4 hiring manager rejections before the first good candidate" problem is a calibration failure. It happens when the recruiter introduces candidates who haven't been properly screened for the technical depth the role actually needs — because the recruiter can't assess it themselves.
A technically literate recruiter (ex-engineer, technical PM, or someone with deep domain fluency) can run a structured 30-minute screen that filters out 80% of "looks-good-on-paper" candidates before they eat a hiring manager's time. Add a standardized take-home or live coding assessment for the remaining 20% and the hiring manager's conversion from "first round" to "move to on-site" jumps from maybe 15% to 60%.
This is the single highest-leverage change most teams never make. Not because it's hard — because the recruiting team doesn't have the technical fluency to do it.
4. Compress the calendar, not the rigor
By week 6 in most cycles, there's a good candidate in the funnel but the calendar is killing the process. One on-site that has to be spread across three days because people are traveling. A take-home that sits for five days before the reviewer gets to it. Offer discussions that bounce through legal and finance before reaching the candidate.
The compression here isn't about cutting steps — it's about collapsing them in time. Run the on-site as a single-day event. Have the take-home reviewer calendar blocked for the 24 hours after submission. Pre-approve offer parameters with legal before the offer stage, not during it. None of this reduces the quality of the process. It removes the dead calendar time that accumulates invisibly.
The math
If you do all four, here's what the 90-day cycle compresses to:
- Days 1–2: Brief written and agreed.
- Days 2–12: Parallel sourcing, 200+ outreach, 30+ engaged responses.
- Days 8–18: Technical screens and structured assessments.
- Days 15–22: On-site interviews compressed into single-day events.
- Days 22–28: References and offer.
- Days 28+: Notice period (varies).
From 90 days to 28. A 70% compression. The gap between those two numbers is where reputation, velocity, and hundreds of thousands of dollars live.
The uncomfortable part
None of the four compressors are secret. Every senior talent leader has heard variations of all of them. The reason they're rarely all implemented at once is that they require the recruiter to be a peer to the hiring manager, not a service provider — and that's a hard role to hire for.
Which is the longest-running argument for why most in-house teams and most general recruiting agencies don't move the needle on senior tech hires. They can't run the four compressors because they don't have the right recruiter in the chair. Getting there isn't a process problem. It's a people problem. Solving it is how you get from 90 days to 21.
— The Uplyft Talent team