How to Write a Job Brief That Actually Attracts the Right Candidates
Most job briefs are vague and generic. How to write one that defines the role clearly enough to attract the right candidates and evaluate them consistently.
The job brief is the most important document in any hiring process — whether you are an in-house team filling your own requisition or an agency taking a mandate from a client. It is also the most frequently treated as an afterthought.
A vague job brief produces applications from people who cannot do the job. A specific job brief produces fewer applications from better-matched candidates. This sounds obvious. The practice is rare.
Here is why most job briefs fail and how to write one that actually works.
Why most job briefs are bad
Job briefs are usually written by one of three people: the recruiter, internal or agency (who does not know the role deeply enough), the hiring manager (who knows the role but writes the same brief they have written for the last three iterations of this position), or HR (who uses the standard template from 2019).
The result is a brief that describes the category of person needed rather than the specific person. "5+ years of experience in B2B SaaS sales" describes a category. "Has rebuilt a stalled enterprise pipeline from 8 accounts to 30+ in a market where they had no existing relationships" describes a person.
Category descriptions attract everyone who fits the category. The right candidate is somewhere in that pile, but so are fifty wrong candidates. Specific descriptions attract the people who have done the specific thing you need. Application volume drops. Interview quality rises. Time-to-hire falls.
The five questions a good job brief answers
1. What does this person need to have done before?
Not what skills they need. What they need to have actually done. There is a difference between "strong communication skills" and "has successfully managed C-level relationships through a complex 6-month enterprise sales cycle." The second one is evaluable. The first one is not.
2. What does success look like at 90 days?
This question does more to clarify a role than anything else. If you cannot answer it specifically, you do not understand the role well enough to write a brief for it. "Ramped and contributing to the pipeline" is not an answer. "Has closed the first two pilots from the inherited pipeline and built relationships with all 12 key accounts" is an answer.
3. What would a bad hire in this role look like?
This is the question most hiring managers skip. It is also the most revealing. The failure mode for a role tells you exactly what you are screening against. A bad hire for a Head of Sales role at a bootstrapped startup is someone who is excellent at managing a large team but cannot work without operational support. A brief that does not screen for this will regularly produce this exact candidate.
4. What is the team and culture context?
"Fast-paced startup environment" is meaningless. "Our team of four is fully remote, makes decisions by consensus, has no formal process for anything, and needs someone who builds process rather than follows it" is meaningful. Candidates self-select on specifics, not on adjectives.
5. What is the compensation, and why?
Ranges are not optional. A candidate who expects €120k and a role that pays €85k will both waste each other's time through a four-round process. State the range. If you are worried about candidates negotiating to the top of the range: set the range correctly.
The structure of a good job brief
Role: [Title]
Reports to: [Direct manager title]
Team context: [Team size, structure, working style - 2-3 sentences]
What this person will do in the first 90 days:
- [Specific outcome 1]
- [Specific outcome 2]
- [Specific outcome 3]
What they must have done before (non-negotiable):
- [Specific experience 1]
- [Specific experience 2]
What would make them exceptional (nice to have):
- [Differentiator 1]
- [Differentiator 2]
What a bad hire looks like:
- [Failure mode 1]
- [Failure mode 2]
Compensation: [Range, not a point]
Location: [Remote/hybrid/onsite - specific]
This template takes 45 minutes to fill in properly with the hiring manager. The 45 minutes pays for itself in the first round of screening. Every good brief I have written has produced a shortlist in fewer interviews than every vague brief. If you are not sure which of your open roles is running on a vague brief, a free recruiting process audit shows you where interviews per hire spikes and what that costs you per month.
The AI angle
Pickr's job creation flow is built around this structure. The Deep Dive Questionnaire forces hiring managers through these five questions before the brief is published. AI then cross-references the answers against market data for the role type — flagging inconsistencies, suggesting missing criteria, and checking whether the salary range is competitive for the requirements specified.
The enforced process catches the most common brief failures: vague success criteria, missing non-negotiables, and compensation ranges that are internally contradicted by the seniority of the requirements.
Those failures look identical whether the brief comes from your own hiring manager two desks away or from a client on an agency mandate. So does the fix: half an hour of specific questions, answered before the role goes live, by the person who will actually decide.
Frequently Asked Questions
What should be included in a job brief?
A good job brief includes: specific outcomes expected in the first 90 days, non-negotiable prior experience (what they must have done, not what skills they must have), a description of what a bad hire would look like, team and working context, and compensation range.
What is the difference between a job brief and a job description?
A job brief is an internal document that defines the role clearly for the hiring team and recruiter. A job description is the external-facing document used to attract candidates. The job description should be derived from the brief — not the other way around.
How specific should a job brief be?
Specific enough that two different interviewers would evaluate the same candidate against the same criteria. If the brief can be interpreted differently by different people, it is not specific enough.
How long does it take to write a good job brief?
30-60 minutes with the hiring manager present. The most common reason job briefs are vague is that this conversation was replaced with an email or skipped entirely. The 45-minute intake meeting is not optional — it is where the role gets defined.
Free recruiting audit · 2 minutes
Find out what your hiring process is actually costing you.
Answer eight questions, or connect your current system read-only, and get a report on where your funnel loses candidates and which changes are worth making. No signup, no API key stored, data stays in the EU.
Written by Andreas Amann
Founder of Pickr. Former operator at startups in Berlin and Silicon Valley, where he helped scale companies from 40 to 200+ people. Built Pickr after years of using every major ATS as a recruitment agency owner at ScalingPPL.