On this page
By Mockly English · Last updated:
How a Serbian PM Prepped for Google in English
You know how to do the job. The difficult part is explaining it in English when an interviewer is watching. She was a product manager in Serbia. The gap was behavioral / STAR — not the technical content.
At a glance
| Role | Product Manager |
|---|---|
| Location | Serbia |
| English challenge | behavioral / STAR |
| Interview problem | Behavioral |
| Target | |
| Preparation | Live mocks with English feedback on the same answers |
| Outcome | Gained clearer, more confident English for interviews |
Land your dream tech job. In English.
Practice technical, behavioral & system design interviews with interactive lessons and native-speaking coaches
500+ tech pros preparing for global roles
The Interview Problem
You know how to do the job. The difficult part is explaining it in English when an interviewer is watching. She was a product manager in Serbia. The next interviews were at Google, in English. In the room, behavioral / STAR was what broke down.
Practice this STAR story
Try a locked preview of a behavioral / STAR drill — with English prompts for situation, action, and result.
Sign up to unlock this exercise →The Mock Interview
Practice matched the round she actually had to speak: behavioral / STAR for Google. Each mock got notes on the same answer — where she paused, which words were vague, and where the structure broke.
- Built reusable STAR stories from real work — situation, task, action, result
- Practised answering follow-up questions on the same story instead of switching prompts
- Replaced vague verbs with precise language (decided, shipped, measured)
- Practised giving the result earlier so the interviewer could follow the point
- Repeated the same answer under time pressure as homework
Useful references along the way: STAR interview framework, Pronouncing numbers and metrics.
The Mock That Changed the Answer
The shift came on a story she had already told. Follow-up questions used to break it. We kept the same story and practised the follow-ups until the result came early and the action stayed in first person.
Before and After
Proof of work — one mock session
| Problem | A follow-up on a STAR story the candidate already knew |
|---|---|
| Old approach | Restarted the timeline and lost the result |
| New framework | Result first, then the action in first person, then one metric |
| Result | The same story survived follow-ups without a new invented plot |
How answers sounded before
“So first the team had a problem, and then we discussed, and then maybe we changed the process…”
How answers sounded after
“The result was a 20% drop in incidents. I changed the on-call handoff. The action was mine; the metric is what the interviewer remembered.”
What Changed
Gained clearer, more confident English for interviews. She could explain the work more clearly when questions got hard. That readiness was the goal — not a promised job offer.
Lessons Learned
- Write 5–8 STAR stories from real work. Practise the follow-ups on the same stories.
- Say the result in the first 20 seconds, then the action.
- Use first person for decisions: I decided, I measured, I pushed back.
- Keep answers short. Clear beats a long timeline.
- Practise out loud. Notes on paper do not train retrieval under pressure.
Why Behavioral Interviews Are Difficult in English
A behavioral round asks you to remember an experience, pick the relevant details, structure a story, and still sound natural — all in a second language. You are choosing tenses, names, and numbers while the interviewer asks follow-ups. STAR is useful because it is a spoken order, not a script. Without that order, strong work disappears into a long, unfinished story.
Preparing for a similar path? Read How a Croatian Security Engineer Prepped for Google's Behavioral Interviews.
Practise your next behavioral interview in English
No card required. Start with a 7-day free trial — a lesson, a mock interview, or both.
Create your Mockly account →Other engineers practising interview English
Mockly knows what it takes to get hired. The preparation covers behavioral, algorithm, and system design interviews thoroughly — with real expertise in the STAR method, LeetCode, and Alex Xu’s system design frameworks. And when it comes to English and communication skills, the native-speaking mentors make all the difference.
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.
Frequently Asked Questions
What English should a product manager learn for interviews?
The language of the round you will face — here, behavioral / STAR. Learn full sentences for that format, not a general business-English course.
Should I practise technical interviews in English?
If the real loop is in English, yes. Silent LeetCode or notes in your first language do not train the round the interviewer will hear.
Do I need to sound like a native speaker?
No. Clarity and structure are the bar. A small accent is fine if they can follow your decisions and numbers.
How do you prepare for a product manager interview in English?
Practise the real format out loud, especially behavioral / STAR. Get notes on pauses and vague wording after each mock — not only on the technical content.
Similar case studies
How a Croatian Security Engineer Prepped for Google's Behavioral Interviews
A Croatian Security Engineer was targeting Google. The gap was STAR stories in English — not the technical work. Here's what they practised.
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.
More case studies
Related resources
Case studies are illustrative, based on patterns from real coaching sessions.