A recruiter needs to understand what the hire will build, the decisions they will own, and the conditions they will work in. Give that context through an approved hiring brief. Keep customer identities, unreleased plans, private personnel matters, and internal documents outside the brief unless a specific search decision requires them and sharing is authorized.
The useful question is: What does the recruiter need to understand to recognize relevant experience? That answer is often more specific than a job description and less sensitive than a full account of the business.
Explain the work behind the job title
Before an intake meeting, write down the problem this hire will solve. Describe what exists today, what needs to change, and which responsibilities belong to the new person.
A title such as “senior engineer” leaves room for different interpretations. The recruiter also needs to know whether the job involves building a new capability, improving an existing product, or making delivery more reliable.
Describe the next work at the level needed for the search. For a fictional software role, “the engineer will make a manual customer setup process repeatable” is useful context. It does not require a customer list or an unreleased product plan.
Ask the recruiter to explain the assignment back in their own words. If their explanation points toward a different kind of candidate, resolve that before sourcing begins.
Prepare a brief that can be shared as written
Create a version that participating recruiters can use without having to guess which sentences are private. Include approved information about the business, role outcomes, responsibilities, compensation, working arrangements, and interview process.
Use the startup hiring brief template as a starting point. Add a clear instruction identifying who the version is intended for and whether it can be forwarded to candidates.
| Search question | Useful context to provide | Detail to leave out of the general brief |
|---|---|---|
| What will this person deliver? | The capability or business outcome they will own | Unannounced launch dates and confidential product specifications |
| What makes the work difficult? | Relevant technical constraints, dependencies, and available support | Credentials, private architecture documents, and security weaknesses |
| Who will they work with? | Team functions, reporting relationship, and decision boundaries | Private performance assessments or an individual's circumstances |
| What experience matters? | Prior responsibilities that resemble the upcoming work | Identifiable customer situations or another candidate's background |
| Why might someone join? | Approved company context and an honest description of the opportunity | Unannounced financing, customer contracts, or speculative promises |
Removing a name alone may not make a detail safe to circulate. A distinctive combination of timing, product plans, and circumstances can still identify the company, customer, or person involved. Generalize the underlying requirement instead.
Agree who will receive additional context
Before providing information beyond the approved brief, establish who is working on the search, what they are responsible for, and whether they involve other recruiters or researchers.
Ask how they will use the information, where it will be shared, and who will answer questions about its handling. A platform profile or a familiar introduction does not answer those questions on its own.
When someone requests a sensitive detail, ask which search decision it would change. If the recruiter can identify the right experience from a broader description, use that description. If additional context is necessary, have the appropriate company owner decide what can be shared and with whom.
Keep the approved brief separate from restricted working material. An agreement about confidentiality can support the process, but the people doing the search still need clear instructions about what they may circulate.
Separate candidate-facing information from internal discussion
Recruiters should be able to explain the opportunity accurately to a candidate. Give them wording they can use for the role's purpose, reporting line, approved package, working arrangement, and hiring steps.
An unresolved internal debate should become an open question to settle, rather than a confident promise in an outreach message. If the scope or package is still undecided, decide what the recruiter can accurately say before introductions begin.
The candidate should also understand who is representing the opportunity and where their information is going. Ask the recruiter how they confirm interest and permission before sharing a profile. Keep the expectations clear in both directions.
End the intake meeting with decisions
A useful intake meeting produces something the hiring team and recruiter can work from. Before ending it, confirm:
- The outcome the hire will own and the evidence that would demonstrate relevant experience.
- Which requirements are essential and which are preferences.
- The approved brief and its intended recipients.
- Any open questions, with a person responsible for resolving each one.
- The interview decision owner and how feedback will reach the recruiter.
- How changes to the brief will be communicated.
The length of the meeting is less useful than the clarity of these decisions. If the hiring team cannot yet explain the role, another sourcing channel will not resolve that uncertainty.
Check whether the brief changes the shortlist
When the first submissions arrive, ask the recruiter to connect each candidate's experience to the brief. A relevant answer describes work the candidate personally owned and identifies what still needs checking.
If submissions repeatedly miss the same requirement, review how that requirement was explained. Decide whether the brief needs clarification, the recruiter needs a different sourcing direction, or the interview needs to collect missing evidence.
Keep feedback specific to the work. “We need evidence of owning delivery after launch” gives a direction for the next search. Personal speculation and confidential internal disagreements do not help the recruiter apply the requirement.
For the ongoing process, use the guide to coordinating recruiting partners. It covers search ownership, candidate evidence, and feedback after the initial brief.
Before you start
A clear brief should make the opportunity understandable while giving the company control over what it shares. Start with approved role context, resolve uncertainty with the hiring owner, and add detail only when it helps a specific decision.
If you are choosing outside support, use the recruiting partner checklist. To discuss a search with Refery, share an approved job description or a general outline of the role.