Guides

Should You Apply If You Meet Only 60% of the Requirements? A Decision Rule

2 September 2026 · about 7 min read

Key takeaways

  • The percentage of requirements you meet never decides anything. Which requirements you miss does.
  • Sort the list into gatekeepers, core, and decoration. Miss any gatekeeper: skip. Meet the gatekeepers and most of the core: apply, or adapt if your resume hides it.
  • Two candidates at 60% can have opposite odds — the worked example below shows how.

You have probably heard the number. Men apply when they meet about 60% of the requirements; women wait until they meet 100%. The statistic is usually traced to an internal Hewlett-Packard report and became career-advice canon after it was popularized in the mid-2010s. Its lesson, repeated in every job-search article since: stop waiting for 100%. Apply at 60%.

It is decent advice about confidence. It is useless advice about decisions, because it is missing the only thing that matters.

Sixty percent of what?

A candidate who meets six requirements out of ten and a candidate who meets six different requirements out of the same ten have the same percentage and completely different odds. One of them should apply this afternoon. The other should close the tab. The percentage cannot tell you which one you are.

This article gives you the rule that can.

Requirements are not equal

Read any posting's requirements list and you will find three kinds of item mixed together, in no particular order, formatted identically.

Gatekeepers. A small number of requirements are binary and non-negotiable — not because the hiring manager is rigid, but because the process cannot proceed without them. A professional license. A security clearance. Work authorization in the country. A location that genuinely cannot be remote. A hard experience floor written into a grading scale. A specific tool or language when the role is that tool (an SAP FICO consultant role wants SAP FICO; "or equivalent" is not on offer).

Missing a single gatekeeper is disqualifying, whatever your percentage. Your application will be filtered — by a human or a system — before anyone reads the rest.

Core requirements. Three to five items describe the actual substance of the job: what the person will spend their weeks doing, at what scale, with what autonomy. "Own the monthly close for a multi-entity group." "Lead a team of 6–10 engineers." "Run enterprise sales cycles of 6–12 months." These are the requirements the interview will actually test.

You do not need every one of them. You need most of them, at roughly that scale — and, critically, you need them to be visible (more on that below).

Decoration. Everything else. "Familiarity with" tools. "Nice to have" certifications. Vague virtues ("strategic mindset", "comfort with ambiguity"). Adjacent skills the manager would enjoy but does not need. Postings accumulate decoration because several people contribute to the draft and nobody deletes. Decoration is what the "apply at 60%" advice is really about — and it is right: decoration should never stop you.

The trouble is that the list does not label itself. Sorting it is your job, and it takes about three minutes once you know what you are looking for. (The tells are listed further down, and What "must-have" and "nice-to-have" really mean goes through the full sort.)

The rule

Once the list is sorted, the decision is mechanical:

  1. Miss any gatekeeper → SKIP. Regardless of everything else. Do not spend the hour.
  2. Meet all gatekeepers, meet most core requirements, and your resume already shows it → APPLY. Send it as-is. Do not tailor; you can only make it worse.
  3. Meet all gatekeepers, meet most core requirements, but your resume does not show it → ADAPT. This is the case that deserves the hour, spent on the specific requirements your resume hides.
  4. Meet all gatekeepers but miss most of the core → SKIP, unless you have a referral who will walk your application past the screen. Decoration cannot compensate for missing substance.

Notice what the rule never asks: what percentage you meet. The percentage is a by-product. Two candidates at 60% land in different rows because they miss different kinds of requirement.

A worked example

A posting for a Head of FP&A lists ten requirements:

  1. 10+ years in finance, 4+ in FP&A leadership (gatekeeper — hard floor)
  2. Qualified accountant (CPA, ACCA, or equivalent) (gatekeeper — license)
  3. Own annual budget and rolling forecast for a group of $200M+ revenue (core)
  4. Build and lead a team of analysts (core)
  5. Present to board and investors (core)
  6. Drive the implementation of a planning tool (core)
  7. Experience in SaaS or subscription businesses (decoration — "or similar" in the text)
  8. Advanced Excel and Power BI (decoration)
  9. Anaplan or Adaptive experience (decoration — "a plus")
  10. Strong communicator, comfortable with ambiguity (decoration)

Candidate A meets 1, 2, 3, 4, 5 and 8. Six of ten — 60%. Both gatekeepers clear; three of the four core items met; the misses are one core item (6) and three decorations. This is APPLY or ADAPT, depending only on whether the resume shows items 3–5 clearly. A strong candidate.

Candidate B meets 3, 4, 6, 7, 8 and 9. Also six of ten — also 60%. But item 1 is missed (eight years, two in leadership) and item 2 is missed (no qualification). Two gatekeepers down. This application will not be read, and no tailoring changes that. SKIP, and the hour goes to a posting that fits.

Same percentage. Opposite verdicts. The "apply at 60%" advice would send both of them in and call it confidence.

The requirement you meet but cannot prove

There is a fourth case hiding inside the rule, and for experienced professionals it comes up constantly.

You read item 3 — "own annual budget and rolling forecast for a $200M+ group" — and you think: I've done that. You have. It was your job for three years. But your resume says "Finance Manager" at a company nobody has heard of, and the budgeting work is the fourth bullet, phrased as "supported the planning cycle."

You meet the requirement. Your resume does not show it. To a screener with twenty seconds and forty applications, you do not meet it.

This is the presentation gap — the case the Apply / Adapt / Skip method treats as its own verdict — and it is why the rule has a separate ADAPT row. The fix is not a rewrite; it is two edits — pull the bullet to the top, restate it in the posting's own terms, add the number — that turn a hidden match into a visible one. It takes fifteen minutes and it is the highest-return fifteen minutes in your search.

The mistake most candidates make with a hidden match is to treat it like a missing one: apply anyway, hope the interviewer digs, and lose to someone with a weaker record and a clearer resume.

Tells that a requirement is softer than it looks

Postings leak their own priorities if you read them carefully.

  • "or equivalent", "or similar", "or related field": the writer has already conceded the point. Decoration, or a soft core item.
  • A range ("5–8 years"): the lower bound is the real requirement; the upper bound is aspiration.
  • "Familiarity with", "exposure to", "a plus", "preferred": decoration, explicitly.
  • A requirement repeated in the responsibilities section: core. The writer cares enough to say it twice.
  • A requirement that appears only in the requirements list and nowhere in the role description: often decoration copied from a template.
  • Anything with a number attached to the business (revenue, team size, deal size): core. Numbers get written down when they matter.

When "apply anyway" is still right

The rule has one honest exception. If you miss a core requirement but have a referral — someone inside who will hand your application to the manager — apply. Referrals bypass the screen the rule is designed for. Everything the rule says about gatekeepers still holds: a referral cannot manufacture a license or a work permit.

Running the rule faster

Sorting a requirements list by hand takes three minutes a posting. Reading your own resume the way a stranger would — to catch the hidden matches — is harder, because you know what you meant.

SmarterApply does both reads together: paste the posting and your resume, and it returns APPLY, ADAPT, or SKIP with the specific requirements that decided it — including the ones you meet but do not show. The first analyses are free. Run it on the posting you're hesitating over.

FAQ

Is 60% a real threshold I should use?

No. Use the rule instead: all gatekeepers, most of the core, and make sure the core is visible. A candidate can be a strong fit at 50% of the list and a non-starter at 80%.

What if I can't tell whether a requirement is a gatekeeper?

Ask whether the process can physically proceed without it. A license, a clearance, a permit, a hard year-floor, a tool the role is named after: gatekeepers. Everything else is negotiable to some degree.

Should I explain a missing requirement in my cover letter?

Only a missing core item, and only briefly, with what you have instead. Never explain a missing gatekeeper (it will not be read) or a missing decoration (nobody noticed).

Does this change if the role is a stretch I really want?

A stretch role usually means missing one core item, not a gatekeeper. That is still an ADAPT if you can show the adjacent experience convincingly — Overqualified or under? covers how to score the gap. It becomes a SKIP when the stretch is two or three core items — at that point you are asking the screener to imagine a candidate rather than read one.