Extended definition
The job brief is what the intake meeting produces. Where the job description (or job spec) is candidate-facing — designed to attract applications — the job brief is recruiter-facing, designed to drive sourcing strategy and screening decisions.
The brief is more specific than the JD, includes information the JD would never share publicly (target companies, internal compensation bands, hiring manager preferences), and serves as the contract between recruiter and hiring manager throughout the search. Most TA functions produce JDs religiously and briefs inconsistently; the inconsistency shows up in sourcing that drifts and shortlists that don’t quite hit.
Key elements of a job brief
A working brief covers seven sections:
- Role context — Why the role exists, what the team is doing, what success looks like in the first year. Gives the recruiter the framing needed to position the role to candidates.
- Target candidate profile — The persona — title variations, seniority, years of experience, current company types. The recruiter uses this to write Boolean strings and define outreach lists.
- Sourcing strategy — Which channels to prioritise, what target companies to map, whether referrals or agencies are in scope. Saves the recruiter from reinventing the strategy.
- Competencies and assessment focus — The 3-6 competencies the interview will assess, with brief definitions. Aligns sourcing and screening to interview criteria.
- Compensation parameters — Salary band, equity range, signing bonus authority, level. The recruiter needs this to handle compensation conversations with candidates honestly.
- Process and timeline — Loop structure, stages and owners, target time to fill, key dates the search has to hit.
- Disqualifiers and constraints — Visa requirements, location flexibility, non-compete restrictions, anything that would rule a candidate out at the offer stage. Surfacing these upfront avoids late-stage drama.
The brief lives in the ATS or in a shared workspace, dated and version-controlled. Updates as the role or market context shifts get flagged so all stakeholders are working from the same version.
Why a job brief matters
The job brief is the recruiter’s compass. Without it, sourcing drifts and screening decisions rely on the recruiter’s memory of the intake conversation, which inevitably degrades over weeks.
With it, every sourcing decision can be checked against the brief, every screening pass-through is grounded in agreed criteria, and the hiring manager and recruiter share a single referenceable artefact when the search hits decision points. Beyond the operational case, briefs also shorten onboarding when reqs need recruiter reassignment — a new recruiter coming onto a partly-completed search can read the brief and start contributing within a day, rather than rebuilding context from scratch.
Common mistakes and misconceptions about job briefs
- Confusing the brief with the JD — The JD is candidate-facing; the brief is recruiter-facing. They have different purposes, audiences, and content. Companies that have only one of them usually have JDs without briefs, which leaves recruiters working from incomplete information.
- Skipping the brief because the recruiter “knows the role.” Memory degrades; new context gets layered in; assumptions diverge between recruiter and hiring manager. A written brief locks the alignment that the intake conversation produced.
- Writing briefs that are mostly the JD reformatted — The brief should include things the JD won’t — target companies, internal compensation bands, disqualifying factors, hiring manager preferences. JDs reformatted as briefs miss the operational content that makes briefs useful.
- Failing to update — Briefs from intake that don’t get updated as the role or market shifts become misleading rather than useful. Re-briefing is part of search management when material context changes.
- Treating the brief as the recruiter’s document — The brief is jointly owned with the hiring manager. Recruiter-only briefs miss the chance to surface alignment gaps before they affect the search.
Frequently asked questions
What is a job brief?
A job brief is the recruiter-facing summary of a role — what the role is, who it targets, where credible candidates work, what competencies matter, and what the offer parameters are. It's the operational document that drives sourcing and screening. Where the job description (or job spec) is candidate-facing — designed to attract applications — the job brief is recruiter-facing, designed to drive sourcing strategy and screening decisions.
What's the difference between a job brief and a job specification?
A job brief is recruiter-facing and operational — target companies, sourcing strategy, internal compensation bands, disqualifiers. A job specification (or JD) is candidate-facing and designed to attract applications — role description, qualifications, what the company offers. Both are useful and serve different audiences.
Who writes the job brief?
The recruiter, drawing on the intake meeting with the hiring manager. The hiring manager validates and contributes context, but the recruiter owns the document. Recruiter ownership ensures the brief contains the operational information needed for sourcing and screening, not just the role description.
What should a job brief include that a job description doesn't?
Target companies, sourcing channel priorities, internal compensation bands, disqualifying factors, hiring manager preferences, competency assessment focus, process and timeline details. The JD shows the role to candidates; the brief tells the recruiter how to find and evaluate them.
How often should a job brief be updated?
Whenever the role context, market conditions, or hiring manager priorities change materially during the search. Briefs that don't get updated as the search evolves become misleading rather than useful. Quarterly review for long-running searches is a common cadence.