Often, yes, but not for the reason most advice gives. The usual answer is about confidence: apply anyway, don’t sell yourself short. The more useful answer is about the list itself: most requirements lists mix genuine dealbreakers with items that are really a wish list, and which half you’re missing matters far more than how many lines you’re missing in total.
Meeting eight of ten requirements where the two you’re missing are both dealbreakers is a weaker application than meeting five of ten where every missing item is a nice-to-have. The count on its own tells you almost nothing.
Where requirements lists actually come from
A requirements list is rarely written by the person who will read the applications, and it is almost never written from scratch for one role. It typically starts as a template from a similar past posting, gets added to by whoever is sponsoring the role, sometimes without much editing down, and by the time it’s published it often contains more than the hiring manager would insist on if asked directly about any single line.
That is not a criticism of how hiring works. It is a practical fact about where the document comes from, and it means the list in front of you is closer to “everything that came to mind” than to “the exact and complete bar for this role.”
The requirements that are usually real
A specific license, certification, or legal eligibility to work. These exist because the role cannot legally or practically be done without them, not because someone wanted a longer list. If a requirement of this kind is missing, that is a genuine reason to reconsider applying, not a confidence problem.
A hard skill the job cannot function without on day one. If the role has no ramp-up time built in and requires fluency in a specific tool or system from the start, and you have never used it, that gap is real, not a formality.
Years of experience stated as a floor for a genuinely senior role. For roles where seniority itself is the qualification being screened for, a large gap on years of experience is often a real signal, not padding.
The requirements that are usually a wish list
A long list of specific tools or platforms alongside a broader skill. If a posting asks for five named tools that all do a similar job, the underlying need is usually competence with that category of tool, not every named product on the list.
Soft skills stated as requirements. “Excellent communication skills” and “strong stakeholder management” describe qualities almost every candidate claims and few postings actually screen hard for at the application stage.
A slightly higher years-of-experience number than the role clearly needs. Many postings round up on years of experience the same way people round up on salary expectations, as a starting position rather than a firm bar.
What the useful decision actually looks like
The question worth asking is not “how many boxes do I tick” but “which of the boxes I don’t tick would actually stop this role from working.” If the gaps are in the wish-list category, applying is a reasonable use of your time. If a gap sits in the dealbreaker category, the better use of that time is usually a different posting where it doesn’t. The answer to a partial match is usually a tailoring decision about which parts of your experience to lead with, not a decision about whether to apply at all.
The short version
Requirements lists are not written the way candidates assume, and treating every line as equally firm leads to skipping roles you’d have a real shot at. A missing license or a hard day-one skill is worth taking seriously. A long tool list or a slightly high years-of-experience number usually isn’t. Sort the gap before deciding whether to apply.
We don’t judge which requirements matter for you. What we build is a way to reshape your CV around the parts of your experience that do match a given posting, which is the part of this decision that’s actually worth spending time on once you’ve decided to apply.