Should You Apply If You Don't Meet Every Requirement?

Yes, most of the time. A posting is a description of an ideal candidate written by people who already know they will not get one. The list is a wish, ordered badly, and part of it is copied from a template nobody re-read.

But "apply anyway" is not the whole answer, because a few requirements are real filters and applying through them wastes a week of your search. The useful skill is telling the two apart in the five minutes before you decide.

We can put numbers on part of this. We run an index of live job postings, so we looked at 2,013 of them across 556 companies on 9 November 2026 and counted what employers actually ask for, and how often they contradict themselves within a single ad.

What 2,013 live postings say about their own requirements

Three findings matter for this decision.

Only 32.1% state a number of years at all. Of those, the median ask is five years, with 27% asking three or less and 32% asking seven or more. Method: the smallest figure in the first "X years of experience" phrase in the posting, ignoring numbers that belong to something else. The point is not the median. The point is that two thirds of postings never name a number, so "not enough years" is often a story you told yourself.

27.6% mention a degree, and nearly half of those hedge it. 555 postings name a degree; 261 of them also say "or equivalent", "or related", or "or comparable experience". So the degree requirement, when it appears, is written to be negotiated nearly half the time.

78.5% use the word preferred, nice to have, or bonus somewhere. Most postings separate what is required from what is wanted, in their own text, if you read for it. The distinction is not secret. It is just buried under fourteen bullets.

What this does not tell you is whether a specific hiring manager will screen you out. Nobody can tell you that, including the hiring manager, because the screen happens after a human reads forty applications in an hour.

A requirement is a wish list written by three people

A job post is not a contract with a candidate. It is a document that survives an internal review, and that review leaves marks.

Someone wrote the template. Most bullets come from a company template or the last person who held the role. Nobody deleted the ones that stopped being true, because deleting a bullet is nobody's job.

The hiring manager wrote their ideal. "Kubernetes" is often a preference for the world they came from, not a condition of doing the work.

Someone in finance or HR removed the salary and added the years. Years of experience are the cheapest proxy for seniority available to a company that has not defined its levels.

The team is hiring because something is missing. Read the posting looking for the gap, not the list. A team hiring its first data engineer is not asking for a data engineer with the same profile as the one they had.

That is why the requirements overstate. It is not dishonesty, it is the normal sediment of writing a document by committee.

Sort the requirements into three piles

This takes about a minute per posting and it changes the decision.

Pile one: the verb of the job. One or two sentences describe the work: "you will own the billing pipeline", "you will run discovery calls with enterprise buyers", "you will maintain the design system". If you have done that work, you are qualified for the job regardless of the list. If you have not, no number of matching bullets fixes it.

Pile two: proxies. Years, degree, a specific tool, a specific industry. These are shortcuts to the verb. They are negotiable in the sense that a human can decide the shortcut does not apply to you, and the only way to find out is to apply.

Pile three: hard gates. A licence, a language, work authorisation, a clearance, a legal requirement, a physical requirement. These are not preferences and no amount of good writing gets around them. Skip the posting, not the requirement.

Perfection is not the bar. Pile one is the bar. Piles two and three decide whether the conversation is possible.

How to read a posting in five minutes

1. Find the verb. Read the first three paragraphs only, and write down what the person will do all day.
2. Count repeats. A requirement mentioned twice in different sections is closer to real. A requirement mentioned once, in a bullet list of fifteen, is a wish.
3. Look for the hedge. Words like preferred, plus, bonus, ideally, or equivalent mark the boundary the company drew itself. There is no reason to be stricter than the employer.
4. Check the level words against the numbers. If a posting labelled entry asks for five years, that inconsistency is information: the label is wrong, which means the list was assembled carelessly.
5. Look at the team's other postings. Three openings on the same team with the same requirements usually means one real role described three times.
6. Check the date. A posting refreshed weekly for four months is either a hard role to fill, which favours you, or a pipeline advert, which does not.

Five minutes, and you will have a better read than the person who spent them rewriting their resume for a job they will not get.

Does the 60 percent rule hold?

The version you see online is that you should apply when you meet 60% of the requirements. The number is not a finding, it is a rule of thumb that got repeated until it looked like one. What the data above supports is weaker and more useful:

• Most postings do not state a full set of measurable requirements, so a percentage is not computable in the first place.
• Where they do state a number of years, 27% ask for three or less while 32% ask for seven or more, so the list is not the bar it looks like.
• Where they state a degree, about half accept an equivalent, so the strictest reading of the posting is often the wrong one.

Treat the percentage as a prompt to count, not as a threshold to obey. If you can do the verb of the job and you clear the hard gates, apply. If you cannot do the verb, no percentage saves the application.

What to do about the gap you do have

You will usually have one real gap. One line handles it, and a paragraph about it makes things worse.

Name it once, in the language of the work. "I have run this pipeline in Airflow rather than Dagster, and the migration took two weeks." That is a fact a hiring manager can act on.

Put the evidence next to it. The gap is only a problem if it is the whole story. One example of doing the same work with a different tool beats an assurance that you learn fast.

Do not apologise in the cover letter's first line. The reader has not decided anything yet. Leading with what you lack tells them what to look for.

Use the interview for the rest. Questions about how you would ramp on the missing piece are a better use of the time than a paragraph claiming you already have it.

If the posting is parsed by an applicant tracking system before a human sees it, the tool matters more than the wording: the ATS guide covers what actually gets extracted, and tailoring a resume to one posting covers the fifteen minutes that are worth spending.

When to skip it

Applying widely is the right default, but four situations make it a waste.

• A hard gate you cannot clear. Licence, clearance, language, work authorisation. Nothing in your control changes the outcome.
• A seniority cliff. A staff role asking for eight years of leading a function, when you have two years of doing it well. The gap is not the years, it is the scope, and scope is what gets interviewed.
• A five-year requirement on a technology that is two years old. This is the clearest sign of a wish list. It is also, occasionally, a sign that nobody has read the posting, which means the process is not serious yet.
• A salary ceiling below your floor. Apply only if the range is unknown. If it is published and it is under, the rest of the posting is not worth parsing.

The rest of the time, the honest default is to apply. The math on how many applications to send each week makes the same argument from the other side: the cost of one wrong application is twenty minutes, and the cost of self-rejecting is every job you never saw a reply from.

The Bottom Line

You do not need to meet every requirement. You need to be able to do the work the posting describes, and to clear the handful of requirements that are legal or licenced rather than preferred. Most of what sits between those two is a proxy somebody copied, and the person reading your application knows it.

Read the verb, find the hedges, check the hard gates, then apply. If nothing comes back, the problem is rarely the requirements you did not meet. It is usually the application itself, which is a different guide: why a good resume gets no interviews.