RECREWD FIELD GUIDE · 9 MIN READ
How to write a role brief that improves candidate matching
Define outcomes, scope, constraints and fair evidence before turning a hiring need into a job description.
- For
- Hiring managers and small teams preparing a role
- Published
- Updated
SHORT ANSWER
The practical answer
A useful role brief describes why the role exists, the outcomes expected, the real scope, essential constraints and evidence that would demonstrate capability. It distinguishes requirements from preferences and avoids criteria unrelated to the work. That gives candidates a clearer decision and gives reviewers a common basis for comparison.
Begin with the work
Write three to five outcomes the person should influence in the first year. Describe the current situation and the authority, collaborators and resources attached to the role. Avoid pretending every outcome is fully controllable by one hire.
A title is a routing label, not the brief. Two organisations can use the same title for very different scope.
Separate essential from preferred
For every requirement, ask what job outcome it supports and what alternative evidence could demonstrate the same capability. Skills-first hiring can uncover candidates whose experience does not follow one credential path.
Keep legal and safety requirements where they are genuinely necessary. Remove years-of-experience thresholds or degree requirements that lack a job-related reason.
Use a structured template
Complete these fields before writing promotional copy.
- Purpose: why the role exists now.
- Outcomes: three to five observable results.
- Scope: team, budget, systems, customers and decision rights.
- Essential evidence: experience or demonstrated skills needed from day one.
- Learnable areas: skills the person can develop after joining.
- Constraints: location, schedule, eligibility, travel and compensation.
- Process: stages, assessors, accommodations and expected timing.
Check fairness and clarity
Review whether the language discourages people based on protected characteristics or relies on stereotypes. In the United States, the EEOC states that job advertising, recruitment and hiring cannot discriminate on protected grounds and that seemingly neutral practices can be unlawful when they create unjustified adverse effects.
Requirements and applicable law differ by country and employer. Use local advice where needed; this guide is a drafting method, not legal advice.
PUT IT INTO PRACTICE
Completed role brief: customer operations lead
This fictional employer brief is a drafting example, not an open position. Outcomes, pay and process are explicit scenario choices that a real employer must replace with approved facts.
Purpose and reporting line
Purpose: make customer onboarding more consistent as a software team grows. Reports to the head of customer success and coordinates with product and account teams.
The role owns operational reporting and process proposals. Product owns software priorities; the head of customer success approves staffing and service-policy changes.
First-year outcomes
First 30 days: document the onboarding stages, data owners and current sources of delay. Establish a baseline before promising an improvement target.
By 90 days: pilot a revised handoff with one account team and publish an agreed weekly report.
By six months: evaluate the pilot against the baseline, including incomplete records and customer mix. Recommend expansion only if the evidence supports it.
Essential evidence
Show a process-improvement example with your own contribution, collaborators and outcome clearly separated.
Demonstrate how you check a spreadsheet report for missing data and misleading totals. Explain an operational finding to a nontechnical stakeholder.
Accept relevant work or a defensible practical project as evidence; do not use an unrelated degree as a proxy for these tasks.
Learnable and preferred
Learnable: the company’s CRM and internal onboarding terminology. Preferred: querying data with SQL.
SQL is not a day-one requirement in this scenario because a data analyst supports the reporting workflow. If that support disappears, revisit the requirement and role scope.
Working conditions and resources
Scenario: full-time hybrid work in Vienna, two office days each week, no routine travel. Budgeted annual gross base pay: €60,000–€70,000; this is a fictional budget, not a market benchmark.
No direct reports initially. A named data analyst provides agreed support; a software engineer reviews integration requests. Confirm actual eligibility, employment terms and resources before advertising.
Selection process
Stage one: a 30-minute mutual-fit conversation covering scope and constraints. Stage two: a 45-minute discussion of a redacted past example or equivalent fictional exercise, using the same stated criteria.
Assessors record evidence for process reasoning, data accuracy and communication. Offer an accessible format and a contact for accommodation requests. Publish realistic timing and update candidates if it changes.
Approval and unanswered questions
The hiring manager confirms scope, budget and assessor availability; the relevant local advisers check applicable employment requirements.
Before posting, resolve who owns the baseline, how much analyst time is available and whether every selection criterion is essential to the work.
Make your own working copy
Download the plain-text template or open it below to copy into your preferred notes editor. Your working copy stays with you.
Download blank template (.txt)View and copy the blank template
Recrewd — Completed role brief: customer operations lead Blank working template Use your own facts. Leave unknowns explicit. Do not include private or confidential material. Role title and reason for hiring now: [Complete here] Reporting line and decision rights: [Complete here] First 30 / 90 / 180-day outcomes: [Complete here] Baseline, measures and dependencies: [Complete here] Essential evidence for each outcome: [Complete here] Acceptable alternative evidence: [Complete here] Preferred and learnable skills: [Complete here] Team, tools, budget and support: [Complete here] Location, schedule, travel and approved compensation: [Complete here] Eligibility and terms to verify: [Complete here] Selection stages, criteria and assessors: [Complete here] Accessible formats and accommodation contact: [Complete here] Candidate communication and timeline: [Complete here] Approvers, unresolved questions and publication date: [Complete here]
Put this into practice
Have a role brief ready? See how Recrewd handles a business request and confirms its hiring scope.
Sources and scope
This guide provides general educational information. It does not promise that a particular search, CV, introduction or hiring method will produce an interview or hire.