Mandatory vs. desirable requirements: how to really read a job

A job description looks like a simple list, but it is a document full of levels of importance that most people read as if every item weighed the same. That is where much of the application anxiety comes from: you look at a list of twenty points, find three you do not have, and give up, without noticing that maybe those three were the least important ones.

Really reading a job means separating the requirements by weight before comparing them to your profile. This guide shows how to identify what is mandatory, what is desirable, and what is just noise, and how to use that separation to decide better.

Why the separation matters

The difference between a mandatory and a desirable requirement is not a vocabulary detail, it is what decides whether you have a shot at the job.

Missing a central mandatory requirement usually rules the application out at screening. Missing three desirables rarely changes anything. If you treat both types as equal, you make wrong decisions in both directions: you give up on jobs where you would have a shot and apply to jobs where you lack the minimum base.

Separating before deciding is what turns an anxious read ("things are missing, better not") into a rational one ("desirables are missing, but I have the mandatory ones, so it is worth it").

How to spot a mandatory requirement

Mandatory requirements come with requirement language. Look for markers like:

• "Must have", "required", "essential", "requirement".
• "You need", "we expect you to have".
• Formal, non-negotiable requirements, like a certification required by law or a language the entire role will be conducted in.

Also mandatory, in practice, are the requirements that define the essence of the role, even without the word "mandatory". A backend developer job that does not explicitly mention "programming" still requires programming. Use judgment: what, if missing, would make it impossible to do the work?

How to spot a desirable requirement

Desirables show up with preference language, not requirement language:

• "Desirable", "a plus", "nice to have", "bonus".
• "We value", "counts in your favor", "we would like".
• "Nice to have" lists clearly separated from the main requirements.

These items help rank similar candidates, but rarely eliminate anyone on their own. If you meet the mandatory ones and a desirable is missing, you are still a viable candidate, just not the dream candidate, who almost never shows up.

How to recognize the noise

Much of a job description is not a requirement at all, and treating it as one only adds anxiety for nothing. It is noise, in the sense that it does not change your eligibility:

• Descriptions of company culture, mission, and values.
• Legal notices, equal opportunity policies, and instructions for recruiting agencies.
• Generic adjectives like "proactive", "dynamic", and "passionate", which cannot be proven in a profile.

It is not that culture does not matter, it matters for fit. But it is not a requirement you meet or fail to meet at screening, so it should not weigh on your decision to apply.

Watch out for the misleading "employment type" field

A technical detail that confuses many people: the structured fields LinkedIn shows about a job, like employment type or work model, are not always reliable. The source of truth is the description text.

If the arrangement, the hours, or the work model matter to you, look for the evidence in the body of the description, not just in the label at the top. Jobs show up labeled one way and described another more often than you would think.

From reading to deciding

After separating mandatory, desirable, and noise, the comparison with your profile gets much simpler. You look only at the mandatory ones and ask: do I prove these? If yes, the missing desirables are details and it is worth applying. If central mandatory ones are missing, then the conversation changes.

That is the read that separates people who decide clearly from people who decide in the panic of the first requirement they do not have.

A structured read of the job in seconds

Doing this separation by hand takes time and some practice, and descriptions often come with concatenated items, broken lists, and requirements mixed with boilerplate. Linkediza automates this read: you paste the job URL and your profile URL, and the analysis extracts the requirements already classified by priority (mandatory, desirable, or inferred), each with the literal snippet from the job that produced it, and cross-checks them against the evidence in your profile. You get the structured read ready, without having to decode the description on your own.

Frequently asked questions

How do I know if a requirement is mandatory when the job does not use the word?

Use judgment about the essence of the role: what, if missing, would make it impossible to do the work? Programming in a developer job is mandatory even without the word 'mandatory'. When the requirement is only contextual or shows up as a preference, treat it as desirable.

Are years-of-experience requirements mandatory or desirable?

They tend to be a reference, not a hard barrier. '5+ years of experience' signals the expected level, but relevant, proven experience usually weighs more than the exact number of years. It is worth applying if you cover the substance of the role, even with slightly less time.

Should I trust the employment type shown at the top of the job?

Not always. LinkedIn's structured fields about arrangement and work model are inconsistent. The reliable source is the description text. If the work model matters to you, look for the evidence in the body of the job before assuming anything from the label.

Do culture and values count as a requirement?

They count for fit, not for eligibility screening. You do not objectively meet or fail 'being proactive' in an application. Focus on concrete competence and experience requirements to decide whether to apply, and leave culture for the interview conversation.