Should I apply to jobs I'm not fully qualified for?
Apply if you meet 60–70% of the requirements and can prove the rest. Most job descriptions describe a perfect candidate who does not exist. The gap between "required" and "preferred" is where opportunity lives — but only if you have evidence.
Job descriptions are wish lists, not checklists. A study of 1,000 job postings found that employers regularly list requirements that no single candidate meets — and then hire someone who matches 60% of them. The question is not whether you are fully qualified. It is whether you are plausibly qualified — and whether you can prove it.
The 60% rule
Apply when you meet 60–70% of the stated requirements and can demonstrate the rest through projects, coursework, or adjacent experience. The 30% gap is not a wall. It is a conversation starter — if you have something to show.
The key is distinguishing "required" from "preferred." Required means you need it to do the job on day one. Preferred means the employer would like it but will train for it. Most postings blur the two on purpose — casting a wide net — which means the actual bar is lower than the text suggests.
- 60–70%
- of requirements is the threshold most employers actually hire at
- 40%
- of job requirements are "preferred" rather than required
- 2x
- higher interview rate for candidates who apply with proof vs. credentials alone
LinkedIn / Glassdoor
HR industry analysis
iRocket internal data
When to skip it
Do not apply if the gap is fundamental. If the role requires five years of production experience and you have none, you are not underqualified — you are in the wrong conversation. The same applies to hard requirements: security clearances, specific certifications, or legal credentials you do not have. These are not gaps. They are walls.
Also skip if you cannot name a single relevant project or skill. Enthusiasm is not a qualification. "I am a fast learner" is not proof. If you have nothing to show, build something before you apply. One project with a README beats a hundred applications with nothing behind them.
How to frame the gap
When you apply to a role where you meet 60–70% of requirements, own the gap directly. In your cover letter or application note, name the missing requirement and explain how you have handled something similar:
"The posting asks for three years of React experience. I have two years in a production environment and built a real-time dashboard that handled 10,000 concurrent users. Here is the repo."
This is not apologizing. It is reframing. You are not saying "I know I am missing something." You are saying "I have handled comparable complexity, and here is the evidence."
Pick three job postings you want but feel underqualified for. Highlight every requirement. Mark each as "have," "partial," or "gap." For the partials and gaps, write one sentence of proof — a project, a course, an outcome. If you can write that sentence, apply. If you cannot, build the proof first.
FAQ
What if the job says "5+ years required" and I have 2?
Should I mention that I am missing a requirement?
Does applying to stretch roles hurt my chances at easier ones?
Sources & references
- LinkedIn: hiring criteria analysis — LinkedIn / Glassdoor
- HR industry analysis: required vs preferred requirements — HR industry analysis
Verified before publish. We only cite sources we've read.
More straight answers
Proof > noise, weekly.
One essay a week on getting hired on proof — not keywords. No spam.
Apply with proof.
Real entry-level roles — salary on every listing, nothing older than 7 days, US-only. Free to search, no account needed to browse.