A localization manager proposes switching from human translation to Neural Machine Translation (NMT) for all content. A localization engineer pushes back. Which concern is most valid?
NMT quality is highly content- and language-pair-dependent — "good enough for most content" is not good enough for all content.
NMT performs well for: high-frequency UI strings (short, in-context, high TM leverage), informational content with simple structure, and high-resource language pairs (en→fr, en→de, en→ja). NMT struggles with: creative marketing copy (tone and cultural adaptation), legal text (precise terminology, jurisdiction-specific terms), domain-specific jargon (new product features, technical specifications), and low-resource language pairs (en→Swahili, en→Kazakh). The industry standard today is risk stratification: MT + light MTPE for UI strings, MT + full MTPE for support content, human translation for marketing and legal. No localization engineer should recommend replacing all human translation with NMT without a quality assessment by category.
Key vocabulary: • NMT (Neural Machine Translation) — deep learning-based MT; current industry standard (DeepL, Google Translate NMT, ModernMT) • content risk stratification — categorising content by quality risk to determine appropriate MT+human mix • MT hallucination — MT generating plausible-sounding but factually incorrect translations for domain terms
2 / 10
A project manager asks a localization engineer to explain the difference between full MTPE and light MTPE. Which explanation is correct?
Full vs. light MTPE is a quality level decision — full MTPE targets human-equivalent quality; light MTPE targets "good enough to understand."
Use cases: full MTPE is appropriate for customer-facing product UI (users notice awkward phrasing), marketing content, and any content that will be published without further review. Light MTPE is appropriate for internal documentation, support knowledge base articles, and content that will be read once and discarded (transactional emails, order confirmations). The cost difference is significant: full MTPE takes 30-50% of the time of pure human translation; light MTPE takes 15-25%. The risk: using light MTPE quality for customer-facing content can damage brand perception in subtle ways — the text is technically correct but doesn't sound like the brand voice.
Key vocabulary: • full MTPE — all errors corrected; output equivalent to human translation quality • light MTPE — only critical errors fixed; style and minor fluency issues accepted • post-editing effort — the amount of editing needed to bring MT output to the required quality level
3 / 10
A localization engineer mentions using a QE (Quality Estimation) model to triage MT output before sending it to post-editors. What does QE measure and how is it used?
QE enables intelligent routing: high-confidence MT output goes to light MTPE, low-confidence output goes to full MTPE or human translation — reducing total cost without sacrificing quality.
QE models (e.g., COMET-QE, TransQuest) are trained on parallel data with human quality annotations. They output a score (typically 0-1) for each segment. Integration in a TMS workflow: MT engine translates a batch → QE model scores each segment → TMS creates three queues: (1) >0.85 score → light MTPE queue; (2) 0.60-0.85 → full MTPE queue; (3) <0.60 → human translation queue (MT suggestion shown as a hint only). This saves 30-40% in total translation cost versus sending everything to full MTPE. The limitation: QE scores are probabilistic — some high-QE segments may still have subtle errors.
Key vocabulary: • QE (Quality Estimation) — automated MT quality prediction without a reference translation; predicts post-editing effort • QE score — confidence metric (0-1) for an MT segment; used to route to appropriate post-editing tier • intelligent routing — using QE scores to direct segments to light MTPE, full MTPE, or human translation queues
4 / 10
A team adds their product's key terms to a DNT (Do Not Translate) list before running MT. Which example best justifies having "Firebase" and "Firestore" on the DNT list?
MT engines treat unknown words as candidates for translation or transliteration — DNT lists prevent product and brand names from being incorrectly adapted.
Real examples of MT errors without DNT: "Firebase" → "Feuerbasis" (German, literal translation of fire+base), "Slack" → "Schlaff" (German, meaning "sluggish" — a valid German translation of the English word), "Notion" → "Vorstellung" (German). These are embarrassing product quality issues. DNT lists can be implemented in MT engines as terminology constraints (modern NMT engines like ModernMT and DeepL API support terminology injection). The TMS usually provides a DNT glossary field for each term — the MT engine is instructed to pass these terms through unchanged. The same mechanism works for technical terms that must remain in English (kubectl, npm, API endpoints).
Key vocabulary: • DNT (Do Not Translate) — a list of terms the MT engine must preserve unchanged in the output • terminology injection — feeding a glossary to an NMT engine at inference time to constrain translations of specific terms • transliteration — adapting a word to the target script's phonetic representation (Firebase → Файербейс in Russian Cyrillic)
5 / 10
A localization lead proposes using an LLM (like GPT-4 or Claude) for translation instead of a traditional NMT engine. A senior engineer asks about the main trade-offs. Which assessment is most accurate?
LLMs excel at nuanced, context-rich translation but are slow and expensive at scale — the right tool depends on content type, volume, and quality requirements.
LLM advantages for translation: they handle implicit context ("this button is in a mobile app confirmation dialog"), can be prompted with brand voice guidelines, adapt register (formal/informal) consistently, and handle idioms and cultural adaptation better than NMT. LLM disadvantages: (1) cost — 10-100x more expensive per segment than NMT at scale; (2) speed — 2-10 seconds per segment vs. milliseconds for NMT; (3) terminology control — harder to reliably enforce DNT and glossary constraints vs. NMT with terminology injection; (4) consistency — LLMs may produce slightly different translations for the same source segment in different API calls. Emerging workflow: NMT → QE scoring → LLM post-editing for low-QE or high-value segments.
Key vocabulary: • LLM for translation — using generative AI models for translation; better at nuance, worse at scale economics • tone adaptation — adjusting formality, voice, and style to match brand guidelines during translation • hybrid MT pipeline — combining NMT (speed/cost) with LLM (quality/nuance) based on content type and QE scores
6 / 10
During a Slack discussion about translating a new mobile app's UI into Spanish, Sarah (Localization Engineer) receives the following message from Mark (Product Manager): 'Just use Google Translate – it's free and fast!' Which statement best reflects Sarah's professional response? translate
This scenario tests the engineer's understanding of the limitations of free MT tools. While convenient, Google Translate frequently struggles with nuanced language and technical jargon, leading to errors that can negatively impact user experience and brand reputation. The correct response acknowledges its potential while emphasizing the need for quality control.
7 / 10
You are reviewing a Pull Request description for a localization task. The author writes: 'I've used the MT engine to translate this documentation into French. It should be ready for QA.' What immediate action should you recommend? qa
This question assesses understanding of the crucial role of QA in MT workflows. Machine translation outputs *always* require thorough review and correction by a qualified linguist to ensure accuracy, fluency, and cultural appropriateness before release. The PR description is incomplete without this step.
8 / 10
A localization lead asks you to explain the concept of 'Terminology Management' within the context of LLM-assisted translation. Which statement accurately describes terminology management? terminology
Terminology management is a core practice in localization. It's about systematically identifying and controlling key terms to maintain consistency across translations – crucial when using LLMs which may generate variations or introduce new terminology based on context. This ensures that the translated content aligns with established brand guidelines.
9 / 10
During a standup meeting, your team lead asks: 'How are we mitigating potential biases in translations generated by our LLM?' Which response demonstrates the best understanding of this challenge? bias
LLMs can inherit biases from their training data, leading to skewed or inappropriate translations. Quality Estimation (QE) models are vital for detecting these issues – and using them to refine the LLM's output is a proactive approach to mitigating this risk.
10 / 10
A senior developer asks you: 'We're integrating an LLM for translation. What's the biggest difference in terms of workflow versus traditional NMT?' Which answer best captures this distinction? workflow
The key difference lies in the initial output. Traditional NMT provides a translated result that *requires* substantial post-editing. LLMs often generate outputs that are more editable directly – allowing for greater contextual adaptation and reducing the overall editing effort, though human review remains essential.
This module has 10 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Localization Engineering Language exercises?
Browse the full Localization Engineering Language hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.