On this page

Case studies

By Mockly English · Last updated:

How a Croatian Security Engineer Prepped for Google's Behavioral Interviews

Interviewers are not grading your accent. They need to follow your reasoning in English. She was a security engineer in Croatia. The gap was behavioral / STAR — not the technical content.

At a glance

RoleSecurity Engineer
LocationCroatia
English challengebehavioral / STAR
Interview problemBehavioral
TargetGoogle
PreparationLive mocks with English feedback on the same answers
OutcomeBuilt stronger interview English after earlier unsuccessful rounds
7-Day Free Trial

Land your dream tech job. In English.

Practice technical, behavioral & system design interviews with interactive lessons and native-speaking coaches

Start freeNo card needed
MemberMemberMember

500+ tech pros preparing for global roles

Courses · Coaching · Mock Interviews

The Gap Between Knowing and Explaining

Interviewers are not grading your accent. They need to follow your reasoning in English. She was a security engineer in Croatia. Day-to-day work used AWS. The team often spoke Russian, so live English was not daily practice. The next interviews were at Google, in English. She had already been through an earlier interview round. In the room, behavioral / STAR was what broke down.

Before and After

Before coaching

  • Reached for words mid-answer and translated from a first language
  • Stories ran long and lost the result
  • Long pauses while searching for the next sentence

After coaching

  • Retrieved a small set of precise terms instead of long approximations
  • STAR stories with a clear action and a result said early
  • Finished answers without abandoning the structure

What We Practised

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

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

The Turning Point

The useful change followed an earlier interview round. She stopped treating English as extra polish. The next mocks used the same format that had failed. Answers got a fixed order so follow-ups did not knock her off track.

What Other Engineers Can Learn

  • Treat a failed round as data. Rebuild that exact format out loud.
  • 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.

After the Coaching

Built stronger interview English after earlier unsuccessful rounds. She could tell a clearer story after an earlier interview round. Readiness — not a promised offer — was the goal.

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 Serbian PM Prepped for Google in English.

Where She Started

She prepared for English-language interviews as a security engineer. The stack was AWS. Written English was stronger than speaking under the clock.

The interview process

Earlier roundUnsuccessful — an earlier interview round
TargetGoogle — behavioral / STAR

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 →

Frequently Asked Questions

What English should a security engineer 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.

How long does it take to feel ready as a security engineer?

Many B2+ candidates need several weeks of focused, spoken practice. Weekly mocks beat a last-minute cram.

How do I keep STAR stories short in English?

Lead with the result, then the action you took. Cut the long setup. Practise follow-ups on the same story so you do not invent a new timeline each time.

Can I pass a tech interview if my English isn't fluent?

Yes. Interviewers need to follow your reasoning. A clear structure and the right words matter more than sounding native. This case study is about that gap — not about erasing an accent.