Last month a Java backend engineer posted his CV to a German jobs forum. Strong profile: four years of experience, Spring Boot, Kotlin, microservices handling half a million transactions per run. The kind of résumé that sails through an applicant tracking system without a scratch.
The recruiters who replied were not impressed. One of them wrote, more or less: this isn't a CV, it's a novel. Another flagged a line that read "92% accuracy versus a 71% baseline" and warned that in Germany, numbers like that come across as bragging — or worse, as something you can't actually prove. A third said the summary section at the top should just be deleted. Nobody reads it here.
None of them said the engineer was unqualified. They said his CV was written in the wrong language — and they didn't mean German.
The style that works everywhere except where you're applying
There is a dominant template for the modern tech CV, and most people reading this have internalized it without noticing. Every bullet point follows the same shape: a strong action verb, a piece of technical implementation, and a quantified outcome. "Architected a distributed pipeline that reduced latency by 40%." "Led a migration improving throughput 3x." It reads well. It performs well against keyword scanners. It is, broadly, what American career advice has taught for fifteen years, and what most AI résumé tools now produce by default because that advice is what they were trained on.
The problem is that this style is not universal. It is regional. And the region it comes from is not the one our Java engineer was applying to.
German hiring culture — and this extends across much of the DACH market, Austria and German-speaking Switzerland included — rewards a different set of signals. Formal qualifications matter. Certificates matter. A clear, verifiable record of where you worked and what you were responsible for matters. What tends to not land well is a wall of self-reported metrics. To a German recruiter scanning quickly, "increased accuracy to 92%" is not a flex. It's an unverifiable claim, and unverifiable claims read as inflation. You gain very little by including the number and you risk looking like someone who oversells.
That gap is the whole story. The engineer's CV wasn't bad. It was optimized for the wrong reader.
Why this is getting worse, not better
A few years ago this was just a cultural-translation problem: an American-style CV landing on a German desk. Now there's a second layer on top of it, and it's the reason recruiters are getting twitchy.
AI writing tools have made the action-verb-plus-metric formula not just common but nearly universal. When every applicant uses the same class of tool, every CV starts to converge on the same rhythm. The same cadence. The same suspiciously even polish. Recruiters notice. On that same forum thread, more than one person said some version of "you can tell this was written by AI" — and they were not paying a compliment.
Here's the uncomfortable part. The detectability isn't really about individual words. You can swap "spearheaded" for "led" and "leveraged" for "used" all day and it changes nothing. What gives it away is structure: when every single bullet has the identical architecture — verb, implementation, number, repeat — the pattern itself becomes the signal. A human writing about their own work is messier than that. Some accomplishments have a number attached. Most don't. Some sentences are long because the work was complicated; others are four words because there's nothing more to say. Real careers are uneven. The formula sands all of that down into something that's smooth, confident, and faintly artificial — and a German recruiter, who already distrusts the metric-heavy style on cultural grounds, reads that smoothness as a second red flag stacked on the first.
So the AI-optimized CV manages to fail twice in this market. Once for being too American, once for being too obviously machine-shaped.
What German recruiters actually want to see
If you're applying into the DACH market, the adjustments are not dramatic, but they cut against most of the default advice:
Drop the summary or keep it to a sentence. The space-consuming professional summary at the top is an Anglo-American convention. Many German recruiters skip straight past it to your experience and education.
Shorten the bullets, and don't force a metric into every one. A bullet can simply state what you were responsible for. "Maintained the payment-service backend and its CI pipeline" is a perfectly respectable line. It doesn't need a percentage bolted onto it to justify its existence.
Lead with the verifiable. Where you worked, your role, the dates, your formal qualifications and certificates. These are the things a German recruiter weighs first, because they can be checked. The unverifiable accomplishment is treated with more suspicion than reward.
Let the writing be a little uneven. This sounds strange as advice, but it's the antidote to the machine-shaped problem. If three of your bullets have strong numbers and the rest are plain descriptions, leave it that way. The unevenness is what real experience looks like, and it's far more credible than ten identically-structured lines of polished accomplishment.
And — though it's a harder fix — write in German if the role is German-facing. We've watched applicants get genuine interest from their technical profile and then stall at the language line. Strong English plus B1 German often isn't enough for a role that lists C1. That's a separate barrier from the one this post is about, but it's the one that ends the most processes, and no amount of CV polish gets around it.
The point underneath all of this
The reflex, when a CV gets rejected, is to make it more optimized. More metrics, stronger verbs, tighter keyword coverage. In the DACH market that reflex frequently makes things worse, because the thing being optimized for — a confident, quantified, ATS-friendly American résumé — is precisely the thing the local reader is wary of.
The better instinct is to optimize for the actual person reading it. A German recruiter who scans for formal qualifications and gets suspicious of inflated numbers is a very different reader from a Silicon Valley ATS, and the same CV cannot serve both well. Tailoring isn't only about matching keywords to a job description. It's about matching tone and structure to a hiring culture — and that's the part most tools, and most applicants, still get wrong.
RefactorCV is built around exactly this idea — that a good CV is the one written for the person who'll actually read it, not for a scanner. If the DACH market is where you're applying, that distinction is the whole game.