Should you apply if you don't meet every requirement?

Short answerUsually yes, if you meet the core of the job. Apply when you show the skills the role is built around and most of the required items, even with gaps in preferred ones. Skip it when you are missing a core skill or a hard requirement such as work authorisation, a licence or a clearance; those are the gaps that get applications rejected.

Job postings are wish lists. They are often written by combining a previous posting, a manager's ideal candidate and a template, and few people hired for the role met every line of it. That does not mean every gap is harmless. Some gaps end an application in seconds; others are never checked. The skill is telling them apart.

The "60%" advice, and what it gets right

You may have heard that men apply when they meet about 60% of a posting's qualifications and women only when they meet all of them. The figure is widely quoted from an internal Hewlett-Packard report that has never been published, so treat the number with caution.

The more useful finding came from Tara Mohr's follow-up survey, published in Harvard Business Review in 2014. The most common reason people gave for not applying was not doubting they could do the job. It was believing they would not be hired without meeting every qualification. In other words, people were treating the list as a strict filter when hiring teams often do not.

So the advice is right in spirit: a missing line is not automatically a rejection. But a percentage is the wrong test. Which lines you miss matters far more than how many.

Three kinds of requirement

Sort the posting's list into three groups before you decide.

Hard requirements

These are pass or fail, and they are often checked by a screening question rather than a person:

legal right to work in the country, or the need for visa sponsorship;
a licence, certification or security clearance the role legally needs;
location or on-site attendance, when the posting says it is not negotiable;
a degree, when it is a regulatory requirement rather than a preference.

If you do not meet one of these, applying rarely helps. If you are close (a certification you are sitting next month), say so in the application.

Core skills

Every role is built around a few things: the main language and framework for an engineer, the specific type of accounting for an accountant, the sales motion for a sales role. Postings usually make them obvious: they appear in the title, the first lines, and more than once.

Missing a core skill is the gap that matters most. A backend role in Java is a hard sell with no Java, however good the rest of your profile is. Related experience helps (another JVM language, a similar framework), but it is related, not the same, and you should expect to be asked about it.

Everything else

Preferred and nice-to-have items, secondary tools, and soft skills. These are where the "you don't need all of them" advice applies. Missing several of these is normal.

Years of experience

A stated range ("3 to 5 years") is a guide to the level, not a hard filter. Being a year short with strong, relevant experience is often fine; being five years short usually means the role is a level above you. Being far over the range can also count against you, because the team may expect you to want a more senior role or salary.

A quick test

Apply if all of these are true:

You meet every hard requirement, or can show you will before you start.
Your profile shows the core skills, with real work or projects, not just a skills list.
You meet most of the other required items.

Then spend your effort on the application: tailor the resume to show the core skills first, and if there is a gap you can explain, explain it briefly.

If the first two are not true, the job is probably not a good use of an hour, however good it looks.

If you have applied widely and heard nothing, fit is the first thing to check; our checklist for getting no interviews covers the others.

How Shortlist helps

Shortlist does this sorting for every posting you open. It lists the requirements, marks which are required, preferred or core, checks each against your profile and shows the line that supports it. A missing core skill or required item caps the score, so a job that looks like a match on the title but fails on the essentials does not score as one. The full method is public.

FAQ

Is it bad to apply for jobs I'm underqualified for?

Not if you meet the core of the role. Recruiters see many applications that meet most of a posting; missing a few preferred items is normal. Applying to roles where you miss the core skills mostly adds rejections.

Should I mention missing requirements in my application?

Only when it helps: a certification in progress, or related experience that covers the gap ("five years of Kotlin on the JVM" for a Java role). Do not list what you lack; show what you have.

Do applicant tracking systems reject you for missing keywords?

Rarely on their own. Most automatic rejections come from screening questions, such as work authorisation or location. Keywords matter more for whether a recruiter finds and shortlists you. See how applicant tracking systems rank resumes.

What if I meet every requirement?

Apply, and make it obvious. Put the core skills first in your resume and use the posting's own terms for them, so neither a recruiter nor a search misses the match.