Job Fit

Should You Apply If You Don’t Meet Every Requirement?

By Vichet Horn · Founder, Think Growth Labs

7 min read · Last updated 18 September 2026

The short answer

Almost never do you need to meet every requirement. Job descriptions are wish-lists, not checklists. The real question isn’t how many boxes you tick — it’s whether you can show you’d do the core of the job well. Ignore the famous “apply at 60%” rule; it’s folklore. Judge on evidence instead.

The list is a wish, not a gate

Here is what a requirements list usually is: someone’s idea of the perfect candidate, assembled from a dozen hopes, few of which any real person satisfies completely. Hiring teams know this. They expect to compromise. So when you read fifteen bullet points and count the three you don’t have, you’re holding yourself to a standard the employer isn’t even holding.

This matters because of whyqualified people talk themselves out of applying. When researchers asked professionals why they didn’t apply for jobs where they didn’t meet every qualification, the top reason — for men and women alike — wasn’t lack of skill or confidence. It was that they thought the listed qualifications were mandatory and didn’t want to waste their time (Harvard Business Review, 2014). In other words: the barrier was a misreading, not a real gap.

Forget the 60% rule

You may have heard that you should apply if you meet 60% of the requirements — or the version where “women only apply when they’re 100% qualified and men apply at 60%.” It gets repeated everywhere as fact. It isn’t one. The number traces back to an unverified internal anecdote that no one has ever actually produced, and the threshold shifts depending on who’s quoting it. Treat any specific percentage as what it is: a made-up round number standing in for a real judgment.

The judgment underneath is better anyway, because it’s about you specifically rather than an average. Instead of “do I hit some percentage,” ask: can I point to real evidence that I’d handle what this role most needs?

When requirements ARE firm

One honest exception. In regulated or safety-critical fields — medicine, law, finance, some engineering — a stated license, certification, or minimum credential can be a genuine hard gate, tied to the law or to insurance rather than to preference. If a role names a credential you don’t have and can’t quickly get, believe it. Everywhere else, most “required” lines are softer than they read. Know which kind of requirement you’re looking at before you rule yourself out.

How to decide, honestly

  1. 1

    Find the real must-haves.

    Not the whole list — the three to five things the role clearly can’t do without. See how to read a job description.
  2. 2

    Name your evidence for each.

    One specific example from your own experience per must-have. If you can evidence most of the core, the missing bullets are noise.
  3. 3

    Check for a hard gate.

    Is anything you’re missing an actual legal or licensing requirement? If yes, respect it. If no, it’s a preference.
  4. 4

    Apply to the match, not around the gaps.

    When you apply, make your case speak to the priorities you domeet — don’t spend the application apologizing for the ones you don’t.

Common mistakes

  • Reading the wish-list as a checklist.

    Instead: Assume the list is aspirational. The employer expects to compromise; hold yourself to the core of the role, not every bullet.

  • Trusting a percentage rule.

    Instead: Ignore “60%” and its cousins — they’re folklore. Judge whether you can evidence the role’s real priorities.

  • Ruling yourself out over a preference.

    Instead: Separate genuine hard gates (licenses, credentials) from soft preferences. Most “required” lines are the latter.

  • Applying with no evidence for the core.

    Instead: If you can’t name real examples for what the role most needs, that’s the honest “not yet,” percentage or no percentage.

The better test

None of this means apply to everything — your hours are finite, and a role you can’t evidence isn’t worth them. It means stop deciding by counting. Run the two-column test instead, decide on evidence, and let the folklore go. The question was never “am I 60% qualified.” It was always “can I show I’d do this well.”

Common questions

Do I really need to meet 100% of the job requirements?
No. Postings are typically wish-lists describing an ideal candidate, not a list of hard gates. Research on why people hold back from applying found the top reason was not lack of skill or confidence — it was believing the listed qualifications were mandatory when they were not. Read the list as “here is what would be ideal,” then judge whether you can do the core of the role.
Is it true you only need 60% of the requirements?
That specific number is folklore. It descends from an unverified anecdote about an internal report that no one has ever produced, and the exact threshold changes depending on who repeats it. Ignore the percentage entirely. A better test is concrete: can you point to real evidence that you’d handle the role’s genuine priorities? That’s the thing that actually matters.
When are requirements actually firm?
In regulated or safety-critical fields — medicine, law, finance, certain engineering roles — a stated license, certification, or minimum credential can be a genuine hard gate tied to the law or to insurance, not a preference. Outside those cases, most “required” lines are softer than they look. Know which kind you’re reading before you rule yourself out.
What should I do instead of counting requirements?
Find the three to five things the role most needs (see how to read a job description), then check each against a specific example from your own experience. If you can evidence most of the core, apply — and let your application speak to those matches. If you can’t evidence the core at all, that’s a more honest “no” than any percentage.

You’ve already done the work.

Your career already contains the stories — the projects, the decisions, the moments that prove what you can do. The hard part was never doing the work. It’s remembering the right part of it when someone is sitting across from you and the pressure is on.

That’s why we built ELOQ.

Instead of guessing whether you’re “qualified enough,” ELOQ checks the role’s real requirements against your own experience and shows you exactly where you can back yourself up.

ELOQ helps you remember your experience, rediscover the stories worth telling, and rehearse them until they come back naturally — in your own words, when it matters.

Preparation creates eloquence.

Start preparing with ELOQ →

More interview guides

← Back to How to Decide Whether to Apply for a Job