Germany has a long-standing shortage of IT specialists, and the gap has been reported by the industry association Bitkom as well over a hundred thousand unfilled positions for several years running. Many German IT teams work in English day to day, which is exactly why the German around the edges is so easy to underestimate.
Meetings with your team may be in English. The contract, the payslip, the works council email, the customer call and the security briefing are in German. The vocabulary below is the German that surrounds an IT job rather than the vocabulary inside the code, and it is where most newcomers lose their footing.
The Ceremonies Have German Names
Agile ceremonies are frequently borrowed from English, but German teams also use translated names, sometimes interchangeably within the same meeting. You may hear both the daily and das tägliche Stand-up, or both a review and a Review-Termin, with no inconsistency intended.
The rhythm is worth learning as a cycle, because the German names describe what happens in each phase. Sprint-Planung sets the scope, the daily is the short synchronisation, the Review demonstriert what was built, and the Retrospektive looks at how the team worked rather than what it produced.
The axis shows sequence, not quantity. Knowing the order is what lets you follow a German sprint review without notes.
The Artefacts, in German and in English
German IT vocabulary is unusually bilingual, and the same object often has two names. Tickets are Tickets, but the thing inside them is often die Aufgabe. Bugs are Bugs, but a formal incident report says der Fehler. A pull request may be called a Merge Request, a Pull Request or a Merge-Anfrage, depending on the company's history.
| German term | English meaning |
|---|---|
| das Ticket | the ticket |
| der Fehler / der Bug | the bug |
| die Anforderung | the requirement |
| die Akzeptanzkriterien | the acceptance criteria |
| die Definition of Done | the definition of done |
| der Rückstand / das Backlog | the backlog |
| die Schnittstelle | the interface, the API |
| die Umgebung | the environment |
| die Version | the release version |
| der Zweig / der Branch | the branch |
Incidents Have Their Own Grammar
When something breaks, German changes register and becomes noticeably more formal. Eine Störung is a disruption or incident, ein Ausfall is an outage, and eine Wartung is maintenance. A planned maintenance window is a Wartungsfenster, and deploying to production is die Bereitstellung or das Deployment, depending on how modern the company is.
The single most useful sentence in a German incident call is "Wo hängt es?" which means where is it stuck, and it is asked without any implication of blame. The reply is normally one of three: "Es läuft noch", "Es ist blockiert", or "Wir brauchen ein Rollback". Producing those fluently, without translating, is what it means to learn German for an engineering team.
Writing Status Updates in German
German status updates are shorter than English ones and they lead with the state, not with the narrative. The four states that cover almost everything are Erledigt, In Arbeit, Blockiert and Wartet auf Rückmeldung. Notice that the last one is longer and more specific than the English equivalent, because waiting on another person's answer is treated as a distinct state rather than as a kind of blockage.
Two phrases carry disproportionate weight in written updates. "Ich habe einen Blocker" announces a dependency that needs someone else's decision, and "Ich schaue es mir heute an" commits you to a specific day. German colleagues read both as scheduling information rather than as politeness, so only write them when you mean them.
Security, Access and Data Protection
German IT security language is precise because it is partly legal. Eine Sicherheitslücke is a vulnerability, ein Patch is a Patch, and die Zugriffsrechte are the access rights attached to an account. Two-factor authentication is die Zwei-Faktor-Authentifizierung, and least privilege appears as das Prinzip der minimalen Rechte.
Data protection has its own vocabulary, and in Germany it is a working matter rather than a compliance footnote. Die DSGVO is the GDPR, personenbezogene Daten is personal data, and eine Auftragsverarbeitung is the processing agreement between a controller and a processor. Engineers are routinely asked to confirm that no personal data left the environment, and the question will be asked in German.
The Register Question: du or Sie
German IT splits sharply by company type. In a Berlin startup the whole company speaks du, from the founders downwards. In a Mittelstand software house, an insurer's IT department or a public-sector IT provider, Sie is normal even between colleagues who have worked together for a decade. The safe beginning is Sie until someone offers otherwise.
Email follows the same logic, and German business email is more formal than its English equivalent. Open with "Hallo Frau Berger," rather than a bare first name, close with "Viele Grüße", and use Sie until you are certain. Matching that register while discussing technical detail is precisely what it means to learn German for an IT workplace.
Reacting to German at nine in the morning is a skill, not a vocabulary list. Learn German with stand-ups, code reviews and incident calls built into the course.
Put your German to work. The LanguageSkills German course is self-paced and built around real situations like these — you speak, and your AI tutor corrects you on the spot, from A1 to B2.