Turn a hiring manager’s wish list into a useful candidate brief

A candidate brief should help someone decide whether the work fits them and help the hiring team decide what evidence to gather. A long list of admirable traits does neither unless each item connects to something the person must do.

Start by asking the hiring manager to defend every requirement with a task. “Commercial,” “technical,” and “entrepreneurial” may matter, but they need to become observable work before they guide sourcing or interviews.

Sort the wish list into four groups

Use four labels: required at entry, learnable with stated support, preference, and unresolved. The last category prevents disagreement from being quietly converted into a mandatory filter.

OPM’s job-analysis guidance ties competencies to job tasks. Its structured-interview guide also distinguishes what is needed when a person enters the job. Use that distinction to challenge whether an item really belongs in your initial screen. Read the job-analysis guidance and the structured-interview guide.

A learnable skill needs a learning arrangement. If the manager says someone can learn a tool but cannot name documentation, training, or a person who can help, the brief contains an unfunded assumption.

Rewrite the requirements

The following is a fictional brief for a first customer implementation hire. It demonstrates the editing process; it does not claim these are universal requirements for the role.

Original request	Job-related rewrite	Evidence to seek
A great communicator	Makes an incomplete customer handoff understandable to the next owner	A specific example or short handoff exercise
Has worked at a famous company	Has handled implementations with comparable complexity and limited support	Their own responsibilities and available resources
Knows our exact tracking tool	Can maintain a clear project record; our tool can be learned with onboarding	An example of organizing changing project information
Strategic and hands-on	Can choose a next step and perform the agreed implementation tasks	Example of a tradeoff and the work they personally did
Five years in the industry	Unresolved: identify what indispensable experience the year count represents	Relevant scope and examples; retain any genuinely required qualification separately

Do not remove a qualification that is actually required for the work or by an applicable rule. Do not retain a proxy simply because it is easy to search. The manager should explain the connection.

Write the brief in one page

Use this structure for the brief. Replace the example content with decisions your team has made.

Purpose of the role: Own the coordination of customer implementations so that responsibilities, readiness, and unresolved risks are visible.

Work in scope: Clarify the commercial handoff, maintain the implementation plan, document customer constraints, and coordinate the readiness review.

Work outside scope: Approving contract exceptions, promising new product delivery, and managing a department that does not yet exist.

Required at entry: Evidence of making an unclear operational handoff actionable and of communicating a risk before it becomes a surprise.

Learnable with support: Our product terminology and project tracking tool. The manager owns the training plan and scheduled review time.

Context: Small team, changing process, direct customer communication, and a named product escalation partner.

Assessment evidence: One structured conversation about relevant past work plus a bounded fictional handoff exercise. No request for a previous employer’s confidential materials.

Practical terms: Actual location or working arrangement, expected schedule, compensation information where appropriate or required, and the known selection steps.

Open decision: Whether the forecast workload supports the proposed employment arrangement. Resolve this before asking candidates to invest in later stages.

Make the brief useful to candidates too

Tell candidates what the process will involve and how to request adjustments. CIPD’s selection guidance emphasizes advance information about the assessment and an opportunity for the candidate to evaluate the role. Read the selection-methods guidance.

A realistic brief lets a candidate raise a meaningful concern: “I can own the implementation plan, but who decides when product work takes priority?” That question is useful evidence about your operating setup. It should not automatically count against the candidate.

Avoid presenting uncertainty as excitement. If the reporting line or scope is unsettled, say what is known, who will decide the remaining issue, and when.

Align the people who will use it

Before sourcing, have the manager, recruiter, and interviewers independently mark what they think would exclude a candidate. Compare the answers. If the recruiter treats the exact tool as mandatory while the manager calls it learnable, candidates will be screened against two different jobs.

Version the brief when a substantive requirement changes. Review whether people already assessed need a fair opportunity to address the revised criterion. Do not silently move the standard to fit a favorite applicant.

If you still cannot define the task behind a requirement, return to role research. A focused conversation with someone who has done comparable work can be more useful than adding another adjective to the brief.