When several recruiters contribute to a startup search, the hiring team needs one brief, one person coordinating the process, and a shared standard for candidate evidence. Otherwise, every additional source can become another inbox, another interpretation of the role, and another set of introductions to reconcile.
At Refery, our view is that access to talent and responsibility for selection belong together. A useful recruiting service should help a founder understand why each person deserves an interview and what still needs checking.
This guide describes a way to organize that work. It does not prescribe a fixed number of recruiting partners or promise a particular hiring outcome.
Separate an introduction from an active search
A founder, operator, or investor may know someone whose work they can speak to directly. That person can make a valuable introduction without being available to run a search.
A professional recruiter working on a specific role has a different responsibility: understand the brief, identify relevant people, check interest and constraints, and keep the search moving.
The two contributions can complement each other. Problems start when the hiring team expects a busy contact to behave like a dedicated recruiter, or assumes a warm referral has already been assessed against the role.
| Contribution | What to ask for | What still needs checking |
|---|---|---|
| Introduction from someone who knows the candidate | How they know the person and what work they observed | Interest in this role, relevant responsibilities, and practical constraints |
| Role-specific recruiter search | Why this candidate matches the brief and what has been discussed | The evidence behind the assessment and remaining interview questions |
| Candidate approaching the company directly | Relevant work and the reason for their interest | The same role criteria used for every other source |
A strong introduction is a starting point. Keep the interview standard consistent across sources.
What coordination looked like in a Refery search
A recruiting partner flagged that a full-stack brief was asking one person to cover product work and a deeper specialty overlapping another open role. Refery brought that question to the founder rather than leaving the recruiter to guess which requirement could flex.
The founder agreed to consider a more conventional full-stack profile. Refery then returned that answer to the partner. The anonymized case study follows this exchange.
The transferable lesson is not that every difficult brief should be broadened. It is that someone must own the route from a sourcing concern to a hiring decision and back. A partner should know where to raise a concern, who can decide, and which answer to use in the next conversation.
Give every partner the same current brief
Use a short written brief that states the outcome the hire will own, the essential evidence, location and working arrangement, compensation, and decision makers. Distinguish requirements from preferences.
If the role changes, update the brief and tell the participating partners what changed. Ask them to reassess people already in progress against the revised requirement. This prevents candidates from hearing different versions of the job.
For a fictional example, imagine a startup initially asking for an engineer to build integrations. The team later decides the hire must also lead customer discovery. That change affects the evidence recruiters need to find; adding another technology keyword would not communicate it.
Use the startup hiring brief template to make the decisions explicit before adding more sourcing activity.
For the intake conversation, use the guide to briefing a recruiter without sharing confidential information to agree on what partners can use and forward.
Assign one person to coordinate the search
The coordinator should know who is participating, what each partner is covering, which candidates are already in process, and who owes the next decision. This can be a founder, a talent leader, or an agreed recruiting contact.
Decide how overlapping introductions will be handled before they happen. Keep the coordination record limited to what the search requires, and share candidate information only with the relevant people and appropriate permission. A shared process does not require every partner to see every candidate's details.
Add a partner when they bring a clear contribution: relevant relationships, expertise in the role, or capacity to pursue a defined part of the search. If their coverage simply repeats existing work, first examine why the current search is not producing the evidence you need.
Ask for a candidate brief that separates facts from interpretation
A resume tells the hiring team where someone worked. A useful submission explains what they personally did, why it matters for this role, and what remains uncertain.
Use a consistent format:
| Field | What a useful submission contains |
|---|---|
| Relevant outcome | A specific project or responsibility connected to the hiring brief |
| Personal contribution | What the candidate owned, with the source of that information |
| Assessment | Why the partner thinks the evidence fits the role |
| Confirmed interest | What the candidate has agreed to explore or have shared |
| Practical constraints | Role-relevant availability and working-arrangement requirements |
| Open questions | What the hiring team should verify in the interview |
“Strong startup operator” is an interpretation. “Described owning the first customer integration and its rollout” gives the interview team something to examine. It still needs follow-up; a recruiter’s summary is not independent proof of the candidate’s contribution.
Treat the shortlist as a decision document
Do not judge a shortlist by how full it looks. Each candidate should have a specific reason to be there and a clear question for the next conversation.
If the same essential requirement is missing from every submission, decide whether the problem is the brief, the sourcing approach, or the evidence collected. Sending more profiles through the same process may repeat the uncertainty.
A useful shortlist review asks:
- Which requirement does this person clearly meet?
- What evidence supports that conclusion?
- What remains unknown?
- What would the next interview need to resolve?
- Has the candidate agreed to this next step?
The hiring manager retains the hiring decision. The recruiting process should make that decision better informed, rather than hide uncertainty behind a confident recommendation.
Give feedback that changes the next search action
Feedback such as “not senior enough” is difficult to act on. Explain the missing evidence and connect it to the brief.
In a fictional engineering search, useful feedback might be: “The candidate described implementing features, but we still need evidence of owning deployment and incident response. Please prioritize that responsibility in the next conversations.”
Record whether the feedback changes the role requirement or only the assessment of that candidate. A new requirement should go back to every participating partner. A candidate-specific concern should stay within the relevant discussion.
Know when to pause and recalibrate
Pause new submissions when the hiring team cannot review them, interviewers disagree on the job, or the approved package no longer fits the brief. Resolve the decision before asking partners and candidates to invest more time.
Useful operating measures include time waiting for feedback, repeated introductions, and the requirements most often left unverified. Define each measure consistently. This article provides no performance benchmark or claim that a particular process reduces hiring time by a stated amount.
The founder's responsibility
Recruiting support can organize discovery, screening, and communication. The founder or hiring leader still needs to decide what success looks like, make time for relevant candidates, and resolve tradeoffs promptly.
That is the practical standard we recommend: contributors know what work they own, candidates understand the opportunity, and the hiring team receives evidence it can use.
Before choosing support, use the recruiting partner checklist. If the search is already defined, share your hiring brief with Refery.