Describe the problem before choosing the profile
A useful hiring brief begins with an unfinished piece of work. The team may need to improve service reliability, open a new customer segment or reduce the number of decisions waiting for a manager. Writing that problem down helps everyone distinguish a necessary appointment from a familiar title added to an organisation chart. It also gives a recruiter a credible story to discuss with candidates.
Ask the hiring manager what would remain difficult if the position stayed vacant for six months. Then identify the decisions the new person would own and the outcomes another team would notice. A brief that says 'improve the monthly close' is more useful when it explains which hand-offs currently delay the work and who can change them. Do not turn an unresolved operating problem into a demand for an exceptional individual.
Separate entry requirements from learnable context
List capabilities in three groups: needed on arrival, learnable with support and useful but optional. Keep the first group short enough to defend. For each requirement, ask what would go wrong without it and whether that risk could be reduced through onboarding, a colleague or a different division of work. This prevents desirable experience from quietly becoming a rejection rule.
Be specific about the level of independence expected. Using a reporting tool, designing a reporting process and deciding which information a board needs are different requirements. A candidate should not be rejected for missing a familiar product name when the work depends on a transferable capability. Equally, a role that genuinely requires immediate specialist judgment should explain why there is little room for supervised learning.
Turn requirements into an interview scorecard
For each essential capability, define an observable signal and an interview method. A collaboration requirement might be tested through a discussion of a contested decision, while planning ability might be explored with a short prioritisation exercise. Assign an interviewer to each area so that the panel does not repeat the same conversation and leave another important question unanswered.
Describe what adequate evidence would look like before meeting the first candidate. Keep notes about the person's actions, reasoning and results separate from impressions about confidence or conversational ease. An uncertainty is not automatically a negative score: record what remains unknown and decide whether another conversation could resolve it. The scorecard should support judgment, not disguise unsupported opinions as numbers.
Give the brief an owner and a change rule
A brief will sometimes change as the team learns. That is reasonable when the change is explicit. Name the person who can revise scope, compensation or essential requirements, and keep a short dated record of the decision. Tell the recruiter and interview panel what changed, why it changed and whether candidates already in progress need to be reassessed.
Finish the document with practical operating details: interview stages, feedback owners, decision timing, work location and the person authorised to approve an offer. Review these details at the first hiring meeting. A brief succeeds when it reduces avoidable disagreement during the search; a polished document that nobody uses is simply another attachment.
Frequently asked questions
Who should own the hiring brief?
The hiring manager should own the business outcomes and decisions, with the recruiter helping translate them into a searchable, assessable role. Finance or leadership should approve constraints that the manager cannot change independently.
Should the brief be the same as the job description?
They should agree, but they serve different purposes. The public description explains the opportunity; the internal brief also records assessment responsibilities, unresolved questions and approval boundaries.