An interview in your second language is two tests at once: can you do the job, and can you explain that you can do the job. Preparation is what stops the second test from hiding the answer to the first.
An interview in a second language is two tests running at the same time. One is whether you can do the job. The other is whether you can explain, under pressure, that you can do the job. Candidates lose offers not because they lack the skills but because the second test obscured the answer to the first.
Preparation is what separates them. Interviews are unusually predictable, which means most of the language can be prepared in advance.
Prepare stories, not answers
Memorised answers fail for two reasons: the question is never phrased exactly as you rehearsed, and recited text sounds recited. Prepare five stories from your working life instead:
- A problem you solved.
- A time you worked with a difficult person or team.
- A mistake you made and what changed afterwards.
- Something you led or drove yourself.
- Something you learned quickly under pressure.
Those five cover the large majority of behavioural questions. When a question arrives, you select a story rather than invent language from nothing — which is exactly the kind of retrieval that survives nerves.
Structure each story with STAR
Situation, Task, Action, Result. The structure matters more for a second-language speaker than a native one, because it removes the question "what do I say next?" while you are already busy with grammar.
S: "Last year our team was handling about 200 support tickets a week."
T: "I was asked to reduce the response time without adding staff."
A: "I looked at the most common requests, wrote templates for the top ten, and trained the team to use them."
R: "Response time dropped from two days to about four hours, and it stayed there."
Four sentences. Note the past simple throughout — interviews are mostly narration of finished events, so if one tense is worth polishing beforehand, it is that one (see tenses explained simply).
The standard questions, and what they are really asking
"Tell me about yourself."
Not your life story. A ninety-second professional summary: where you are now, relevant background, and why you are in this room.
"I'm a front-end developer with about four years' experience, mostly in e-commerce. For the last two years I've been at a small agency where I've led the rebuild of three client sites. I'm looking for a role with more ownership of the product, which is why this position interested me."
Present perfect does a lot of work here — "I've been", "I've led" — because it connects past experience to your present situation.
"What's your greatest weakness?"
They are testing self-awareness, not looking for a confession. Name a real but non-fatal weakness, then describe what you do about it. "I used to take on too much rather than delegate. I've started assigning clear owners at the start of a project, and it has made a difference."
Avoid the transparent non-answers ("I'm a perfectionist", "I work too hard"). Interviewers have heard them thousands of times.
"Why do you want to work here?"
This one punishes lack of research more than lack of English. One specific detail about the company plus one honest reason about yourself is enough.
"Where do you see yourself in five years?"
Show direction, not a rigid plan: "I'd like to be leading a small team, and still close to the technical work."
"Do you have any questions for us?"
Always yes. Two or three, prepared: what success looks like in the first six months, how the team is structured, what the biggest current challenge is. Saying "no, I think everything's clear" reads as indifference.
Language for the difficult moments
These phrases are worth rehearsing until they are automatic, because they are needed exactly when your English is under most strain.
Need a moment: "That's a good question — let me think for a second."
Did not understand: "Sorry, could you rephrase that?"
Check you understood: "Just to make sure I've understood — you're asking about…?"
Went wrong mid-sentence: "Sorry, let me start that again."
Do not know: "I haven't worked with that directly, but I've used something similar — and I'd expect to pick it up quickly."
That last one matters. Pretending to know a technology you have never touched usually collapses under one follow-up question. Admitting a gap and showing how you close gaps is a stronger answer.
Useful phrasing for describing experience
- "I was responsible for…" · "My main role was…"
- "I was involved in…" · "I worked closely with…"
- "I led / managed / coordinated…"
- "We managed to…" — useful for achievements with difficulty behind them.
- "That's when I realised…" — a natural way into the lesson part of a story.
Prefer concrete verbs and numbers over adjectives. "I reduced processing time by 30%" is stronger than "I am very efficient", and it is also easier to say correctly.
Online interviews: the extra layer
Most first-round interviews are now video calls, which add their own difficulties for a second-language speaker: compressed audio, slight delay, and no body language to help.
- Test audio beforehand; poor sound is read as poor English.
- Wait a beat before answering — delay causes accidental interruptions.
- If the connection breaks up, say so: "Sorry, you cut out for a moment — could you repeat that?"
- Keep notes just off camera. Not a script — your five story titles and three questions.
How to practise
Reading these answers silently will not prepare you. Say them out loud, to someone, with the pressure of a person waiting.
- Record yourself answering "tell me about yourself" in ninety seconds. Listen back once.
- Have an AI tutor ask you five behavioural questions in random order — the randomness is the point, since it prevents rehearsal.
- Do a full mock interview with a real person in a live Space. Ask them to interrupt and to follow up, because a real interviewer will.
For the fluency habits behind all of this, see twelve habits that actually work, and for written follow-ups after the interview, professional English emails.