Must-Have vs Nice-to-Have Requirements in 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.

We build Talent Summoner, which turns a role brief into a ranked shortlist with must-haves and nice-to-haves kept apart, and your first Role is free with no card. If your candidates come from referrals alone, you can use the method below without it.

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.

What makes a requirement a must-have?

A must-have is a job-related condition necessary in the approved role context. "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. Examples include transferable industry experience or familiarity with a learnable tool.

State the value and trade-off. "Payments experience is helpful because this team serves payment providers" tells reviewers more than "payments background preferred".

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.

"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.

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.

Keep unknowns as unknowns

Candidate material is incomplete. If a CV does not mention a must-have, that usually means unknown, not absent.

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.

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 merely useful, keep it as a preference and weigh the trade-off openly.

Where Talent Summoner fits

Talent Summoner covers AI candidate sourcing, CV ranking and outreach sent from your own connected Gmail, Outlook or LinkedIn after you review each message and confirm the send. Its Candidate Ranking tool, checked 3 October 2026, accepts up to 50 CVs in PDF, DOCX, MD or TXT, needs no account and creates a shareable report with plain-English reasoning; it never rejects anyone automatically.

Candidate sourcing starts from a role brief, searches LinkedIn, GitHub and other public professional sources across 200M+ profiles, and returns must-haves, nice-to-haves and reasoning. Pricing, checked 3 October 2026, is US$29 for one Role, US$79 for three, US$59 per month for 10 Roles or US$299 per month for Unlimited; your first Role is free and your second is US$4, an intro price shown at checkout, not on the pricing page.

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.

Talent Summoner product facts read from our live candidate sourcing, candidate ranking and pricing pages, verified 3 October 2026. We re-verify this page quarterly — tell us if something changed.