You found a job you want. You read the requirements. You meet most of them — but there are two or three you don't, so you close the tab.
That decision, made in a few seconds, is one of the most consequential moves in a job search, and most people make it on autopilot. The instinct feels responsible: don't waste anyone's time, don't apply for things you're not qualified for. But it rests on an assumption that is often wrong — that the list of requirements is a set of hard gates, and that missing any of them disqualifies you.
You've probably heard some version of a rule for this. Apply if you meet 70% of the requirements. Or 80%. The rule is meant to be reassuring, but it answers the wrong question, because it treats requirements as interchangeable — as if missing two minor ones and missing two essential ones were the same thing. They aren't. The real question was never how many requirements you meet. It's which ones you don't.
What Percentage of Job Requirements Do You Need to Meet?
There's no reliable percentage. A posting's requirements aren't weighted equally, and it almost never tells you how they're weighted. So the honest answer is that the number doesn't matter — what matters is which requirements you're missing.
A single job description usually mixes several different kinds of line. There are the genuine must-haves — the two or three things the role actually turns on. There are the strong preferences, the things that would help but won't sink you. There's boilerplate carried over from older versions of the posting. There are aspirational items HR added to attract a unicorn nobody expects to find. And occasionally there's a true hard gate — a license, a clearance, legal work authorization — that isn't negotiable at all.
Treating those as one flat checklist is the mistake. Missing a strong preference is not the same as missing a must-have, and missing a must-have you can demonstrate a different way is not the same as missing one you genuinely don't have. A percentage flattens all of that into a single number that tells you nothing about whether you should apply.
You're Probably Talking Yourself Out of It
The most-quoted line on this topic is that men apply to jobs when they meet about 60% of the qualifications, while women apply only at 100%. It gets repeated everywhere as a story about confidence — but it traces to an unpublished internal Hewlett-Packard tally that no one has ever been able to verify. The more useful research is what happened when someone actually asked people why they hadn't applied.
In 2014, the writer Tara Sophia Mohr ran exactly that survey for Harvard Business Review. The most common reason people gave for not applying to a job that interested them — cited nearly twice as often as any other — wasn't "I didn't think I could do the job." It was "I didn't think they would hire me since I didn't meet the qualifications, and I didn't want to waste my time and energy." Men gave that answer 46% of the time; women, 41%. (Mohr didn't publish the survey's sample size, so read the exact split as directional.)
Sit with that for a second. The barrier wasn't self-doubt about the work. It was a belief about the hiring process — specifically, that the qualifications are a hard filter and applying without meeting all of them is pointless. Mohr called it a mistaken perception about the hiring process — and it's worth noting the numbers puncture the usual framing: men reported this reasoning slightly more than women. This isn't a confidence gap in one group. It's a misread that runs across the board, not a women-specific one.
I Don't Have the Degree Half My Employers "Required"
I'll put my own cards on the table here. I don't have a college degree. More than half the jobs I've been offered listed one as a requirement. I applied anyway, and I was hired anyway.
That's not a story about rules not mattering. I've also been on the other end — roles where the degree was a true hard line, where no amount of experience was going to move it, and where applying genuinely was a waste of both our time. But those were the minority. Far more often, "bachelor's degree required" turned out to mean "bachelor's degree, or convince us you don't need one." When an employer wanted the candidate, the requirement they'd written in stone became a preference they were glad to trade for a few more years of experience.
I'm one person, and one career isn't evidence. But it lines up with what the research shows at scale — and the research is where this stops being a personal anecdote and starts being a pattern you can count on.
The List Asks for More Than the Job Needs
Job descriptions routinely ask for more than the job actually needs — and where researchers have measured it, the gap is striking.
A 2017 Harvard Business School report with Accenture and Grads of Life, Dismissed by Degrees, analyzed 26 million job postings and surveyed more than 600 business and HR leaders. In one stark example, 67% of postings for production-supervisor roles required a college degree — while only 16% of the people already doing that job had one. The requirement on the posting and the requirement of the work had come completely unmoored from each other. Those incumbents are doing the job without the credential the posting treats as mandatory — direct evidence the work gets done without it. The same report found that three in five employers admit to rejecting qualified middle-skills candidates with relevant experience in favor of recent graduates — and two-thirds concede that demanding a degree makes a middle-skills role harder to fill.
That's the structural reality behind my own experience. When you read "required" on a posting and take it literally, you're often taking literally a line the employer themselves doesn't enforce literally. The list is often a wish, inflated by habit and caution. Reading it as a contract is reading it more strictly than the people who wrote it.
The Three Kinds of "Missing" Requirement
Here's the distinction that actually tells you whether to apply. When you're "missing" a requirement, you're in one of three situations, and they're nothing alike.
A real gap means the experience isn't there and you have nothing equivalent to put in its place. The posting needs five years of managing a P&L and you've never owned a budget. That's a genuine absence, and no clever wording fixes it.
A framing gap means the experience is there — you've just described it in different words than the posting uses. The role asks for "stakeholder management" and you wrote "worked with other departments." It asks for "cross-functional delivery" and you called it "helping other teams ship." The work is identical. The recognition fails because the vocabulary doesn't match.
A substitution gap is the one in between, and it's the most commonly mishandled. You don't have the literal thing the posting names — but you have something employers routinely accept in its place. No bachelor's degree, but ten years doing the work. No PMP, but a decade of running projects. No experience in their exact industry, but years in an adjacent one. On a strict reading the requirement is unmet, and you're still a credible hire. That's the situation I described earlier: no degree, but enough experience that most employers were glad to take it instead.
Two of those three aren't the problem they look like. A framing gap is a wording problem. A substitution gap is a make-the-trade-visible problem. Only the real gap is a genuine absence. Whether it matters depends on how central the requirement is to the role.
The employers themselves confirm how often the "missing" requirement isn't really missing. A 2021 Harvard Business School study with Accenture, Hidden Workers: Untapped Talent, built on surveys of more than 8,000 hidden workers and over 2,000 executives, found that 88% of employers agree that qualified candidates get filtered out of the process because they don't match the exact criteria in the job description. Eighty-eight percent. That is consistent with framing and substitution gaps at scale — qualified people screened out not for lacking the ability, but for not matching the posting word-for-word. The study estimated roughly 27 million "hidden workers" in the U.S. — a population it links in part to rigid hiring practices that screen out people who could do the work.
If your "gap" is a framing or substitution gap, you don't have a qualifications problem. You have a visibility problem — your real qualifications just aren't legible to the reader yet, and that's fixable. (The mechanics are covered in Keywords Aren't a Trick — They're a Translation Problem and in how to tailor a resume.)
Not sure whether you're missing a requirement or just haven't shown it? RigTheResume analyzes your resume against any job description and sorts them out — what you've genuinely covered, what you've covered but haven't made visible, and what's actually absent. Check where you stand free →
Which Requirements Are Actually Gates
None of this means every requirement is soft. Some are exactly as hard as they look, and knowing which is part of reading the posting honestly.
A few categories really are non-negotiable: professional licenses, security clearances, legal authorization to work, and certifications that are legally required to do the job. If the role needs a CPA license or an active clearance and you don't have one, the posting means it. There's also a quieter category of hard gate built into the screening software itself — Hidden Workers found that roughly half of U.S. companies automatically filter out anyone with a gap of more than six months in their work history. Those are rules, not preferences.
For everything else, the job is to read the posting closely enough to tell the must-haves from the noise. A few signals are reliable: requirements that appear near the top tend to matter more than those near the bottom; anything repeated in both the responsibilities and the requirements sections is usually load-bearing; and ownership language — "lead," "own," "define" — points to what the role actually turns on. The boilerplate, the long preferred-qualifications wishlist, and the aspirational extras are where the give is. (This is the same decoding work covered in how to tailor a resume.)
So — Should You Apply?
Run each requirement you don't meet through three quick questions, in order:
- Is it a framing gap? The experience is there and you've only worded it differently — not a gap at all. Reword it and apply.
- Is it a substitution gap? You lack the literal credential but have a credible equivalent — years of experience for the degree, a track record for the certificate, an adjacent field for the exact one. Apply, and make the substitute explicit so they can choose to accept it.
- Is it a real gap on something central? The experience is genuinely absent, you have nothing equivalent, and it's one of the role's true must-haves — not boilerplate or a nice-to-have. A required license, clearance, or work authorization you don't hold is the sharpest version. That's the case where sitting it out is rational; almost everything else is worth an application.
The honest summary: apply unless the gap is real — genuinely absent, no equivalent — and lands on something core to the role. Both at once. A legal hard gate you can't clear is the clearest example. That's a much smaller set than the two or three missing bullets that made you close the tab.
The substitutions in my own career didn't happen because the requirements were fake. They happened because I applied, got into the room, and gave them a reason to want me — at which point the line they'd written in stone turned out to have some give in it. You can't get waived past a requirement you've already disqualified yourself from. The employer never gets the chance to decide they want you badly enough to bend, because they never see you at all.
The screening out that 88% of employers acknowledge isn't malice — it happens because hiring processes match on exact criteria, and candidates often get worded out by a framing gap or talk themselves out of applying entirely. Both of those are things you can change. The requirement you can't meet is rarer than it looks. The requirement you only think you can't meet is everywhere.
Find Out Which Requirements You Actually Meet
RigTheResume analyzes your resume against any job description and shows you exactly where you stand — which requirements you've covered, which you've met but haven't made visible, and which are genuinely missing. So you can decide whether to apply based on what's real, not on a misread you made in a few seconds.
No credit card required · 5 free analyses/month