Diglot workflows by task and native language
Concrete walkthroughs of how Diglot fits your writing — essay, research paper, business email, cover letter, LinkedIn profile — tuned to your specific L1 transfer patterns. Honest about what changes and what stays generic.
All use cases
- Business email
Writing a business email in English for Arabic speakers
An Arabic business email carries elaborate greetings and «al-» into English, where short and warm wins. Here's the Diglot workflow for emails that read professional, not ceremonial.
Read the workflow → - Business email
Writing business emails in English for Chinese (Mandarin) speakers
Chinese professionals writing English business emails face two register problems at once: tense consistency drift in transactional updates, and over-formal phrasing leftover from Chinese business norms. Diglot identifies both as Chinese-leak.
Read the workflow → - Business email
Writing business emails in English for Japanese speakers
Japanese professionals writing English business emails face a register collision: Japanese business correspondence trains formal humility that translates as deferential understatement in English business context, where directness is the convention. Plus Japanese grammar omits subjects and relies on particles.
Read the workflow → - Business email
Writing a business email in English for Korean speakers
A Korean business email drops articles, swaps prepositions, and uses «until» for a deadline. Here's the Diglot workflow for emails that read clear and professional.
Read the workflow → - Business email
Writing a business email in English for Russian speakers
A Russian business email translated word-for-word reads blunt in English — the directness that's normal in Russian lands as cold. Here's the Diglot workflow for emails that stay warm and professional.
Read the workflow → - Business email
Writing business emails in English for Spanish speakers
Spanish-speaking professionals write business emails 3× slower than native-English colleagues. Diglot tunes for English formal register — without making your emails sound robotic.
Read the workflow → - Cover letter
Writing a cover letter in English for Arabic speakers
Arabic speakers writing English cover letters face a register problem — the formal Arabic conventions that signal respect read as stiff or over-deferential in English. Diglot tunes for English hiring register.
Read the workflow → - Cover letter
Writing a cover letter in English for Chinese (Mandarin) speakers
A Mandarin-influenced cover letter drops tense and plural endings and pairs «although» with «but». Here's the Diglot workflow for a letter that reads native.
Read the workflow → - Cover letter
Writing a cover letter in English for Japanese speakers
A Japanese cover letter translated directly undersells you — the humility that's polite in Japanese reads as weakness in English. Here's the Diglot workflow for a confident, natural letter.
Read the workflow → - Cover letter
Writing a cover letter in English for Korean speakers
Korean speakers writing English cover letters face a structural mismatch: Korean clause endings (-고, -며) allow long flowing chains that translate as English run-on sentences. Plus Korean grammar lacks articles and plural marking that English hiring conventions demand.
Read the workflow → - Cover letter
Writing a cover letter in English for Russian speakers
A Russian cover letter translated directly arrives missing «the», missing «is», and either too ceremonial or too blunt. Here's the Diglot workflow for a confident, natural letter.
Read the workflow → - Cover letter
Writing a cover letter in English for Spanish speakers
A Spanish-influenced cover letter trips on false friends — «assist to the interview», «actually» — and a too-formal opening. Here's the Diglot workflow for a letter that lands like a native wrote it.
Read the workflow → - Essay
Writing an essay in English for Arabic speakers
Writing an English essay when you think in Arabic means fighting «the» where English wants nothing, and a missing «is» where English needs it. Here's the Diglot workflow for academic essays in one editor.
Read the workflow → - Essay
Writing an essay in English for Chinese (Mandarin) speakers
Chinese students writing English essays land at a specific friction: Chinese has no verb tense inflection, so essays drift between past and present even within paragraphs. Plus Chinese clause-chaining produces comma splices, and classifier patterns leak as awkward English phrasing.
Read the workflow → - Essay
Writing an essay in English for Japanese speakers
Writing an English essay when you think in Japanese means supplying articles that do not exist in Japanese and trimming hedges that do. Here's the Diglot workflow for academic essays in one editor.
Read the workflow → - Essay
Writing an essay in English for Korean speakers
Korean students writing English essays face structural mismatch: Korean clause endings (-고, -며) allow flowing chains that translate as English run-ons. Plus Korean lacks articles and optional plural marking that English demands.
Read the workflow → - Essay
Writing an essay in English for Russian speakers
Writing an English essay when you think in Russian shouldn't mean three browser tabs. Here's the Diglot workflow for academic essays — drafting, translating, revising in one editor.
Read the workflow → - Essay
Writing an essay in English for Spanish speakers
Spanish speakers writing English essays land at a specific friction point: false friends slip through unnoticed, ser/estar conflations leak as «is/are» misuse, and Spanish gerundio over-translates as English gerund. Diglot identifies the Spanish-transfer signature.
Read the workflow → - LinkedIn profile
Writing a LinkedIn profile in English for Arabic speakers
Arabic-speaking professionals writing English LinkedIn profiles face a register collision: Arabic professional convention trains elaborate formality that translates as stiff over-deferential English. Plus Arabic's «al-» definite article + VSO word order leak as passive English.
Read the workflow → - LinkedIn profile
Writing a LinkedIn profile in English for Chinese (Mandarin) speakers
A Mandarin-influenced LinkedIn profile drops tense and plural endings and pairs «although» with «but». Here's the Diglot workflow for a profile that reads native.
Read the workflow → - LinkedIn profile
Writing a LinkedIn profile in English for Japanese speakers
Japanese-speaking professionals tend to undersell on English LinkedIn — humility conventions translate as understatement. Diglot tunes for confident-but-honest English self-positioning.
Read the workflow → - LinkedIn profile
Writing a LinkedIn profile in English for Korean speakers
A Korean-influenced LinkedIn profile drops articles and plurals and adds stray prepositions. Here's the Diglot workflow for a profile that reads native — without overselling or underselling.
Read the workflow → - LinkedIn profile
Writing a LinkedIn profile in English for Russian speakers
Russian-speaking professionals writing English LinkedIn profiles face two transfer pressures: grammatical (article omission, missing copula) and cultural (Russian professional CV register reads as overly modest in English LinkedIn context).
Read the workflow → - LinkedIn profile
Writing a LinkedIn profile in English for Spanish speakers
A Spanish-influenced LinkedIn «About» trips on false friends — «actually», «assist», «sensible» — that mean something else in English. Here's the Diglot workflow for a profile that reads native.
Read the workflow → - Research paper
Writing a research paper in English for Arabic speakers
An Arabic-influenced research paper carries «al-» into English «the», drops «is» before adjectives, and chains methods with «and». Here's the Diglot workflow for journal-ready English.
Read the workflow → - Research paper
Writing a research paper in English for Chinese (Mandarin) speakers
Chinese researchers writing English papers face specific transfer patterns — Diglot catches tense drift in methods sections, classifier-leak in noun phrases, and run-on sentences from long Chinese subordination.
Read the workflow → - Research paper
Writing a research paper in English for Japanese speakers
Japanese researchers writing English papers face an architectural mismatch: Japanese grammar omits subjects and relies on particles, while English requires explicit subjects + prepositions. Plus Japanese academic humility translates as English understatement.
Read the workflow → - Research paper
Writing a research paper in English for Korean speakers
A Korean-influenced research paper drops articles Korean has none of, inserts prepositions where English wants none, and leaves plurals unmarked. Here's the Diglot workflow for journal-ready English.
Read the workflow → - Research paper
Writing a research paper in English for Russian speakers
Russian researchers writing English papers face transfer patterns that show up most concentrated in methods sections — article omission before specific nouns, missing copula in present-tense claims, perfective aspect mapping wrongly to English progressive.
Read the workflow → - Research paper
Writing a research paper in English for Spanish speakers
Spanish researchers writing English papers face transfer patterns concentrated in methods + results sections: false friends slip through unnoticed («eventually» means «possibly» in Spanish), ser/estar conflations leak as «is/are» misuse, and Spanish long-subordinated sentence structure produces 50+ word English sentences that read as dense.
Read the workflow →
Don't see your use case + language combo?
We're shipping first-wave use cases — essay, research paper, business email, cover letter, LinkedIn profile, across 6 deeply-modeled L1s. More combinations are coming. If your specific task isn't yet documented, sign up — the workflow patterns apply to most ESL writing tasks even before we publish the specific page.
Start for freeQuestions about these workflows
Which native languages does Diglot cover here?
These guides cover six deeply-modeled first languages — Arabic, Chinese (Mandarin), Japanese, Korean, Russian, and Spanish — across essays, research papers, business emails, cover letters, and LinkedIn profiles.
What if my exact task and language combination is not listed?
The workflow patterns apply to most ESL writing tasks before a specific page exists. The product itself is not limited to the combinations documented here — these pages are guidance, not a feature gate.
Why does the guidance differ by native language?
The mistakes that survive into an English draft depend on the first language — article use, verb aspect, and word order break in different places for a Russian speaker than for a Korean one. Generic advice misses those.
Do I need a paid plan to use these workflows?
No. The Free plan covers the core bilingual workflow with limited word counts, which is enough to test whether the approach in these guides fits how you actually write.
