Job brief template: what great hiring managers actually specify

Most job briefs read like the job ad got there first and the thinking never caught up. Title, years of experience, a list of tools, a line about "fast-paced environment." Nothing a recruiter could actually search against.

The intake call is supposed to fix that. Most of the time it doesn't, because nobody's working from a real template, so the call drifts to whatever the hiring manager happens to mention first, in whatever order it occurs to them.

Here's the template that actually holds up, field by field, with the exact questions that get you a usable answer instead of a vague one.

Role context

Don't ask "tell me about the role." You'll get the job title back in more words. Ask instead:

• "What happens if this role stays open another three months?"
• "Is this a backfill, and if so, why did the last person leave?"
• "Is this new headcount, or did someone finally win the argument for it?"

The answer tells you whether "urgent" is real or just a word someone put in the ticket. A backfill from a manager who pushed the last person out means something different than a backfill from someone who was blindsided by a resignation. You need to know which one you're recruiting into.

Must-haves, separated from preferences

Never let a hiring manager hand you a list. Go through requirements one at a time and ask, for each one: "If someone was strong everywhere else but didn't have this, would you still take the call?"

Watch for the pause before the answer. A fast no is a real must-have. A slow no, or a "well, ideally," is a preference wearing a must-have's clothes, and it's exactly what makes searches drag for months. Write must-haves and nice-to-haves as two visibly separate lists in the brief, not one list with different fonts.

Specific traps to ask about directly, because hiring managers rarely volunteer them unprompted:

• A specific tool or platform version, when the underlying skill transfers fine from adjacent tools
• A years-of-experience number that's really a proxy for seniority they haven't defined otherwise
• Industry background, when what they actually need is the transferable skill, not the sector

Team structure and reporting line

Get names, not titles. "Who specifically will this person report to, and who's on the team already?" Candidates ask this in round two regardless, so if the recruiter doesn't have it, they're either guessing or promising something the org chart won't back up later.

Also ask: "Has this reporting line changed in the last six months, or is it about to?" A team mid-reorg is a different pitch than a stable one, and candidates can usually tell when they're being sold a version that isn't quite true yet.

Salary and work model

Ask for a number, not a range description. "What's the actual band, and who signed off on it?" If the hiring manager can't name who approved it, it isn't approved yet, it's a hope.

For work model, ask the follow-up nobody asks: "If a great candidate wanted the opposite of what's listed, is there any flexibility, or is this genuinely fixed?" Get the honest answer before you're relaying a policy that turns out to be negotiable, or promising flexibility that doesn't exist.

Hiring process and timeline

Map it out loud on the call, stage by stage: "Walk me through what happens after I submit a candidate. Who looks at the CV first? How long before they hear back? How many rounds, and who's in each one?"

Then ask the question that actually predicts whether this search will stall: "What's the slowest part of this process usually?" Every hiring manager knows the answer. Most won't say it unless asked directly, and it's the single best predictor of whether you'll be chasing feedback for two weeks after a strong first round.

Market and risk context

Three questions that prevent a shortlist built against stale information:

• "Has this role been open before? What happened?"
• "What are competitors in this space currently offering for this profile?"
• "Has anyone internal already been considered or ruled out for this?"

That last one matters more than it looks. If an internal candidate was quietly passed over, external candidates are being compared to a real, specific bar the hiring manager has in their head but hasn't said out loud yet.

The short version

A job brief isn't a summary of what was said on the call. It's a document someone else on the team could run the search from without calling you to ask what was actually meant.

The test: hand the brief to a colleague who wasn't on the call. If they'd need to ping you before they could start sourcing, the brief isn't done, no matter how long the intake call ran.

Sonarnote records intake calls locally, without a bot joining the meeting, and turns them into structured job briefs your whole team can work from. See how it works.