Which US Job Requirements Are Must-Have vs Nice-to-Have

12 min read

You've read the posting three times and still can't tell which lines actually gate the screen. That's normal. US job requirements are written for compliance and search, not for your sanity. The skill isn't memorizing every bullet. It's sorting must-have vs nice-to-have before you spend an hour rewriting a resume for a role you'd never clear.

Check your resume for free against the same posting once you've tagged the gates. If your file shows the preferred tool in Skills but never names the required license in a dated bullet, you're optimizing the wrong line. Recruiters in Workday and Greenhouse filter on gates first. Nice-to-haves rarely save a missing must-have.

Below is a five-step procedure: read the req like a screener, rank the top three gates, map proof, park preferences honestly, and verify before upload. You'll also see before/after pairs, two edge cases, and the mistakes that make strong candidates look like they never read the posting.

This won't turn a missing CPA into a pass for a controller role. It will stop you from skipping roles you could win because you treated a bonus line as a hard stop, or from wasting nights tailoring to tools that never controlled the screen.

How US job requirements are actually written

Postings mix legal language, hiring-manager wish lists, and keyword soup for the ATS import. The section headers matter more than tone. Required, Minimum qualifications, and Must have usually gate the screen. Preferred, Nice to have, Bonus, and Plus often do not.

The bar your resume must clear: every must-have appears in a dated Experience bullet with scope you can defend in a five-minute screen. Nice-to-haves earn a mention only when proof exists. A Skills footer full of preferred tools does not replace a missing gate on bullet one.

Order signals weight. The first three bullets under qualifications are what I ctrl-f before I forward a file. A tool named once at the bottom after twelve other lines is usually a hiring-manager preference, not a filter the recruiter set in Greenhouse.

Repetition upgrades weight. If Kubernetes appears in the summary, bullet two of qualifications, and the screening questionnaire, treat it as a gate even when the word required never appears. If GraphQL shows up once under Preferred, it's a tiebreaker for finalists, not a reason to skip applying.

Licenses and clearances are almost always gates. Active RN license, CPA, Series 7, TS/SCI, bar admission in state X: these lines are written for compliance. Do not reinterpret them as nice-to-have because the rest of the posting sounds friendly.

Read how to tailor a resume to a job description after you sort the list. Tailoring without sorting wastes time on preferences while gates stay missing.

If the portal asks for a short note, generate a cover letter that names one must-have you clear and one nice-to-have you're building. Honest beats overstated every time.

Five steps to sort US job requirements: must-have vs nice-to-have

Work these in order on every posting you're serious about. Examples use composite roles. Swap in your stack, license, and years.

Step 1: Tag gate language in the posting

Print or paste the req into a doc. Highlight every line under Required, Minimum, Must have, or equivalent in green. Highlight Preferred, Nice to have, Bonus, and Plus in yellow. Unlabeled bullets get a third pass: if it mentions license, clearance, or minimum years, mark green.

Before: I'll read the whole posting tonight and rewrite everything to match.
After: Green: active CPA, 5+ years GL close, NetSuite admin. Yellow: Tableau, prior SaaS. I'll mirror green lines in bullets one and two before I touch yellow.

Step 2: Rank the top three gates

From your green list, pick the three lines that would make you stop the screen if they were missing. Usually that's years in the core function, a license or cert, and the primary system or domain. Write them at the top of a one-page worksheet.

For a mid-level data analyst req, the top three might be: 4+ years SQL in production, dbt or equivalent transform layer, and stakeholder-facing dashboards. A fourth line about Python is often preferred unless it repeats in the summary.

Step 3: Map each must-have to a dated bullet

Open your resume. For each green gate, find the employer block where you used it. Rewrite bullet one or two to include the posting phrase, the system, and one outcome. If you cannot find a home, you have a gap decision to make: apply with an honest note, or skip and save the evening.

Before: Skills: NetSuite, CPA, month-end close, Tableau.
After: Owned month-end close for three entities in NetSuite, reconciled 120+ balance sheet accounts, and cut close cycle from 9 days to 6 days across FY2024.

Edge case: you meet the years gate in a adjacent title. Name the function in the bullet, not just the employer brand. A composite marketing ops lead who ran Salesforce campaigns for four years should say campaign operations and CRM admin in bullet one, not only Marketing Coordinator on the header.

Step 4: Place nice-to-haves only with proof

Walk your yellow list. For each line, ask whether you have a project, employer month, or cert lab that supports it. If yes, add bullet three or a short Projects subline. If no, leave it off. Do not move a yellow line into Skills to feel competitive.

Before: Preferred: Kubernetes, GraphQL, Terraform. (All three added to Skills with no dates.)
After: Bullet three: Containerized two internal APIs on Kubernetes in a staging environment for a platform migration pilot, documented runbooks for the DevOps team, Q2 2025. (GraphQL and Terraform omitted.)

Edge case: you're building a nice-to-have in a current role. Say pilot or limited production scope with a month. Recruiters accept honest growth on preferred lines. They reject senior claims on required lines.

Step 5: Verify gates before upload

Paste the posting and your plain-text export into a checker. Confirm each green gate registers in Experience, not only in Skills. Read the file aloud once. If you stumble explaining a must-have, the bullet needs scope, not another keyword.

I've passed on files that listed every preferred tool but never showed the required license in a dated line. The opposite also happens: candidates skip applying because they lack a yellow-line tool while clearing every green gate in the interview stories they tell friends.

Copy-paste worksheet block

Copy this into a doc beside the posting:

Role: [title] · Req ID: [if shown]

Must-have 1: [gate] → Resume bullet: [employer, month year, proof line]
Must-have 2: [gate] → Resume bullet: [employer, month year, proof line]
Must-have 3: [gate] → Resume bullet: [employer, month year, proof line]

Nice-to-have (proof?): [tool] → [yes: bullet three / no: omit]
Hard stop missing?: [yes/no] → [apply anyway with note / skip]

Recruiter question if unsure: Which of these are hard filters in your Greenhouse req?

Pair the worksheet with resume rejected by ATS if the file parses but still disappears. Format can hide gates even when you sorted them correctly.

Where applicants misread US job requirements

Treating every bullet as equal weight. You rewrite for a preferred tool while the required license never appears in Experience. The screen stops before a human admires your formatting.

Self-rejecting on yellow lines. Missing GraphQL when you clear SQL, years, and dashboard delivery is not the same as missing an active license. Apply when gates are green. Address preferences honestly in a note or bullet three.

Stuffing Skills to match the whole posting. Parsers may light up. Recruiters ctrl-f inside employer blocks. A twenty-item Skills row without dated proof reads like keyword spray.

Ignoring repetition. A tool named once at the bottom is often preference. The same tool in the summary and bullet two is a gate. Read frequency, not only headers.

Overstating nice-to-haves as must-haves on the resume. Claiming expert Terraform when you ran one pilot is worse than omitting it. Preferred lines forgive gaps. Required lines do not forgive inflation.

Skipping the recruiter question. When headers are vague, a thirty-second email saves a wasted rewrite. Ask which gaps are hard stops. Good recruiters answer.

Using the same sorted list for every similar title. Two analyst reqs from the same company can gate on different stacks. Sort each posting fresh. Do not recycle last week's green/yellow map.

Confirm gates on the file before you apply

Sorting the req is step one. Proof on the PDF is step two. Paste the posting into the free ATS checker and confirm each must-have registers under an employer header with dates. A gate that only appears in Skills is still a risk when a recruiter screens in Workday.

Then score your job match on the same file. Low fit after format fixes usually means a true gate gap, not a bad luck day. Fix the bullet or pick a closer req before you spend political capital on a referral.

Save the checker output next to your green/yellow worksheet. When a recruiter asks about a gap, you'll know whether it's a hard stop or a preferred line you can address in one sentence.

Sort the req tonight

Which US job requirements are must-have vs nice-to-have is a sorting job, not a memorization job. Tag gate language, rank the top three, map proof, park preferences honestly, and verify on the file before upload.

Pick one posting on your list. Run the five steps and the copy-paste worksheet. If every green line has a dated bullet, apply. If a true gate is missing, skip without guilt or ask the recruiter before you self-reject on a yellow line.

You don't need to match the entire wish list. You need to make the gates obvious in Experience so the human screen takes less than five minutes. That's the difference between a file that forwards and one that dies in keyword spray.