You Don't Meet Every Job Requirement. Should You Still Apply?

Short answer: if you meet the genuine must-haves and roughly 60–80% of the full list, apply — that is the normal profile of a serious candidate, not an impostor. Requirement lists describe an ideal person who rarely exists; hiring managers write them as a wish list, then interview the closest real matches. The skill you actually need is not "meet everything" — it is telling the three requirements that are non-negotiable apart from the seven that are trainable.

Here is how to make that call in about ten minutes, before you spend an evening on the application.

Why the list is longer than the job

Job ads are written to filter, and often by committee: the hiring manager adds what the job needs, HR adds what the last person had, and someone adds "nice to have" items that migrate into the requirements block over time. The result is a description of an ideal candidate — one who, if they existed, would probably want more money than the position pays.

Recruiters know this. That is why they routinely interview candidates who match well but not perfectly, and why "we hired someone who grew into it" is one of the most common hiring stories there is. When you treat every bullet as a hard gate, you are applying a stricter filter to yourself than the company will.

The practical consequence: the question is never "do I meet everything?" It is "do I meet the right things?"

Step 1: Find the knockout criteria (two minutes)

Some requirements really are binary, and pretending otherwise wastes everyone's time. Scan the posting for these:

• Legal authorization. If the posting requires an existing Swiss work permit and you would need third-country sponsorship, that is a real gate — read how to handle permit status honestly before deciding. (EU/EFTA citizens: your citizenship usually is the authorization; that line rarely knocks you out.)
• Licenses and protected qualifications. Driving licenses, FINMA-relevant certifications, medical or legal credentials, safety certificates. No workaround exists.
• Hard language thresholds. "German C1 required" for a client-facing role in Zürich means it. "Good English a plus" does not.
• Non-negotiable seniority. "Minimum 5 years leading teams" for a role that is team leadership is structural. "5+ years' experience" for an individual contributor role is usually a preference — see below.

If you fail a genuine knockout: don't apply for this one, and don't take it personally. Everything else on the list is negotiable evidence, not a gate.

Step 2: Sort the rest into three piles (five minutes)

Take the remaining requirements and sort each one:

Core — mentioned in the title, the first paragraph, or repeated more than once. These define the job. You want to match most of these clearly.

Supporting — real but secondary: a tool, a methodology, an industry. Adjacent experience usually counts here. Someone who ran projects in Jira can run them in another tool; a recruiter knows that even when the posting doesn't say so.

Wish list — "a plus", "ideally", "would be an advantage", or anything that reads like the last person's biography ("experience with our specific ERP setup"). Missing these costs you almost nothing.

Now count honestly: if you clearly match most of the core pile and at least half of the supporting pile, you are in the zone where applications succeed. If you are stretching to claim even the core items, the posting is telling you something — and there is a more rigorous way to measure exactly this.

Step 3: Translate your experience — never inflate it

The most common mistake in the 60–80% zone is not applying with gaps. It is papering over the gaps with vague claims. The opposite move works better:

• Map your vocabulary onto theirs. If they say "stakeholder management" and you have "coordinated between clients, engineering and management" — that is the same competence in different words. Say it in their words, backed by your example. That is tailoring, not lying.
• Address one real gap head-on, in the letter, briefly. One sentence: acknowledge, then counter with your strongest adjacent evidence. Confidence with honesty reads as senior; silence reads as either oblivious or hiding.
• Career changers: your match calculation runs differently — transferable competencies weigh more, tool checklists less. We wrote a dedicated guide for applying as a career changer in Switzerland.

What never works: claiming the missing experience outright. Swiss interviews are thorough, references get called, and Arbeitszeugnisse put your actual history on paper. An invented competence doesn't survive contact with a second interview.

The shortcut, if you do this weekly

Everything above is doable by hand with the posting in one window and your CV in the other — that is exactly how we recommend doing it the first few times, because the judgment is the skill. If you are applying to several positions a week, this analysis is also the step that automates well.

Frequently asked questions

Is there an official percentage of requirements I should meet? No — the popular "women apply at 100%, men at 60%" statistic is a survey anecdote, not a hiring rule. The honest version: meet the knockouts, most of the core requirements, and enough of the rest to argue your case in one paragraph.

Does applying anyway hurt me with that company later? A reasonable near-miss application does not blacklist you — recruiters see thousands. What does leave a mark is a chaotic application that ignores obvious knockouts (no permit, no required language). Judgment, not volume, is what gets remembered; if you're RAV-registered, quality is literally what's assessed.

Should I mention gaps in the cover letter or hope nobody notices? For core requirements: address the biggest one briefly and confidently. For wish-list items: say nothing. A letter that apologizes for five missing bullets talks the reader out of an interview they were ready to give you — here is how to write one that doesn't.

What if I match nearly everything — am I overqualified? Different problem, same method: check whether the seniority signals (title trajectory, salary band, scope) point below your level. Slight overmatch is a strong application; a full level of overmatch deserves an honest sentence about why the role attracts you anyway.