Translating a Cover Letter: Why You Shouldn't Trust Google Translate Blindly
You have written your cover letter. The job posting is in English. You copy the text into Google Translate, click the button, and paste the result into your application. It looks like English. It is English, mostly. And it is the kind of English that gets your application sorted into the rejection pile before a human reads a single line.
This is not a warning about machine translation in general. Modern translation models are genuinely good at moving meaning between languages, and the reasons why are worth understanding. The problem is narrower and more specific: a general-purpose translator like Google Translate ignores the things that decide whether a cover letter lands or gets skimmed in five seconds. Register, cultural convention, idiomatic phrasing, the difference between sounding professional and sounding like a machine pretending to be professional. These are exactly the things a hiring manager notices first, and exactly the things a paste-and-click workflow does not check.
Recruiters report that they can identify machine-translated cover letters at a glance and routinely discard them without reading further. In discussions on r/AskAGerman, users warned that applications translated with Google Translate face what amounts to a desk reject. Threads on r/recruitinghell describe the same pattern from the other side: recruiters who spot AI-generated or machine-translated text and immediately move on. The damage is not a slightly worse impression. It is that nobody reads the letter at all.


What goes wrong: five concrete failures
The failures below are not hypothetical. They are the patterns that show up when you run a German cover letter through Google Translate and read the result as an English speaker would.


1. Register and formality
German has a built-in formal/informal distinction that runs through every sentence: Sie versus du, "Sehr geehrte Damen und Herren" versus "Hallo." English cover letters have their own register conventions, but they do not map one-to-one. Google Translate has no register toggle. It guesses the formality from the input, and it guesses wrong often enough to matter. "Mit freundlichen Grüßen" becomes "kind regards," which is fine. But "Ich freue mich auf ein persönliches Gespräch" might come back as "I'm looking forward to a personal chat," which reads as casually conversational in a context where "I welcome the opportunity to discuss my application in person" is what the register demands. A tool that lets you set the formality before translating avoids the guess entirely.
2. Formulaic phrases that do not survive translation
German cover letters lean on set phrases that signal professionalism precisely because every recruiter has read them a hundred times. "Wie Sie dem beiliegenden Lebenslauf entnehmen können" is one. Google Translate produces "As you can see from the enclosed CV," which is technically correct and stylistically flat. An English cover letter that says "As you can see from the enclosed CV" sounds like it is narrating its own paperwork. The natural English equivalent is to let the CV speak for itself and focus the letter on what the CV cannot show.
3. Idioms that become nonsense
"Ich habe mir in diesem Bereich die Sporen verdient" means "I have earned my spurs in this field," an equestrian metaphor for proven experience. Google Translate sometimes produces "I have earned the spurs in this area," which sounds like a line from a Renaissance faire. The idiom exists in English too, but it is archaic enough that a hiring manager will hear it as a translation artifact, not as confident self-presentation. Every language has these. The point is not that idioms are untranslatable; it is that a tool with no meaning notes to flag what is happening will hand you a sentence that is technically faithful and pragmatically wrong.
4. Passive voice
German cover letters frequently use passive constructions: "Es wurden folgende Projekte umgesetzt" (literally "the following projects were implemented"). English cover letters favor active voice: "I implemented the following projects." The passive is not wrong in either language, but the convention is different, and a hiring manager reading an English letter full of passives hears someone who is not taking ownership of their work. Google Translate preserves the structure of the source text, which means it preserves a structure that reads as evasive in the target language.
5. Gender and forms of address
German marks gender on nouns: "der Bewerber" (male applicant), "die Bewerberin" (female applicant). When translating into a language like French or Spanish, Google Translate often picks a default gender that may not match the applicant. In English the problem is subtler but still present: "der Bewerber" is frequently rendered as "the applicant" (neutral), but possessive pronouns and some phrasings can still carry an unintended gender marker. For someone applying in a language with grammatical gender, this is a detail that a tool without explicit gender controls will get wrong silently.
Tool comparison: Google Translate vs DeepL vs Fink
The table below compares the free web versions of each tool. Features in paid tiers are noted but not credited to the free version.
| Google Translate | DeepL (free) | Fink (free) | |
|---|---|---|---|
| Register / formality control | No | No (Pro only, 10 languages) | Yes (Formal / Neutral / Informal) |
| Back translation | No | No | Yes, runs automatically |
| Meaning notes (cultural nuance) | No | No | Yes |
| Glossary for consistent terminology | No | No (Pro only) | Yes, automatic |
| Languages | 249 | ~33 | 25 |
| Data location | US servers | EU option in Pro | EU (Helsinki), free and paid |
| Price | Free | Freemium (free tier heavily limited) | Freemium (~50 translations, no account) |
Comparison based on the respective free web versions, September 2026. Paid plans may offer additional features. DeepL's formality toggle is available only in the Pro tier, for Dutch, French, German, Italian, Japanese, Polish, Portuguese, Russian, Spanish, and Vietnamese. Google Translate has no register or formality control in any version. Fink's register setting is available in the free tier.
DeepL deserves credit where it is due: in blind tests conducted in March 2026, DeepL won 94 percent of head-to-head matchups against Google Translate across 48,000 evaluations and 16 language pairs, judged by professional linguists. For European languages in particular, DeepL's translation quality is consistently rated higher. Google Translate's strength is breadth: 249 languages, more than any competitor, and entirely free. Fink's strength is the part neither tool addresses: not the raw translation, but the verification layer that catches the errors that read smoothly and are wrong. Fink replaces neither a good translator nor a native-speaker review. It is a translation refinement tool, not a proofreading service.
Google Translate is a product of Google LLC. DeepL is a product of DeepL SE. This comparison is an independent editorial assessment and was not authorized by either company. All trademarks belong to their respective owners.
What hiring managers actually see


The threads on r/AskAGerman and r/recruitinghell describe a consistent pattern. When a cover letter reads as machine-translated, it is not scored lower on a rubric. It is set aside. The reasoning is straightforward: if the candidate could not be bothered to produce a letter in the language of the job posting, the reasoning goes, how much do they actually want the job? Whether that reasoning is fair is beside the point. It is what happens.
The tells that recruiters describe are the same ones that the failure modes above produce: syntax that is technically correct but rhythmically off, prepositions that are close but not quite right, literal renderings of idioms that a native speaker would never use, and a tone that shifts unpredictably between formal and casual within the same paragraph. None of these are individually fatal. Together, they signal that the letter was not written so much as generated, and the response is not to read it more carefully but to not read it at all.
The irony is that the content of the letter may be excellent. The candidate's qualifications may be a strong match. But the letter is the first thing a hiring manager sees, and a letter that announces itself as machine-translated closes the door before the qualifications get a chance to walk through it.
Try Fink for your next translation
See the translation, every change, and the why on one screen.
Open AppHow to translate a cover letter properly


The steps below assume you are starting with a cover letter written in your own language and need to submit it in another. They are not a substitute for having a native speaker review the final text, but they will get you closer than paste-and-click.
Write in the target language first, if you can. Even a rough draft written directly in English, in your own words, gives you something to refine. A translation of a native-language draft gives you something to polish. The difference matters: the first is your voice in another language; the second is your language filtered through a machine.
Set the register before you translate. Decide whether the letter should be formal, neutral, or informal, and make sure your tool can honor that decision. Google Translate cannot. DeepL can, but only in the Pro tier. Fink's register setting is available in the free tier and treats a wrong formality level as a named issue, not something to silently smooth over.
Run a back translation. Take the translated letter, translate it back into your own language, and read what comes back. If the round trip returns the meaning you intended, the translation probably survived. If it comes back as something you did not mean, you have found a problem before the hiring manager does. Back translation is the standard quality check that most applicants skip, and it is the single most effective way to catch silent errors.
Check the meaning notes. A translation tells you what was said. The notes tell you what the sentence is doing beyond the words: whether an idiom was rendered literally, whether a phrase carries a connotation you did not intend, whether the register drifted. A tool that explains the translation turns invisible errors into visible ones.
Keep terminology consistent with a glossary. If you mention a specific software, a certification, or a job title more than once, it should be translated the same way each time. A glossary that populates as you translate and locks key terms prevents the same word from appearing in three different renderings across the same letter.
Have a native speaker read the final version. No tool replaces this step. The best translation tool gets you 95 percent of the way there. The last 5 percent is the kind of thing only a native speaker catches: a phrase that is technically correct but idiomatically unusual, a tone that is one degree too formal or too casual, a cultural reference that does not land. If you do not know a native speaker, professional proofreading services exist for exactly this purpose.
Checklist: what to check before you submit
The steps above describe the workflow. The list below is what you check in the finished text, line by line, before you send it. Run through it every time, even if the letter is short.
- Register consistency. Read the letter start to finish and mark every pronoun and verb form. Is the formal register consistent throughout, or does it slip into casual somewhere in the middle? A single "I'm really excited" in an otherwise formal letter is the kind of inconsistency that signals machine translation.
- Set phrases. Search the letter for any phrase that reads like a translation of a formula from your own language. "As you can see from the enclosed CV," "I refer to your advertisement," "I hereby apply for" — these are the fingerprints of a source-language convention carried over. Replace each one with what an English letter would actually say.
- Idioms and metaphors. Any figurative language in the source text needs to be checked. "Die Sporen verdient," "sich einbringen," "auf Augenhöhe" — these either have natural English equivalents or they do not, and the only way to know is to check each one. If the English reads like a literal rendering, rewrite it.
- Passive to active. Scan for every passive construction. "It was implemented," "the project was led by me," "the following results were achieved." Convert each one to active voice unless the passive is genuinely doing work. An English cover letter should be full of "I" statements, not "it was" statements.
- Gender and pronouns. If the target language has grammatical gender, check every gendered noun, adjective, and pronoun against the applicant's actual gender. If the target language is English, check that pronouns are consistent and that no gendered phrasing has been inadvertently introduced.
- Salutation and closing. Does the salutation match the target culture? "Dear Hiring Manager" for an English letter, not "Dear Sir or Madam" unless you genuinely do not know the recipient's identity. Does the closing match? "Sincerely" or "Kind regards" — not "With friendly greetings."
- Formatting conventions. Is the letter one page? Does it follow the structural expectations of the target country? A letter that follows German formatting conventions but is written in English will read as foreign, not just translated.
- Consistent terminology. If you mention a job title, a certification, or a piece of software more than once, is it translated the same way each time? Inconsistent rendering of the same term within a single letter is a red flag.
- Prepositions. Go through the letter and check every preposition against what a native speaker would use. "Responsible for," not "responsible of." "Experience in," not "experience on." These are small, but a cluster of slightly wrong prepositions is the single most reliable signal that a letter was machine-translated.
- Read it aloud. If anything sounds stilted when spoken, it will sound stilted when read. The ear catches what the eye skips over: a rhythm that is off, a sentence that runs too long, a word that is technically correct but nobody actually says.
Cultural differences in cover letters


A good translation is not just about language. It is about conventions. The cover letter format that is expected in Germany is not the same one expected in the United States or the United Kingdom, and a letter that follows the wrong conventions signals that the applicant does not understand the context they are applying into.
Length and structure. German cover letters are typically one page, highly structured, with a formal subject line (Betreff) and a precise, factual tone. American cover letters are also one page but tend to be more narrative and persuasive, with a stronger emphasis on selling the candidate's fit for the role. British letters are similar to American ones but slightly more reserved in tone.
The CV or resume. A German Lebenslauf is typically two to three pages, detailed, and includes personal information such as date of birth and nationality. An American resume is one to two pages, achievement-focused, and deliberately excludes personal details that could trigger discrimination concerns. Including a photo on a resume is standard in Germany and discouraged or even risky in the United States.
Salutation. "Sehr geehrte Damen und Herren" maps to "Dear Hiring Manager" or, better, "Dear [Name]" if you can find the hiring manager's name. Addressing a specific person is valued in English-language applications more than in German ones, where the formal generic salutation is still accepted.
Self-presentation. German cover letters tend toward understatement: factual, specific, letting achievements speak for themselves. American and British letters expect more direct self-advocacy. A German candidate translating a German-style letter into English risks sounding passive by Anglo-American standards, not because the content is weak but because the convention is different.
References. Anglo-American letters often close with "References available upon request." German letters typically do not. Including the line in an English letter is harmless and conventional; omitting it is also fine. The point is that conventions exist, and a translated letter that follows the source-language conventions will read as slightly off to a target-language reader.
Questions people ask about this
Can I use Google Translate for my cover letter? You can, but the result will likely read as machine-translated to a hiring manager, and many recruiters discard machine-translated applications without reading further. If you do use it, at minimum run a back translation to check for silent errors, and have a native speaker review the final text.
Is DeepL better than Google Translate for cover letters? DeepL consistently outperforms Google Translate in blind tests, particularly for European languages. However, the free version of DeepL does not include the formality toggle, which is one of the most important features for a cover letter. Without it, you have the same register-guessing problem as Google Translate.
How do I translate my cover letter into English correctly? Write in English first if you can, set the register explicitly, run a back translation to catch errors, check meaning notes for cultural nuance, keep terminology consistent with a glossary, and have a native speaker review the final version. Tools like Fink handle the middle steps; the first and last are on you.
What mistakes does Google Translate make with cover letters? The five most common: wrong register or formality, literal translations of set phrases, idioms rendered as nonsense, passive voice preserved where the target language expects active, and gender markers applied incorrectly in languages with grammatical gender.
Should I have my cover letter professionally translated? If the job is important to you, yes. A professional translator or a native-speaking proofreader will catch the 5 percent that no tool catches. A tool like Fink can get you to 95 percent and make the proofreader's job faster, but it does not replace one.
Can a hiring manager tell if I used Google Translate? Often, yes. The tells are inconsistent register, slightly wrong prepositions, literal idioms, and syntax that is grammatically correct but rhythmically unnatural. A hiring manager who reads cover letters regularly will recognize these patterns immediately.
Sources and further reading
The comparison data draws on DeepL's own quality benchmarks (March 2026 blind tests, 48,000 evaluations across 16 language pairs), Google Translate's language coverage (249 languages as of 2024), and DeepL's formality feature documentation (Pro only, 10 languages). Reddit discussions on machine-translated applications can be found on r/AskAGerman and r/recruitinghell. German and American cover letter conventions are compared in guides from Expatrio and CareerBee. For the broader question of why modern translation models are good at translation but still fail silently, see why LLMs are good at translation. For the technique of back translation as a quality check, see how to use a translator to learn a language.