Cover letters across languages:
the parts that don't translate

If you're applying to jobs in more than one country, the cover letter is often where the quiet mistakes happen. Not the obvious ones, the subtle ones. A salutation phrased the way an English speaker would translate it, which reads as slightly off to a native German reader. A date in the wrong format. A subject line that's correct in your language and invisible in theirs.

These are small details. They're also the kind a hiring manager notices without consciously noticing: the letter feels off, they're not sure why, they move on. This post is about what actually changes when a cover letter crosses a language boundary, and why direct translation is not the fix.

Why translating a cover letter doesn't work

If you take an English cover letter and run it through any translator (DeepL, Google Translate, ChatGPT), what comes out is grammatically correct and culturally wrong in specific, predictable ways.

An English letter opens with "Dear Hiring Manager,". Translated literally into Italian, you get "Caro/a Responsabile delle Assunzioni," which no Italian would write. An Italian letter opens with "Spett.le [company name]" or "Gentile [name]," depending on formality. The two conventions serve the same purpose but are not translations of each other.

Same with closings. The English "Best regards,". Translated to German, you get "Beste Grüße,", which works, but a native German formal letter ends with "Mit freundlichen Grüßen,". Translating the English phrase produces something grammatically correct but culturally muted.

And date formats: "January 15, 2026" in English becomes "15. Januar 2026" in German, "15 gennaio 2026" in Italian, "2026年1月15日" in Japanese. The month name changes language; the order changes; the punctuation changes. None of this is what a generic translator will reliably produce.

The point: a cover letter is not a paragraph. It's a structured document with culturally-specific scaffolding, and the scaffolding has to be produced correctly for each target market, not translated from one market's version.

The four parts that don't translate

When you cross a language boundary, four specific parts of the letter change independently of the body content. These are the places where direct translation fails most visibly.

1. Salutation

Every language has its own formal and semi-formal opening. And every language has a different convention for what to do when you don't know the recipient's name.

• English (US/UK): "Dear Hiring Manager," or "Dear [Name]," if known.
• German: "Sehr geehrte Damen und Herren," (no name) or "Sehr geehrte Frau [Surname] / Sehr geehrter Herr [Surname]," (with name).
• French: "Madame, Monsieur," (no name) or "Madame [Surname] / Monsieur [Surname]," (with name).
• Italian: "Spett.le [company]," or "Gentile [Name]." Note that the abbreviation "Spett.le" is standard and translation doesn't produce it.
• Japanese: Highly context-dependent, with specific forms depending on company type and seniority of addressee.

A letter that uses the translated-from-English version of a salutation in any of these markets reads as written by someone who didn't bother with the local conventions.

2. Subject line

European formal letters often include a subject line (Oggetto: in Italian, Betreff: in German, Objet: in French). English letters typically don't. If you're writing in English to a European recipient, including a subject line is fine and often improves clarity. If you're writing in German and you omit it, the letter reads as informal or incomplete.

The subject line also follows local conventions: "Application for the role of [Title]" in English; "Bewerbung als [Title]" in German; "Candidatura per il ruolo di [Title]" in Italian. The role name itself is sometimes translated, sometimes kept in English, depending on the industry, the company, and norms. Tech roles ("Software Engineer") are often kept in English even in German-language applications. Other roles are translated.

3. Date format

This is the easiest to get wrong mechanically, because every language has a specific preference:

• US: "January 15, 2026"
• UK: "15 January 2026"
• German: "15. Januar 2026" (note the period after the day)
• French: "le 15 janvier 2026"
• Italian: "15 gennaio 2026"
• Japanese: "2026年1月15日"
• Spanish: "15 de enero de 2026"

Getting this right is not just about knowing the language. It requires knowing which format is canonical for each specific market. A date in the wrong format on a formal document is a minor but real cultural error.

4. Closing

The closing phrase is culturally specific:

• English: "Best regards," or "Sincerely,"
• German: "Mit freundlichen Grüßen," (formal) or "Viele Grüße," (less formal)
• French: "Cordialement," or the more formal "Je vous prie d'agréer, Madame, Monsieur, l'expression de mes salutations distinguées,"
• Italian: "Cordiali saluti," or more formal variants.
• Japanese: specific formal closing phrases that don't translate directly.

The French formal closing in particular is a multi-clause construction that has no natural English equivalent. A translation of "Cordialement" into English is fine; a translation of the English "Best regards" into the French formal closing is not. It misses the formal register entirely.

What actually needs to be generated per letter vs reused

Split the letter into two mental layers.

Scaffolding: salutation, subject, date, closing, the recipient block, your contact block. These are culturally specific and small in word count. They vary by market but not per-application within a market. Once you know the conventions for Germany, every German cover letter reuses them.

Body: the actual paragraphs that pitch you for the specific role. These genuinely change per application: different company, different role, different argument for why you'd fit.

The mistake most tools make is treating these two layers as the same problem. They run the whole letter through an AI translator and get inconsistent scaffolding across candidates, because the model has seen many bad translated letters in its training data and sometimes produces their hybrid.

The better approach: hand-author the scaffolding per market (once), and reserve the generation work for the body. That way the structural elements of every letter sent to Germany follow German conventions; every letter sent to Italy follows Italian conventions; and the intellectual energy goes into what the letter actually says.

The visual template layer, independent of language

Language is one axis. Visual template is another, and they vary independently.

A cover letter in German can be rendered in a minimalist layout, a traditional serif layout, a modern tech-industry layout, a traditional formal layout. The choice is visual and usually depends on the industry and seniority of the target role. The same letter content renders in any of these templates. The template doesn't change the content; it changes the impression the physical document makes before anyone reads a word.

The separation matters: data (contact info, role, body paragraphs) is structured; the template applies visual styling; the language applies local scaffolding. Each layer is independent. Changing the template doesn't change the language; changing the language doesn't force a specific template.

What users care about

Readers of this blog don't care about the machinery. They care that:

• The letter reads right to a native recipient.
• The visual style matches the feel of the role they're applying to.
• They don't have to memorize the difference between "Mit freundlichen Grüßen" and "Viele Grüße" to produce a letter that uses the right one.
• The time they spend on each letter goes into the one or two sentences that actually matter (the sentences that reference something specific about the company), and not into looking up whether German cover letters include a subject line.

A good cover letter tool lets you pick a target market, write (or review) the body, and get a letter shaped correctly for the recipient without having to think about the scaffolding. That's the whole job.

The parts you still need to do yourself

Tooling doesn't replace judgment. Three things remain candidate work:

• The one or two specific sentences that reference something real about the company or the team: a product detail, a recent launch, a team dynamic. No generic prompt produces these. They are the whole point of the letter.
• The decision of whether to write a letter at all. Cover letters are warranted in some cases, optional in others. The tool does not decide this for you.
• The cultural calibration for industries with atypical norms. Tech applications in Germany are often informal enough to use English or semi-formal German. Law applications in Germany are never. Knowing which culture applies in your specific target industry is something the tool can help with but can't fully determine.

The honest take

The hard thing about cover-letter tooling isn't generating text: large language models generate text adequately. The hard thing is producing text that reads as if a native speaker wrote it in a locally conventional format. That's a conventions problem, not a language problem.

When the conventions are handled correctly in the background, the letter stops being a localization problem and goes back to being what it was always supposed to be: a short, specific pitch for why this candidate is right for this role. Everything else fades into infrastructure.

Jobiz cover letters are written in English, and they follow the split above. The scaffolding (subject line, salutation, date, closing) comes from a hand-written file, not from the model, so it's the same on every letter; the salutation uses the hiring manager's name when the posting gives one. The model writes only the four body paragraphs, with the tone set by the job's country: factual and evidence-led for German-speaking markets, understated for the UK, direct for the US. The date follows the order that country uses. And the same letter renders in any of four templates (Professional, Modern, Double Frame, Geometric), switchable without regenerating it.