1The Difference Is Bigger Than You Think
Every job posting has requirements. But not all of them carry the same weight, and most postings don't make the distinction clear. "Required" and "preferred" mean fundamentally different things, yet companies often lump them together under one heading or use vague language that leaves candidates guessing.
Here's the basic breakdown. Required qualifications are the things you genuinely need to do the job on day one. The hiring manager wrote these with a specific person in mind. Preferred qualifications are the wishlist items. They'd love to find someone who has them, but they'll hire someone who doesn't. And "nice to have" means exactly that: genuinely optional, won't factor into the decision unless two candidates are otherwise identical.
The problem is that candidates treat every bullet point as a pass/fail test. They count the total requirements, calculate what percentage they meet, and decide whether to apply based on a number. That math doesn't work because it treats "must have 5+ years in B2B SaaS" the same as "familiarity with Figma is a plus." Those aren't in the same category.
2How "Required" Qualifications Get Written
Understanding who writes each part of the job description helps you decode what's actually required. In most companies, the hiring manager drafts the core requirements based on what they need. Then HR adds compliance language, and sometimes a recruiter adds items based on what's worked in past searches.
The hiring manager's requirements are the real ones. These are the skills and experience that directly map to the job's day-to-day responsibilities. If the role involves managing paid ad campaigns, "experience with Google Ads and Meta Ads" is a real requirement. The hiring manager needs someone who can step in and run campaigns without three months of training.
HR-added requirements tend to be more generic: "Bachelor's degree or equivalent experience," "strong communication skills," "ability to work in a fast-paced environment." These are often boilerplate that appears on every posting at the company. They're technically required on paper but rarely the reason someone gets rejected.
The recruiter-added items are where "preferred" qualifications tend to live. Based on the candidate pool from previous similar roles, the recruiter might add: "experience with HubSpot is a plus" or "MBA preferred." These reflect patterns they've seen in successful hires, not hard requirements from the hiring manager.
- Hiring manager requirements: Core technical skills, specific experience, tools you'd use daily
- HR boilerplate: Degree requirements, generic soft skills, legal compliance language
- Recruiter additions: "Preferred" qualifications, "bonus" items, industry-specific experience
3Decoding the Language
Companies don't always label their requirements as "required" or "preferred." But the language they use tells you everything if you know what to look for.
"Must have" / "Required" / "Minimum" = These are the real dealbreakers. If you don't have these, your application will likely get filtered out at the recruiter stage. These are non-negotiable in most cases.
"Experience with" / "Knowledge of" = Slightly softer than "must have." The hiring manager wants someone who's worked with this tool or concept, but "worked with" can mean different levels. If you've touched it in a real project, you probably qualify.
"Proficiency in" / "Expert-level" = Stronger than "experience with." This means the hiring manager expects you to be productive from week one without training. Don't claim proficiency if you'd need to Google the basics.
"Preferred" / "Ideally" / "Bonus" = Wishlist items. The hiring manager would love this but won't pass on a strong candidate who's missing it. These should never stop you from applying.
"Familiarity with" / "Exposure to" = The lowest bar. They want you to know what this thing is and have some context. A single project or a few months of experience usually counts.
"Nice to have" / "A plus" = Genuinely optional. If you have it, mention it. If you don't, don't worry about it for a second.
ShouldApply's scoring engine separates must-haves from nice-to-haves automatically. Paste any job description and see exactly which requirements carry real weight.
Decode a Job Posting4The Qualification Spectrum (With Examples)
Let's look at a real-world example to make this concrete. Here's a fictional but realistic "Marketing Manager" posting broken down by what each line actually means.
Required: "5+ years of B2B marketing experience." This is real. The hiring manager wants someone who understands long sales cycles, multiple stakeholders, and enterprise buyers. Could someone with 3.5 years of strong B2B experience get the job? Possibly. But 1 year of B2C experience won't cut it.
Required but flexible: "Bachelor's degree in Marketing, Business, or related field." The "or related field" part opens this up significantly. And at many companies, relevant experience without a degree is accepted. If you have the years of work experience, this one is rarely a hard stop.
Preferred: "Experience with Marketo or HubSpot." They use one of these tools and would prefer someone who already knows it. But if you've used a different marketing automation platform (Mailchimp, ActiveCampaign, Pardot), your skills transfer. Don't skip the application over this one.
Nice to have: "MBA or advanced degree preferred." This is almost never a dealbreaker for a mid-level role. It might matter for director-level and above at certain companies, but for a Marketing Manager position, your work results matter more than an extra degree.
Filler: "Strong communication and organizational skills." Every job posting includes some version of this. It's not a qualification you need to prove on your resume. It's something they'll evaluate during the interview.
5When Missing "Required" Qualifications Is Actually Fine
I know I just said required means required. But here's the nuance: companies regularly hire people who don't meet every "required" qualification. Studies consistently show that the final hire matches about 70-80% of the posted requirements.
There are a few situations where missing a "required" item won't hurt you. Years of experience is the most flexible requirement. If they ask for 5+ years and you have 3.5 with strong results, apply. Nobody is counting months. Your accomplishments speak louder than a number.
Industry experience is usually preferred, not required, even when they label it as required. A marketing manager from SaaS can move to fintech. A project manager from healthcare can move to tech. The core skills transfer. You just need to connect the dots in your resume so the recruiter can see the relevance.
The real dealbreakers are hard technical skills you can't learn in a few weeks (programming languages for engineering roles, licensed certifications for regulated industries) and security clearances or legal requirements. If you're missing one of those, the posting means what it says.
Stop guessing which requirements are firm and which are flexible. ShouldApply parses the job description and shows you exactly where you stand on each one.
Check Your Match6How to Address Gaps in Your Application
If you're missing a preferred qualification, the worst thing you can do is ignore it. The second worst thing is lie about it. The best approach is acknowledge the gap and redirect to a related strength.
In your cover letter or resume summary, try something like: "While my direct experience is in B2B SaaS rather than fintech, I've managed campaigns targeting enterprise buyers with 6-12 month sales cycles, which maps closely to the financial services buying process." You're not pretending you have fintech experience. You're showing that your experience is relevant.
For "preferred" technical tools you haven't used, mention adjacent tools and emphasize your ability to learn. "Experienced with HubSpot and ActiveCampaign; quick to pick up new marketing automation platforms" covers the gap without overstating your experience.
Don't waste space addressing "nice to have" items you don't have. Nobody is tracking whether you mentioned every optional qualification. Focus your application on the requirements that actually matter.
7The Decision Framework
Here's a simple framework for deciding whether to apply based on qualifications. I use this myself and recommend it to anyone who asks.
If you meet all the "required" qualifications and some of the "preferred" ones, apply with confidence. You're exactly who they're looking for.
If you meet most of the "required" qualifications (missing one or two non-core items) and have relevant transferable experience, apply. You're in the competitive range.
If you're missing a core "required" qualification (the primary technical skill or a legal requirement), skip it unless you have a strong reason to believe your background compensates. Your time is better spent on roles where you're in the strike zone.
And if you're debating whether a qualification is really "required" or secretly "preferred," paste the job description into ShouldApply. The scoring breakdown separates hard requirements from wishlist items, so you don't have to play detective.
Written by
Jesse Johnson
Founder, ShouldApply
Founder of ShouldApply. I write about job search strategy, hiring, and how to spend your time on opportunities that actually fit. Full bio →
Keep Reading
Frequently Asked Questions
Preferred qualifications are the hiring team's wishlist. They'd love to find a candidate who has these skills or experiences, but they won't reject someone who's otherwise strong. Think of it as bonus points on a test where you can still pass without them. In practice, preferred qualifications are most useful as tiebreakers. If two candidates are equally qualified on the required items, the one who also has preferred qualifications gets the edge. But a candidate who nails the required qualifications will almost always beat someone who has the preferred ones but is weak on the core requirements.
Yes, absolutely. Preferred qualifications are not meant to discourage you from applying. They exist to help the company find the best possible candidate, but "best possible" doesn't mean "checks every box." If you meet the required qualifications and can make a strong case for your experience, apply. I'd estimate that 40-50% of hires are missing at least one preferred qualification. It's the required ones that gatekeep. Preferred ones influence ranking, not elimination.
Look at where it appears and how it's worded. True requirements tend to be listed first, use strong language ("must have," "required"), and directly relate to the job's core function. If a qualification appears later in the list, uses softer language ("ideally," "experience with"), or seems tangential to the main role, it's likely preferred even if it's not labeled that way. Another trick: if the qualification appears in both the requirements list AND the role summary, it's almost certainly a hard requirement. If it only appears in the requirements list, it might be padded in.
In most cases, yes. When a company writes "Bachelor's degree or equivalent experience," they're signaling that the degree is a proxy for a certain level of knowledge and professional maturity, not a strict requirement. The hiring manager typically cares about what you can do, not where you learned to do it. That said, some industries and roles do require specific degrees for regulatory or licensing reasons. Healthcare, engineering, and finance roles may have hard degree requirements. For everything else, "or equivalent" is a genuine invitation to apply if your experience compensates.
ShouldApply's scoring engine analyzes the language patterns in the job description to classify each requirement. It looks at position in the list, keyword signals ("must have" vs "nice to have"), and the relationship between the requirement and the role's core function. Requirements classified as must-haves carry more weight in your match score, while preferred items contribute less. This means a candidate who nails the must-haves but misses some preferred items will still score well, accurately reflecting how most hiring decisions work in practice.
Free Tools
Related Posts
How to Know If You're Qualified Before Applying
A scoring framework for deciding if you have a real shot at the role.
Should I Apply If I'm Underqualified?
A data-backed answer on when gaps are dealbreakers vs bridgeable.
How to Read a Job Description
What companies actually care about vs what's filler in a posting.
Know what's required. Skip the guessing.
ShouldApply parses any job description, separates must-haves from nice-to-haves, and scores your resume against each one. See exactly where you stand before you apply.
Try It Free