multilingual

A product design question where the obvious feature, answering homework questions, works against the user's real goal. Strong answers design for learning, for the exam, and for the phone the student actually has.

Small sellers have little time, uneven digital skills and thin margins. The strong answer finds the two jobs where AI changes their week, and avoids an assistant that sounds helpful and does nothing.

The user is driving. Every design choice follows from that, and candidates who sketch a chat screen fail the question in the first minute.

A principal-level design and strategy question. Every default assumption (literacy, a good phone, fast data, English, a credit card) fails. The answer has to pick a job worth solving and an economic model that survives.

Translation is the smallest part of multilingual AI UX. The interviewer wants script choice, code-mixing, voice, cultural norms, and honest handling of languages where quality is weaker.

Faster speech can make a conversation take longer. Diagnose premature turns, design recovery after interruption and protect actions when a caller changes their mind.

A question about fairness and unit economics hiding in a tokenizer. The interviewer wants the mechanism, the arithmetic, and options that do not leave non-English users with a worse product.

Voice adds two models and a much tighter latency budget to a text assistant. The interviewer wants the pipeline, the turn-taking problem, and the failure modes that text products never face.

Translation through English helped low-resource Indian languages and hurt Hindi in one benchmark. Route by language, protect what must not be translated and measure on your own customers' messages.

A large-scale design question where every error is someone's real harm: harmful content left up, or legitimate speech taken down. Strong answers tier by severity and confidence, keep humans in the hard cases, and measure both kinds of error per language.

Translation looks solved until a price, a date or a promise is mistranslated between two strangers doing business. The design centres on speed, protecting critical details, and letting both sides see the original.

A principal-level design question with money, regulation, fraud and a dozen languages in one queue. The answer that scores separates complaint types by what the agent may do, and keeps every money decision in deterministic systems.

A translated English eval set can miss code-switching, transliteration and local support needs. Decide what to sample in each language and who can judge the replies.

Benchmarks die from leakage, label errors and saturation. Hold back a private split, audit labels with experts, score abstention, watch the public-private gap and publish when you will retire it.

English-only evaluation hides regressions that land on most of the world's users. The interviewer wants a plan that covers languages by importance, uses native evaluation, and gates release on per-language results.

Prototypes tested in English hide most of what goes wrong for users in other languages. The interviewer wants a prototype cycle that tests real speech and text from target users, with native evaluation.

Progressive constraints test whether you can adapt under pressure without breaking what works. Principal-level candidates handle each constraint with the right mechanism, verify each change, and explain trade-offs.