The most-cited stat in career-advice writing for the past decade comes from a Hewlett-Packard internal report: women applied to jobs only when they met 100% of the listed requirements, while men applied at around 60%. Tara Mohr wrote about it in HBR in 2014 and the number went on to appear in roughly every "lean in" piece since.

The interesting thing about the number is that it's been read backwards as often as forwards. The popular interpretation — "women should apply more, men have it figured out" — misses what the data actually says. Both groups are doing something rational. Women are reading job descriptions literally and respecting the stated bar. Men are reading them as a wishlist. Most postings are written as wishlists. That's the structural fact behind the gap, and it's the foundation of any decision rule you build on top of it.

This post is about what to do with that. When does it actually pay off to apply when you're underqualified? When is it volume-with-no-conversion? A short rule, with the underlying logic.

What the number really tells you

The simplest way to read the gap: postings list more requirements than the role actually needs. Hiring managers add nice-to-haves to filter for "ambitious" candidates who'll claim them anyway. HR adds requirements to comply with vague job-family templates. Recruiters re-post old listings with the requirements unchanged from a year ago. By the time the posting hits the public, it represents a wishlist, not a bar.

The "60% applier" reads this correctly — most of the requirements aren't enforced — and the "100% applier" reads it as written. The result: the 60% group ends up in interviews for roles they aren't a perfect fit for and gets hired into them, while the 100% group sits out roles they would've gotten.

What this doesn't mean: you should apply to anything. Some requirements are real — and recruiters do filter on years of experience and specific certifications when the volume of applicants is high. The rule isn't "ignore requirements," it's "distinguish wish-list from must-have, and apply when you hit the must-haves."

What counts as 70% fit

The rule of thumb: 70% of the must-haves — not 70% of every requirement listed.

When reading a posting, separate it into three layers:

• Layer 1: Required skills/tools. Anything in "Requirements," "Qualifications," or "Must have."
• Layer 2: Preferred / nice to have. Anything under "Preferred," "Bonus," or buried in responsibilities.
• Layer 3: Tone and emphasis cues. Words that repeat — "cross-functional," "data-driven," "ambiguity."

The 70% rule applies to Layer 1 only. If a posting lists ten requirements and seven are in the must-have section, you need to credibly check off five of those seven. Hitting 70% of the must-haves while missing 100% of the nice-to-haves is fine — that's normal for a tailored applicant.

Hitting 30% of the must-haves and 80% of the nice-to-haves, by contrast, is wishful — you're an entry-level applicant for a senior posting, or a generalist for a specialist posting. The math works against you.

The decision matrix

The other variable that affects the call: the posting's credibility. A real posting where you're a stretch is worth applying to. A ghost-class posting where you're a stretch is volume with no conversion. The 2x2:

The two cells worth focusing on are the diagonal:

• Stretch + real is where the 70% rule earns its keep. You're underqualified, but the role is real, the recruiter is reading applications, and your tailored resume has a chance. Apply.
• Stretch + ghost-class is the trap. The math says no — even if you're a perfect fit, the role might not exist. As a stretch applicant, your odds are bad on both axes.

The other two cells are more nuanced. Solid + real is the obvious yes — you should be over-applying here. Solid + ghost-class is where intuition usually wins; if it's a top-three role and you have a referral, apply; otherwise skip and save the polish for verifiable roles.

A worked example

Take a posting for "Senior Product Manager — B2B SaaS" with the following requirements:

Must-have:

• 5+ years of product management experience
• B2B SaaS background
• Experience with technical PM work (APIs, data products)
• Stakeholder management with engineering and sales

Preferred:

• MBA
• Series B–D startup experience
• Prior people management

Tone:

• "Cross-functional partnership"
• "Ambiguity"
• "Owner mindset"

A candidate with 6 years of PM experience at a B2B SaaS company, with API/data work but no people management, has:

• Must-have: 4/4 (assuming "stakeholder management" is yes by default for any senior PM)
• Preferred: 1/3 (Series B–D yes, no MBA, no people management)

Must-have is 100%. The candidate is not a stretch — they're a solid match. The "preferred" gaps are normal, not disqualifying.

Now consider a candidate with 3 years of PM experience, B2B SaaS yes, no API work, no formal stakeholder management role:

• Must-have: 2/4 (50%)
• Preferred: 0/3

Must-have is 50%. Below the 70% bar. This is a wishful applier — the role is a real stretch, and unless they have an exceptional reason (a portfolio that demonstrates the missing skills, a referral) the math doesn't work.

The three-check decision

In practice, most candidates don't separate must-have from nice-to-have when reading a posting. They feel underqualified or qualified as a gestalt. The three-check version forces the actual analysis:

The first check (count the must-haves you have) is the highest-leverage move in the whole post. Most "I feel underqualified" judgments dissolve once you actually count.

What this isn't

A few things this rule doesn't say:

• It's not "apply to anything." Volume matters, but volume of bad-fit applications wastes time on the recruiter's side and your own. The 70% bar is exactly that — a bar.
• It's not "ignore the nice-to-haves." Mention them when they're true. They tip a "stretch" application toward "solid." But don't let them disqualify you from applying.
• It's not "fake the requirements you don't have." That's a separate problem — see the tailoring piece on the line between matching and lying. The 70% rule is about applying when you don't meet every listed thing, not about claiming things you haven't done.

Once you've applied

Apply at 70% — and treat the gaps as known. When the recruiter calls, you don't pretend the missing requirements aren't missing. You explain how the experience you do have addresses what they're asking for, and what you'd need to ramp on.

In our experience, recruiters respect this. Pretending to meet a requirement you don't is a fast way to get marked unreliable. Naming the gap and showing how the rest of your experience compensates is the move that lands stretch applications.

The 70% rule isn't permission to apply more aimlessly. It's permission to apply when you're a credible stretch — and to skip when you're not.