How a Senior Data Scientist Prepared for Google and Revolut Cases in English
He had already sat Google. Revolut’s product case was next - in English.
What this case shows
A senior data scientist from Russia, based in Singapore, had sat Google and was prepping Revolut product cases in English.
At a glance
| Role | Senior data scientist (cybersecurity background; targeting lead) |
|---|---|
| Region | From Russia; Singapore for 4 years |
| Starting Point | Hard to explain technical work and cases in English |
| Target | Big Tech; Google already interviewed; Revolut case next |
| Outcome | clear non-overlapping case structure + leadership vocabulary |
Timeline
Senior DS
Focus
Google loop (past)
Outcome
Revolut case ahead
“I can see the metric drop. I need the English to walk a VP through why - without drowning them in method.”
The Problem
He was a senior data scientist aiming at a manager or team-lead seat. He had already interviewed at Google and had a Revolut case on the path. Cybersecurity work was technically deep. In English, project explanations and product cases stalled: a metric drop, a new market, an A/B test - he could solve them and still not sound like a mini-CEO inside the business. Leadership vocabulary was part of the brief, not a separate course.
Before and After
Before coaching
- He struggled to explain technical concepts in English.
- His cases lost the business recommendation.
- The Google interview loop had already happened without enough case English.
- Lead-level vocabulary was missing.
After coaching
- Clear, non-overlapping case frames for metric and launch problems.
- Statistics used as support, not as the whole answer.
- Project stories with a result a hiring manager could repeat.
- Language for leading a slice of the product.
What We Practised
Hours looked like Revolut and Big Tech cases: a metric drop, a moderation system, a launch in a new country. English feedback landed on the same case - structure, stats, and the recommendation.
- He practised product cases such as a regional user drop, content moderation, and A/B tests.
- He split each case into clear, non-overlapping parts, then used enough statistics to defend the decision.
- He practised leadership vocabulary for a move from individual contributor to lead.
- He practised explaining data-science projects without drowning in method.
Useful references along the way: Pronouncing numbers and metrics, STAR interview framework.
Starting Point
Four years in Singapore, originally from Russia. Tennis and travel outside work. Interview formats he asked for: product cases first (users drop in a region; content moderation; Vietnam launch / A/B test), behavioral later. Revolut specifically: run a mini-startup inside the company, with statistics in the argument.
The interview process
| Already interviewed (notes do not record an offer) | |
| Revolut | Product case / mini-CEO format ahead |
| Coaching focus | Cases first; behavioral later |
The Result
He had already sat Google. Coaching was for the next cases - especially Revolut - and for sounding like someone who could own a problem in English, not only compute it. Notes do not claim a Google or Revolut offer.
What He Would Do Differently
- Practise product cases before the first Big Tech loop, not after.
- End every case with a recommendation in one sentence.
- Prepare lead-level language even if the résumé still says individual contributor.
- Use statistics as evidence, not as the whole story.
Why This Matters for Data Scientists Interviewing at Google or Revolut
DS loops at product companies are cases, not Kaggle recitals. Google and Revolut both reward a clear decision in English. Senior ICs who skip that practice sound more junior than their models.
Preparing for a similar path? Read How an Israeli Account Manager Prepped for Google in English.
Learning paths
Practise in the course
Start with your introFAQ
Questions
More questions? Email us at contact@mocklyenglish.com.
Practise your next behavioral interview in English
No card required. Start with a 7-day free trial - a lesson, a mock interview, or both.
Join 500+ preparing for global roles
Other engineers practising interview English
Mockly’s approach is genuinely personalized - they use a variety of methods tailored to your specific needs. With their help, I improved my spoken English and prepared thoroughly for behavioral interview questions across different companies. This not only helped me refine my stories grammatically but also ensured I was using the right examples to answer specific questions effectively.
Mockly was a huge help in preparing for my interviews. We worked on both technical and behavioral questions, and I received great advice on how to approach them and what to focus on. I feel significantly more confident as a result. They also helped me with my CV and cover letter - showing me how to structure them properly and highlight my strengths. I appreciate that they always ask how you’d like to structure your sessions and adjust to your goals. It keeps you on track and makes the whole process far more effective.
Similar case studies
How an Israeli Account Manager Prepped for Google in English
A Tel Aviv account manager preparing Google, Meta, and Waze interviews practised STARLF stories, Googleyness, and community language in English - no offer claimed.
How a São Paulo Engineering Manager Prepped After a Failed Google Design Round
A São Paulo engineering manager failed Google’s system design round. Coaching rebuilt vocab and full-loop English, including Airbnb.
More case studies
Related resources
Case studies are illustrative, based on patterns from real coaching sessions.