Why Your English Sounds Translated

Your grammar is fine. That is what makes this hard to fix.

Spell check passes. Grammarly passes. You read the sentence back and cannot point at anything wrong with it. And still, somewhere between your screen and the reader, something registers as off. Not wrong - foreign.

This is first-language interference, and it is not a sign of weak English. It is the predictable residue of knowing another language well. Your first language has habits: where it puts the verb, how much it hedges, whether it needs an article, how formal a request has to be before it counts as polite. Those habits survive translation even when the vocabulary does not.

Below are the patterns that give it away, sorted by first language. Most people recognise two or three of their own immediately.

Why grammar checkers cannot see this

A grammar checker evaluates a sentence against the rules of English. Interference produces sentences that break no rules.

"I would like to kindly ask you if it would be possible to send me the document" is flawless English. It is also three times longer than a native speaker would make it, and the excess politeness reads as either sarcasm or anxiety depending on the reader.

The tool has nothing to flag. The problem is not correctness, it is register, rhythm, and idiom - the layer above grammar, where choices are conventional rather than rule-governed.

That is why running the same text through another grammar pass never fixes it. You need a different kind of edit.

What this is not

It is worth saying plainly, because most people carrying these patterns assume the opposite: interference is not a competence problem, and it is not a vocabulary problem.

The people who produce the most interference are usually the ones with the strongest command of their first language. A rich, precise instrument in one language leaves a deeper imprint on the second. Someone who writes beautifully in Portuguese carries more Portuguese structure into English than someone who writes plainly in it.

So the patterns below are not a list of mistakes to feel bad about. They are a map of where two systems overlap, which is exactly the kind of thing you can fix mechanically once you can see it.

German and Dutch speakers

The stacked noun

German builds meaning by compounding. English prefers to unpack.

Interference: "We need a customer data quality improvement process."
Natural: "We need a process for improving customer data quality."

Three or more nouns in a row is the tell. English readers parse noun stacks slowly, because they cannot tell which noun is the head until they reach the end.

Formality that reads as distance

German business register is genuinely more formal than English business register. Translating it faithfully overshoots.

Interference: "I hereby inform you that the deployment has been completed."
Natural: "The deployment is done."

False friends

"Actual" does not mean current. "Eventually" does not mean possibly. "Become" does not mean receive. Each of these produces a sentence that parses cleanly and means something you did not intend, which is worse than an obvious error.

Speakers of Romance languages

Spanish, Portuguese, Italian, French.

Sentences that will not end

Romance prose tolerates - and rewards - long subordinate chains. English business writing does not.

Interference: "Considering that the migration was scheduled for Friday, and taking into account that the team responsible for the validation will not be available until Monday, I believe that it would be preferable to postpone."
Natural: "The validation team is out until Monday. I suggest we postpone the migration."

Same information, half the words. The English version reads as decisive. The original reads as hesitant, even though nothing in it is actually hedged.

Politeness inflation

Interference: "I would want to ask you if you could possibly review my pull request."
Natural: "Could you review my PR when you get a chance?"

The false friends that survive spell check

"Assist" for attend. "Pretend" for intend. "Sensible" for sensitive. "Library" for bookshop. "Comprehensive" for understanding.

Speakers of Slavic languages

Polish, Russian, Czech, Ukrainian, Serbian, Croatian.

The missing article

Slavic languages have no articles, so English articles have to be learned as a separate system with nothing to lean on.

Interference: "I sent you document about problem with database."
Natural: "I sent you the document about the problem with the database."

This is the most recognisable interference pattern in English, and the one native speakers notice fastest - not because it obstructs meaning, but because it is so consistent.

Aspect showing through

Slavic verbs encode whether an action is complete. English does the same work with tense and adverbs, and the mapping is not clean.

Interference: "I am working on this ticket since Monday."
Natural: "I have been working on this ticket since Monday."

Mandarin and Cantonese speakers

Tense carried by adverbs

Chinese marks time with adverbs rather than by inflecting the verb, so the adverb arrives and the verb stays bare.

Interference: "Yesterday I go to the office and fix the bug."
Natural: "Yesterday I went to the office and fixed the bug."

Countable and uncountable nouns

Interference: "I have three feedback for you."
Natural: "I have three pieces of feedback for you."

Topic-first ordering

Interference: "This bug, I already fixed it."
Natural: "I already fixed this bug."

Japanese and Korean speakers

The vanishing subject

Both languages routinely drop the subject when context supplies it. English almost never does.

Interference: "Checked the logs. Seems to be a timeout."
Natural: "I checked the logs. It looks like a timeout."

In a Slack message this reads as terse rather than wrong. In a document it reads as unfinished.

Hedging past the point of confidence

Japanese and Korean encode deference grammatically. English encodes it with words, and every hedge you add costs you authority.

Interference: "I think that maybe it might be possible that this could perhaps be a caching issue, but I am not sure."
Natural: "This looks like a caching issue. I have not confirmed it yet."

Both sentences admit uncertainty. Only the second sounds like it came from someone who knows what they are doing.

Topic-comment structure leaking through

Interference: "About the deployment, it was decided that it will be delayed."
Natural: "We decided to delay the deployment."

Note what disappeared: the passive voice. Topic-comment structure plus a preference for impersonal phrasing produces agentless English, and agentless English reads as evasive to an American or British reader even when nothing is being evaded.

Hebrew and Arabic speakers

Directness that lands as an order

Hebrew and Arabic business communication carries less softening than English does. Translated at face value, requests arrive as instructions.

Interference: "Send me the report."
Natural: "Could you send me the report when you have a minute?"

This is the mirror image of the Romance problem, and it is more expensive. Over-politeness makes you sound uncertain. Under-politeness makes you sound rude, and readers usually attribute rudeness to character rather than to language.

Present tense doing too much work

Hebrew has no verb "to be" in the present tense, which produces:

Interference: "The build broken."
Natural: "The build is broken."

Nordic language speakers

Swedish, Norwegian, Danish, Finnish.

Directness without the cushion

Nordic languages are direct, and Nordic speakers of English are usually fluent enough that readers stop attributing bluntness to language at all.

Interference: "This is wrong."
Natural: "I think there might be an issue here."

The fluency is the trap. A reader who hears an accent forgives directness. A reader looking at flawless written English does not.

Hindi, Bengali, Tamil and Urdu speakers

English in South Asia is often a first working language rather than a foreign one, which produces a different pattern: not errors, but a distinct and internally consistent register that reads as formal to American and British ears.

Inherited formality

Interference: "Please do the needful and revert at the earliest."
Natural: "Could you take care of this and let me know when it is done?"

"Revert" meaning reply, and "do the needful", are standard in Indian English and unfamiliar or archaic elsewhere. Neither is wrong. They just mark the writing as coming from a different English.

The continuous tense doing extra work

Interference: "I am having a question about the deployment."
Natural: "I have a question about the deployment."

Prepositions that shifted

Interference: "Let us discuss about the timeline."
Natural: "Let us discuss the timeline."

The pattern everyone shares: over-explaining

Across every language above, there is one habit in common. When you are less certain of your English, you compensate with volume - more context, more qualification, more restating of what you just said, in case the first version did not land.

Interference: "As I mentioned earlier in my previous message, and I hope this is clear, the issue that we are seeing seems to be related to the cache, which as you know we changed last week."
Natural: "I think this is the cache change from last week."

Volume reads as uncertainty in English, not thoroughness. The shortest version of your point is almost always the most confident-sounding one, and confidence is what most of these patterns are quietly costing you.

The two-minute self-check

Before sending anything that matters, run these five:

Count your hedges. More than one "I think", "maybe", "perhaps" or "possibly" in a single sentence is one too many.
Find the longest sentence. If it has more than two commas, split it.
Look for noun stacks. Three nouns in a row: unpack them.
Check who is doing things. If your sentences have no subject, put the people back in.
Read it as your reader. Does the request sound like a request, like an order, or like an apology?

That check catches most of what a grammar tool misses. It also takes two minutes you do not always have, which is the real problem.

The faster path

Interference is persistent because it happens before you write. You compose the thought in your first language, translate it, and the translation carries the structure across. Editing afterwards means fighting your own draft.

The alternative is to stop doing the translation step badly and let something else do it. Write the message in the language you actually think in, then convert it in place. You skip the translation tax, and the output does not carry your first language's sentence shape, because it was never built out of it.

That is the approach I wrote about in Write 2x Faster in Your Native Language (opens in new tab). Echoo runs it as a keyboard shortcut inside most Mac apps, after you grant macOS Accessibility permission, so the conversion happens where you were already typing - Slack, Mail, a pull request comment - with no browser tab in the middle.

Your first 10 credits are included, with no API key and no card. You can also connect your own provider key and run in BYOK mode.