Better expectations create faster hiring.
Kristina Golovko
MindDesign
The SLA system
Responsibility
Who owns what
Timing
How fast each step moves
Communication
What gets reported and when
Accountability
What happens when SLAs slip
A hiring SLA is not bureaucracy. It's a shared operating agreement that replaces assumption with clarity.
Why this matters
The founder expects profiles by end of week. The recruiter is waiting on a finalised brief. The founder marks the search as 'stalled'. The recruiter marks it as 'blocked'. Both are right. Neither knows it.
These misalignments are not personality conflicts. They are the predictable outcome of working without a shared operating agreement. A hiring SLA defines what each party is responsible for, how fast they'll move, and what they'll communicate when they can't.
When SLAs exist, accountability becomes structural rather than personal. Slippage is visible. Root causes are findable. And both founder and recruiter spend less energy on misalignment and more on finding the right person.
Founder reality
Before a search begins, align on these with your recruiting partner:
How many qualified profiles should be delivered in the first 10 days?
What is the maximum time between a recruiter submission and founder feedback?
Who owns candidate communication at each stage?
What triggers a search pause versus a search reset?
How will both parties flag when something isn't working?
SLAs only work when both sides have agreed to them — not when one side imposes them on the other.
The SLA framework
Define these at the start of every search. Revisit at the midpoint.
Responsibility — who owns which part of the process
Sourcing, screening, scheduling, communication, feedback collection, offer negotiation. Every activity needs a named owner. Shared ownership is deferred ownership.
Timing — how long each stage is allowed to take
Define maximum stage durations: brief sign-off (48h), profile delivery (7 days), interview scheduling (48h after acceptance), feedback (24h post-interview), offer (24h post-decision). These aren't aspirational — they're operational commitments.
Communication — what gets reported, by whom, and how often
A weekly update cadence prevents assumptions from accumulating. Recruiter reports: profiles submitted, feedback received, pipeline status. Founder reports: brief changes, timeline shifts, decision updates.
Accountability — what happens when the SLA is missed
Missed SLAs are data, not failures. Agree in advance: if the founder misses a 48h feedback window three times, the search pauses. If the recruiter misses profile volume, a root cause review happens. Accountability removes blame.
Common mistakes
01
SLAs defined by the recruiter but not agreed by the founder
An SLA that only one party has signed up to is a wishlist. It must be a bilateral agreement to function as an operating system.
02
No SLA review when the search stalls
When hiring slows, the reflex is to add more sourcing. Often the stall is in founder feedback speed or brief quality — not candidate volume.
03
Treating the brief as static
Role requirements shift. When they do, the SLA must update. Recruiting against a stale brief wastes everyone's time and produces candidates who don't match current thinking.
04
Measuring recruiter performance against timelines without context
Timelines slip for many reasons — founder availability, market conditions, unclear briefs. Accountability must be contextual, not just metric-driven.
Example scenario
A Series B SaaS company engaging an external recruiter for a Head of Engineering search. Previous search took 18 weeks and ended without a hire.
What went wrong in the previous search
Recruiter submitted 12 profiles over 5 weeks. Founder reviewed 4. The rest were never responded to.
Two candidates progressed to final round and waited 3 weeks for a decision.
Brief changed twice without being communicated to the recruiter.
No regular update cadence — recruiter had no visibility on internal priorities.
The SLA agreed for the new search
Founder commits to feedback within 48 hours on every submission.
Recruiter commits to 8 qualified profiles in the first 10 days.
Brief changes communicated within 24 hours with written rationale.
Weekly 30-minute sync — recruiter reports pipeline, founder reports priorities.
The outcome
Head of Engineering hired in 9 weeks. No dropped candidates. Offer accepted on first attempt.
Hiring SLAs make expectations structural.
They replace assumptions with agreements — and transform the founder-recruiter relationship from reactive to operational.
Related thinking
Continue reading
Candidate Funnels That Don't Break →