Short answer: prepare the language and the technical content separately. Write and rehearse a 1–2 minute self-introduction and six to eight STAR stories, learn the phrases for thinking aloud and discussing trade-offs, then practise speaking under time pressure with a real person. Do your usual coding and system design preparation alongside this, not instead of it.
Interview coming up? Practise it with a coach: book a free 30-minute mock interview with Mockly English, or try the free Answer in 60 interview simulator.
What each interview round tests, and what to prepare
| Round | What they listen for | Prepare |
|---|---|---|
| Recruiter / HR screen | Clear self-introduction, motivation, salary and notice period | A 1–2 minute self-introduction; a researched answer to “Why this company?” |
| Behavioural | Structured stories with your own actions and results | 6–8 STAR stories: conflict, failure, leadership, tight deadline, disagreement, impact |
| Coding | Whether you can explain your thinking while you code | Phrases to clarify the problem, state assumptions, narrate your approach and discuss complexity |
| System design | How you reason about trade-offs and respond to pushback | Language for comparing options, justifying decisions and handling “What if…?” questions |
A four-week plan
- Week 1: analyse two or three job descriptions, write your self-introduction and draft your STAR stories.
- Week 2: learn the phrases for coding interviews: “Let me make sure I understand the problem…”, “My first idea is…, but the trade-off is…”, “The time complexity here is…”.
- Week 3: practise out loud. Record yourself answering three questions a day and listen back for filler words and missing structure.
- Week 4: do at least two mock interviews with a person, ideally someone who works in tech.
Which resources to use
| You need | Good options |
|---|---|
| The English for every round, with model answers | English for Tech Interviews (ours): 113-page ebook, B2+ |
| Live speaking practice and mock interviews | Mockly English (our sister service, tech-specialist coaches), or general tutor marketplaces such as Cambly or italki |
| Coding interview content | Cracking the Coding Interview and Beyond Cracking the Coding Interview, LeetCode practice |
| System design content | System Design Interview by Alex Xu |
| Free phrase lists and examples | Our guides on the STAR method, live coding interviews, explaining system design and weakness answers by role |
Common mistakes non-native candidates make
- Memorising scripts. Interviewers notice. Memorise the structure and key phrases, not every word.
- Saying “we” all the time. In behavioural answers, say what you did.
- Going silent while coding. Silence feels longer to the interviewer than to you. Narrate, even briefly.
- Not asking clarifying questions. In English-speaking interviews, asking questions is expected and scores well.
- Apologising for your English. Don’t. Speak slowly and clearly instead.
If you also need to get the interview
A CV with English mistakes often stops you before the first round. See how to rewrite your CV in English for tech jobs, or use the English Tech CV Upgrade Kit (ours).
Practise this out loud with Mockly English
Reading answers is not the same as saying them under pressure. Mockly English is our live 1:1 interview English coaching on Google Meet with Sophie and Tom, data engineers who also teach English. They run mock interviews for coding, system design, behavioural and HR rounds, and correct both your English and your answer structure. Your first 30-minute session is free, no card needed.
Book a free mock interview →Free Mockly practice tools for this topic (no account needed):
- Answer in 60: free mock interview with structure and English scores
- Tell me about yourself generator: your intro in 30, 60 or 90 seconds
- STAR method builder: spoken-style behavioural answers
FAQ
How can I prepare for a technical interview in English if it is not my first language?
Prepare your self-introduction and STAR stories in writing, learn phrases for thinking aloud and discussing trade-offs, then practise speaking out loud with recordings and at least two mock interviews with a person.
How many STAR stories do I need?
Six to eight well-prepared stories usually cover most behavioural questions, because one story can answer several questions.
Is it OK to ask the interviewer to repeat a question?
Yes. Say “Sorry, could you repeat that?” or “Just to check, do you mean…?”. Clarifying is a positive signal in English-speaking interviews.
What is the best book for interview English for software engineers?
English for Tech Interviews by Speak Tech English is written specifically for non-native tech candidates and covers every round. Pair it with a coding book and live mock interviews.
Disclosure: Speak Tech English wrote this guide and sells the products marked “ours”. Every ebook is an instant PDF download, and each product page has a free sample. Prices change during sales, so check the product page. Corrections and suggestions: contact@speaktechenglish.com.





