How to Know If You're Qualified for a Job Before Applying

The 70% Rule (and Why It's Not Quite Right)

You've probably heard the advice: "Apply if you meet 70% of the requirements." It's a decent starting point, but it treats all requirements equally. They aren't.

Meeting 70% of the bullet points means nothing if the 30% you're missing includes the core technical skill. Which requirements you meet matters more than how many. A data analyst role that lists SQL, Python, Tableau, and "experience with stakeholder presentations" has one real dealbreaker in that list. The presentation skills? They can teach you that in a week.

Here's a better way to think about it. Picture two candidates applying for a marketing manager role. Candidate A meets 8 out of 10 requirements but is missing "Google Ads experience" and "team leadership." Candidate B only meets 6 out of 10 but has both Google Ads and team leadership covered. Candidate B gets the interview almost every time. The percentage doesn't matter. The coverage of core skills does.

• •Hard technical skills in the first 3 bullets are usually non-negotiable
• •Years of experience is the most flexible requirement. 3 years vs 5 years rarely matters if your work is strong.
• •Industry experience is preferred but almost never required. Skills transfer.
• •Soft skills listed in job descriptions are filler 90% of the time

Must-Haves vs Nice-to-Haves

Most job descriptions don't label which requirements are required and which are preferred. You have to read between the lines. Here's what to look for.

The language tells you everything. "Must have" and "required" mean what they say. "Preferred," "bonus," and "ideally" mean they'll consider you without it. But the tricky ones are the requirements that don't use any qualifier at all. Those are usually listed in order of priority.

• •Top 3 bullets in the requirements section carry the most weight
• •"Or equivalent experience" after a degree requirement means the degree isn't required
• •"Familiarity with" vs "proficiency in" is a huge difference. Familiarity means you've used it. Proficiency means you could teach it.
• •Anything in a "bonus" or "nice to have" section is genuinely optional. Don't skip a job over those.

What Actually Disqualifies You

Let's flip it around. Instead of asking "am I qualified enough?" ask "is there a reason they'd immediately reject me?" That's a more useful question.

Real disqualifiers are rare, and they're usually obvious. If a job requires a nursing license and you don't have one, that's a disqualifier. If they need someone in New York and you're in Seattle with no plans to relocate, that's a disqualifier. Most other things are negotiable.

Here's the math that puts it in perspective. Say a job lists 10 requirements. Two are legal or licensing requirements, three are core technical skills, two are "preferred" experience, and three are soft skills. You really only need to worry about those first five. If you clear those, the remaining five are bonus points, not gatekeepers. Too many people talk themselves out of applying because they're missing "preferred" items that the hiring manager would happily train someone on.

• •Legal requirements (licenses, certifications, security clearances) are real blockers
• •Location with no remote option is a real blocker
• •Missing the core skill entirely (applying for a Python developer role when you only know JavaScript)
• •Seniority mismatch by 2+ levels (applying for VP when you're an individual contributor)

A Quick Scoring Framework

Here's a practical way to evaluate whether you should apply. Go through the job description and sort every requirement into one of three buckets.

• •Green (I have this): You can demonstrate this skill with real examples from your work
• •Yellow (I'm close): You've done something similar, or you could learn this quickly
• •Red (I don't have this): You have no experience and can't fake it

How ShouldApply Does This for You

That green/yellow/red framework works great when you do it manually, but it takes time. You have to read the full job description, identify each requirement, compare it against your experience, and decide which bucket it falls into. For one job, that's fine. For a dozen jobs a week, it adds up fast.

ShouldApply automates the whole process. Paste a job description and your resume, and it scores every requirement against your actual experience. Green for skills you clearly have, yellow for things you're close on, red for gaps. You get a single match score plus a breakdown of exactly where you stand.

The scoring isn't just keyword matching, either. If the job asks for "content strategy" and your resume says "developed editorial calendars and managed a 50-post blog," ShouldApply recognizes that as a match. It reads context the way a human recruiter would, not just ctrl+F for exact words.