Every job description you’ve ever written is a shopping list. Five years of experience. Proficiency in React. “Strong communication skills.” You know the drill. The problem isn’t that these things don’t matter — it’s that they tell the candidate nothing about the actual problem they’ll solve on day one.
A hiring brief flips the script. Instead of listing traits, it describes the situation: what’s broken, what good looks like, and what the first 90 days should produce. It’s a problem statement, not a wish list.
We made this switch at Jobsly eighteen months ago. Since then, every role we’ve filled has started with a brief. The effect on candidate quality, alignment, and close rate has been measurable. This post explains what we changed, why, and how you can do the same thing before your next hire.
Why JDs fail
Job descriptions were designed for a world where companies had all the leverage. Post the requirements, let candidates self-select, filter the pile. That world is gone. Top candidates have options, and they’re evaluating you as much as you’re evaluating them.
A JD says “we need someone who can do X.” A brief says “here’s the problem we’re solving, here’s why it’s hard, and here’s what we’ve tried.” The brief respects the candidate’s intelligence and gives them something to react to.
There’s a subtler issue too. JDs attract people who match keywords. Briefs attract people who match problems. A senior engineer reading a brief can immediately assess whether they’ve solved something like this before and whether the constraints are interesting. A JD gives them nothing to react to except checkboxes.
We analyzed our first 30 hires. The ones sourced with JDs had a 40% higher drop-off rate after the first interview. The ones sourced with briefs were three times more likely to say the role was “exactly what they expected.” Expectations matter because mismatched expectations are the leading cause of early attrition.
The anatomy of a good brief
A hiring brief has four parts: the context (why this role exists now), the problem (what’s not working), the outcome (what success looks like in 90 days), and the constraints (budget, timeline, team dynamics). No bullet points. No “nice to haves.”
When you write a brief, you’re forced to think about what actually matters. And when a candidate reads it, they can immediately tell whether this is a problem they’re excited to solve.
The context section is the most underrated. It answers the question every good candidate asks: “Why is this role open?” Is it a new function? Did someone leave? Is the company growing into a new market? The context tells the candidate what kind of situation they’re walking into. It sets expectations before day one.
The outcome section is where most founders struggle. “Own the backend” isn’t an outcome. “Reduce API latency below 200ms and migrate the monolith to three services” is. Specificity is kindness. It tells the candidate exactly what they’ll be measured on.
Common mistakes when writing briefs
The most common mistake is writing a JD in disguise. You swap the format but keep the same content: a list of skills with some context sprinkled on top. A real brief should read like a memo, not a checklist. It should tell a story.
Another mistake is being too aspirational. If you describe the role as more senior than it is, or the problem as more interesting than it is, you’ll attract candidates who are overqualified or who disengage when they see the reality. Honesty in the brief is what creates trust in the process.
The third mistake is writing the brief alone. The best briefs come from a conversation between the hiring manager, a team member who’ll work closely with the new hire, and someone outside the team who can pressure-test assumptions. Three perspectives, one page.
How to make the switch
Start with your next hire. Write the brief before you write the JD. Share it with your team and ask: “Does this accurately describe what we need?” If the answer is no, you’ve just saved yourself a bad hire.
At Jobsly, every role starts with a brief. Rob uses it to understand the real requirements, not the stated ones. The result: better candidates, faster closes, and fewer mis-hires.
You don’t need to abandon JDs entirely. Some job boards still require them. But let the brief drive the process. Use the JD as a simplified public version of the brief. Internally, the brief is the source of truth.
What we’ve seen since switching
Since we moved to briefs, our average time-to-fill has dropped by 30%. Candidate NPS scores on the interview process went from 62 to 84. And our 90-day retention is at 96% — up from 78% when we used traditional JDs.
The numbers tell part of the story. The more interesting signal is qualitative: candidates come into interviews having already thought about the problem. They ask better questions. They challenge our assumptions. The brief gives them permission to show up as a peer, not a supplicant.
We’re not claiming this is a silver bullet. Hiring is still hard. But the brief is a better starting point than the JD. It aligns the team, attracts the right people, and sets the stage for an honest conversation. That’s worth the extra thirty minutes it takes to write.