Software Engineer CV in Germany: What's Different for Tech

If you've already read our guide to the German CV format, you know the base rules — tabular structure, dated entries, personal data, a signature line. Tech roles follow that same base, but about half a dozen things shift enough to be worth a dedicated look. Here's the delta.

In short

  • English is genuinely acceptable more often in tech than in the German job market generally — check the company and posting before defaulting to German.
  • Photo expectations are looser at startups and international tech companies — many explicitly prefer none.
  • Structure your tech stack by category (languages, frameworks, cloud, databases) instead of one flat list.
  • GitHub, a portfolio, or a personal site belong on a tech CV — they're not part of the general format.
  • IT has genuine, documented advantages for work authorization in Germany — a lower Blue Card salary threshold and a no-degree recognition path for experienced professionals.

Is this a different format, or the same one?

The base is the same — reverse-chronological, tabular, dated entries, a Persönliche Daten block — everything covered in our German CV format guide. What changes for tech is narrower than it looks: which language to write in, how firmly the photo convention actually applies, how you present a stack instead of a job history, what links belong on the page, and a couple of work-authorization details that are genuinely different for IT.

English or German?

Tech is the one field in Germany where defaulting to English is a genuinely reasonable bet — more so than the general guidance to default German covered in our eligibility section elsewhere. International startups, and the Berlin and Munich tech scenes generally, often run entirely in English, end to end. More traditional employers — banks’ internal IT departments, automotive suppliers, public-sector IT — usually still expect German, same as any other field.

The clearest signal is the job posting itself: if it’s written in English and the listed team or stack looks international, English is very likely fine. If it’s in German, or the company is a traditional Mittelstand employer with an IT department rather than a tech-first company, default to German.

The photo question, for tech specifically

The general guidance is “still commonly expected, though not required” — in tech, that expectation is noticeably weaker. International startups and tech subsidiaries frequently skip it entirely, sometimes as a deliberate policy to reduce bias in early screening. More traditional IT departments — the same ones that expect German over English — tend to expect a photo too. When you genuinely can’t tell, including a professional one is the safer default; see our full photo section for what “professional” means here.

Structuring your tech stack

A single flat list of technologies under “Skills” undersells you and is hard to skim. Group it by category instead, the way a Kenntnisse section can actually be structured:

Kenntnisse

Languages

TypeScript, Python, Go — daily use · Java — familiar

Frameworks & Libraries

React, Next.js, Node.js, Django

Cloud & DevOps

AWS (EC2, S3, Lambda), Docker, Kubernetes, Terraform

Databases

PostgreSQL, Redis, DynamoDB

Skip the vague self-ratings entirely — “daily use” or “familiar” (or, if you prefer, years of hands-on experience) tells a hiring engineer something concrete. A 1-to-5 star rating or a progress bar next to “Python” doesn’t.

If your experience is thin

Bootcamp graduates and career switchers into tech often have less traditional Berufserfahrung to show, and lean on it more elsewhere. That’s fine — list your bootcamp as its own dated entry with a real bullet on what you built, and treat a serious personal project or an open-source contribution as a legitimate line item, not filler.

What doesn’t work is inventing metrics for a project nobody ever used — “reduced load time by 40%” on something that never had real users reads as fabricated the moment it’s asked about in an interview. Describe what you actually built and shipped instead.

Certifications

A proctored, effortful certification — AWS or Azure/GCP, Kubernetes (CKA/CKAD), a real Scrum/PSM credential — is worth a short line in Kenntnisse or its own brief list. Free course-completion badges from online platforms generally aren’t worth the CV space; keep the list to credentials that actually required demonstrating something.

Visa advantages specific to IT

Two things worth knowing if immigration status is part of what’s holding you back, beyond the general eligibility factors covered elsewhere. First, the EU Blue Card has a lower minimum salary threshold for shortage occupations, and IT specialist roles are on that list — a meaningfully lower bar than the Blue Card’s general threshold. Second, German immigration law recognizes IT professionals with several years of relevant, recent hands-on experience as qualified even without a matching degree, or without a degree at all — an exception most other regulated fields don’t get. We cover the newer Chancenkarte (Opportunity Card) path in a dedicated guide.

Get your tech CV scored against the German standard

Free, 14-check score covering both ATS parseability and the format conventions covered here — see exactly what to adjust.

Score your CV for free

Frequently asked questions

Do I still need the German tabular format if the job posting is in English?

Usually yes for the structure — an English-language job ad tells you the application language, not necessarily the format. Plenty of Berlin and Munich tech companies hire in English but still expect the same tabular, dated structure covered in our format guide. Check the company's own application instructions if you're unsure.

Do I need to translate my GitHub project descriptions into German?

No — code, READMEs, and commit history are read as-is by both recruiters and hiring engineers, and translating them buys you nothing. Keep GitHub in whatever language you wrote it in originally.

Is a photo really optional in tech?

More so than in most other fields, but it still depends on the specific company. International startups and tech subsidiaries frequently skip it entirely; more traditional IT departments at established Mittelstand or corporate employers often still expect one. When you can't tell, including a professional one is the safer default.

What if I don't have a CS degree?

It matters less in tech than in most other regulated fields — German immigration law has a specific recognition path for IT professionals with several years of hands-on professional experience, degree or not. On the CV itself, lean on real project work, bootcamp training, and any open-source contributions to show the same thing a degree would.

See how your CV actually holds up

Upload it and get a free, detailed breakdown — no guesswork about what to change.

Check your CV for free