Key Takeaways

  • Required and preferred are different, and treating them as one list is the most common reading error.
  • Repetition marks priority. A requirement stated three times matters more than one mentioned once.
  • The first three bullets carry the most weight, because postings are written in descending order of importance.
  • The language is the specification. Screening matches their words, not your synonyms for them.
  • Ten minutes of proper reading changes the whole application more than an hour of rewriting does.

The structure of a posting

What each part is actually telling you.

The title sets the band. It maps to an internal salary range and seniority level, and it is the single most reliable indicator in the document.

The opening paragraph is usually marketing and can be read quickly, though it occasionally names the actual problem the team is solving.

The responsibilities section describes the work, and it is written by someone closer to the role than the requirements section usually is.

The requirements section is the screen. This is what gets filtered on, and it deserves the most careful reading of anything in the document.

The preferred or nice to have section is negotiable, and candidates routinely disqualify themselves by treating it as mandatory.

The benefits and culture section tells you about the employer rather than the role, and it is worth reading for what it omits as much as what it includes.

And the application questions, where they exist, frequently contain the real requirements, because they are written to filter rather than to attract.

Required versus preferred

The distinction that changes who applies.

Wording What it means How to treat it
Must have, required, essential Genuine filter Address directly or reconsider
Preferred, desirable, nice to have Tie-breaker Include if you have it, ignore if not
Bonus, a plus, advantageous Weakest signal Never disqualify yourself over this
Proven track record of Wants evidence, not years Show a concrete result
Familiarity with Exposure is enough Do not overclaim depth
Expert, deep, extensive Genuine depth expected Be honest with yourself

The verbs matter as much as the nouns. Familiarity with a tool and expertise in it are different requirements, and matching the wrong one either undersells you or gets exposed at interview.

Years of experience are softer than they appear in most private sector postings, and a strong candidate one or two years under a stated figure is routinely considered. In public sector and regulated hiring the same number is frequently a hard gate.

And the required list is often aspirational. Many postings describe an ideal candidate who does not exist, which is precisely why roles get reposted with reduced requirements.

Extracting the vocabulary

The mechanical step that does most of the work.

Pull the nouns first. Tools, systems, methodologies, deliverables and domain terms are the concrete items a screen can match on, and they belong in your resume in the employer's exact form.

Then the verbs. Whether the posting says built, managed, owned, supported or led tells you what kind of contribution they expect, and mirroring that verb in your bullets aligns the framing immediately.

Note the acronym and the expansion. Postings vary in which they use, and including both once each covers either form without looking repetitive.

Preserve their spelling and casing for named technologies, because a mismatch between your version and theirs can genuinely cost a match.

Distinguish the domain terms from the generic ones. Everyone writes communication skills; far fewer write the specific process or regulation your industry uses, and those specific terms carry far more weight.

Count the repeats. Anything appearing three or more times across the posting is central, and if it is missing from your resume that is the first gap to close.

And write the list down separately rather than working from memory, because tailoring from a written extraction is faster and considerably more accurate than tailoring from an impression.

Deciding whether you qualify

Turning the reading into a decision.

Count only the required items and ignore the preferred list entirely for this calculation.

Meeting most of the required list is enough to apply in ordinary private sector hiring, and waiting for a complete match means applying to almost nothing.

A missing item you can evidence adjacently is usually not a real gap. Experience with a comparable tool, a related regulation or the same problem in a different context frequently satisfies the underlying need.

A missing item that is the core of the role is a genuine gap, and applying anyway is a low-probability use of your time unless something else is exceptional.

Hard credentials are different. A required licence, registration, clearance or degree is usually absolute, and no amount of adjacent experience substitutes for it.

And the honest assessment protects you. Applying to roles you cannot do wastes the effort that would have gone into roles you can, which is the real cost of a scattergun approach.

Mini checklist

  • unchecked: Title mapped to a seniority level you recognise
  • unchecked: Required and preferred separated into two lists
  • unchecked: Repeated terms identified across all sections
  • unchecked: First three responsibilities noted as priorities
  • unchecked: Exact vocabulary extracted, not paraphrased
  • unchecked: Application questions read before starting
  • unchecked: Salary band noted where present
  • unchecked: Genuine gaps identified honestly
  • unchecked: Your interpretation of the core role written in one sentence

Scenarios

Scenario 1: The requirements list is twenty items long

Nobody meets all twenty and the employer knows it. Identify the four or five that repeat or appear in the responsibilities as well, treat those as real, and treat the rest as a wish list.

Scenario 2: The responsibilities and requirements contradict each other

Trust the responsibilities. They are usually written by the hiring manager and describe the actual work, while requirements are frequently assembled by HR from a template.

Scenario 3: The posting is mostly culture and benefits

Read what little describes the work very closely, then research the company to fill the gap. A posting this thin usually means the description was not written by anyone who does the job.

Tip: Read the posting once for comprehension, then a second time with a highlighter looking only for repeated nouns and verbs. The words that appear in both the responsibilities and the requirements are the ones the screen is built on, and they belong in your resume verbatim.

Do's and Don'ts

Do

  • Separate required from preferred explicitly
  • Note which terms repeat across sections
  • Use their exact vocabulary in your resume
  • Weight the first three bullets most heavily
  • Read the application questions early
  • Apply when you meet most required items

Don't

  • Treat preferred items as mandatory
  • Paraphrase their terminology into your own
  • Skim the requirements section
  • Assume years of experience are absolute
  • Ignore contradictions between sections
  • Tailor before you have read it twice

Common Mistakes

  • Conflating required and preferred. It stops qualified people applying.
  • Paraphrasing their language. Screening matches words, not meaning.
  • Skimming to save time. This is the highest-value ten minutes available.
  • Weighting all bullets equally. Order signals priority.
  • Missing repeated terms. Repetition is the clearest priority marker there is.
  • Ignoring the application questions. They are frequently the real filter.

Keep building on this with the related guides in this series:

You can also check your resume's ATS score for free, generate a tailored cover letter, or build a portfolio website in minutes.

Frequently Asked Questions

What is the most common mistake reading a job description?

Treating preferred requirements as mandatory. It causes qualified candidates to disqualify themselves from roles they would have been competitive for.

How do I know which requirements are real?

Look for repetition. A skill named in the title, the responsibilities and the requirements is genuinely central; one mentioned once at the bottom of a long list usually is not.

Do years of experience matter exactly?

In most private sector hiring, no. A strong candidate slightly under the stated figure is routinely considered. In public sector and regulated roles the number is far more often a hard gate.

Should I use their exact words?

Yes. Screening systems and busy human readers both match on specific terms, and paraphrasing into your own vocabulary loses the match even when the meaning is identical.

What if requirements and responsibilities disagree?

Trust the responsibilities. They are usually written by the hiring manager and reflect the actual work, while requirements are often assembled from a template.

How long should reading a posting take?

About ten minutes across two passes. It is the highest-return time in the entire application, and it is the step most people skip when rushing.

How do I extract keywords from a job description?

Pull the concrete nouns and the action verbs separately, preserve the employer's exact spelling and casing, include both acronym and expansion once, and note anything repeated three or more times as central.

How many requirements do I need to meet?

Count only the required items, not the preferred ones. Meeting most of them is enough in ordinary private sector hiring, though licences, clearances and required degrees are usually absolute.

Free · No account needed

What is your resume scoring right now?

Scan it against a job description and get your ATS match score in about a minute.

Drop your resume here or choose a file

PDF only. Max 2 MB.

We never share your data or use it to train AI models.

TailorCV ATS scorecard showing an overall score with per-section checks passed and failed
What you get back: an overall score plus every check that passed or failed, section by section.

Was this guide useful?

Be the first to rate it.