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 interview stories - not the technical content.
What this case shows
A Serbian product manager was targeting Google. Behavioral stories in English were the gap. Here is what she practised.
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 |
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 behavioral rounds, her stories ran long or lost the result, and she paused to find words in English.
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 interview stories for Google. After each mock, she got notes on the same answer - where she paused, which words were vague, and where the structure broke.
- She built reusable work stories with a clear structure: situation, task, action, and result.
- She practised answering follow-up questions on the same story instead of switching to a new example.
- She replaced vague verbs with precise language (decided, shipped, measured).
- She practised saying the result early so the interviewer could follow the point.
- She repeated the same answer under time pressure as homework between sessions.
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
She 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 five to eight work stories from real projects. Practise follow-up questions on the same stories.
- Say the result in the first twenty seconds, then explain the action.
- Use first person for decisions: I decided, I measured, I pushed back.
- Keep answers short. A clear point beats a long timeline.
- Practise out loud. Notes on paper do not train speaking 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.
Learning paths
Practise in the course
Start with your introPractise 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 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.
FAQ
Questions
More questions? Email us at contact@mocklyenglish.com.
Similar case studies
How a Croatian Security Engineer Prepped for Google's Behavioral Interviews
A Croatian security engineer was targeting Google. Behavioral stories in English were the gap. Here is what she practised.
Preparing for a Google Behavioral Interview in English
A software engineer in Germany was preparing for a Google behavioral interview in English. Here is the practice that changed the delivery.
More case studies
Related resources
Case studies are illustrative, based on patterns from real coaching sessions.