Hiring process
How to work with a recruiter as a startup
By Nick Kimball · Published 2 September 2025 · Last updated 30 August 2026 · 4 min read
Most stalled searches stall on the client side. Not on sourcing. The recruiting team is usually waiting on feedback, a scheduling slot, or a decision about a band nobody signed off. Getting the value out of an engagement is mostly about removing those blocks, and it takes about two to four founder hours a week.
Do a real intake per role
A forwarded job description is not a brief. An intake session takes an hour and should produce:
- The two or three outcomes the hire owns in their first year, stated as results rather than tasks.
- What good looks like and, more usefully, what would make you reject someone who looks good on paper.
- The salary band, approved by whoever approves it.
- The interview loop, with named interviewers who have agreed to the time.
- The story. Why the role exists, why someone strong would want it, what is genuinely hard about the company right now.
That last one matters more than founders expect. The recruiting team is pitching your company to people who have other options, and they can only pitch what you have given them.
Give feedback the same week, with reasons
The single highest-leverage thing you control.
Not useful: "not quite right", "too junior", "let's keep looking".
Useful: "strong on the infrastructure side but has never owned a number, and this role owns a number." That reshapes the search within days.
Two rounds of specific feedback usually calibrate a pipeline properly. Two rounds of vague feedback produce a third vague batch and a month lost.
Keep the clock short
Candidates worth hiring have other conversations running. Every day of internal delay is a day a competitor's process moves ahead of yours.
The three that cost the most:
| Delay | Typical cause | Fix |
|---|---|---|
| Days between interview and feedback | Interviewer has not written it up | Feedback due within 48 hours, in writing |
| Loop cannot be scheduled | Three calendars never align | Pre-block interview slots weekly |
| Offer waits on a band | Nobody approved the number | Approve bands at intake, before sourcing |
None of these are recruiting problems. All of them look like recruiting problems in the outcome.
Have one decision-maker per search
Not a committee. One person with the authority to say yes, whose job it is to gather other opinions rather than to relay them.
Searches with three equal decision-makers converge on the least objectionable candidate, slowly. Searches with none stall at final stage while everyone waits for someone else to commit.
Tell them when the plan changes
Startups pivot. That is normal and not a problem. Not saying so is.
Budget shifts, a role gets reshaped, a founder decides they want more seniority, hiring pauses while a round closes. If they hear about it three weeks late, that is three weeks of sourcing against a brief that no longer exists, which you paid for.
A two-line message the day it changes saves the whole thing.
Let them do the parts you are worst at, and keep the parts you are best at
The split that works:
- The recruiting team runs the funnel. Market mapping, outbound, first screens, scheduling, feedback chasing, offer mechanics, keeping candidates warm, and replying to the people who are not a fit.
- You take final interviews and the close. A founder describing why the company matters beats anyone doing it second-hand, and it is why offers get accepted. The caveat is worth stating plainly: founders are busy, and the first thing that slips is replying to candidates who are not a fit. That silence turns into Glassdoor reviews, and the next candidate reads them before they reply to you. Founder-led is not automatically a better candidate experience.
Founders who insist on doing first-round screens put the most expensive hour in the company at the widest part of the funnel. Founders who delegate the close lose candidates at the last step.
Treat them as part of the team
Access to the ATS, company email addresses, a seat in the relevant Slack channel, an introduction to the interviewers. It costs nothing and it is the difference between a team that can fix a stalled loop and one that can only send you CVs.
It also shows up in candidate experience. A team that reads as part of the company gets better replies than one that reads as an agency working through a list.
A weekly fifteen minutes
One short standing meeting covering: pipeline by role, anything blocked, anything that has changed. It is enough, and it prevents nearly every three-week surprise.
If you are still deciding whether to engage someone, how to hire a recruiter covers scoping and contracting, and how to measure recruitment success in startups covers what to track once it is running.
Frequently asked questions
- How much founder time does an engagement need?
- Roughly two to four hours a week once it is running, plus an intake session per role at the start. That covers a weekly check-in, same-week feedback on candidates, and your own time in final interviews and closes. Engagements fail when a founder expects zero hours, because feedback and closing cannot be delegated.
- What is the most common reason a search stalls?
- Client-side latency, by a wide margin. Feedback that takes a week, loops that cannot be scheduled, a salary band nobody has approved. Candidates accept elsewhere while that plays out, and it looks like a sourcing problem when it is a calendar problem.
- Should the founder be in first-round interviews?
- Generally no, and it is one of the clearest wins from having help. Founders should be in final interviews and closing conversations, where their pitch is irreplaceable. Doing the first thirty-minute filter on every applicant puts the most expensive hour in the company at the widest part of the funnel.
- How do I give feedback that actually improves the next batch?
- Say what was missing against the agreed outcomes, not whether you liked them. Too junior is not usable. Strong on the systems side but has never owned a number, and this role owns a number, is. Specific rejections calibrate sourcing within days, and vague ones produce another vague batch.