The research: why you're probably more qualified than you think
A widely-cited internal study from HP found that men apply for a job when they meet 60% of the qualifications; women apply only when they meet 100%. Subsequent research from LinkedIn and other sources has consistently confirmed the pattern across genders, though the gap narrows: most people significantly under-apply relative to their actual qualified candidate pool.
The data-backed threshold is 60–70% of stated requirements. If you meet that bar, you have a statistically meaningful shot at getting through initial screening and into a recruiter conversation — where your actual skills, not a checkbox list, determine what happens next.
Two important reasons why this threshold works:
1. Job descriptions routinely overstate requirements. The person who writes a job description is the hiring manager, not an HR scientist. They write their ideal candidate — the person with everything — not the minimum viable hire. "10 years of experience" often gets hired as a 6-year candidate. "Must know Kubernetes" often means "we'd like you to know Kubernetes."
2. Hiring decisions are made on the whole person, not a checklist. Once you're in a conversation with a recruiter or hiring manager, a missing item on the job description can be outweighed by strong communication, a relevant project, or a credible plan to get up to speed quickly.
How to read a job description like a recruiter
Job descriptions have two tiers of requirements, even when they don't explicitly label them:
Hard requirements — skills or qualifications where the role genuinely cannot function without them. A nursing role requires a nursing licence. A pilot role requires flight hours. A lawyer role at most firms requires a law degree. These are real filters.
Aspirational requirements — the wish list the hiring manager wrote assuming they'd get the best possible candidate. "7+ years of experience" for a role that a 4-year candidate could clearly do. "Familiarity with [niche tool]" that takes a week to learn. "MBA preferred" for a strategy role where results clearly matter more than a degree.
Most job descriptions are 80% aspirational. Read them critically:
- "Required" vs "preferred" or "nice to have" — take the required section seriously; treat preferred as a bonus
- Years of experience — subtract 30–40% and apply if you're near that range
- Specific tools and technologies — if you know adjacent tools well, you can learn the named tool
- Degree requirements — many companies have quietly dropped these; apply and let them screen
The one hard question to ask yourself: Is there anything on this list that would prevent me from doing the job on day one? Not "would I need to learn something" — everyone needs to learn something. But "is there a core function of this role I genuinely cannot perform?" If the honest answer is no, apply.
The real reason to apply when underqualified: your odds at zero are zero
If you don't apply, your probability of getting the role is exactly 0%. If you apply and are underqualified by one reasonable measure, your probability is low — but it's not zero. A 2% chance is infinitely better than a 0% chance, and at sufficient application volume, that math compounds.
The mental model that works: treat each application as a lottery ticket with varying odds, not a performance review. A role where you meet 80% of requirements is a high-odds ticket. A role where you meet 55% is a low-odds ticket. Both are worth buying because the cost is low (one application) and the upside is the same (a job offer).
The mistake most job seekers make is treating each application as a high-stakes bet where rejection is painful feedback. At scale, rejection is just the expected outcome for most tickets — including perfectly qualified candidates. Understanding the math helps here: the average response rate across all applications is 2–3%, even for fully qualified candidates.
When not to apply
Despite the general "apply anyway" argument, there are cases where the gap is genuinely too large:
Hard credential requirements. Medical licences, bar admissions, security clearances, pilot certifications. These are binary — you either have them or you don't, and no amount of enthusiasm changes that.
Seniority mismatches of more than one full level. Applying for a VP role as a Coordinator is a misspend of your time. One level up (Senior → Director) is often achievable with a strong narrative. Two or more levels up rarely makes it past initial screening.
Highly technical specialisations. If a machine learning role requires 5 years of PyTorch experience and you've never used it, "adjacent skills" won't bridge the gap for a role where PyTorch is the primary daily tool.
Roles explicitly outside your geography without a remote option. Some roles require a specific legal right to work in a country and are non-negotiable about it. Don't apply to roles you'd need a visa for if the company doesn't sponsor.
Outside of those cases: if your gut says "I could do this job with 3 months of ramp-up" — apply.
How to frame your application when you're underqualified
Don't pretend the gap doesn't exist in your cover letter — address it briefly and redirect:
"I don't have direct experience with [specific thing], but I've worked extensively with [adjacent thing] and am confident I can get up to speed within [timeframe]. What I do bring is [your strongest relevant strength]."
One sentence of honest framing followed by a redirect to your genuine strengths is far more effective than hoping the reviewer doesn't notice the gap, or over-explaining it defensively.
For resume: don't pad or misrepresent. Do make sure everything relevant is visible. Use the job description language to describe your actual experience — keyword matching matters for ATS, and if your real experience overlaps but uses different terminology, align the terminology.