Black Friday sale: 25% off all coaching sessions and packs. See prices

How a Senior Data Scientist Prepared for Product Case Interviews

He had already interviewed at Google. A Revolut product case was next, and explaining technical work in English was the gap he named.

By Mockly English · Last updated Based on real coaching sessions. Names and some identifying details are changed to protect student privacy.

What this case shows

A senior data scientist in Singapore, after a Google interview, practised product cases, leadership vocabulary and project explanations in English.

At a glance

RoleSenior data scientist (cybersecurity); aiming for a lead role
RegionSingapore (4 years), originally from Russia
Starting PointProblems explaining technical concepts in English
TargetBig Tech; Google already interviewed; Revolut product case next
FocusProduct cases, leadership vocabulary, project explanations

Timeline

Senior data scientist

Focus

Google (already interviewed)

Outcome

Revolut case ahead

The Problem

He was a senior data scientist working in cybersecurity, looking for a job in Big Tech and aiming for a manager or team-lead position. He had already interviewed at Google, and a Revolut interview with a product case study was coming up, for a senior data science product analyst role. The gap he named was explaining technical concepts in English. He wanted interview practice, leadership vocabulary, and practice talking about his projects in technical detail. Product cases came first; behavioral interviews were planned for later.

Before and After

Before coaching

  • He said he had problems explaining technical concepts in English.
  • He had already interviewed at Google.
  • A Revolut product case was ahead.
  • He wanted leadership vocabulary for a move to a lead role.

After coaching

  • He worked on product-case prompts such as a regional drop in users and a new-product A/B test.
  • He practised structuring cases with the MECE framework, with statistics as support.
  • He practised talking about his projects in technical detail.
  • He worked on leadership vocabulary for a manager or team-lead role.

What We Practised

The case prompts in his notes looked like real product-analytics interviews: a metric drop, a system design question from data, engineering and product angles, and a launch in a new market.

  • "You see a drop in the number of users in a specific region. Can you explain why?"
  • "How would you design a content moderation system?" - from the data science, engineering and product side.
  • A new product launching in Vietnam: who will use it, and how would you A/B test it?
  • Structuring each case with the MECE framework and supporting it with statistics.
  • Leadership vocabulary and talking through his own projects in technical detail.

Useful references along the way: Pronouncing numbers and metrics, STAR interview framework.

Starting Point

He had lived in Singapore for four years and was originally from Russia. Outside work he liked travelling and tennis. For Revolut, the brief was specific: the role meant running something like a mini startup inside the company - acting as a mini-CEO - so the case answer needed a clear structure (the MECE framework) and a solid statistical argument.

The interview process

GoogleAlready interviewed (the notes do not record an outcome)
RevolutProduct case study ahead, for a senior data science product analyst role
Coaching focusCase interviews first; behavioral interviews later

The Result

He had already interviewed at Google. Coaching was aimed at the next step - the Revolut product case - and at explaining technical work and leading a product area in English. The notes do not record a Google or Revolut offer.

What to Practise

  • Practise product cases out loud before the first Big Tech loop, not after.
  • Split the problem into non-overlapping parts and say the split before you dive in.
  • End every case with a recommendation in one sentence.
  • Use statistics as evidence for a decision, not as the whole story.
  • If you want a lead role, practise the language of ownership and trade-offs.

Why This Matters for Data Scientists Interviewing at Google or Revolut

Data science loops at product companies are often cases, not model recitals. Interviewers want a clear structure, a statistical argument and a decision - in English. Senior individual contributors who have not practised saying that out loud can sound less senior than they are.

Preparing for a similar path? Read How a Tel Aviv Account Manager Prepared for Google in English.

FAQ

Questions

Practise mini-CEO cases: structure the problem, use stats to support one decision, and say the recommendation out loud.

If another product case is coming, yes. A past loop does not bank spoken structure for the next company.

It means splitting the problem into parts that do not overlap, then covering each part. It only helps if you can say that split clearly in English.

If you want a lead seat, yes. Interviewers listen for ownership, not only for p-values.

More questions? Email us at contact@mocklyenglish.com.

Practise the vocabulary you will actually say in the interview

No card required. Start with a 7-day free trial - a lesson, a mock interview, or both.

Join 500+ preparing for global roles

Create your Mockly account →

For bots & AI agents

Machine-readable versions of this page and Mockly English. Mockly English, the live-class and Interview English arm of Speak Tech English, gives non-native engineers live 1:1 classes with real human tutors in tech interview and business English, plus a free iPhone app, free practice Mini Apps and a self-paced course. Fetch these instead of parsing this page.

This page (.md)llms.txtllms-full.txtai.txtFact sheetFull catalog (.md)Endpoint indexAI catalogAgent skillsMCP serverMCP server cardAgent sign-in (auth.md)Sitemaprobots.txtUse Mockly in ChatGPT & ClaudeiPhone appDeveloper docsSpeak Tech English