Blog › Job search

How to read a job description: must-haves, nice-to-haves, red flags

A five-minute method for reading a job description: separate must-haves from wish lists, spot what the role really is, and decide whether to apply.

Nov 14, 2026 · 5 min read

To read a job description well, separate what the employer must have from what they would like, work out what the job actually involves day to day, and check for the practical deal-breakers: location, level and pay. Five minutes of careful reading tells you whether to spend an hour applying. Most people skim the title and apply, which is why so many applications go nowhere.

Why postings are hard to read

A job description is rarely written by one person with a clear plan. It is assembled from an old posting, a manager's wish list and standard company text. The result often describes an ideal candidate who does not exist.

Your job is to find the real role inside it.

Step 1: read it twice

First pass, thirty seconds. Title, company, location, level. Any immediate deal-breaker? If so, stop.

Second pass, four minutes. With a pen or a highlighter. Mark three things: what they must have, what the work is, and anything odd.

Step 2: separate must-haves from nice-to-haves

Clues that something is essential:

• It is in the first three or four requirements.
• It is repeated in different sections.
• It appears in the title or the opening summary.
• The wording is firm: "required", "must", "essential".

Clues that something is optional:

• "Preferred", "a plus", "ideally", "nice to have", "familiarity with".
• It comes at the end of a long list.
• It is one of many tools named together.

A workable rule: if you meet most of the must-haves, apply. You do not need all of them, and you do not need the nice-to-haves. Do not apply where the core requirement is simply absent: a role built around a language or licence you do not have.

Step 3: find the actual job

Look at the verbs in the responsibilities. They describe the day.

A "Marketing Manager" role full of "coordinate" and "report" is a different job from one full of "write" and "launch". The title is a label. The verbs are the truth.

Notice the order too. What is listed first is usually what matters most.

Step 4: check the practical terms

• Location. Which city? "Remote" from where? Many remote roles are limited to certain countries or time zones.
• Work pattern. On-site, hybrid, remote. Days in the office.
• Level. Years of experience asked for, and who the role reports to.
• Pay. Stated or not. If it is, does it fit?
• Contract. Permanent, fixed-term, contract.
• Authorisation. Any requirement about the right to work, or clearance.

One mismatch here outweighs a perfect skills fit.

Step 5: read the signals

Good signs

• A clear, specific list of responsibilities.
• A stated salary range.
• A named team or manager.
• A description of the hiring process.
• Realistic requirements for the level.

Reasons for caution

• A very long list of unrelated requirements. Nobody has all of them. The role may be undefined.
• Senior responsibilities at a junior title or pay.
• "Wear many hats", "fast-paced", "like a family". Not always bad. Ask what they mean in practice.
• No information about the company.
• Open for many months, or re-posted often. It may be hard to fill, paused, or always open.
• "Talent pool" or "general application". Not a specific opening.

Caution is not rejection. Note the question and ask it if you get an interview.

Reasons to walk away

• Any request for payment.
• An offer with no interview.
• A contact address unrelated to the company, combined with vague details.
• Pay far above the market for little work.

See job scam red flags.

Step 6: decide

Score it quickly:

Four yeses: apply, and tailor. Three: apply if you have time. Two or fewer: move on, without guilt.

Then use what you marked

The reading is not wasted. The requirements you highlighted are exactly what your application should answer.

• Put matching experience at the top of your CV, in their words. See how to tailor your CV.
• Mention the two strongest matches in your application email.
• Save the posting's text. It will be gone when you need it for interview preparation.

Having the first read done for you

Reading every posting this carefully is the right thing to do and takes time you may not have.

Job Scout does a first read of each posting against your CV and shows the result in a consistent shape:

• A score, and one line on why.
• Sub-scores for skills, experience, and location and remote. Salary too, when both you and the posting state it.
• You match: skills the posting asks for that your CV names.
• Worth learning or mentioning: skills it asks for that your CV does not mention.
• Watch out: clashes such as a posting that limits who can be hired, an on-site or relocation demand that does not fit your locations, or a seniority gap, plus flags on old, re-posted or general talent-pool listings.

A skill is shown only when it is really in the posting and in your CV. Postings below your threshold are not hidden: they are listed with the reason, and you can still draft an application if you disagree.

Treat the score as a first read. The decision in step 6 is still yours.

Frequently asked questions

Should I apply if I do not meet all the requirements?

Yes, if you meet most of the essential ones. Requirement lists are often wish lists. Skip roles where a core requirement is missing entirely.

What does "preferred" mean in a job description?

That the employer would like it and will consider candidates without it. Treat preferred items as a bonus, not a barrier.

How can I tell what a job really involves?

Read the verbs in the responsibilities section and note their order. They describe the daily work more reliably than the title does.