Should You Apply If You Don’t Meet Every Job Requirement?

Yes, sometimes. You do not need to treat every line in a job description as equally important. But that does not mean every requirement is optional.

The better question is: What kind of requirement are you missing, and how important is it to doing or being eligible for the job?

Missing a preferred tool is very different from missing a legally required license. Being one year short of an experience target is different from having no experience with the core work. And a resume that fails to mention a skill you already use has a different problem from a resume that accurately reveals you do not have that skill.

That is why rules such as “apply if you meet 60%,” “70%,” or “80% of the requirements” are unreliable. A raw percentage counts every item as if it carries the same weight. Real hiring decisions often do not work that way.

A more useful decision is:

• Apply when you meet the core requirements and your gaps are minor, learnable, preferred, or mostly about how your experience is described.
• Stretch when one or two meaningful gaps exist, but you can still perform most of the job and can make a credible case using adjacent or transferable experience.
• Skip or close the gap first when you are missing a genuine eligibility requirement or a capability that is central to the role.

Current SHRM guidance makes a similar distinction: candidates do not necessarily need every listed qualification, but required licenses, clearances, legally mandated credentials, and truly essential capabilities can be real barriers.^[1]

Why job requirements are not an equally weighted checklist

Imagine two candidates applying to the same data analyst role.

Candidate A matches 7 of 10 listed items. They have SQL, Excel, dashboard experience, stakeholder reporting, data cleaning, basic Python, and the requested degree. They lack Tableau, have two years of experience instead of three, and have never worked in the employer's industry.

Candidate B also matches 7 of 10 items. They have Tableau, Excel, the degree, three years of experience, industry experience, communication skills, and Python. But they do not know SQL, have never built recurring reports, and have no experience analysing business data.

Both candidates match “70%.”

Their situations are not equivalent.

For this role, SQL and practical analysis may sit at the center of the job. Tableau might be replaceable with another BI tool. One missing year of experience may or may not matter. Counting requirements cannot tell you that.

Instead, classify each requirement by its role in the hiring decision. If you want the broader method first, see how to analyze a job description before you apply.

The six kinds of requirement gaps

1. Eligibility gaps

These are requirements that determine whether you are legally, operationally, or procedurally able to take the role.

Examples can include:

• a license required to practise a regulated profession,
• required work authorization,
• a mandatory security clearance or the ability to obtain one,
• a legally required credential,
• a location or shift condition that the employer treats as non-negotiable.

These deserve the most caution.

For example, nursing licensure in the United States is governed by nursing regulatory bodies, and authorization to practise depends on the relevant jurisdiction.^[2] In situations like that, “I meet most of the other requirements” does not substitute for the required authorization.

Some recruiting systems can also be configured with knockout questions. Workable, for example, allows employers to automatically disqualify applicants who answer “No” to selected yes/no application questions.^[3] That is very different from a mythical universal ATS rule that rejects everyone below a certain resume-match percentage.

Practical test: If the requirement appears to determine whether you are allowed or able to perform the role at all, verify it before applying.

2. Core capability gaps

A core capability is something the person is expected to do repeatedly in the job.

For a backend engineer, that might be building and maintaining APIs. For a data analyst, it might be querying and analysing data. For a recruiter, it might be sourcing and screening candidates. For an accountant, it might be preparing or reviewing financial records.

Missing one named tool does not always mean you are missing the capability.

A candidate who has used Power BI for years may still understand dashboards, data modelling, stakeholder reporting, filters, measures, and KPI design even if the vacancy mentions Tableau. That is a tool gap.

A candidate who has never built a dashboard at all has a deeper capability gap.

Ask:

1. What would I actually spend my week doing?
2. Can I already perform most of that work?
3. Can I point to evidence that I have done something comparable?

If your answer to the second and third questions is no, the gap matters more than the number of requirements you match elsewhere. A useful next step is to identify the skills that matter most before treating every listed skill equally.

3. Experience-depth gaps

“3+ years,” “5 years,” and similar requirements need interpretation, not automatic acceptance or rejection.

Years of experience are often used as a proxy for depth, independence, exposure, or seniority. What matters is whether your actual experience provides enough evidence for the level of responsibility.

A person with four highly relevant years may sometimes have a stronger case for a “5 years” role than someone with five loosely related years. SHRM's September 2026 guidance explicitly gives an example in which five highly relevant years can still justify applying to a role asking for seven, depending on the rest of the candidate's background.^[1]

That does not mean experience requirements never matter. A role expecting someone to independently lead architecture, manage major client accounts, supervise clinical work, or own complex financial decisions may require depth that cannot be replaced by enthusiasm.

Use the job responsibilities as your reality check.

When being short on years is usually a smaller concern

Consider applying when:

• your experience is directly relevant,
• you already perform many of the listed responsibilities,
• the gap is modest,
• your scope or results show the required level of independence,
• the posting does not make the experience threshold an explicit knockout condition.

When being short on years is more serious

Be cautious when:

• the job is several seniority levels above your current work,
• you have never owned the core responsibilities,
• the missing experience involves regulated or safety-critical work,
• the role requires leadership, commercial, technical, or operational judgment you have not yet had to exercise.

4. Tool-specific gaps

Tool requirements are often easier to evaluate when you ask what the tool is being used to accomplish.

Suppose a vacancy asks for:

Experience building dashboards in Tableau.

You use Power BI, not Tableau.

That does not automatically mean you are qualified, but you can examine the underlying capability:

• Have you designed dashboards?
• Do you understand metrics and data visualisation?
• Have you connected to data sources?
• Have you worked with calculated fields or equivalent logic?
• Can you learn the new interface quickly enough for this role?

Now compare that with:

Advanced Kubernetes administration in a production platform environment.

If you have never used containers in production, the gap is not merely the name of a tool. You may be missing the underlying operational capability.

This distinction prevents two common mistakes: rejecting yourself because a tool name differs, or pretending that adjacent experience is equivalent when it is not.

5. Preferred and bonus qualification gaps

Words such as preferred, desirable, nice to have, bonus, or advantageous usually signal a different level of importance from required, must have, or essential.

That wording is not perfectly standardized between employers, so read the whole description. Still, the distinction matters. SHRM's current job-description guidance recommends separating mandatory requirements from preferred skills, which reflects their different functions in a posting.^[4]

If you meet the core role and are missing only preferred items, that is often a reasonable application.

The mistake is assuming the opposite: that every item under “requirements” is automatically flexible. Some employers use screening questions specifically for must-have skills, location, experience, or qualifications.^[5]

6. Keyword or framing gaps

Sometimes the skill is present in your background but absent from your resume.

Suppose a job requires:

• stakeholder management,
• forecasting,
• Python,
• monthly KPI reporting.

You have done all four, but your resume says:

Worked with multiple teams to produce performance reports.

The underlying experience may be there, but the evidence is weak. “Worked with multiple teams” does not clearly show stakeholder management. “Performance reports” does not reveal forecasting, Python, or a recurring KPI reporting process.

That is a framing gap, not necessarily a skill gap.

Do not solve it with keyword stuffing. Solve it by making genuine experience explicit.

For example:

Automated monthly KPI reporting in Python and presented forecast variance analysis to finance and operations stakeholders.

Only write that if it is true.

Why there is no reliable “percentage of requirements” rule

Searches such as “should I apply if I meet 70% of the requirements?” are understandable because a percentage feels objective.

The problem is that the denominator is arbitrary.

A job may list:

• 4 essential requirements,
• 5 preferred skills,
• 3 tools,
• 2 broad personality traits,
• 1 legal requirement.

Matching 12 of 15 looks strong. But if the three missing items include the legal requirement and two core capabilities, the percentage is misleading.

The reverse can also happen. You might match only 9 of 15 items while satisfying every essential requirement and missing six minor preferences.

So do not ask only:

What percentage do I match?

Ask:

Which requirements do I match, which ones do I miss, and what would each gap prevent me from doing?

What about the famous “men apply at 60%, women at 100%” statistic?

Treat it cautiously.

A 2014 Harvard Business Review article popularized the 60%-versus-100% claim.^[6] It is often repeated as if it were a universal scientific threshold for applications. It is not a useful rule for deciding whether you should apply to a specific vacancy.

Even if a candidate meets 60% of listed items, that tells you little unless you know which 60%.

The useful lesson is not “60% is enough.” The useful lesson is to avoid turning a job description into a simple count of boxes.

Apply, Stretch, or Skip: a better decision framework

Use three buckets.

Apply

Apply when most of the following are true:

• you can perform the central responsibilities,
• you meet explicit eligibility requirements,
• you have evidence for the most important capabilities,
• your missing items are mostly preferred, tool-specific, or modest experience gaps,
• you can truthfully tailor your resume to make the fit clear.

Example:

A marketing analyst role asks for SQL, dashboarding, campaign analysis, stakeholder communication, and “Tableau preferred.” You have SQL, Power BI, campaign reporting, stakeholder work, and strong analytical experience.

You are missing the exact BI tool, not the analytical capability.

That is a sensible Apply case.

Stretch

Use Stretch when the role is plausible but the gap is meaningful.

Typical stretch cases:

• you are slightly below the stated experience level,
• you have adjacent rather than exact industry experience,
• you lack one important but learnable tool,
• you have performed similar work at a smaller scale,
• your evidence is strong in most of the role but weaker in one area.

A stretch application should still be credible. “Stretch” does not mean “apply to anything.”

Example:

A data engineer role asks for Python, SQL, ETL pipelines, cloud experience, orchestration, and production Spark. You have Python, SQL, Airflow, cloud storage, and production ETL experience, but only academic Spark exposure.

Whether this is worth applying to depends on how central Spark is to the actual role. If most responsibilities revolve around Spark optimization at scale, the gap is substantial. If Spark is one technology in a broader data-platform stack, the application may still be credible.

Skip or close the gap first

Skip, or deliberately close the gap before applying to similar roles, when:

• you lack a legally required license or mandatory credential,
• you cannot perform a central responsibility,
• several core capabilities are missing,
• the role is far beyond your current level of ownership,
• you would need to misrepresent your experience to look qualified,
• the application has a hard knockout condition you cannot truthfully satisfy.

Skipping one vacancy is not wasted effort if it reveals a recurring market gap.

If six similar roles all require a skill you lack, that is more useful information than one isolated posting.

A simple decision tree

Start with the missing requirement.

Is it legally or operationally mandatory?

• Yes → verify the rule. If you cannot satisfy it, skip or obtain the requirement first.
• No → continue.

Is it central to the work described in the responsibilities?

• No → it may be a preferred or secondary gap. Consider applying.
• Yes → continue.

Can you demonstrate an equivalent or closely transferable capability?

• Yes → likely Apply or Stretch, depending on the distance between your experience and the role.
• No → continue.

Could you become credible in the gap quickly enough without misrepresenting your current ability?

• Yes → Stretch or close the gap first.
• No → Skip for now.

This is deliberately not a scoring formula. It forces you to inspect the consequence of the missing requirement.

What to do when one important skill is missing

First, decide whether you are missing the skill, the tool, or the evidence.

Consider a vacancy asking for “forecasting.”

• You have built forecasting models but never used the word “forecasting” on your resume → evidence/framing gap.
• You have built projections in Excel but never used the employer's requested forecasting package → possible tool gap.
• You have never worked on predictions, projections, time-series analysis, budgeting forecasts, demand forecasts, or comparable work → genuine capability gap.

If it is a genuine capability gap, ask two more questions:

1. How central is it to the job?
2. How often does it appear across other jobs you want?

A recurring requirement across many target roles deserves more attention than an isolated preference in one vacancy.

For fields where project evidence is meaningful, a learnable gap can sometimes be turned into demonstrable work. A software candidate might build and deploy a small service. A data candidate might create an analysis with a public dataset. A designer might develop a case study.

A project does not automatically substitute for professional experience. Its value is that it can provide evidence that you understand and can apply the skill.

What if you have fewer years of experience than requested?

Do not calculate the difference in isolation.

Compare your scope with the role's expected scope.

For example, a posting asks for five years of analytics experience. You have three and a half years, but during that time you have independently owned reporting, automated recurring work, handled stakeholder requests, and supported decisions using data.

That is different from having three and a half years in a role where you only assisted with basic reporting.

Ask:

• Have I already performed the main responsibilities?
• At roughly what scale?
• How independently?
• What decisions or outcomes did my work influence?
• Is the employer describing years as required, preferred, or approximate?
• Does the application include a hard screening question about the number?

If the answers show strong overlap, the role may be a stretch rather than a skip.

Do not change your dates or inflate your years to satisfy the posting.

How to interpret missing degrees and certifications

Start with the wording.

If the posting says “required”

Investigate whether it is genuinely mandatory for the role, the employer, a client contract, a regulator, or another formal reason.

Do not assume that all “required” degrees are flexible.

If it says “degree or equivalent experience”

Your task is to show the equivalent experience clearly.

Do not merely write “equivalent experience” in a summary. Demonstrate it through responsibilities, results, technical depth, projects, leadership, or domain knowledge that maps to the work.

If it says “preferred”

A missing preferred degree or certification is normally less severe than missing a required credential, but the rest of your profile still needs to support the role.

If it is a regulated qualification

Check the relevant official regulator rather than relying on generic career advice. Requirements differ by profession and jurisdiction. In U.S. nursing, for example, the relevant nursing board determines authorization to practise.^[2]

Required versus preferred still needs context

Labels help, but do not stop at labels.

An employer may put an important skill under a general “What we're looking for” heading without explicitly calling it required. Another may place an enormous list under “Requirements” even though only some items are used in screening.

Use three signals together:

1. Wording — required, must, essential, preferred, bonus.
2. Responsibilities — what you will actually be expected to do.
3. Application questions — what the employer explicitly verifies before review.

For a deeper breakdown, see Required vs Preferred Qualifications and Must-Have vs Nice-to-Have Skills in a Job Description.

How to strengthen the application after deciding to apply

Once you decide the role is credible, the goal is not to hide the gaps. It is to make the real fit easy to see.

Lead with the evidence that maps to core responsibilities

If the role prioritizes SQL, reporting automation, and stakeholder communication, those should be easy to find in your resume if you genuinely have them.

Translate adjacent experience

Do not assume the employer will make the connection for you.

Instead of:

Built dashboards for internal teams.

A stronger version might be:

Built weekly operational dashboards used by sales and finance managers to track conversion, backlog, and revenue trends.

The second version explains the scope and relevance without pretending it is identical to the employer's environment.

Use the employer's terminology only when it is accurate

If you did “customer segmentation” and the job calls it “audience segmentation,” using the employer's phrase may be reasonable if the concepts truly align.

If the job asks for Kubernetes and you have only Docker experience, adding “Kubernetes” because it is related would be false.

Address a meaningful gap through evidence, not apology

If you lack one requested tool but have equivalent experience, show the equivalent.

If you are short on years but have unusually relevant scope, show the scope.

If the skill is genuinely missing, do not pretend otherwise.

When applying is probably a poor use of time

An application is less attractive when the gaps accumulate around the center of the role.

Examples:

• A role requires professional licensure you do not have.
• A senior engineering job expects system design, production ownership, mentoring, and incident leadership, while your experience is limited to small supervised projects.
• A financial role requires a credential because of regulatory or client obligations, and you do not possess it.
• A job's main responsibility is enterprise sales, but your experience is entirely in non-commercial customer support.
• The application explicitly asks a knockout question you cannot truthfully pass.

The point is not to avoid stretch roles. It is to separate a credible stretch from an application that depends on the employer overlooking the core of the job.

Use skipped jobs as market intelligence

A skipped vacancy can still tell you what to do next.

Keep a simple record of recurring gaps:

After ten or twenty relevant postings, patterns become more useful than any single job description.

A skill appearing across many target roles may deserve investment. A requirement appearing once may simply reflect one employer's stack or preference.

That is also why a job-search system should not treat every missing keyword as equally important.

Two candidates, same match percentage, different decision

Consider a cybersecurity analyst role with ten listed qualifications.

Candidate 1: 70% match

They meet:

• SIEM monitoring,
• incident triage,
• networking fundamentals,
• Linux,
• scripting,
• ticket handling,
• security reporting.

They lack:

• Splunk specifically,
• one preferred certification,
• experience in the employer's industry.

This may be an Apply or Stretch case. The candidate appears to have the central security operations capability.

Candidate 2: 70% match

They meet:

• the degree,
• the preferred certification,
• the industry background,
• Python,
• Linux,
• documentation,
• communication.

They lack:

• SIEM monitoring,
• incident triage,
• hands-on security operations.

The same numerical score hides a much more serious gap.

This is the core reason to stop using raw requirement percentages as the decision.

FAQ

Should I apply if I don't meet all the requirements?

Possibly. Focus on whether you meet the eligibility requirements and can perform the core responsibilities. Missing a preferred tool or having a modest experience gap is different from missing a mandatory credential or the main capability the role exists to use.

Should I apply if I meet 60% of the requirements?

Do not use 60% as a universal cutoff. The percentage does not tell you which requirements are missing. You could meet 60% while missing the most important requirement, or miss 40% that consists mostly of secondary preferences.

Should I apply if I meet 70% or 80% of the requirements?

Use the same principle. A 70% or 80% match can be strong or weak depending on the importance of the missing requirements. Evaluate eligibility, core capabilities, experience depth, tools, and preferred qualifications separately.

What if I am one or two years short of the requested experience?

That can still be a credible application if your experience is highly relevant and you can already handle the responsibilities at the expected level. Review whether the years appear to be a hard screening requirement or a proxy for depth and seniority.

What if I am missing one required skill?

Find out whether the skill is truly central. If it is fundamental to the daily work and you have no transferable capability, the gap is meaningful. If the requirement is really a specific tool and you have strong equivalent experience, the application may still be viable.

Can an ATS reject me because my match score is too low?

Do not assume there is a universal ATS percentage. ATS platforms can support employer-configured screening and knockout criteria. Workable, for example, allows auto-disqualification based on selected yes/no questions.^[3] That is not the same as every ATS automatically rejecting resumes below a standard keyword-match score.

Are preferred qualifications optional?

“Preferred” normally indicates lower priority than “required,” but it does not mean the qualification has no value. Employers may use preferred qualifications to distinguish between otherwise credible candidates. The important point is that missing a preferred item should not be treated the same as missing a mandatory requirement.

What is the difference between a skill gap and a keyword gap?

A skill gap means you cannot yet perform the capability. A keyword or framing gap means you have relevant experience, but your resume does not make it visible using clear, accurate language.

See Resume Skill Gap vs Keyword Gap for the deeper distinction.

Should I apply when I have equivalent experience but not the exact background requested?

Often that is a reasonable stretch application if the underlying responsibilities are genuinely comparable. Make the transfer explicit. Show the problems you solved, scale, tools, decisions, and results rather than expecting the recruiter to infer equivalence from a job title.

The rule to remember

Do not ask whether you match enough boxes.

Ask:

Can I legally and practically do this job, and can I prove enough of the important parts from my existing experience?

If yes, apply.

If mostly yes, but one meaningful gap remains, treat it as a stretch and decide whether the gap is learnable or transferable.

If no because the missing requirement is genuinely central or mandatory, use the job as evidence of what to build next rather than forcing an application.

Sources

1. SHRM, “Ask Johnny: Should I Apply If I Don’t Meet Every Requirement?” September 16, 2026. https://www.shrm.org/in/topics-tools/news/employee-relations/ask-johnny-should-i-apply-if-i-dont-meet-every-requirement
2. National Council of State Boards of Nursing, “Licensure.” https://www.ncsbn.org/nursing-regulation/licensure.page
3. Workable Help, “Auto-disqualify candidates using application form questions.” https://help.workable.com/hc/en-us/articles/115012238688-Auto-disqualify-candidates-using-application-form-questions
4. SHRM, “Writing Clear and Effective Job Descriptions: A Beginner’s Guide.” June 8, 2026. https://www.shrm.org/in/topics-tools/news/blogs/beginners-guide-clear-effective-job-description
5. Workable Help, “Best practices: Candidate Screening.” https://help.workable.com/hc/en-us/articles/23365968258711-Best-practices-Candidate-Screening
6. Harvard Business Review, Tara Sophia Mohr, “Why Women Don’t Apply for Jobs Unless They’re 100% Qualified.” August 25, 2014. https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified
7. Indeed Career Guide, “How To Get a Job You’re Not Fully Qualified for.” Updated June 16, 2026. https://www.indeed.com/career-advice/finding-a-job/how-to-get-job-youre-not-qualified-for