How to Write A Role Brief A Recruiter Can Act On in 15 Minutes
A practical guide to writing clear role briefs that help recruiters find the right candidates faster.
Allangkrita Banerjee
Content Strategist • Hiringhood
Most role briefs fail because they are copied from an old job description, they list tools instead of work, and they leave the recruiter guessing. The guessing costs a week or more before the first useful feedback arrives, in a hiring cycle that already runs about 135 days.
A recruiter only needs enough information from the brief to start searching the same day. That means a clear picture of what the person will own in six months, which skills are essential and which can be taught, where the role sits, what the budget is, how long the team can wait, and how the interview process works. Those six answers fit in fifteen minutes of writing.
In India, the notice period, the risk of counter-offers and the way compensation is structured all change how a brief should be written. Managers who address these early lose fewer candidates late. This piece walks through each part, shows a weak and a strong brief for the same role, and suggests how the approach differs for startups, scale-ups and large companies.
01 Why Role Briefs Go Wrong in IT Hiring
Most role briefs begin as a forward. A hiring manager finds an old job description, changes the title, and sends it to the recruiter with a line asking for profiles by Friday.
The recruiter reads it and sees a list of tools. Java, Spring Boot, AWS, Kubernetes, 5 to 8 years. It says nothing about what the person will actually do, why the seat is open, or what the manager would trade off to fill it. So the recruiter does what anyone would do and guesses. A few profiles go out, the manager rejects most of them, and the feedback arrives a week later in one line. "Not the right fit."
That week is where the time goes. In IT hiring, the process already runs long. Hiringhood's own numbers put the average cycle at about 135 days, and most of that is the notice period a candidate has to serve after accepting. A vague brief adds more delay to a timeline that has none to spare.
The problem is rarely effort. Hiring managers are busy, and writing a good brief feels like homework. But the hour saved at the start usually costs three weeks at the end.
02 What a Recruiter Needs in the First 15 Minutes
A recruiter does not need a perfect document. They need enough to start searching and screening on the same day.
That means they should be able to answer five things after one read. What will this person do? Who are they likely to be today, in terms of current role and company type? What would make you say no to a profile straight away? What is the pay range? And how long can the team wait for them to join?
If a recruiter can answer those without calling you back, the brief has done its job. If they have to ask, the brief was incomplete, and every question they ask costs you a day.
Fifteen minutes is also a useful limit for the manager. It forces you to write what matters and leave out what doesn't. Nobody needs a page on company culture before the first search is run.
03The Role Brief Framework - 6 Key Questions
Answer these six questions in plain sentences before you send anything to a recruiter.
What will this person own in the first six months?
Skip the generic duties. Write the actual work. “Rebuild our data pipeline so reports run daily instead of weekly” tells a recruiter far more than “responsible for data engineering.” The best candidates read a role like this and know within a minute whether it interests them.
What must they already know, and what can they pick up on the job?
Most briefs treat every skill as essential. Few roles are that strict. Split the list in two. The first part is what the person must bring on day one. The second is what you are happy to teach. A recruiter with this split can consider candidates who would otherwise be screened out for missing one tool.
Where does the role sit?
Say who they report to, how big the team is, and who they will work with every day. Candidates ask about this early, and recruiters can only answer if you have told them.
What is the budget, and how firm is it?
Give a range. If you can stretch for the right person, say so and say by how much. Recruiters lose good candidates late in the process when the numbers turn out to be different from what they assumed.
How long can you wait?
In India, a notice period of 60 or 90 days is common in tech. Decide whether your team can wait that long, whether you would buy out a notice period, and whether an earlier joiner is worth a slightly weaker profile. This one answer changes who the recruiter should approach.
What does the process look like, and who decides?
List the rounds, who takes them, and how quickly feedback will come. If one person has the final say, name them. Hiring slows down most when a recruiter does not know whose opinion counts.
Six questions, answered honestly, make a brief a recruiter can act on. Most managers can write them in under fifteen minutes. The ones who do tend to see their first shortlist within days, not weeks.
04India-Specific Considerations
Hiring in India has a few quirks that a brief written for another market will miss.
Start with the notice period
Most tech employees here are bound to 60 or 90 days, and that wait sits between the offer and the first day at work. A candidate who says yes in week four may not join until week sixteen. Plenty of managers treat this as a fixed fact of life. It is not. Some companies buy out part of the notice, some agree to a later joining date for a stronger candidate, and some decide up front that they will only look at people who can join within 30 days. Whichever way you lean, put it in the brief. A recruiter who knows your limit will search a very different pool.
Then there are counter-offers
A candidate who resigns will often get one, sometimes within hours. Hiringhood's own data shows that only about one in four people who accept an offer end up joining, and a counter-offer is one of the usual reasons. A manager can't prevent this, but the brief can help. If the role has a clear reason to exist and a clear path forward, the recruiter has something real to talk about when the candidate's current employer starts bargaining. If the brief is thin, the recruiter has only the salary to fall back on, and the counter-offer usually wins that argument.
Compensation bands are the third piece
Candidates in India often compare offers by the fixed component, the variable, and the joining bonus separately, and they read the structure as closely as the total. Give the recruiter the range and the split. If the top of the band is negotiable, say by how much and for what kind of profile. Recruiters lose candidates at the final stage when the number on the offer letter is not the number they were quoted in the first call.
05Common Mistakes Hiring Managers Make
Most of these are small, and most are fixed in a single conversation.
Asking for everything
A brief that wants ten years of experience, three cloud platforms, team leadership experience and a startup mindset describes a person who may not exist. Recruiters can't search for that, so they search for a loose version of it and hope you will be flexible. You would have been, had you said so.
Hiding the budget
Some managers think a lower number will come out in negotiation if they keep the range vague. What actually happens is that good candidates drop out in the second or third round, after everyone has spent time.
Slow feedback
A recruiter sends five profiles on Monday and hears back on Friday. By then two of the candidates have taken other interviews. In a market where good people are off the market in a week or two, feedback that takes days costs you the shortlist.
Changing the role halfway through
The first batch of profiles gets rejected, and the manager decides they actually want something different. That is a reasonable thing to learn, but it should have been learned in the intake call. Ask yourself early what a perfect candidate looks like, and whether you would also interview a second type of person.
Leaving the recruiter out of the decision
They talk to candidates daily and hear what the market is saying about your role. If they tell you the range is too low or the skill mix is rare, that is useful information, not pushback.
06A Weak Brief vs a Strong Brief
Here is the same role written two ways. The company is hiring a data engineer.
The weak brief - Looking for a Data Engineer. 5 to 8 years of experience. Must know Python, SQL, Spark, Airflow, AWS. Good communication skills. Should be a team player. Budget as per market. Immediate joiners preferred.
A recruiter can search on this, but not well. Five to eight years is a wide band. "Budget as per market" tells them nothing. "Immediate joiners preferred" quietly removes most of the available pool, and the recruiter doesn't know whether that is a firm rule or a wish.
The strong brief - We need a data engineer to rebuild our reporting pipeline. Today, our reports refresh once a week and take about two days to prepare by hand. In the first six months, we want them running daily with no manual steps.
The person will report to the head of engineering and work with a team of four. They should already be comfortable with Python, SQL and Airflow. Spark and AWS are useful, but we can teach either one.
The budget is 24 to 30 lakh fixed. We can go up to 32 for someone who has built pipelines at scale. We can wait up to 60 days for the right person, and we will cover part of a 90-day notice period if needed.
Our process has three rounds. One technical, one with the head of engineering, one with the founder. We give feedback within two working days of each round.
The second version takes about ten minutes to write. A recruiter can read it and start calling people the same afternoon. They know what the work is, what to screen for, what the money looks like, and how much the manager is willing to bend. That is all a brief has to do.
07Recommended Approach by Team Type
The same six questions apply everywhere. What changes is which ones carry the most weight.
Startups
In a startup, the person hiring is usually the founder or the head of engineering, and they are doing three other jobs. The brief often exists only in their head. Write it down anyway, even as five lines in a message. The most useful thing a startup can add is the reason the role exists now. A candidate weighing a startup against a stable offer wants to know what the company is trying to do over the next year, and the recruiter needs that story to tell.
Startups also have less room on pay, so be honest about it. If the fixed component is lower than the market, say what else is on offer, whether that is equity, scope or speed of growth. A recruiter can work with a clear trade-off. They can't work with a surprise.
Scale-ups
Scale-ups usually hire in batches, and that is where briefs start to drift. Five managers write five slightly different versions of the same role, and the recruiter ends up searching for five different people. Agree on one brief per role type, and keep a single person responsible for it.
The other pressure point is speed. Teams at this stage often promise a fast process and then slow down once the interview panel gets busy. Be realistic about how quickly feedback will come, and tell the recruiter the real number. A candidate who is told two days and waits six will not trust the process.
Enterprises
Large companies tend to have the opposite problem. The brief exists, but it is a formal job description approved by three departments, and it reads like a policy document. Keep that version for the record. Then write a short working brief next to it for the recruiter, covering the real work, the real flexibility and the real constraints.
Enterprise hiring also involves more people in the decision. Name who they are, in what order they see the candidate, and who can say yes. Pay bands are often fixed by grade, so the recruiter needs to know early whether there is any room above the band, and what it takes to get an exception approved.
Conclusion
A good role brief does not take long to write. It takes details of what the role needs, what the budget allows, and how long the team can wait. Managers who write one usually find that the recruiter's first shortlist is closer to what they wanted, and that fewer candidates drop out after the offer.
The brief is also the one part of hiring that sits fully in the manager's hands. Notice periods, counter-offers and market rates are things you work around. A clear page at the start is something you control.
At Hiringhood, we work with a pool of pre-vetted candidates in AI, ML and Data Engineering, and we begin the conversation with candidates while they are still serving their notice period. That only works when the role is well described. If you are about to open a position, send us your brief, even a rough one. We will tell you what is missing and who in our pool might fit.
Share this article:
Copy Link
LinkedIn
Twiter / XIn This Article
01 Why Role Briefs Go Wrong in IT Hiring02 What a Recruiter Needs in the First 15 Minutes03 The Role Brief Framework - 6 Key Questions04 India-Specific Considerations05 Common Mistakes Hiring Managers Make06 A Weak Brief vs a Strong Brief07 Recommended Approach by Team TypeHire AI/ML Talent in Days, Not Months
Join 500+ companies leveraging Hiringhood to hire exceptional talent with unmatched speed and accuracy.
FAQ
Frequently Asked Questions
Frequently Asked Questions
Everything you need to know about writing a role brief a recruiter can act on. Can't find what you're looking for? Our team is one message away.
A role brief should include the exact title, must-have technical skills, years of experience, salary band, location/remote policy, and the business reason the role is open. Vague briefs are the single biggest cause of mismatched candidates.
A clear, actionable role brief can be written in under 15 minutes if you separate must-haves from nice-to-haves upfront and avoid generic jargon like "rockstar" or "ninja" that recruiters can't screen against.
A job description is written for candidates and focuses on selling the role. A role brief is written for the recruiter or sourcing team and focuses on screening criteria, what to filter for, what to reject, and how to rank candidates.
Most delays come from unclear briefs, recruiters can't tell the difference between "has used an LLM API" and "has fine-tuned a model in production," so they either over-source or under-source candidates. A specific brief removes that ambiguity.
It should answer: what model types the candidate will work with, what stage of the ML lifecycle they'll own (training vs. deployment vs. monitoring), what tools/stack are in use, and what "good" looks like in the first 90 days.
A bad brief forces recruiters to guess at screening criteria, which leads to unqualified candidates reaching interview stage, repeated re-briefing cycles, and wasted engineering interview time, often adding weeks to the hiring timeline.
Yes, AI can turn a plain-English description of the role into a structured brief with screening criteria in minutes, which is faster and more consistent than a manual back-and-forth between hiring manager and recruiter.
More from the Hiringhood Blog
Build, Buy, or Borrow? How Indian CTOs Should Decide on Their AI Team
Indian CTOs setting up an AI team have three routes. They can build in-house, buy off the shelf, or borrow talent through contract specialists and hiring partners…
What the Best AI Teams Look Like in 2026
AI has long surpassed the experimental phase. It has become a business imperative that drives ROI. Walk into any organisation, and you are likely to find AI initiatives in various stages of developement, from a…
AI/ML Hiring in India 2026 - The 5 Stats You Need to Know
AI talent shortage in India is widening as the demand for AI/ML talent continues to exceed the current ta …