Job Interview in English as a Non-Native Speaker: CV, Notes and Calls

A job interview in English can feel like two tests at once when English is your second language: the job itself, and the language. It helps to separate them. A tech interview checks whether you can do the work and explain it clearly, and that's something you can prepare for in a structured way. This guide covers CV phrasing, short cover notes, screening calls, technical rounds and the phrases that buy you time when you need it.

What you're actually being assessed on

In most tech hiring, nobody is grading your grammar. The questions behind the interview are simpler: do you understand what's being asked, can you explain what you did and why, and would the team be able to work with you day to day? An accent is not the problem. Being hard to follow is, and that's mostly fixed by structure and preparation, not by perfect English.

Your CV in English

Most CV problems for non-native speakers come from translating phrases word for word. A few patterns to fix:

Start bullets with a verb that says what you did. Not "Participated in the development of a payment service" but "Built the refund flow for a payment service". "Took part in" hides your contribution.
Replace "responsible for" with the result. "Responsible for CI/CD" becomes "Moved the team's builds to GitHub Actions and cut manual release steps."
Drop "successfully" and "have experience in". They add nothing. Say what you did, and list the stack.
Use past tense for past jobs, present for the current one, and keep it consistent.
Keep sentences short. One idea per bullet. Short sentences are easier to get right and easier to skim.
Use the job titles the market uses. If your title was unusual, describe it in terms of the role you applied for: Backend Engineer, Product Analyst, QA Engineer.
Only include numbers that are real. If you don't know the exact figure, describe the change instead of guessing.
State your English level honestly, in plain words ("professional working proficiency") or with a certificate level if you have one.

Read your CV aloud before sending it. Clumsy phrasing is much easier to hear than to see. For matching your CV to a specific role, see how to tailor your CV to a job posting.

Cover notes: short is safer

A short note in simple English reads better than a long one full of formal phrases. Three or four sentences are enough:

The role you're applying for and one specific reason you're interested.
One relevant thing you've done, with a concrete detail.
Anything practical they need: where you're based, your notice period.

Avoid openings like "I am writing to express my interest". Just say what you want to say. We have ready-made examples in short cover note templates.

Screening calls

The first call with a recruiter is the most predictable part of the process. You can prepare most of it in advance:

A 60-second introduction: who you are, what you work on, what you're looking for. Practise it aloud until it sounds natural, not memorised.
"Why this company?" One or two honest reasons, specific to them.
"Why are you looking?" A calm, short answer, without criticising your current employer.
Practical questions: notice period, location and work authorisation, time zone, salary expectations. Our guide to salary expectations in applications helps with the last one.

Write down key phrases, not full scripts. Reading from a script sounds stiff, and you'll lose your place when the question comes in a different form.

Phrases that buy you time

Everyone asks for clarification sometimes, native speakers included. Having a few phrases ready stops a moment of confusion from turning into panic:

"Could you rephrase that, please?"
"Just to make sure I understand: you're asking about how we handled the migration?"
"Let me think about that for a moment."
"Sorry, the connection cut out. Could you repeat the last part?"
"I'm not sure of the exact term in English, but what I mean is..."

Checking your understanding is a good habit, not a weakness. Answering the wrong question confidently is worse than asking once.

Technical rounds

Many developers know the technical vocabulary in English already, because documentation, code and error messages are in English. The hard part is using it in full sentences while thinking.

Practise thinking aloud. Solve a small problem while describing each step in English. Record yourself and listen back.
Prepare one project story in depth: the problem, your decision, what went wrong, what you'd change. You'll use it in several rounds.
Learn the connecting phrases: "the trade-off here is", "one option would be", "the bottleneck is likely", "I'd start by".
For take-home tasks, write a clear README in simple English. Short sentences and bullet points are fine.

Small things that help

Use a headset and test the call software beforehand. Bad audio makes any language harder.
If the platform offers live captions, it's fine to turn them on.
Don't open with "sorry for my English". It sets a tone you don't need.
After the call, send a two-line thank-you in simple English, mentioning one thing you discussed.

If you're getting few replies, the problem may be earlier in the process than the interview; see no replies to job applications. And if you're looking in Berlin, where many candidates don't speak English natively either, see tech jobs in Germany without German.

Hot Jobs won't write your CV or prepare you for interviews. What it can do is send new postings from 390+ company career pages and two remote boards to Telegram, usually within about half an hour of going live, so you have time to prepare a careful application instead of a rushed one. €3, paid once. Connect the bot