Must-have vs nice-to-have: how to stop over-speccing roles

Pull up any job that's been open more than two months and count the requirements on the brief. It's almost always past ten. Somewhere in that list is the reason nobody's moving forward, buried between three things that actually matter and the rest, which just sounded reasonable to write down back in intake.

Over-speccing isn't a market problem. It's an intake problem, and it gets created in the same call where it could be fixed.

Where the extra requirements come from

Most bloated briefs trace back to the same handful of habits.

The job description gets copied from the last time the role was open, or from a competitor's posting, and only the title changes. Every outdated assumption comes along for free.

The last good hire becomes the template. "Someone like Sarah" turns into a checklist describing Sarah specifically, including the parts that had nothing to do with why she was good at the job.

A past bad hire gets overcorrected into a new rule. Someone struggled with ambiguity, so the next brief says "5+ years in a fast-paced environment," which screens for tenure instead of the actual missing trait.

And nobody owns cutting the list down. Hiring managers write requirements optimistically because more detail feels like more thought. Recruiters don't push back on the first intake call because it feels combative. The list ships as written and becomes the filter for the next two months of screening.

A better test than "need vs want"

"Need versus want" is too easy to argue around, almost anything can become a need if you frame it right. A sharper question during intake: would this one requirement, on its own, disqualify someone who's excellent everywhere else?

Ask it out loud, line by line, in front of the hiring manager. Not as a monologue prompt, force an actual answer on each item: "If someone nailed everything else but didn't have this, are we saying no?"

The hesitation tells you everything. A flat "yes, dealbreaker" is a real must-have. A pause followed by "well, ideally" means it's a preference that got dressed up as a requirement because it read well in a bullet list.

Two follow-ups cut through the rest fast. Ask who's done this job well without that requirement, if that person exists, it isn't load-bearing. And ask what actually breaks if it's missing, a slower ramp or a wrong hire. Slower ramp is trainable. Wrong hire is a must-have.

What this looks like on a real brief

A sales role came in with eleven requirements, everything from a specific CRM to a bachelor's degree to bilingual Spanish. After running the test with the hiring manager, three survived: quota history at the role's target, willingness to be in-office for client visits, and comfort with cold outbound, since the role was mostly new logo work. The CRM requirement dropped once we admitted anyone with comparable tool experience ramps in under two weeks. The degree and the language requirement had never actually predicted anything, they were just on the list because they sounded like good filters.

A data role did the same thing in reverse. Nine requirements down to two once the hiring manager realized the team's actual daily work was SQL-heavy, not Python-heavy, and the warehouse platform listed was an assumption nobody had tested against real candidates.

Why the short list works better

A three-to-five item list gives a recruiter a real filter instead of a vibe check, and it stops rejecting strong candidates over things that were never actually dealbreakers. The nice-to-have list doesn't go away, it just moves to a smaller job: breaking a tie between two finalists who both already clear the bar. That's a much better use for it than gatekeeping the whole funnel.

The short version

Run every line on the brief through one question during intake: would this alone disqualify someone excellent? Hesitation means nice-to-have, no matter how firm it sounded on paper. Most roles land at three to five real must-haves. If the brief has more than that, it's probably inherited from an old posting, modeled on one past hire, or an overcorrection from someone who didn't work out for a different reason entirely. Worth finding out which before the search opens, not eight weeks in.

Sonarnote records intake calls locally, without a bot joining the meeting, and turns them into structured job briefs. Running this test live on the call means it's documented at the source instead of reconstructed from memory later. See how it works.