How a UAE-Based Backend Engineer Prepped for Meta in English

The Problem

He was a backend engineer targeting Big Tech from the UAE. Coding practice was already a habit: system design, algorithms, and coding problems. Live behavioral rounds were not. He paused searching for the right verb, over-explained, and lost the result of the story. Interviewers at Meta and Amazon were not asking him to prove he could sort an array. They were asking him to sound like someone they could work with - in English - for forty-five minutes.

Starting Point

He had already sat technical screens at Huawei and Adobe, with an Amazon onsite and a Meta interview loop on the calendar. Primary goal: interview English, especially behavioral rounds. Secondary: general business English for the rest of the week. Sessions split: one hour on CV and interview answers, one hour on discussion so the language was not only mock-shaped.

Before and After

What We Practised

Hours stayed close to the interviews on his calendar. Behavioral first, then technical narration, then a lighter discussion hour so fluency was not only interview-shaped.

• He practised work stories for Meta- and Amazon-style behavioral prompts, using situation, task, action, and result.
• He used a spoken system-design order: scope, approach, then trade-offs.
• He did homework after each mock so phrases were still available in the next interview.
• He alternated one interview-focused hour and one business-English hour.

Useful references along the way: STAR interview framework, What to expect in English interviews.

The Turning Point

The shift showed up on a Meta-style behavioral mock: a conflict story. Before, he narrated every meeting and never landed the decision. We cut the story to situation, one action, one result. In the next run he finished inside the time limit and the interviewer still had room for a follow-up. That was the version he took into the real interviews.

The Result

He completed the Meta and Amazon interviews in English instead of stalling on behavioral answers. He later joined Revolut. The interview problem was no longer searching for the next sentence while the interviewer waited.

What He Would Do Differently

• Treat behavioral English as a separate skill from coding practice.
• Book mock interviews before the onsite is on the calendar.
• Write three clear work stories and say them out loud weekly.
• Keep one hour for interviews and one for general fluency - do not mix them.

Why This Matters for Engineers Interviewing at Meta from the UAE

Big Tech loops in English are not only coding screens. Behavioral rounds reward a result you can say cleanly. Engineers who live in a second-language workplace still freeze when the story has to land in 90 seconds. That is the gap this coaching closed.

Preparing for a similar path? Read How a Switzerland-Based ML Engineer Passed Meta's Interview in English.