You find a job you want. You read the requirements. You meet six of nine. Do you apply?
Yes, almost always. But which three you are missing changes everything, and the way you handle them in your application decides whether it works.
How a requirements list is actually written
A job ad's requirements section is rarely a checklist of hard minimums. It is usually written by combining what the team needs, what the last person in the role had, and what the hiring manager would like in an ideal world. Very few candidates match all of it, and hiring teams know this when they write it.
German postings often signal this themselves. Look for the split between:
- Muss / zwingend erforderlich / Voraussetzung — genuine requirements
- Wünschenswert / von Vorteil / idealerweise — nice to have
If a skill sits under wünschenswert, missing it is not disqualifying. If it sits under Voraussetzung, take it seriously.
The three kinds of gap
Not all gaps are the same, and treating them identically is where applications go wrong.
1. Hard gaps. Legal or formal requirements: a specific degree, a professional licence, a work permit, a recognised qualification, sometimes a certified language level. These are usually genuine. Applying without them is normally wasted effort, and no amount of good writing fixes them.
2. Experience gaps. "Three years of experience" when you have none. These are softer than they look. Years are a proxy for competence, and a hiring manager will trade years for demonstrated ability, especially in a student, graduate or Werkstudent role where nobody expects three years anyway.
3. Skill gaps. A named tool, language or method: SQL, Python, a CAD package, a testing framework, a specific analysis method. These are the most fixable and the most commonly mishandled.
What most students do with a skill gap, and why it backfires
Two failure modes.
Option A: don't apply. The most common, and the most expensive. You disqualify yourself from a role you could have got because of one line in an ad that was probably marked wünschenswert anyway.
Option B: claim it anyway. Add "SQL" to the skills section and hope. This survives exactly until someone asks a follow-up question, and in German hiring the follow-up question is very likely. Interviewers here tend to probe specifics rather than take a claim at face value. Being caught inflating a skill does not just cost you that role, it costs you credibility for everything else on the page.
The third option
Close the gap, then say so.
A skill gap is one of the few problems in a job search you can genuinely fix in a short amount of time. Not to expert level. To the level of having done something real with it that you can show, describe and defend.
This is what ProoV is for. You do a real, company-style project in the specific skill, your work is evaluated against a rubric, and you get a certificate with a public verification page that a recruiter can check independently. The gap goes from a hole in your application to a line that reads: I did not have this, so I did a project in it, here is the evidence.
That sentence is stronger than having quietly had the skill all along. It shows the skill and it shows how you respond to a gap, which is the thing a hiring manager is actually trying to work out about a junior candidate.
Finding the gap that is actually worth closing
Do not fix gaps one posting at a time. Fix the one that repeats.
Collect the five to seven postings you genuinely want. List every requirement. Count how many ads ask for each one. The requirements appearing in most of them are your real target profile, and the highest-frequency one you cannot evidence is your next project. Anything appearing once is noise.
The German Application Builder does this ranking for you: paste two to seven real job ads, and it ranks the shared requirements with each ad's verbatim line as evidence, then marks each one covered, partial or missing against your own CV. It is deliberately blunt about which is which.
How to write about a gap you have closed
In the Anschreiben, briefly and without apology. Name the requirement, say what you did, point at the evidence.
Für die ausgeschriebene Position ist SQL zentral. Da ich hierzu bisher nur Lehrveranstaltungen vorweisen konnte, habe ich ein vollständiges Analyseprojekt mit SQL bearbeitet und zertifiziert abschließen lassen; die Verifikation ist unter [Link] einsehbar.
Three things happen in that sentence. You show you read the ad properly. You show initiative. You hand over something checkable.
What about a gap you have not closed?
Leave it out of the cover letter and do not draw attention to it. There is a real difference between honesty and volunteering your weakest point unprompted. If it comes up in interview, answer plainly: you have not worked with it, here is the closest thing you have done, here is how quickly you picked up the last comparable tool.
What you must not do is claim it in writing.
The rule of thumb
Apply if you meet the hard requirements and most of the Voraussetzung items, even with an experience gap. Close the skill gap that keeps recurring across the roles you want, and say so plainly.
Six out of nine with one gap visibly closed beats nine out of nine that nobody can verify.