Original research
How many job requirements do you actually need to meet?
The standard answer is “about 60%”. That figure traces back to an unpublished internal report, and no one appears to have measured it against real applications. So we measured ours: 1,793 resumes, each compared against the specific job it was being sent to.
Last updated: September 9, 2026
The short answer
People who check a resume against a posting are already covering a median of 79% of that posting’s requirements — well past the threshold the usual advice worries about. For them the coverage question is largely settled, and the gap that remains is a different one: a median of 6 skills that the resume names but never demonstrates in any bullet point.
Put plainly: hitting a percentage of the requirements list is not the hard part. Proving the ones you claim is.
Where the 60% rule comes from
Search for this question and nearly every answer quotes a percentage. Follow the citations and they converge on one place: an internal company report, referenced second-hand in a widely read magazine article, and never published. The sample, the method, and even the definition of “requirement” are all unavailable.
The number is not stable either. Asked three closely related versions of this question on the same day, Google’s own AI summary answered “60% to 70%” twice and “40% to 60%” once, citing career forums and news columns rather than any measurement.
We are not claiming the figure is wrong — we cannot check something that was never published. We are saying it has never been measured, and that a measurement is more useful than a number passed hand to hand. The full provenance audit, including the other recycled statistics in this field, is open on our public research repository.
What we measured
Every record is one resume compared against one real job description that someone supplied, between March 2026 – September 2026. For each pair we extract the posting’s requirements, classify each as required or preferred based on how the posting frames it, then resolve each one against the resume into one of three states:
| State | Meaning |
|---|---|
| Matched | Present in the resume and demonstrated in experience |
| Named but not shown | Listed as a skill, but no bullet point demonstrates it |
| Missing | Not in the resume at all |
That middle state is why this data answers a question the usual advice cannot. A resume that lists twenty skills and demonstrates none of them looks complete under a simple present-or-absent check, and incomplete under this one. Both readings are true about different things.
Results
Median coverage of the posting's requirements
79%Share of the requirements in that specific posting that appear anywhere in the resume.
n = 1,793
Median required skills genuinely missing
6Named in the posting, absent from the resume entirely.
n = 1,793
Median skills named but not evidenced
6Listed in a skills section, but no experience bullet demonstrates them.
n = 660
Share of gaps the posting framed as required
74%The rest were framed preferred, or nice to have.
n = 1,433
What the overall judgement looked like
Each analysis also produces one judgement for that resume against that posting. The middle band is the striking one:
| Judgement | Share | Meaning |
|---|---|---|
| Ready to send | 13.6% | Fit is there and the resume shows it |
| Fix it first | 70.2% | Realistic fit, but the resume undersells it |
| Not a fit | 16.3% | Not a realistic match for this posting |
n = 707
What this suggests
The requirements list is not usually what stops you. Coverage sits high, and the smallest group in the judgement table is the one that is genuinely not a fit. The largest by far is the group where the fit is real and the document does not show it.
Required and preferred matters less than the advice suggests. 74% of the gaps we see were framed as required rather than preferred. The common reassurance that missing items are usually just nice-to-haves does not hold in this sample.
Experience is not the barrier either. Median experience on the resume was 4 years against a median posting request of 4 years. People are broadly applying within their own range.
The real gap is evidence, not coverage. A median of 6 skills per resume are named without ever being demonstrated. Related work on how often resume bullets contain a measurable result points the same way.
What this does not show
- No hiring outcomes. Nothing in this data records whether any application led to an interview or an offer. This cannot tell you that meeting more requirements gets you hired — only what resumes contain relative to what postings ask for.
- The people are self-selected. Everyone here chose to check a resume against a posting. They are not a random sample of applicants, and their high coverage may partly reflect work they had already done.
- The postings are self-selected too. People may run checks disproportionately on jobs they feel unsure about.
- The judgement is a model’s. It is an assessment of a document, not a prediction tested against real hiring results.
- These are resume-vs-job-description analyses run on ResumeAtlas, not a survey of all resumes. The sample skews toward software, data and engineering roles, so the specific tools below reflect those postings more than hiring overall.
Related questions
- Should you apply for a specific job — the decision itself, for one posting, rather than the measurement behind it.
- The full dataset behind this page — every measurement from the corpus, free to cite, with a downloadable copy.
- How much should you tailor a resume — the effort question, once you know what the gap is.
- How often resume bullets contain a number — the evidence gap, measured directly.
- Our open research repository — datasets, methodology, limitations, and the provenance audit, all public.
Check a posting you are considering
The same analysis that produced this data will run on your own resume and one specific posting: which requirements you cover, which you name without showing, and which are genuinely missing.