Applying to a Role You Are Not Fully Qualified For
Postings describe an ideal that rarely exists. Which requirements are binary, which are aspirational, and how to apply without pretending.
Job postings list an ideal candidate assembled from several people's wishes. Very few applicants meet all of it, and the people who get hired frequently did not. For a workplace perspective on stereotyping and assumptions, consult workplace stereotyping.
The useful question is not whether you meet everything. It is which of the things you are missing are binary. For an independent public reference, consult CareerOneStop job-application guidance.
The two categories
Binary requirements end the application. Work authorisation, a required licence or registration, a specific qualification the role legally needs, minimum years where a filter is set. These are usually asked as screening questions and they are checked. See screening questions.
Everything else is a preference, in practice — the long list of technologies, the soft skills, the "nice to have" section, and frequently the years of experience where no filter is set.
Learn to tell them apart. Repetition, position in the posting, and whether it appears in the title. See reading a job description.
The threshold
If you meet the binary requirements and most of what is genuinely central: apply.
If you meet the binary requirements and about half of the central things, with a good reason: apply, and address it.
If you fail a binary requirement: do not. It will not be waived, and applying wastes your time.
If you meet everything comfortably, consider whether the role is a step forward or a lateral move that will bore you within a year.
What to do about the gap
The part that decides whether the application works.
Name it, briefly, rather than hoping it is missed. A reader who spots a gap you have not mentioned wonders whether you noticed. One you address reads as self-aware.
Show the adjacent thing. Most gaps have a nearest equivalent: a different tool in the same category, the same work at smaller scale, the same responsibility under a different title.
The posting asks for Salesforce. I have used HubSpot for four years, which covers the same ground, and I would expect a short ramp-up.
Do not overstate the equivalence. A reader who knows both will notice, and it costs more than the gap did.
Be specific about the ramp. "I would expect to be productive in this within a month" is a claim you can defend and it addresses their actual concern, which is time to contribution.
Put it in the cover letter, not the CV. The CV states what you have done. See cover letters.
What not to do
Do not claim experience you do not have. It is exposed by one follow-up question and it is the fastest way to lose a process you might have won. See where the line is.
Do not apologise. A letter that opens by explaining what you lack has framed the whole application around it.
Do not apply to everything on the theory that requirements are meaningless. They are not; the binary ones are binding and the central ones matter.
And do not talk yourself out of it over the fourth item in a preferred list. This is the more common error by a wide margin, and it disproportionately affects candidates who read requirement lists as checklists.
The confidence asymmetry
Worth stating plainly, because it changes behaviour.
People differ substantially in how completely they believe they must match a posting before applying, and the difference does not track actual capability. Some candidates apply at 50% and some wait until 100%, and the second group is not more qualified — they are more cautious about the same evidence.
If you are in the cautious group, the practical adjustment is to apply at the threshold above rather than at the point where you feel ready, and to let the employer decide.
They are the ones with the information about what the role actually needs, and they are the ones who wrote a list that describes nobody.
In the interview
Expect the gap to be raised. Prepare the answer rather than hoping.
Acknowledge it directly, say what is adjacent, and say how you would close it. Thirty seconds.
Do not oversell. "I'd need to learn it and I've learned comparable things quickly — here's an example" is stronger than claiming it is not a gap.
And have an example of learning something under time pressure. That is what the question is really asking about. See preparing for an interview.
When you are over-qualified
The mirror problem, and it is real.
Employers worry you will be bored, will leave, or will resent the level. Those are reasonable concerns and they need addressing rather than ignoring.
Say why you want this specific role — a deliberate step back, a change of field, a priority that is not seniority. Be honest, because the reason will be probed.
Be clear about compensation early, so nobody wastes time.
And expect it to be raised. Prepare that answer too.
The short version
Only the binary requirements are binding — authorisation, licences, mandated qualifications, filtered minimums.
Meet those and most of the central things, and apply.
Name the gap briefly, show the adjacent experience, and say how long the ramp would be.
Never claim experience you do not have — one follow-up question finds it.
And if you are the cautious type, apply earlier than feels comfortable, because the person who wrote the list already knows it describes nobody.