Design a runtime localization (i18n) system
PremiumFrontend systemMedium
- ICU MessageFormat
- CLDR plural rules
- Over the air copy updates
Quick answer
This frontend system interview question asks you to design a runtime localization (i18n) system. Aim for a design that loads fast, stays responsive and is easy to maintain, then explain components, state, data fetching and trade-offs. Interviewers want to see how you structure the interface, manage state and keep the experience fast.
The problem
Design a runtime localization (i18n) system for a large web app, like the translation layer big consumer sites use to ship in dozens of languages. It loads UI copy per locale at runtime, formats variables and plurals, and lets writers push copy changes without a code release. The hard parts are bad pushes, missing translations and longer text breaking layouts.
What must a runtime localization (i18n) system do?
- Formatting: Render messages with variables, plurals and select, plus locale-aware numbers, dates and currencies, using each locale's plural rules.
- Copy without release: A published copy change reaches users within 10 minutes without a new build, and can be rolled back in one step.
How well must it do it?
- Never break the page: A bad or failed copy push never crashes rendering or shows blank text; the app keeps the last good copy.
- Load cost: Translations add under 15 KB gzipped to a route's first load and no extra request before first render.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- ICU MessageFormat
- CLDR plural rules
- Over the air copy updates
- Fallback locales
- Pseudo localization
- RTL layout
How you’ll practise
- Requirements
- Components
- State and data
- Network and caching
- Performance and accessibility
- Wrap-up
Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.
What do interviewers look for?
In any frontend system design round.
- Starts from the user flows and the screens
- Splits the interface into clear components
- Decides where state lives and how it stays in sync
- Plans data fetching, caching and loading states
- Covers performance, accessibility and error states
- Explains how the design holds up on slow networks and small screens
Questions people ask about this interview question
- Which design type is this question?
- It is a frontend system question. You design a runtime localization (i18n) system and explain your choices the way you would in an interview.
- Is this question asked at entry level?
- It is marked Medium. Entry-level engineers can practise it, but it expects you to reason about requirements and trade-offs, not only list components.
- What should I cover first?
- Start with the main user flows, the screens and the data each one needs. Agree on scope with the interviewer before you design anything.
- Can I practise it for free?
- It is a premium question. Sign up and unlock it once for 10 credits; it then stays unlocked. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.
Related questions
Updated · Written by the SevyDevy team