Should You Apply If You Don't Meet All the Requirements?

Should you apply if you don't meet all the requirements?

Usually yes. The requirement list on a posting is a wish list written before the role was fully defined. If you meet the core requirements and can point to experience that covers the gap, apply. The exceptions are hard credentials: licenses, certifications, or degrees the role legally requires.

Nothing in the system is auto-rejecting you for a missing line item. In Enhancv's study of 25 recruiters, 92 percent said their ATS does not auto-reject, and Huntr's analysis of 1.7 million applications found no major screening system removes candidates without a human decision. The rejection you fear is usually a human reading a resume, which means your framing of the gap matters more than the gap itself.

That is the honest version of the "apply anyway" advice: not that every application wins, but that an application you can defend beats a self-cancelled one. Most people who feel they are applying into a black hole have talked themselves out of the applications that fit, and spent the saved energy on ones that never did.

Why the "apply anyway" advice exists (and when it is wrong)

The advice exists because hiring managers over-specify. They paste in skills from the last hire, add the tools the team hopes to adopt, and leave the list online long after the real need narrowed. The result is a posting that describes nobody, and a rule of thumb that says apply at 60 to 70 percent match.

The advice goes wrong when it becomes spray-and-pray. Blanketing every posting, including ones where a hard credential is missing, turns each submission into a lottery ticket. That is how people end up at 110 applications to 1 interview: volume without a filter. The fix is not to stop applying, it is to apply where the match is real and defensible.

Required vs preferred qualifications: how to tell the difference

Start with the words. "Must have," "required," and "essential" signal the floor. "Preferred," "nice to have," "a plus," and "or equivalent" signal the wish list. When a posting says "5+ years" but the team would take 3 strong years with proof, the number is softer than the word that frames it.

Then look at the consequence of missing it. Can the company train it? Is it a tool anyone can pick up in a month? Those are preferred skills in disguise. If missing the item would stop you from doing the core job on day one, it is required. A required item is a reason to pause; a preferred item is a reason to think about how you present the skills you have.

The 60-70% rule: where it comes from and how to use it

The rule of thumb that you need to meet only 60 to 70 percent of requirements to apply has circulated in career advice for years, from The Muse to Hays to Harvard Business Review's coverage of the question. It is a heuristic, not a measured threshold: a way to stop strong candidates from filtering themselves out.

Real data points the same way. One applicant's 512-application tracker found an interview rate of roughly 1.3 percent when match was below 60 percent versus about 15 percent when it was 80 percent or higher. The pattern is not that low matches never work, it is that the return is dramatically better where the fit is real. Use the rule to sort your list: spend the deep tailoring on the 70 percent and above.

When you should absolutely NOT apply

Skip the posting when a hard credential is non-negotiable. Licensed roles (nursing, teaching, law, medicine), regulated work, and jobs where the "requirement" is a compliance gate are not wish lists. Applying there is noise for the recruiter and a wasted evening for you.

Also skip when the gap is the core function. If the role is senior engineering and you have never written production code, no phrasing makes that true. That is not a judgment on you; it is a mismatch between the role's floor and your current experience. The useful move is to find the adjacent role you can actually defend, and grow toward the bigger one.

How to write the resume when you are missing a preferred skill

Do not hide the gap and do not fake it. Address it by leading with the experience that covers the function: the project where you used a comparable tool, the result you delivered that mirrors what the role needs. Recruiters reading for fit want to see the closest evidence you have, not a confession paragraph.

Name the missing item once, in context, with the equivalent. "Figma: fluent in Sketch and Adobe XD, picked up Figma on a client project" reads as capable. A blank where the skill should be reads as a gap. And keep the whole file honest: Resume Genius's 2026 survey found 80 percent of hiring managers say they can spot AI-written resumes, so a paste of job-description keywords without real substance gets recognized, not rewarded.

Jobbris (https://jobbris.app) helps you put that experience in order, so a gap in the preferred column does not hide the strengths you do have. Your experience, intelligently emphasized. Nothing invented.

The overqualified flip side: what managers actually worry about

The mirror image of under-qualification is overqualification, and job seekers feel it as a rejection: "overqualified has become my most frustrating rejection," as one Reddit thread put it. Managers hesitate because they fear retention, boredom, and salary expectations, not because they doubt you can do the work.

If you are applying a level or two down, address that worry directly. Say why this role fits your life right now: the industry, the commute, the stage of the company, the problem they work on. A manager's real question is "will this person stay," and a specific, honest answer beats a generic "I'm just looking for stability." The decision stays theirs, but you stop letting an unstated fear end the conversation.