Most bad shortlists do not start with bad sourcing. They start with a bad brief. The hiring manager says "get me a strong backend engineer," the recruiter fires off a search, and two weeks later everyone is confused about why the profiles feel off. A hiring brief is the contract between the person who owns the role and the person who fills it. Write it well and the rest of the process gets easier. Write it lazily and you will pay for it in wasted interviews.
What a hiring brief actually is
A hiring brief is not a job description. A JD is the public-facing advert you post on your careers page. A brief is the internal document that answers one question: what does this person need to make true in the first year for us to call this a good hire? It captures the outcomes, the must-haves, the trade-offs you are willing to make, and the boundaries of the budget. It is short. One page is usually enough. The discipline is not in the length, it is in the specificity.
The reason briefs matter more now is that sourcing has become fast and cheap. You can pull hundreds of matching profiles in minutes. The bottleneck has moved from "can I find people" to "do I know what good looks like." If you cannot describe good, no tool will find it for you. This is the same idea behind outcome-based hiring, and it starts at the brief.
Run the intake meeting before you write anything
The brief comes out of a 30 minute conversation with the hiring manager, not out of your own head. Recruiters who skip the intake and reverse engineer a brief from an old JD end up sourcing last year's role. Book the meeting, come with questions, and do not let the manager get away with adjectives. "Strong," "rockstar," "go-getter" tell you nothing. Push for specifics.
Ask these five questions and write the answers down verbatim:
- If this person joins on day one, what does their first 90 days look like? What must ship or move?
- Show me the last person who was great at this. What did they do that the average person did not?
- What are the two or three things this person will be doing every single day?
- What is the real budget, in LPA, fixed and variable, and how much flexibility do we have for someone exceptional?
- What would make you reject a candidate in the first five minutes of the interview?
That last question is the most useful and the most skipped. Rejection criteria are sharper than selection criteria. A manager who cannot tell you why they would say no does not actually know what they want yet, and it is your job to find that out before you start sourcing.
The six parts of a brief that works
1. The outcome, in one sentence
Not the title. The outcome. "Own our payments reliability and get checkout failures below 0.5 percent by Q3" is a brief. "Senior Backend Engineer" is a filing label. When you lead with the outcome, sourcing and screening both anchor to the same target.
2. Must-haves versus nice-to-haves
Force the manager to sort every requirement into two buckets. Most JDs list twelve requirements and treat them all as mandatory, which is how you end up rejecting the person who could have done the job brilliantly because they were missing one framework. A real must-have is something the person cannot succeed without in the first six months. Everything else is a nice-to-have. In practice a good brief has three to five must-haves, no more.
3. The signals that predict a yes
Beyond skills, name the patterns that tend to correlate with success in your context. For a founding sales role in a Gurgaon SaaS startup that might be someone who has sold into Indian mid-market before, carried a quota rather than a support target, and has stayed at least two years somewhere. These are the kinds of signals that predict a yes, and writing them into the brief means your screening has something real to grade against.
4. The comp band and the notice reality
Put the number in the brief. A role budgeted at 18 to 24 LPA fixed is a completely different search from one budgeted at 35 LPA, and pretending the number is flexible when it is not just wastes everyone's time. Also write down what notice period you can absorb. If the manager needs someone in six weeks, a candidate on a 90 day notice is a real problem, and you want to know that before you fall in love with their profile.
5. The dealbreakers
The reject-in-five-minutes list from your intake meeting goes here. Maybe it is job hopping every eight months, maybe it is a candidate who has only ever worked in large IT services and never touched a product team. Write it plainly. Dealbreakers save you more time than any other part of the brief.
6. The scorecard
End the brief with three to five things every interviewer will grade, each with a simple high, medium, or low. When the whole panel scores the same dimensions, debrief conversations stop being about vibes and start being about evidence. This is also the artifact you carry into a tool. When your criteria are written down, TalentGPT can rank up to 500 candidates against those exact outcomes and show you the reasoning behind each score, so the shortlist reflects your brief instead of a keyword soup.
A quick before and after
Before: "Looking for a senior product manager, 8+ years, strong stakeholder skills, fintech preferred." After: "Own the lending product line, ship the new EMI flow by Q2, and lift approval-to-disbursal conversion. Must-haves: shipped a consumer fintech product in India, worked directly with credit and risk teams, comfortable with 20 to 28 LPA. Dealbreaker: only ever a program manager, never owned a roadmap." The second brief sources itself.
Common mistakes that quietly wreck your search
The most common one is copying the previous person's resume into the brief. You do not want a clone of the last hire, you want someone who can deliver the outcome, and those are different things. The second is inflating years of experience as a proxy for quality. Eight years at a slow IT services shop can teach less than three years at a fast startup, so anchor on what they did, not how long they did it. The third is writing the brief alone and never showing it back to the hiring manager. Send it back, get a one line "yes this is right," and only then start sourcing.
A tight brief also pays off downstream. It is what lets you reduce time to hire because everyone is chasing the same target, and it is what makes it possible to screen hundreds of candidates without the exercise turning into guesswork. The brief is the cheapest leverage you have in the whole funnel.
Frequently asked questions
How long should a hiring brief be?
One page. If it runs longer you are probably confusing the brief with the job description or padding it with requirements that are really nice-to-haves. The value is in forcing decisions about what matters, and that discipline breaks down once the document gets long.
Who owns the hiring brief, the recruiter or the hiring manager?
The recruiter writes it, the hiring manager signs off on it. The recruiter runs the intake and drafts the document, but it is not final until the manager confirms in writing that the outcomes and must-haves are correct. That shared sign-off is what prevents the "these profiles are all wrong" conversation later.
Do I need a new brief for every role?
Yes, even for roles with the same title. Two senior engineers on two different teams can need almost opposite profiles depending on the outcome. You can reuse a template, but the outcome, must-haves, and dealbreakers should be written fresh each time.
How does a brief connect to AI sourcing tools?
A good brief converts directly into search criteria. Because TalentGPT takes plain-English descriptions of the outcomes you need and ranks candidates against them across 300M+ profiles, the sharper your brief, the better the ranking. The tool can only be as precise as the target you give it.
Write the brief, get the sign-off, then let the sourcing do the heavy lifting. Turn your next hiring brief into a ranked shortlist with TalentGPT and see the reasoning behind every candidate before you spend a single interview slot.