Product manager interview English (non-native speakers)

Use a spoken template per round: pitch, STAR, estimation, design, improve-a-product, and metrics. State the user problem first, trade-offs second, and a metric last. Do not translate a written case mid-answer.

Tell me about yourself, then behavioural ownership, then estimation and product design. Most UK/US PM loops cycle those formats. One rehearsed structure per type beats memorising book answers.

Only if you cannot state a user, a problem, and a metric. Panels do not need native idioms. They need to hear a recommendation. Practise “I would ship X first because Y, and measure Z” until it is automatic.

Clarify the ask, state assumptions, walk the maths, then sanity-check. “I will assume 50 million users and 10% weekly use.” Say the numbers slowly so the interviewer can follow. Wrong precision with clear speech beats silent calculator energy.

PM cases stay with the customer and the product. You define success, weigh shipping trade-offs, and say how you would measure the outcome. You rarely get neat consulting tables. Recommend an MVP or experiment, not only a spreadsheet.

Do not jump to features. Clarify who the user is, the job to be done, and one success metric. Then list three options and pick one. Short sentences. Features without a user sound like a translated spec.

Use books for frameworks, then convert them into spoken scripts. Memorise structures and one story per signal, not every sample answer. Out-loud rehearsal beats silent reading for English loops.

Pick four you can say cleanly: retention, conversion, latency, and revenue or engagement. Define each in one clause if needed. “Retention — the share who come back in week four.” Wrong jargon used confidently is worse than a simple definition.