The short answer: You don't need to meet every requirement to be a strong candidate. Many job descriptions are wish lists, and employers often hire people who are strong where it matters most. But you do need to meet the truly essential requirements, like a required license or work authorization, and be able to show evidence for the core work. Weigh the requirements instead of counting them.
You find a job that genuinely interests you. You understand most of the responsibilities. You can picture yourself doing the work.
Then you reach the qualifications. They want eight years of experience; you have six. There's a platform you've never used. Industry experience is preferred, and you're coming from somewhere else.
So you close the tab without applying.
This happens every day. Qualified people talk themselves out of good opportunities because they read a job description as a checklist. Meanwhile, others hear "you don't need to meet every requirement" and take it as permission to apply to almost anything.
I've seen this from the hiring side. I was once hiring a senior product manager for a specific domain, and the resume that stood out came from someone who'd never worked in it. She was a senior product manager in a different domain, but her resume showed clear evidence of scope and experience. Domain experience was a preferred requirement, not a must-have. Meanwhile, several candidates who did come from the domain couldn't show evidence of their impact, or that they understood the problem we were hiring for. I hired her.
Both extremes cause problems. The question isn't "Do I meet every requirement?" It's "Do I understand what this company needs, and can I show I can deliver it?"
Is a job description an accurate list of what the job needs?
Not always. Job descriptions are often written by a recruiter rather than the hiring manager, copied from an older role, stitched together from several stakeholders' wish lists or written before the team fully agreed on what it needs. Some describe an ideal candidate who may not exist.
A company might ask for ten years of experience, five platforms and three industries, then hire someone who doesn't match every line but is especially strong in what matters most. That doesn't mean you should ignore job descriptions. It means you should interpret them.
Does every requirement matter equally?
No, and treating them as equal is one of the biggest mistakes candidates make. Most requirements fall into one of four types.
Mandatory requirements. These are conditions the employer can't or won't change: a legally required license, work authorization they can't sponsor, an active security clearance, a required location or schedule. If a role needs an active nursing license and you don't have one, transferable skills won't replace it. These gaps usually matter.
Core capabilities. This is the work the person must actually do. For a product manager, that might mean setting direction, prioritizing a roadmap, understanding customers, working with engineering and delivering measurable outcomes. Your title doesn't have to match if your experience proves you've done the work. But "I know I can do it if someone gives me a chance" is far less persuasive than showing where you already have.
Preferred qualifications. Look for words like "preferred," "ideally," "a plus" or "nice to have." These strengthen an application but don't usually decide eligibility. They matter more when many applicants already have them, but missing one isn't a reason to rule yourself out.
Trainable requirements. A collaboration tool, a related platform, a company-specific process or a certification you could earn in a reasonable time. The real question isn't whether you lack it. It's whether you could learn it quickly, and whether the employer expects you to arrive with it.
Does "required" always mean required?
Not always. An employer might list eight years of experience, a specific industry, a particular platform and a certain degree, then hire someone with six years of highly relevant experience, a comparable platform and proof of solving the same business problem.
That's because hiring isn't about who checks the most boxes. It's a comparison of whole candidates. One person has the exact industry background but weak leadership evidence. Another lacks the industry but has solved the same problem in a similar regulated environment. The employer decides which strengths matter most and which gaps it can live with.
Still, don't assume every requirement is flexible. Mandatory requirements usually aren't. Read the context.
What do "years of experience" really mean?
Years are usually a stand-in for a level of capability. When an employer asks for eight years, it often wants someone who can work independently, handle complexity, influence senior stakeholders, make hard decisions and take ownership quickly.
But years are easy to count and hard to trust. One person might repeat similar work for eight years. Another might take on growing responsibility, harder problems and bigger scope in five.
If you're slightly under the number but can show the expected level, the gap may not rule you out. If the role needs senior leadership and you haven't yet owned work at that scale, the gap is about more than time.
Don't fixate on the number. Ask what the employer expects those years to represent.
What if you've never used the exact tool they list?
It depends on the tool's role in the job. If it's central and takes deep expertise, the gap can be significant. If it's just the company's chosen platform for work you already know how to do, the gap is much smaller.
Say a role asks for a project management platform you haven't used, but you've run delivery in two comparable systems: configuring workflows, managing backlogs, tracking dependencies and reporting to executives. You can likely learn the new interface quickly, because you already understand the work underneath it.
Don't pretend you've used the platform. Explain the adjacent experience honestly:
Experienced in managing cross-functional delivery through comparable work management platforms, including backlog prioritization, dependency tracking and executive reporting.
That shows the gap is one of familiarity, not capability.
What if you're changing industries?
Industry experience can matter a lot in fields with complex regulation, specialized customers, high safety stakes or unique terminology. But industry experience isn't the same as industry capability. Your experience can transfer when the underlying problems are similar.
Financial services and healthcare are both heavily regulated. Retail and hospitality both depend on customer experience operations. Logistics and healthcare operations both involve complex, time-sensitive coordination.
A strong career changer doesn't say, "I don't have industry experience, but I'm a fast learner." They explain the bridge: which problems they've solved, which skills carry over, what's different about the new context, what they've already done to learn it and why an outside perspective could add value.
Transferable experience should be shown, not just claimed.
What percentage of the requirements should you meet?
There's no universal percentage. "Apply if you meet 60%" or "Never apply below 80%" sounds helpful because it simplifies the decision, but it treats every requirement as equal.
One candidate might meet nine of ten requirements and still lack the one legally required license. Another might meet six of ten, with all the essentials covered and only preferred qualifications missing. The second candidate is the stronger bet.
Don't count requirements. Weigh them. One missing essential matters more than three missing nice-to-haves.
And remember, being eligible isn't the same as being competitive. Eligible means you meet enough basics to be considered. Competitive means your experience compares well with the people you're likely up against. Stop asking only "Am I allowed to apply?" and start asking "How strong is the case I can make?"
How do you check your fit for a job?
Instead of calculating a percentage, sort the job description into four questions.
- What's essential? Identify the requirements the work can't happen without: legal qualifications, core technical expertise, work authorization, location, critical industry knowledge. Be honest about any gaps here.
- What can you prove? For each major responsibility, find evidence. Where have you done this? At what scope? What changed because of your work? Don't count something as a match just because it sounds familiar.
- What's transferable? Look for experience that isn't identical but is relevant: a comparable tool, a related industry, an adjacent function, the same kind of business problem. Then check that you can explain the connection without stretching it.
- What's genuinely missing? Face the gaps. Is each one essential? Could you learn it quickly? Would the employer reasonably train someone? Does another strength make up for it?
Knowing your gaps helps you make a better decision, and it prepares you to discuss them with confidence in an interview.
Should you apply, strengthen first or skip a stretch role?
Once you understand the requirements, choose one of three actions. (We cover this framework in more depth in Mass Applying Is Not a Job Search Strategy.)
Apply when you meet the essential requirements, your experience lines up with the main responsibilities and your gaps are limited, trainable or balanced by real strengths. You don't need perfect alignment. You need credible alignment.
Strengthen first when you need to find out whether a requirement is truly essential, your resume doesn't yet explain your transferable experience, you need clarity on location, sponsorship or pay, or the role is a stretch that deserves a more thoughtful application. This doesn't mean putting it off forever. It means preparing before you submit.
Skip when you lack a mandatory license or qualification, can't meet the location or schedule, can't work there legally, are far above or below the level or lack most of the core capabilities. Skip it, too, if your only reason for applying is that someone told you to "shoot your shot."
Confidence is valuable. But confidence doesn't turn an unsuitable role into a good opportunity.
How do you apply when you don't meet every requirement?
Lead with your strongest alignment. Your summary and recent achievements should connect directly to the role's main priorities, so your best evidence is the first thing a recruiter sees.
Translate adjacent experience. Don't expect the recruiter to connect the dots. If your experience comes from a different industry, tool or function, spell out how the underlying skills relate.
Address the business problem. Look past the list of duties to what the employer needs this person to accomplish, then show where you've solved something similar.
Don't apologize for every gap. Your resume doesn't need to announce what you lack. If a real gap comes up in an interview, address it honestly and explain how you'd close it.
Never manufacture qualifications. Don't inflate a job title, claim a certification you don't hold or pretend you've used a system you haven't touched. A strong application makes the best case using the truth.
Start closing reasonable gaps. Take a relevant course, study the industry, try a free version of the platform, build a small project or talk to people in the field. Don't claim mastery after a short course, but showing initiative makes your interest more believable.
Is it a stretch, or a fiction?
A good stretch role asks you to grow: operate at a slightly larger scale, learn a new platform, enter an adjacent industry, manage broader stakeholders or take on more ownership.
An unrealistic application asks you to be someone else: hold a license you don't have, show expertise you've never built, lead far above your experience or do work unrelated to your background.
There's a difference between growth and fiction. Don't reject yourself just because you'd need to grow into part of the role. But the employer should still see the person you are today as a credible foundation for the person the role requires.
The goal isn't to be a perfect match
Very few candidates match every line of a job description. Hiring involves trade-offs. One candidate brings deeper industry experience, another stronger leadership, another an unusually good understanding of the customer, another a valuable outside perspective.
Your job isn't to become every possible candidate. It's to understand the role and present the strongest, most truthful version of your fit.
Before you rule yourself out, ask: Do I meet the essential requirements? Can I do the core work, and what's my evidence? Which gaps really matter, and which are trainable? Can I explain my transferable experience? Is this role aligned with where I want to go?
If you can answer those well, you may have a stronger case than a checklist suggests.
Frequently asked questions
Should I apply if I don't meet all the requirements?
Often, yes. Many job descriptions are wish lists. Apply if you meet the essential requirements, can show evidence for the core work and your gaps are limited or trainable.
What percentage of job requirements should I meet?
There's no reliable percentage, because requirements aren't equal. Missing one essential requirement, like a required license, matters more than missing several preferred qualifications.
What's the difference between required and preferred qualifications?
Required qualifications are usually needed to do the job or be eligible for it. Preferred qualifications strengthen your application but don't usually rule you out on their own.
Can I apply if I have fewer years of experience than listed?
Often, if you can show the level of capability those years represent, such as independent ownership, complexity and stakeholder influence. A large gap in senior-level experience is harder to bridge.
How do I apply for a job in a new industry?
Show the bridge between industries: the similar problems you've solved, the skills that transfer, what you've done to learn the new industry and why your outside perspective adds value.
Understand your fit before you decide
A job description shouldn't scare you away from a strong opportunity, or push you toward one that was never realistic.
SBMark helps you separate essential requirements from preferences, spot your transferable experience and understand where you're strong, where you have gaps and what those gaps actually mean.
Don't reject yourself too early. Don't apply blindly either.