Should You Apply If You Don't Meet All the Requirements?

Should you apply if you don't meet all the requirements? The short answer is yes — most of the time. Research consistently shows that job descriptions are aspirational documents, not rigid checklists. If you meet roughly 70% of what is listed, you are likely a viable candidate. The challenge is knowing which 70% matters. Here is how to tell.

The 70% Rule and Why It Exists

The 70% rule is simple: if you meet about 70% of the stated qualifications in a job posting, you should apply. This rule of thumb has been circulated by career coaches for years, but it is grounded in how hiring actually works.

A widely cited internal study at Hewlett-Packard found that men typically apply to jobs when they meet about 60% of the qualifications, while women tend to wait until they meet 100%. This gap is not about competence — it is about confidence thresholds. The 70% rule exists partly to counteract that hesitation.

But there is a more fundamental reason the rule works: job descriptions almost never describe the actual minimum requirements for the role.

Why Job Postings Are Aspirational

Job descriptions go through multiple hands before they are published. A hiring manager writes their wish list. HR adds standard language. A recruiter adds keywords for searchability. Legal adds compliance text. By the time the posting goes live, it describes the perfect candidate — someone who rarely exists.

Here is what typically happens behind the scenes:

| What the posting says | What they actually need | |---|---| | "5–7 years of experience" | 3+ years with the right depth | | "Expert in Python, Java, and Go" | Strong in one, familiar with the others | | "MBA preferred" | Can think strategically about business problems | | "Experience with Salesforce, HubSpot, and Marketo" | Comfortable learning new tools quickly | | "Must have managed teams of 10+" | Has some leadership or mentorship experience |

Hiring managers know this. When they review applications, they are not checking boxes against their own posting — they are looking for people who can do the job. If your experience tells a compelling story about your ability to succeed in the role, the fact that you are missing one or two listed qualifications matters far less than you think.

Must-Haves vs. Nice-to-Haves: How to Tell the Difference

Not all requirements are created equal. The key to applying strategically — instead of either avoiding everything or applying to everything — is learning to distinguish between genuine requirements and wishlist items.

Signs a requirement is a must-have

It appears in the job title or first paragraph. If the role is "Senior Data Engineer" and the first sentence mentions building data pipelines, that is a core requirement. You need relevant data engineering experience.

It is a legal or regulatory requirement. Licensed professions (nursing, law, accounting, engineering) have non-negotiable credentialing requirements. If a role requires a CPA and you do not have one, that is not flexible.

It is repeated multiple times. If "SQL" appears in the requirements, the responsibilities, and the preferred qualifications, they really need SQL. This is not a nice-to-have.

The responsibilities depend on it. Read the responsibilities section carefully. If four of the six listed responsibilities require experience with a specific tool, framework, or skill, that skill is load-bearing.

It involves safety or compliance. Security clearances, specific certifications for regulated industries, language fluency for customer-facing roles in specific markets — these are not negotiable.

Signs a requirement is a nice-to-have

It appears only in the "preferred" or "bonus" section. Postings often split requirements into "required" and "preferred." Take them at their word — preferred means preferred, not required.

It is one of many tools in a long list. "Experience with Jira, Asana, Monday.com, Trello, or similar" means they want someone who can use project management software. Any one of those (or a comparable tool) counts.

It is soft and subjective. "Excellent communication skills" and "strong attention to detail" are table stakes for any professional role. These are not differentiators in the screening process.

It is a "years of experience" threshold. The difference between 5 years and 7 years of experience is almost meaningless in practice. What matters is what you did during those years, not the calendar count.

It uses hedging language. "Familiarity with," "exposure to," "understanding of" — these signal that deep expertise is not expected. They want someone who will not start from zero.

A Framework for Deciding Whether to Apply

Use this decision tree when you are on the fence about a specific role.

Step 1: Count the must-haves

Go through the posting and identify the true must-have requirements using the criteria above. Most roles have 3–5 genuine must-haves, even if the posting lists 15 qualifications.

Step 2: Check your match rate on must-haves

If you meet 80% or more of the must-haves, apply with confidence. If you meet 50–80%, apply with a strong cover letter that addresses the gaps. Below 50% on must-haves, this role is probably not the right fit right now.

Step 3: Look for transferable skills

For every requirement you do not meet directly, ask: "Do I have a transferable skill that accomplishes the same thing?"

Examples of transferable skills:

| They want | You have | Why it works | |---|---|---| | Salesforce experience | HubSpot experience | Both are CRMs; the workflow logic transfers | | Team management | Project leadership | Coordinating people toward a goal is the same skill | | Python | R or Julia | The analytical thinking transfers; syntax is learnable | | SaaS experience | Enterprise software experience | Business models differ, but product thinking is similar | | Public speaking | Client presentations | Same skill, different stage size |

Step 4: Consider your unique angle

Sometimes you bring something the posting does not even mention but the team actually needs. Industry expertise, a specific network, a combination of skills that is rare — these can offset a missing qualification.

If you have a compelling reason why you would succeed in the role despite not checking every box, that is worth an application.

When You Should Definitely Apply

You meet the must-haves but miss some nice-to-haves. This is the clearest case. You are qualified. Apply.

You have strong transferable skills. If your background is adjacent — different industry, similar role, or different role, similar skills — and you can articulate the connection clearly, apply.

You have a referral or internal connection. A warm introduction from someone inside the company can compensate for a gap or two on paper. Referral candidates are hired at significantly higher rates than cold applicants.

The role is a stretch, but you learn fast. If the posting asks for experience with a tool or methodology you have not used but have the foundation to pick up quickly, that is often fine. Hiring managers expect a ramp-up period for new hires.

Your IPS is 40 or above. If you are using Winnow Career Concierge to evaluate your matches, an Interview Probability Score of 40+ means the data sees enough alignment to justify an application. The IPS accounts for partial matches and transferable skills, so even if you feel underqualified, a 40+ score means the objective signals are there.

When You Should Probably Skip

You are missing core technical requirements. If the role requires hands-on machine learning and you have never built a model, the gap is too large to bridge with a cover letter.

Licensing or certification is required and you do not have it. A nursing role that requires an RN license, a legal role that requires bar admission, an accounting role that requires a CPA — these are non-negotiable. Check whether "required" actually means legally required.

The experience gap is dramatic. If they want 10+ years and you have 2, or they want VP-level experience and you are an individual contributor, the gap is likely too wide. There are exceptions (startups, fast-growing companies), but they are rare.

Every responsibility is unfamiliar. If you read the responsibilities section and none of them describe work you have done or could do, this is not a stretch role — it is a different career entirely.

You would not accept the role if offered. If the location, salary range, travel requirements, or core responsibilities do not work for you, do not apply just to practice. It wastes your time and the hiring team's time.

How to Apply When You Are Underqualified

If you have decided to apply to a role where you do not meet every requirement, how you apply matters more than usual.

Address the gap directly

Do not ignore the elephant in the room. If the role asks for experience with Kubernetes and you have not used it, your cover letter should acknowledge this and explain why it is not a dealbreaker.

Bad: (ignoring the gap entirely) Good: "While I have not worked with Kubernetes directly, I have extensive experience with Docker and container orchestration principles. I am confident I can ramp up quickly, and I bring deep expertise in [their other requirements] that would contribute immediately."

Lead with your strongest match

Your resume and cover letter should front-load the qualifications you do meet. If you match 8 of 10 requirements, make those 8 impossible to miss. The reader should see your fit before they notice the gaps.

Quantify your impact

Numbers are the fastest way to establish credibility. "Managed a team of 6" is more convincing than "leadership experience." "Reduced churn by 12% through targeted outreach" is more persuasive than "strong customer focus." When you are compensating for a gap, concrete results in adjacent areas carry extra weight.

Show you have done the research

A generic application to a role where you are underqualified will be filtered out immediately. A specific, thoughtful application that demonstrates you understand the company's challenges and how your background maps to them will stand out — precisely because most applicants do not bother.

What the Data Says About Partial Matches

Check the Candidates FAQ for more on how Winnow evaluates match quality, but here is the key insight: partial matches are not failures. They are the norm.

Very few candidates match 100% of a job posting's requirements. Hiring managers expect this. The typical hire matches 70–80% of the listed qualifications. The remaining 20–30% is made up of some combination of transferable skills, learning potential, and intangible qualities that emerge during interviews.

This means that when you see an IPS of 45 or 55 — not a perfect score, but solidly in the "decent fit" range — you are looking at a realistic opportunity. The system is accounting for the same partial-match dynamics that hiring managers evaluate.

The Confidence Gap Is Real

Research from multiple sources confirms that many qualified candidates — particularly women, people of color, and first-generation professionals — systematically underestimate their readiness for roles. If you tend to wait until you meet every single qualification before applying, you are almost certainly leaving opportunities on the table.

The 70% rule is not about encouraging unqualified people to waste everyone's time. It is about recalibrating the threshold for what "qualified" actually means in practice. Job postings describe an ideal. You do not need to be the ideal. You need to be good enough to do the job well, with some room to grow into it.

The Bottom Line

Read the posting carefully. Separate must-haves from nice-to-haves. Check your match rate on the requirements that actually matter. If you are at 70% or above on the true must-haves and you can tell a coherent story about why you would succeed, apply. If you are well below that threshold on the core requirements, move on to a role that fits better.

The worst thing you can do is not apply out of fear of rejection. The second worst thing is apply to everything indiscriminately. The sweet spot is in between: strategic, honest self-assessment combined with the confidence to put yourself forward when the fit is real.