German for IT professionals

Work-ready German.
Not a language course.

1:1 training built around your actual job — tickets, incidents, standups, handovers, stakeholder updates. You practice the situations you're in. Not grammar drills.

Jira / tickets
Standups
Incident updates
Handovers
Interviews
See packages
session_context.log
$ role
DevOps / QA / Support Ops
$ situation
Working in a German-speaking team
$ blockers
Writing incidents in DE without sounding
  like Google Translate
$ session --mode live_simulation
Training loaded. Let's go.
// how sessions are structured

Three modes. One topic.

Every session covers your specific situation — not generic "business German".

📄
01 — Applying

Job hunting in the DACH market

CVs, cover letters, interview answers and salary negotiation — in the register German hiring managers actually expect.

See posts in this mode →
🌐
02 — English-First

Team uses EN, client is German

You write tickets in English but escalations go to a German stakeholder. Practice the switch — and the register.

See posts in this mode →
💬
03 — German-Native

Your whole team speaks German

Daily standups, post-mortems, Slack threads, retros — full immersion. Build fluency in the situations you're already in.

See posts in this mode →
// deliverables

What you leave with.

01

Phrase bank — your role

Reusable vocabulary for your actual tickets, updates and messages. Organised by situation.

02

Copy-paste templates

Incident updates, handover notes, status messages. Low-risk wording, clear ownership, ETA format.

03

Live simulation feedback

You run the scenario, I give real-time correction. Not grading — "would land well" vs "sounds off".

04

Session notes

After each session: a summary of what came up, corrections, and what to work on next.

// packages

Pick your focus.

All sessions are 1:1. We start from your context — not a curriculum.

Speaking Lab

Work Communication

For: DevOps, QA, Support, Sysadmins, Solution Architects

  • Tickets, incidents, escalations — in DE
  • Standups, retros, handovers
  • Stakeholder updates and status messages
  • Live simulation with real-time correction
Phrase bank (role-specific) Reusable message templates Session notes after each call
Send intake → this package
Interview Mode

Interview Prep

For: anyone applying to DACH companies

  • Mock technical + behavioral interviews
  • Answer structure for German HR expectations
  • Salary and negotiation phrases
  • DACH culture: what signals seniority
Answer templates DE register cheat sheet Written feedback after mock
Send intake → this package
Ticket & Message Clinic

Writing Clinic

For: anyone whose written DE needs a quick fix

  • Bring real tickets / emails / Slack messages
  • Live rewrite + explanation of why
  • Focus on clarity, ownership, next steps
  • One-off or add-on to Speaking Lab
Corrected versions of your messages Pattern list: your recurring mistakes
Send intake → this package
// process

How a session runs.

step_01

Context intake

You fill in a short form — role, team setup, what situations feel hardest. I review it before we meet. No cold starts.

step_02

Live simulation

We run the real scenario — I play the stakeholder, the teammate, the interviewer. You respond. I give real-time correction without interrupting the flow.

step_03

Takeaways

After the session: phrase bank update, message templates for your situation, session notes. You leave with something you can use that day.

// proof by example

What changes.

// situation: incident update to German stakeholder
before
There is a problem with the server. We are working on it. Sorry for the inconvenience.
after
Betroffen ist [Service X]. Ursache wird untersucht (erste Hypothese: DB-Timeout). Nächstes Update in 30 Min. Zuständig: [Name].
// situation: Jira ticket description
before
The button doesn't work sometimes. Maybe a cache issue. Please fix.
after
Reproduzierbar bei: [Schritte]. Erwartetes Verhalten: [X]. Aktuelles Verhalten: [Y]. Mögliche Ursache: Cache-Invalidierung. Prio: Medium.

// all examples anonymised — from real session work

// blog

German for the situation you're in.

Every post covers one work scenario — with vocabulary and templates for all three modes.

See all posts →
// faq

Common questions.

No. There are no levels, no grammar drills, no curriculum. We start from your actual role and work through the situations you're in. If your biggest blocker is writing escalation emails in German — that's where we start.
Only when it blocks you in practice. If a grammatical mistake causes actual misunderstandings at work, we address it. But grammar for grammar's sake is not the focus — clarity and sounding appropriate for the context is.
Yes — actually these roles are often the best fit. DevOps, QA, support specialists and solution architects tend to have more communication-heavy work than pure developers: incident ownership, stakeholder updates, cross-team handovers.
Sessions can be conducted in English or Polish — depending on what's more useful for you. The goal is that you get the most out of the session.
Fill in the intake form — role, team setup, 2-3 situations that feel hardest. If you have real examples (a ticket you weren't sure about, an email you rewrote 4 times), bring them. No other preparation needed.
You need enough German to be in a situation where it matters for your work — usually around B1+. If you're completely starting from scratch, mention it in the intake form and we'll figure it out together.
// intake form

Tell me what you're working with.

Fill this in and I'll reply within 48h with whether I can help and what a first session would look like.

No auto-booking.
I review every intake before replying.
If it's not a good fit, I'll tell you honestly.
new_intake_request