What "Must-Have" and "Nice-to-Have" Really Mean in Job Descriptions

Key takeaways

• The "Required" and "Preferred" headings are unreliable; sort every line yourself with two questions: can the process proceed without it? and does it describe the weekly work?
• Gatekeepers block the application; core sets the fit; decoration never changes a verdict.
• Read the responsibilities section first — it is the honest half of any posting.

Every posting sorts its requirements for you. "Required." "Preferred." "Bonus points." "What you'll bring."

The sorting is unreliable, and experienced candidates learn this the hard way in both directions: a "required" item that turned out to be negotiable, and a "nice-to-have" that turned out to be the whole job.

The reason is mundane. Postings are written by several people — a hiring manager, a recruiter, an HR template, sometimes a legal review — and each adds requirements without removing any. The headings survive; the meaning behind them does not. So the labels are a starting point, and the real classification has to come from reading the posting itself.

This guide gives you the procedure. It takes about three minutes per posting and it feeds directly into the Apply / Adapt / Skip verdict.

Three classes, two questions

The 60%-of-the-requirements rule rests on this classification, so it is worth being precise.

Gatekeepers are requirements the process cannot proceed without. Not "the manager would prefer" — cannot proceed. A professional license the role legally needs. A security clearance. Work authorization. A location when the job is genuinely on-site. A hard experience floor tied to a grading scale. The specific system when the role is that system.

Core requirements describe the substance of the job — the three to five things that fill the person's weeks. They are what the interview will probe and what the first six months will test.

Decoration is everything else: adjacent tools, wish-list certifications, vague virtues, skills the manager would enjoy but does not need.

Two questions sort almost any line:

1. Can the process proceed without it? No → gatekeeper. Yes → continue.
2. Does it describe what the person will actually do most weeks? Yes → core. No → decoration.

The procedure

Step 1 — Read the responsibilities section first, not the requirements. The responsibilities describe the job; the requirements describe the imagined candidate. The job is the more honest of the two. Underline the three to five activities that recur or carry numbers (revenue, team size, volume, deal size).

Step 2 — Cross-reference. Now read the requirements. Any requirement that maps to an underlined responsibility is core. A requirement that appears only in the requirements list, with no echo in the responsibilities, is usually decoration — often pasted from a template.

Step 3 — Isolate the gatekeepers. Run question 1 on what is left. There are rarely more than two or three. If you find six, you are misreading preferences as gates; go back.

Step 4 — Everything remaining is decoration, including most of what sits under "Required."

The phrase table

Postings leak their priorities through wording. These are the reliable tells.

Wording	Usually means	Class
"Must", "required", with a number attached to the business	The writer measured it	Core
A requirement stated twice — once in responsibilities, once in requirements	The writer cares	Core
"X+ years" with no range	A floor, often HR-imposed	Gatekeeper if tied to a grade; otherwise soft core
"5–8 years"	The lower bound is real; the upper is aspiration	Soft core
"or equivalent experience"	The degree is negotiable	Decoration
"or similar", "or related field"	Point already conceded	Decoration
"Familiarity with", "exposure to", "working knowledge of"	Not needed on day one	Decoration
"Preferred", "a plus", "bonus", "ideally"	Explicitly optional	Decoration
"Strong communicator", "self-starter", "comfortable with ambiguity"	Filler no one screens on	Decoration
A named licence, clearance, or authorization	Legal or contractual	Gatekeeper
A named system when the title contains that system	The role is the tool	Gatekeeper

The special cases

Years of experience. The most misread line in any posting. "10+ years" is a gatekeeper only when it is tied to an internal grade or a client contract; otherwise it is a proxy for scope, and scope is what the screener actually checks. A candidate with eight years who has run the scale the posting describes usually clears it; a candidate with twelve years who has not usually does not. See Overqualified or under? How to score yourself before applying for the scope question.

Degrees. "Bachelor's degree in a related field or equivalent experience" is decoration — the writer said so. "MBA required" in a posting that mentions it nowhere else is usually decoration too. A degree becomes a gatekeeper when it is a legal condition of practice (medicine, law, some engineering) or a client-imposed condition.

Certifications. A certification is a gatekeeper when the work cannot legally or contractually be done without it (a PMP on a government contract that mandates it, a licence to advise). It is decoration when it appears in a "preferred" list, and it is soft core when the posting describes work that the certification exists to certify.

Tools. The rule is the title test: if the title contains the tool ("Salesforce Administrator", "SAP FICO Consultant"), the tool is a gatekeeper. If the tool sits in a list of four with "or similar", it is decoration. In between — one named tool, no "or similar", used in a described responsibility — treat it as core, and expect to be asked about it.

What each class does to your verdict

• A missing gatekeeper is a SKIP. Nothing else in the posting can outvote it.
• Core requirements set the fit. Meet most of them at roughly the described scale and the fit is real; the verdict is then APPLY or ADAPT depending only on whether your resume shows it.
• Decoration never changes a verdict. It is not a reason to skip, and — the mistake in the other direction — meeting all of it is not a reason to apply when the core is missing.

If you find yourself hesitating over a posting because of decoration, you have misclassified it. Reread the responsibilities.

Reading the rest of the posting

Requirements are one section. The responsibilities, the reporting line, the numbers, and the posting's age each carry signals that decide the verdict as much as the requirements list does. Reading a job description like a recruiter covers the full read.

Running the sort faster

The classification above is what SmarterApply does first when it reads a posting: it separates gatekeepers from core from decoration before it compares anything to your resume, so a missing "nice-to-have" never costs you a verdict and a missing gatekeeper never wastes your hour. Paste the posting and your resume; the first analyses are free. Try it on the posting whose "required" list is giving you doubts.

FAQ

The posting says "required" for everything. What then?

Then the heading carries no information and you sort by the two questions alone. A list where everything is required is, in practice, a list where nothing has been prioritized — usually a template.

Should I ignore "preferred" qualifications entirely?

Ignore them for the decision. Once the verdict is APPLY or ADAPT, a preferred qualification you happen to have is worth one line, because it separates you from candidates with the same core fit.

What if I miss a core requirement but exceed the others?

Missing one core item out of four with the other three strongly met is usually still an ADAPT — show the adjacent experience honestly. Missing two of four is a SKIP unless you have a referral.

How do I know whether a years-of-experience line is a hard floor?

Look for a grading signal: a level in the title (Senior, Principal, Grade 7), a public-sector or regulated employer, or a salary band tied to years. Without one, treat the number as a scope proxy and judge the scope.