Let me start with the story that still bugs me. A friend of mine (sharp engineer, six years in, honestly better at distributed systems than I’ll ever be) spent three months getting nowhere with her German job hunt. Forty-odd applications, two replies. When she finally gave up and sent me her CV, I understood the problem in about four seconds. Two columns. A headshot she’d paid a real photographer for. Little skill bars, “React ▮▮▮▮▯”. And up top, bold, the kiss of death: “results-driven, passionate engineer with a track record of excellence.” It was a gorgeous American résumé. In Germany it was getting binned before a human looked at it.
We rebuilt the thing in one evening. Barely touched the content. Same jobs, same numbers, same person on the page. We just made it German: single column, no photo, no adjectives, dates that actually add up. Four interviews in three weeks. Same engineer, remember. The only variable that changed was the document. That gap, the one between a good CV and a German CV, is the entire reason I sat down to write this.
And I’m not writing it from theory. I did this move myself, Amsterdam to Munich, start of 2024, my wife and me dragging eleven suitcases through Hauptbahnhof. Since then I’ve answered a truly depressing number of the same DM: “200 applications, zero replies, is Germany even real?” It is real. The vacancies are real. But most people lose the game at the document stage, before anyone has even judged their code, and they never find out why. So this is the why.
I already wrote the field manual on getting hired from abroad, which is the big-picture map: pipelines, ATS tricks, who actually sponsors. This is me zooming all the way in on one paragraph of that guide. Just the documents. How to build a Lebenslauf and an Anschreiben that a German recruiter reads as serious instead of foreign, in 2026, in a market that’s split down the middle: half of it wants a lean English CV now, the other half still wants the full formal German folder. Fair warning, I’m going to be a bit opinionated. Most of the CV advice on the expat forums is either a decade stale or lifted straight from a US career blog, and I’ve tried to keep this one pinned to what German employers and the government’s own Make-it-in-Germany portal actually say.
Two things worth doing before the wall of text: run yourself through the visa checker so you know which permit you’re even writing this CV for, and if you want real postings to tailor against, the tech jobs with visa sponsorship board is where I’d start. A CV aimed at a specific ad beats a generic one every time. Not sometimes. Every time.
One running example throughout, because abstract advice is useless: Priya. 29, backend engineer, from Pune, about four years of Go and Python, wants Berlin fintechs. She’s the same Priya from my Opportunity Card guide, German at A2 and grinding toward B1, and that A2-going-on-B1 status is exactly why she can’t get away with one CV. She needs two. Steal her structure, it’s all at the bottom as PDF and Word.
The one rule, and it governs everything else 🎯
Here’s the thing nobody tells you cleanly: Germany in 2026 runs two completely different hiring cultures at the same time, and applicants keep guessing wrong about which one they’re in.
Track one is the English-first scale-up. N26, Trade Republic, Personio, Zalando, Celonis, DeepL, basically the whole Berlin-and-Munich hub crowd. English is the working language, the forms are in English, usually no photo, and half the time no cover letter at all. Some of them literally just want a CV and a “why us?” text box. For these places a lean English CV isn’t you cutting corners. It’s the thing they actually prefer.

Track two is the traditional Mittelstand. The mid-sized, often family-owned firms, plus the stiffer end of the corporate world, plus banks, insurers, public sector. These still want the classic German Bewerbung: an Anschreiben, a proper tabellarischer Lebenslauf, and Anlagen (attachments), in German, usually with a photo. The whole folder.
So here’s the only rule you really have to memorise, and everything below is just detail hanging off it: write in the language of the ad, and match how formal it is. English ad, English CV. German ad, German Lebenslauf, but only if your German genuinely survives an interview (I’ll come back to that trap, it’s a real one). And when you’re staring at some named old-school employer and you can’t tell which track you’re on, go more formal, not less. Being slightly too buttoned-up for a Berlin startup costs you almost nothing. Firing a one-page American résumé into a Mittelstand system costs you a rejection you never even see land.
Priya is stuck straddling both, which is common. She’s applying to Personio-type scale-ups in English and keeping a German package loaded for the one Munich Mittelstand fintech she actually wants. So we build both off a single master profile and just swap the surface. That’s the model I’d give anyone: one source of truth, two versions rendered out of it. Don’t maintain two CVs from scratch, you’ll drift and contradict yourself.
Your Lebenslauf is a record, not a sales pitch 📄
If you fix one mental model, fix this one, because it quietly fixes about eighty percent of everything else. A German Lebenslauf is a factual record. An American résumé sells. Once that clicks, most of the fiddly little rules stop feeling arbitrary and start feeling obvious.

What German employers expect in 2026 is a tabellarischer Lebenslauf, meaning tabular and reverse-chronological, most recent job first, on one to two pages, as a PDF. Karrierebibel’s recruiter surveys reckon the big majority of hiring managers read the Lebenslauf first or read only it, and honestly that matches everything I’ve seen. This is the document that decides whether a human ever appears. One page is fine for a junior. Two is normal for someone at Priya’s level. Three you save for genuinely senior people. And the old fully-chronological thing, where you list your Gymnasium and work forward, that’s dead for tech. Nobody wants your school.
The section order German parsers and recruiters both expect:
- Persönliche Daten — name and contact, often as a header
- Kurzprofil — optional three-line factual summary. Newer trend, and actually a good one
- Berufserfahrung — the jobs: role, company, city, MM/YYYY–MM/YYYY, and three to five bullets that are achievements, not duties
- Ausbildung — education
- Kenntnisse / Fähigkeiten — skills
- Sprachen — languages
- Zertifikate / Weiterbildungen — certificates
- Ort, Datum, Unterschrift — place, date, signature, the very-German formal closer
Small thing that silently kills people: use MM/YYYY, never just the year. Write “2024–2025” and a German recruiter immediately wonders what you’re hiding in those twelve months, because that range could be hiding a four-month gap. Some ATS setups will flag a year-only CV as incomplete and bin it without a human ever knowing. Always 08/2021 – heute. This one caught me out on my very first draft, so, you know, don’t be me.
Converting from a US, Indian or UK CV
If you’re porting an existing CV, the mistakes are almost always structural, not about your actual experience:
- From a US résumé: kill the “Objective” or “Summary” marketing paragraph. That “dynamic, results-driven professional seeking a challenging opportunity” line reads as pure noise here. Drop the one-page religion, two is fine. References go on a separate sheet on request, never on the CV itself. And for Mittelstand, add the signature line back.
- From an Indian CV: off comes the Declaration (“I hereby declare that the information above is true and correct to the best of my knowledge…”), the father’s name, the marital status, the 10th and 12th standard percentages. I know, we were all trained to put them. Here they don’t just waste space, they actively brand you as not knowing German norms before the recruiter reaches your first real bullet. And keep it reverse-chronological. Never functional.
- From a UK CV: closest relative of the three, but Germany often still wants a photo (Mittelstand), wants explicit MM/YYYY, and wants the literal word “Lebenslauf” on the German version. British “CV” is basically the German “Lebenslauf”. The US thing where “CV” means the academic ten-pager doesn’t apply here at all.
One more, and this one genuinely trips German readers up: German grades run 1.0 to 5.0, and 1.0 is the good one. The exact opposite of an Indian percentage or CGPA. So an 8.5/10 CGPA looks like a disaster to a German unless you translate it. Priya writes “Final grade: 8.5/10 CGPA (≈ German 1.5)” and suddenly a number the recruiter couldn’t parse becomes “oh, top of her class”. Do that conversion. It takes ten seconds and it matters more than you’d think.
Priya’s CV, before and after
Enough rules in the abstract. Here’s what they add up to on one page. This is roughly the CV Priya first sent me, the Indian/US hybrid that would quietly die in a German pipeline:
PRIYA SHARMA
Pune · +91-98765-43210 · [email protected]
Objective: Dynamic, results-driven software engineer seeking a challenging and growth-oriented role to leverage my exceptional skills and passion for cutting-edge technology.
Father’s Name: Rajesh Sharma · DOB: 14/07/1997 · Marital Status: Single · Nationality: Indian
Skills: Go ★★★★★ · Python ★★★★☆ · Leadership ★★★★★ · Communication ★★★★★
Experience: Software Engineer, Finmark Technologies (2021–present). Worked on backend systems. Team player, hard worker, quick learner.
Declaration: I hereby declare that the information above is true to the best of my knowledge.
Nearly every line is working against her. Now the same person, same jobs, same numbers, rebuilt as a German-market English CV, the version that actually got the interviews:
Priya Sharma
Pune, India (relocating to Berlin) · +91 98765 43210 (WhatsApp) · [email protected] · linkedin.com/in/priyasharma-dev · github.com/priyasharma
Work authorization: EU Blue Card eligible (IT-specialist route, §18g AufenthG)Profile — Backend engineer with 4 years building high-throughput services in Go and Python. Owns services end-to-end, from design through deployment and on-call.
Experience
08/2021 – present · Backend Engineer, Finmark Technologies, Pune
— Reduced API p99 latency by 40% by redesigning the Redis caching layer for the payments service
— Migrated a monolith module into 6 Go microservices handling 12,000 req/s at peak
— Built CI/CD pipelines (GitHub Actions, Docker, Kubernetes), cutting deploy time from 40 to 8 minutes
07/2019 – 07/2021 · Software Engineer, Zeta Systems, Pune
— Built REST/gRPC APIs in Python (FastAPI) for a B2B SaaS platform serving 500,000 users
— Raised test coverage from 45% to 82% with automated integration testsSkills — Programming: Go (primary), Python, SQL · Frameworks: Gin, FastAPI, gRPC · Cloud/DevOps: AWS, Docker, Kubernetes, GitHub Actions, Terraform · Databases: PostgreSQL, Redis, MongoDB
Education — 08/2015 – 06/2019 · B.Tech Computer Science, Savitribai Phule Pune University · Final grade 8.5/10 CGPA (≈ German 1.5)
Languages — English C1 (verhandlungssicher, IELTS 7.5) · Hindi & Marathi Muttersprache · German A2 (in progress, targeting B1 by Q4 2026)
Certifications — AWS Solutions Architect Associate (2023) · Certified Kubernetes Administrator, CKA (2024)
References — Available on request
Every single edit there maps back to a rule from above:
- Objective blurb → three-line Profile. The marketing paragraph is gone; the Profile states facts.
- Father’s name, DOB, marital status, the Declaration → deleted. All AGG-sensitive or just dated, none of it earning its space.
- Star bars → grouped, plain-text skills. A parser can read these, and “Leadership ★★★★★” as a “skill” has vanished entirely.
- Year-only → MM/YYYY. No more hidden months.
- CGPA → converted. “8.5/10 (≈ German 1.5)” instead of a number a German reader can’t place.
- Work-authorization line added. Answers the visa question before it’s asked.
- References → “on request”, off the body, and every bullet is now a quantified achievement instead of “team player, hard worker”.
That AFTER version is your template. The finished files — this English one, plus a German Mittelstand Lebenslauf with the photo and the Ort/Datum/Unterschrift line — are in the downloads as PDF and editable Word.
The photo question, honestly 📸
This is far and away the most common question I get about CVs, and the honest answer is: it’s moved, but not nearly as far as the English-language guides want you to believe.
Legally it’s settled. Under the Allgemeines Gleichbehandlungsgesetz (AGG), on the books since 2006, nobody can require a photo or punish you for skipping it. Some ads now say “Bewerbung ohne Foto” right in the posting. But culture lags the law, always does. Karrierebibel’s surveys still put something like 92% of recruiters as preferring to see a photo, and that pull is strongest in exactly the traditional corners (banking, insurance, manufacturing, public sector, anything customer-facing) where the Mittelstand lives.
In tech though, and at the English-first scale-ups, the photo is genuinely fading. Zalando basically prints “you’re welcome to leave out your picture, age, or marital status” on its postings. N26, DeepL, Celonis run photo-optional pipelines. So the rule I hand every international applicant is dead simple and it depends on which version we’re talking about:
- English scale-up version: no photo. Looks modern, and it’s one less thing an ATS can trip over.
- German Mittelstand version: put a proper professional photo top-right of page one, or on a Deckblatt. Actual photographer, neutral background, business clothes, roughly 4.5×6 cm. Not a cropped holiday selfie with your ex still visible on the left edge. A bad photo is genuinely worse than no photo.
Priya keeps both, obviously. Personio-track CV is photo-free. Munich-Mittelstand Lebenslauf has a real headshot. Two files, one profile, no drama.
What to leave off: personal data after the DSGVO
Foreign CVs almost always carry too much personal data, not too little. Here’s where the line sits in 2026.
Put in: your full name, a postal address (your home-country one is fine while you’re still abroad, nobody minds), a phone number in international format with the country code (+49 … or +91 …, and drop the leading 0, German numbers hate that trunk zero), a professional email, and optionally LinkedIn, GitHub, a portfolio.
Leave off, all of it AGG-sensitive and all of it optional: date of birth, place of birth, nationality, marital status, kids, religion. Modern guidance treats marital status, children and religion as flat-out outdated now, so putting them on actively signals that your application knowledge is stuck in about 2012. Date of birth is still very commonly included voluntarily, no harm there. Nationality is a judgment call.
Here’s the one genuinely non-obvious move for us non-EU folks, and it’s a small edge. Priya adds a single voluntary line near her contact block: “Work authorization: EU Blue Card eligible (IT-specialist route, §18g AufenthG).” Not required. But it answers the recruiter’s very first silent question (“wait, can we even hire her?”) before they’ve finished thinking it. I put a version of that line on every single application I sent. It turns a quiet worry into a solved problem, and quiet worries are what get you filtered.
The skills block: group it, be specific, and please kill the star bars
Two rules and we’re done.
One: group into labelled clusters and be concrete about it. Not a forty-word comma soup. Clusters a human and a parser can both read. Priya’s:
- Programming: Go (primary), Python, SQL
- Frameworks/Libraries: Gin, FastAPI, gRPC
- Cloud/DevOps: AWS, Docker, Kubernetes, GitHub Actions, Terraform
- Databases: PostgreSQL, Redis, MongoDB
- Methods: Microservices, REST/gRPC APIs, CI/CD, Agile/Scrum
Two: bin the graphical skill bars, the stars, the little percentage donuts. I know a five-segment “Go ▮▮▮▮▯” bar feels like information. It isn’t. A CV parser can’t read it, and a German recruiter reads it as filler. If you want to signal depth, use words: “Go — 4 Jahre”, or “Go (sehr gut)”. That’s it. I will die on this hill.
And this is the free-points one: mirror the exact words in the ad. If the posting says “Kubernetes”, you write “Kubernetes”, not just “K8s”. If it’s a German ad that says “Softwareentwickler”, get that literal word onto the page next to “Software Engineer”. The machine is doing a dumb literal keyword match before any person is involved. This is the cheapest score on the whole page and people skip it constantly.
Languages: use CEFR, and for the love of god, be honest
Languages go on the CEFR scale, A1 to C2. Not “basic / intermediate / fluent”, not those percentage bars again. CEFR is the clearest signal and the most reliably parsed. Here’s the mapping so you can read the German descriptors in job ads:
| CEFR | German descriptor |
|---|---|
| C2 | verhandlungssicher / annähernd muttersprachlich |
| C1 | fließend / verhandlungssicher |
| B2 | fließend / gute Mittelstufe |
| B1 | sichere Gesprächsführung |
| A2 | fortgeschrittene Grundkenntnisse |
| A1 | Grundkenntnisse |
| — | Muttersprache = native, and only for a language you actually grew up in |
Now the part I care about most, and I’ll say it plainly: do not inflate your level. Roughly one applicant in six pads their language line, and German recruiters have a beautifully simple counter. They just switch into the claimed language mid-interview and watch you drown. Claiming B2 German and then freezing when the recruiter casually drops into German is an instant, unrecoverable no. Worse, it poisons the whole CV, because now they quietly doubt every other number on it. An honest A2 with a direction beats a fictional B2 every time. This isn’t even close.

Priya’s block, doing it right:
Sprachen: Hindi & Marathi — Muttersprache · English — C1 (verhandlungssicher, IELTS 7.5) · Deutsch — A2 (in Vorbereitung auf B1, Ziel Q4 2026)
Naming the trajectory (“targeting B1 by Q4”) is both honest and it reads as commitment. It tells a German employer she means to stay, which they care about more than most foreigners realise. For English-first tech roles, English at C1 is the real bar and German is a bonus, and there’s a whole shortlist of companies that hire in English if your German isn’t there yet. For a German-language Mittelstand role, B2 is usually the working threshold, and B1 also happens to unlock the faster 21-month route to permanent residence, so chase it regardless. I’m still chasing mine, so no judgment from me.
The Anschreiben: when to bother, and how to not blow it
The cover letter has quietly collapsed as a hard requirement in tech. The employer surveys over the last couple of years put it as genuinely mandatory at well under a third of companies, and most Berlin/Munich scale-ups (N26, Personio, Zalando and that crowd) don’t even show a cover-letter field. If the form doesn’t have a slot, do not force one in. For a senior SWE role at an international-facing company in 2026 you usually don’t need a classical Anschreiben at all.
But. At the Mittelstand, in banking and insurance, in the public sector, and any time you apply over plain email, it’s still expected, and its absence reads as either lazy or clueless. So here’s how to do it right when you do have to.
The format is rigid, and the rigidity is exactly the point. Nailing it signals you understand how Germans do professional. DIN 5008 business-letter layout, one A4 page:
- Briefkopf — your contact block, then the company plus a named human where you can find one
- Ort, Datum — right-aligned (“Berlin, 13.07.2026”)
- Betreff — a bold subject line with the role and any reference number, and you don’t write the word “Betreff” itself
- Anrede — “Sehr geehrte Frau Müller,” / “Sehr geehrter Herr Schmidt,” — named wherever humanly possible; “Sehr geehrte Damen und Herren,” only when you truly can’t find a name
- Einleitung — why this role, this company. A hook, no hype
- Hauptteil — motivation plus two or three quantified things you actually did, mapped onto what the ad asks for
- Schlussabsatz — the practical bits the ad requested: earliest start, notice period, salary expectation, then a confident closing line that isn’t begging
- Grußformel — “Mit freundlichen Grüßen”
- Signature
Tone is where foreigners bleed out. German cover letters are specific, evidence-based, and understated. Swap “I’m an exceptional, world-class engineer with a passion for scalable systems” for “In my current role I cut our API p99 latency by 40% by redesigning the Redis caching layer.” Prove it, don’t claim it. And don’t overcorrect into the empty German Floskeln either, “teamfähig, belastbar, engagiert” with no evidence is just as hollow as the American superlatives, it’s the same sin in a different accent. The words that actually land in German professional writing are the boring reliable ones: gründlich, zuverlässig, strukturiert, sorgfältig.
Language of the letter follows the ad, with one hard caveat: only write it in German if your German is honestly C1 or better. A cover letter in wobbly German screams that you lied about your level, and that’s a harder no than sending no letter. And for us non-EU applicants, one sentence pre-empting the visa question earns its space every time: “Für die Anstellung benötige ich eine EU Blue Card über die IT-Fachkräfte-Route (§18g); IT ist ein Engpassberuf, und die Bearbeitung über das beschleunigte Fachkräfteverfahren dauert in der Regel vier bis acht Wochen.” Closes the objection before they’ve formed it.
Here’s Priya’s full German Anschreiben for that one Munich Mittelstand fintech, visa sentence and all, on a single A4 page:
Priya Sharma · Koregaon Park, Pune 411001, Indien · +91 98765 43210 · [email protected]
Rheinwerk Software GmbH · z. Hd. Frau Dr. Sabine Müller · Maximilianstraße 12, 80539 München
Pune, 13. Juli 2026
Bewerbung als Backend Engineer (Go/Python) — Referenz-Nr. 2026-BE-14
Sehr geehrte Frau Dr. Müller,
als Backend-Entwicklerin mit vier Jahren Erfahrung in Go und Python habe ich Ihre Ausschreibung mit großem Interesse gelesen — insbesondere Ihr Ziel, die Plattform auf eine Microservice-Architektur umzustellen, entspricht genau meinem Schwerpunkt.
In meiner aktuellen Position bei Finmark Technologies habe ich einen Monolithen in sechs Go-Microservices überführt, die 12.000 Anfragen pro Sekunde verarbeiten, und die p99-Latenz unserer APIs um 40 % gesenkt. Meine CI/CD-Pipelines (GitHub Actions, Docker, Kubernetes) haben die Deploy-Zeit von 40 auf 8 Minuten reduziert. Diese Erfahrung möchte ich gerne in Ihr Team einbringen.
Für die Anstellung benötige ich eine EU Blue Card über die IT-Fachkräfte-Route (§18g). IT ist ein anerkannter Engpassberuf; die Bearbeitung über das beschleunigte Fachkräfteverfahren dauert in der Regel vier bis acht Wochen. Gerne stehe ich Ihnen ab dem 01.09.2026 zur Verfügung, ein früherer Eintritt ist nach Absprache möglich. Meine Gehaltsvorstellung liegt bei einem Bruttojahresgehalt von 70.000 €.
Über die Einladung zu einem persönlichen Gespräch freue ich mich sehr.
Mit freundlichen Grüßen
Priya Sharma
Look how understated it is: not one adjective about herself, just the migration, the latency number, the deploy time, and the practical paragraph the ad asked for. That’s the register you want. The English scale-up version, plus both of these as editable Word, are in the downloads.
The Bewerbungsmappe: the attachments no one warns you about
Right, this is a concept with genuinely no US or Indian equivalent, and it blindsides nearly every international applicant. A “vollständige Bewerbung”, a complete application, is not just a CV and a letter in Germany. It bundles a set of supporting documents called Anlagen:
- Arbeitszeugnisse — employer reference certificates. The single most important attachment to a German reader, by a distance
- Zeugnisse — degree and diploma certificates
- Zertifikate — the relevant ones (AWS, CKA, Scrum, whatever)
- Arbeitsproben — work samples, where they make sense
Order for a digital application: Anschreiben → optional Deckblatt → Lebenslauf → highest degree certificate → Arbeitszeugnisse (reverse-chronological) → certificates. Keep the whole thing compact, ten pages-ish, last decade only, and merge it into one sensibly-named PDF like Bewerbung_Priya_Sharma_Backend_Engineer.pdf. Never a ZIP. Never originals, only copies.
Now the part that’ll actually bite you. The Arbeitszeugnis is a legally-mandated German reference document, and German HR reads it in a code you’ve almost certainly never heard of. Because the law says these references must be simultaneously truthful and benevolent (you can’t legally trash someone), German employers evolved a secret grading language buried inside friendly-sounding phrases:
- “stets zu unserer vollsten Zufriedenheit” = grade 1, very good
- “stets zu unserer vollen Zufriedenheit” = grade 2, good
- “zu unserer vollen Zufriedenheit”, no “stets” = grade 3
- “stets zu unserer Zufriedenheit” = grade 4
- “hat sich stets bemüht”, literally “always made an effort” = the notorious grade 5-6 death sentence
Indian and US employers don’t issue these, and here’s where people panic. So do two things. First, don’t you dare fabricate a German-style Zeugnis, a German recruiter smells a fake instantly. Second, ask each old employer for a detailed English reference letter covering your role, your dates, the tech you touched, and how you performed, and label it clearly as a reference. Counter-intuitive bit: a missing Arbeitszeugnis actually reads worse to a German recruiter than a mediocre one. So a real, clearly-labelled English reference letter is the right stand-in, and it pulls double duty as evidence for the §18g route we’ll get to in a minute. (I’m keeping this short on purpose, the full decode-the-code deep-dive deserves its own article. The field manual has the working short version for now.)
Surviving the ATS: Workday, SuccessFactors, Personio 🤖
Your CV meets a parser before it meets a person, and the parser is dumber and more literal than you’d ever hope. Among the big enterprises Workday and SAP SuccessFactors dominate (Jobscan’s usage report has them at the top, though those are global Fortune-500 numbers, so read them as directional rather than a German market share). In the German Mittelstand and scale-up world it’s Personio everywhere, Munich-born, 10,000-plus companies on it, with Softgarden, rexx and Greenhouse also common. Personio parses PDF or DOCX and it explicitly falls over when your name or email is trapped inside an image.
The formatting that survives all of them:
- Single column. Two at the absolute most. Multi-column layouts and text boxes scramble the order the parser reads in
- Never put your name, contact info, or critical keywords inside an image, a graphic, or the photo
- Use the standard headings the parser is looking for: Berufserfahrung / Work Experience, Ausbildung / Education
- Reverse-chronological, not functional. Functional layouts confuse the machine about when things happened
- Text-based PDF is the German standard, DOCX only when asked. And avoid Europass, its table-heavy layout parses badly and, between us, signals low effort to recruiters
- Mirror the ad’s keywords, in German too when the ad’s in German
And keep both a German and an English version, sending whichever matches the ad’s language. An English CV is completely correct in Germany when the posting is in English, don’t second-guess that. (I go much deeper on reading an ATS straight from its URL, and which employers sit on the friendly ones, in the field manual. Worth it before you spray applications.)
Salary and availability: the right number, only when asked
Two lines that turn up in nearly every German application, both with conventions people fumble.
Gehaltsvorstellung, salary expectation. State it only when the ad asks for it. Give an annual gross (brutto) figure or a tight range. Never a monthly number, never net. For a mid-level backend engineer aiming at Berlin, the common ask sits somewhere around €65,000–€75,000 gross, but do your homework on the specific company before you anchor. There’s an immigration angle stapled to this too: your base has to clear the 2026 EU Blue Card floor of €45,934.20 for shortage/IT occupations (the general floor is €50,700), and only guaranteed, contractually-written pay counts toward it. Discretionary bonus, stock, sign-on, none of it counts. So model your base against that number before you pop the champagne over a fat total-comp figure. The salary calculator and my breakdown of what developers actually take home will keep you honest about the distance between the sticker number and your Steuerklasse reality, which is bigger than you think.
Verfügbarkeit and Kündigungsfrist, availability and notice. German notice is governed by §622 BGB: the statutory baseline is four weeks to the 15th or the end of a calendar month, and two weeks during a Probezeit (probation, max six months). Senior contracts often stretch it, three months to quarter-end is common, and contracts can lengthen the statutory floor but never shorten it. Applying from abroad, Priya’s actual availability is “immediate minus relocation and visa time”, which is genuinely a selling point. So sell a firm, predictable start date instead of overpromising speed you can’t control.
Degrees, anabin, ZAB, and the §18g escape hatch 🛂
This is the bit where a lot of non-EU engineers quietly lose their minds, and mostly they don’t need to. Let me walk the general machinery first, then Priya’s shortcut, because the shortcut is the whole point.
anabin, the free KMK/ZAB database, rates two things. Your institution: H+ (recognised), H+/− (case-by-case), H− (not recognised). And your degree, by equivalence. For the Blue Card degree route, the government’s Make-it-in-Germany rule is that two anabin printouts are enough only when both your institution shows H+ and your specific degree rates “entspricht” or “gleichwertig”. IITs, NITs, most central and state universities are H+. A lot of the private, deemed-to-be and newer universities are H+/− or just not listed. If yours is in that gap, you need a ZAB Statement of Comparability (Zeugnisbewertung), an official document that slots your degree into the German system. You apply online (you’ll need a BundID), the fee is €208, and while the standard turnaround is around three months, ZAB explicitly fast-tracks Blue Card cases to roughly two weeks if you attach the work contract. This isn’t hypothetical to me, by the way. A friend from my Pune college got caught exactly here, his college simply wasn’t in anabin, and he lost weeks he didn’t have to it.
But here’s the escape hatch, and it’s the route Priya actually takes. Since the Skilled Immigration Act reform, §18g lets IT specialists get an EU Blue Card without a recognised degree at all, on experience alone: at least three years of relevant IT experience in the last seven, roughly graduate-level, plus an offer that clears the salary floor. IT sits in ISCO-08 group 25, a shortage occupation, so the lower €45,934.20 threshold applies automatically. Priya’s got four years in the last seven. She skips anabin and ZAB entirely, her contracts, reference letters, payslips, GitHub and certs carry the whole load instead of a diploma. This is why I keep begging experienced engineers not to torch three months on degree recognition they might not even need. Do the whole thing in parallel if you want the safety net, but don’t let it become the bottleneck. The full walkthrough (thresholds, the Bundesagentur consent step, the residence timelines) is in the EU Blue Card guide. Either way, go check your own university in anabin before you bank on the degree route. That one’s on you, and it matters more than any formatting tip in this whole article.
The rejection triggers that actually kill international applications
After a couple of years of reading strangers’ CVs in my DMs, the same failures come round and round. Here’s the table I wish someone had handed me on day one: the trigger, why it fails specifically here, and the fix.
| Trigger | Why it fails in Germany | The fix |
|---|---|---|
| US hype and superlatives | Reads as untrustworthy; the norm is understatement | Quantified, factual achievements (“cut latency 40%”) |
| Overstated language level | Exposed the second a recruiter switches languages | Honest CEFR level plus a trajectory (A2, targeting B1) |
| Unexplained gaps (Lücken) | A gap over ~3 months, unexplained, looks hidden | Label it in one line (“03–08/2024: German course + job search”) |
| Year-only dates | Hide gaps; CV treated as incomplete, sometimes auto-binned | Always MM/YYYY |
| Wrong or missing photo | Selfie at a Mittelstand; or a photo where a scale-up wants none | Professional photo for Mittelstand, none for English-first tech |
| Missing Anschreiben where expected | Damaging at Mittelstand and corporate | One-page tailored Anschreiben, unless the form has no slot |
| Missing Arbeitszeugnisse | Reads worse than weak ones | Clearly-labelled English reference letters |
| US one-pager into a German ATS | Missing expected sections, parse fails, human rejects | Structured Lebenslauf with standard German headings |
| Degree-recognition blind spot | Assuming a foreign degree is auto-accepted | Check anabin; use the §18g route or file a ZAB statement |
| Functional / graphic-heavy layout | Breaks Workday/SuccessFactors/Personio parsing | Single-column, text-based, no critical text in images |
| Generic, untailored application | Fails the keyword match and bores the recruiter | Mirror the ad’s exact words, per posting |
The do / don’t, on one screen
Tape this one above your monitor.
| ✅ Do | ❌ Don’t |
|---|---|
| Match the ad’s language and formality | Fire one generic file at every employer and hope |
| Reverse-chronological, MM/YYYY dates | Send year-only dates that hide gaps |
| Group and label your skills | Use star / bar / percentage skill graphics |
| List languages on CEFR, honestly | Overstate your German (they’ll test it live) |
| Single-column, ATS-safe PDF | Bury your name or contact inside an image |
| Mirror the ad’s exact keywords | Keep a US “Objective” or superlatives block |
| Convert your CGPA to the German 1.0–5.0 scale | List marital status, religion, or father’s name |
| One named, understated Anschreiben where there’s a slot | Force a cover letter where there’s no slot |
| Salary as gross annual, only when asked | Fabricate a German-style Arbeitszeugnis |
| Label any gap over ~3 months; check anabin early | Assume your foreign degree is auto-recognised |
A phrase bank you can just lift
The lines I reuse constantly, in both languages. Swap the specifics, ship it.
Salary expectation
- 🇬🇧 “In line with my experience, my gross annual salary expectation is €70,000.”
- 🇩🇪 “Meine Gehaltsvorstellung liegt bei einem Bruttojahresgehalt von 70.000 €.”
Availability / notice
- 🇬🇧 “I am available from 1 September 2026 and can start earlier by arrangement.”
- 🇩🇪 “Gerne stehe ich Ihnen ab dem 01.09.2026 zur Verfügung; ein früherer Eintritt ist nach Absprache möglich.”
- 🇩🇪 “Meine Kündigungsfrist beträgt vier Wochen zum Monatsende.”
The visa pre-empt (put a version of this in every application)
- 🇬🇧 “I’ll need EU Blue Card / §18g sponsorship — IT is a shortage occupation, and processing via the accelerated skilled-worker procedure typically runs 4–8 weeks.”
- 🇩🇪 “Für die Anstellung benötige ich eine EU Blue Card (§18g); IT ist ein Engpassberuf, die Bearbeitung dauert in der Regel vier bis acht Wochen.”
Closing line
- 🇬🇧 “I would welcome the opportunity to discuss how I can contribute to your team.”
- 🇩🇪 “Über die Einladung zu einem persönlichen Gespräch freue ich mich sehr.”
Skills, honest qualifier
- 🇩🇪 “Go — 4 Jahre · Python — 3 Jahre · Kubernetes — sehr gute Kenntnisse”
The questions I actually get asked
Do I need a German-language CV if I only apply to English-first companies?
No. English ad, English company, English CV, even in Germany. Keep a German Lebenslauf loaded only if you’re also going after Mittelstand or German-language roles. Priya keeps both because she’s hedging both tracks. If you’re pure Berlin-scale-up, one clean English CV is plenty.
Should I put a photo on my CV?
Berlin/Munich tech scale-ups, no. Traditional Mittelstand, banking, insurance, public sector, yes, a clean professional headshot top-right. It’s never legally required (AGG), so when you genuinely can’t tell, leave it off for tech.
Is the Anschreiben dead?
For tech, mostly, most scale-up forms don’t even ask. But it’s alive and well at the Mittelstand, in corporates, and any time you apply over email. Don’t force one where there’s no slot. Do write a tailored one where there is.
My degree isn’t clearly recognised in anabin. Am I stuck?
Probably not, if you’ve got experience. The §18g IT-specialist route gets you a Blue Card on 3+ years of relevant experience in the last 7, no degree recognition needed. If you’d rather use the degree route, a ZAB Statement of Comparability (€208, ~2 weeks in the Blue Card fast-track) settles it. Full thing in the Blue Card guide.
How do I explain a gap in my CV?
Briefly and factually, right there in the date column. “03/2024–08/2024: Intensivkurs Deutsch + Jobsuche” is completely fine. What’s not fine is leaving a visible hole and hoping nobody clocks it, because a German recruiter always clocks it, and the unexplained version reads far worse than the honest one.
Can I use one CV for everything?
You can, and it’ll quietly underperform for months while you wonder why. Mirror each posting’s keywords, match its language, match its formality. Two versions rendered from one master profile, retargeted per application. That’s the entire game.
Where to point yourself next
The documents get you read. They don’t get you hired, that’s the next fight. Once the Lebenslauf and Anschreiben are clean, the leverage shifts to targeting and pipeline. So: check your permit in the visa checker, model your real take-home in the salary calculator, then go fishing in Germany tech jobs, the visa-sponsorship board, the backend developer roles Priya’s chasing, the company directory, and the visa + relocation collection. For the whole from-abroad strategy, my field manual. For the interviews that come after, Ashley’s German tech interview guide is the companion. And when you land the thing, my first-90-days checklist picks up right where this stops.
Last thing, and I mean it. The market genuinely wants you. The Bundesagentur was carrying around 700,000 open vacancies going into 2026, and IT is a shortage occupation. What stands between a good non-EU engineer and a Berlin desk is almost never talent. Half the time it’s a document that reads as foreign when, with one evening’s work, it could read as serious. Go fix the document. My friend did, and it took her an evening. You’ve got this.
📎 Download Priya’s CV & cover letter
Steal the structure, not the details. Each comes as PDF (for sending) and Word/DOCX (for editing):
- English CV — Berlin scale-up version: PDF · Word/DOCX
- English cover letter: PDF · Word/DOCX
- German Lebenslauf — Mittelstand version: PDF · Word/DOCX
- German Anschreiben: PDF · Word/DOCX
Names, companies and contact details in the examples are illustrative — swap them for your own.
Sources & where these numbers come from
The hard figures are from official sources. The softer stuff (how recruiters read things, response patterns) is synthesised from a couple of years of DMs and public write-ups, and I’ve flagged that in the text. Thresholds and procedures move, so confirm the current version before you act on it.
- Anti-discrimination basis for the photo / personal-data rules — AGG: gesetze-im-internet.de/agg (Federal Ministry of Justice)
- Notice periods — §622 BGB: gesetze-im-internet.de
- EU Blue Card and the §18g experience route: gesetze-im-internet.de
- Application documents, Blue Card, degree recognition: Make-it-in-Germany (Federal Government portal)
- Degree recognition database: anabin (KMK/ZAB) — German only
- 2026 Blue Card salary thresholds: confirmed by the Bundesministerium des Innern (BMI); the shortage floor tracks the 2026 pension ceiling.

This is my own read from doing the move and helping a lot of people through it, notes and opinion, not legal advice. Immigration and employment rules shift, so confirm the specifics with official sources or a Fachanwalt für Migrationsrecht before you file. 🙂
