Should I apply if I don't meet every requirement?

~52%

Average threshold where men decide to apply

Behavioural Insights Team, 2022

4.7%

Of applicants meet 80%+ of listed requirements

Lighthouse Hiring AI, 2026

16%

Higher hire rate for women vs men after applying

LinkedIn / FlexJobs

The myth of the perfect match

You have probably heard the rule: men apply when they meet 60% of qualifications, women only at 100%. It sounds authoritative. It is also wrong. The statistic traces back to a speculative comment by a Hewlett Packard executive, not a study. When researchers actually measured it, the gap was far smaller — and the real story is more useful.

The more important point: most job postings are written as wishlists, not contracts. Hiring managers know they will not find someone who checks every box. They are looking for the closest reasonable fit who can learn the rest. Treating requirements as mandatory is a common mistake that filters out good candidates before the process even starts.

What the research actually shows

A 2022 study by the Behavioural Insights Team tested over 10,000 job seekers and found that men typically apply when they meet about 52% of requirements, women at about 56%. The difference is real but small. Both groups apply well before hitting 100%.

Meanwhile, Lighthouse Hiring AI analyzed 50,885 applicants against structured hiring criteria and found that 66.4% met less than 40% of requirements. Only 4.66% met 80% or more. In other words, nearly everyone who applies is partially unqualified. The people who get hired are not the ones who match everything — they are the ones who match enough and make a credible case.

Should you apply? A quick checklist

Use this before deciding to skip a posting. If you hit at least three of these, apply.

1. You meet 50% or more of the core requirements. Not every bullet point — the ones that matter. If the role asks for Python, SQL, and AWS, and you have two of three, that is enough.
2. You have a transferable skill that covers the gap. You do not know AWS yet, but you have deployed to GCP or Azure and can learn the console in a week. Say so.
3. The missing requirement is learnable in under 90 days. If the posting asks for a specific CRM you have not used, that is different from asking for five years of M&A experience.
4. You can point to one concrete result that maps to the role. Numbers work best: "built a dashboard that reduced reporting time by 40%" beats "familiar with data tools."
5. The role is not wildly above your level. A senior position when you have zero experience is different from a mid-level role when you have one year. Apply to stretch roles, not unrealistic ones.

How to pitch yourself when you are not a perfect match

Do not apologize for gaps. Redirect attention to what you do bring.

• Lead with the overlap. In your cover letter or application, start with the requirements you meet, not the ones you lack.
• Name the gap and close it. "I have not used Salesforce directly, but I administered a HubSpot instance for 200 users and migrated data between three platforms. I can get certified before start date if needed."
• Show learning velocity. One recent project in a new stack is worth more than three years in a stagnant one.
• Use the job description language. If the posting says "cross-functional collaboration," say that exact phrase back with a specific example. It signals fluency.

Frequently asked questions

What if the posting says "required"? "Required" in job postings is often aspirational. Unless it is a licensed role (nursing, law, aviation), apply if you are close. The worst outcome is silence. A good outcome is an interview.

Should I mention the gap in my cover letter? Only if it is obvious and large. If you have 1 year and they ask for 3, do not mention it — let your results speak. If you are missing a major skill, address it briefly with a concrete plan.

What if I have zero experience in the field? Then focus on adjacent experience. Customer support to sales, teaching to training, analytics to product. Map your existing skills to the role's outcomes.