Talent SummonerMust-Have vs Nice-to-Have Requirements in Candidate Matching
Learn how to separate must-have and nice-to-have requirements, weigh evidence, handle unknowns and keep preferences from distorting candidate matching.
Must-have and nice-to-have requirements answer different hiring questions. A must-have is a condition the person needs to meet. A nice-to-have is a useful advantage, but is not necessary to do the work. Matching becomes unreliable when preferences become requirements or outweigh genuine needs.
Define the distinction before reviewing candidates. Ask why each criterion matters, what evidence supports it, what an acceptable equivalent looks like and how to treat silence. This keeps the ranking challengeable and the decision human-owned.
What makes a requirement a must-have?
A must-have is a job-related condition necessary in the approved role context. It may involve an immediate capability, a responsibility the person must own, a genuine working constraint or a qualification. "Can own production incident response" is more useful than "senior engineer": one describes a responsibility, the other an imprecise label.
Necessity should be explainable without referring to a favoured candidate. If the team cannot state what would fail without the criterion, it may be a preference or unresolved question. Define relevant equivalents in advance: adjacent experience may satisfy the underlying need when work, scope and evidence are comparable.
What belongs in nice-to-have?
A nice-to-have is a beneficial signal, not a disguised gate. It might shorten onboarding, add context or help with a future responsibility. Examples include transferable industry experience, familiarity with a learnable tool or a second language useful to a customer group but not needed for core work.
State the value and trade-off. "Payments experience is helpful because this team serves payment providers" tells reviewers more than "payments background preferred". Specific or searchable does not mean important.
Define evidence before names
Write an evidence rule for every important criterion. Evidence might be a relevant project, owned responsibility, work sample, qualification or documented constraint. Record scope, context and ownership. "Used Kubernetes" may support exposure, but does not establish production ownership. A job title is a search signal, not proof of the work behind it.
Use the same interpretation for comparable candidates. Accepting one person's equivalent project while discounting another's different title measures familiarity, not the requirement. Keep source text separate from interpretation and mark evidence supported, adjacent, contradicted or unknown.
Weight requirements without hiding the boundary
Decide the hierarchy before ranking. A genuine must-have should remain visible as one, even when a candidate has attractive preferences. A nice-to-have can order candidates similarly supported on essentials; it should not compensate for an unproven core capability.
Weighting depends on the role and tool, so avoid universal cut-offs or treating a percentage as a hiring verdict. Inspect which criteria moved the order and whether that reflects the brief. If a preference becomes decisive, record who approved it, why the work requires it and whether the rule applies to everyone. Re-run after a documented change rather than editing an explanation after seeing a name.
Keep unknowns as unknowns
Candidate material is incomplete. If a CV does not mention a must-have, that usually means unknown, not absent. Ask whether the source had a fair opportunity to provide the information and whether the gap can be checked consistently. Missing scope or ownership should produce a focused verification question.
Unknown is different from supported, but does not justify automatic rejection. For each material gap, define the next action and answer that could change the status. Offer comparable candidates the same question or work sample. If evidence contradicts a requirement, check dates and context; preserve the distinction between contradiction and silence.
When can a preference become required?
A preference can become required when approved role conditions change or the team shows that the underlying need is material. For example, a licence may become necessary for a defined responsibility, or a schedule constraint may become real when coverage cannot otherwise be provided. State the change in job-related terms, approve it and apply it consistently.
Do not promote a preference because a favoured candidate has it, it shrinks the shortlist or it is convenient to filter. Revisit equivalents, training time and the work dependency. If necessary, update the brief before further matching and explain the evidence standard. If merely useful, keep it as a preference and weigh the trade-off openly.
Where Talent Summoner fits
Talent Summoner is our product. Its Candidate Ranking tool, checked 19 August 2026, accepts up to 50 CVs in PDF, DOCX, MD or TXT format, requires no account and creates a shareable report with plain-English reasoning. Use it to inspect how requirements relate to the shortlist; it does not make the decision or automatically reject candidates.
For a new search, candidate sourcing starts with a role brief and searches LinkedIn, GitHub and other public professional sources across 200M+ profiles. It returns must-haves, nice-to-haves and reasoning. Pricing, checked the same date, lists US$39 for one Role, US$99 for three Roles or US$79 per month for four Roles. Review evidence and unknowns before contacting anyone.
FAQ
How many must-haves should a role have?
There is no universal number. Limit the list to genuinely necessary conditions, define evidence and check whether any item is only a preference. A defensible list is easier to apply consistently.
Can a nice-to-have outweigh a must-have?
Not when the must-have is genuinely necessary and unsupported. Preferences can order candidates similarly supported on essentials, but should not substitute for core evidence.
Is a missing requirement proof that a candidate lacks it?
Usually no. Treat silence as unknown and use a consistent verification question or assessment. Record absence only when a reliable source establishes it.
Should a ranking automatically reject someone who misses a must-have?
No. People should check evidence, acceptable equivalents and context before deciding. Keep disposition human-owned.
Choose one open role and create a two-column brief: must-haves with evidence rules, and nice-to-haves with intended value. Run the same candidate set through the Candidate Ranking tool, inspect a top and surprising result, then record each unknown and next step.
Related: How to Spot a Weak AI Shortlist Before Contacting Anyone · How to Read Evidence Behind a Candidate Match · How to Evaluate an AI-Ranked Candidate Shortlist
Talent Summoner product facts read from our live candidate sourcing, candidate ranking and pricing pages, verified 19 August 2026. We re-verify this page quarterly — tell us if something changed.
