English job interview: the 12 questions that always come up

If you have an interview in English coming up, start here. These are the 12 questions that appear in almost every interview with an international company: tell me about yourself, why this role, why are you leaving, your strengths, your biggest weakness, a project you're proud of, a mistake you made, a conflict with a colleague, how you prioritise, how you work remotely, your salary expectations, and what questions you have for them. There's a script for each below.

You probably already understand everything the interviewer is going to say. You read documentation in English, you watch shows without subtitles, you follow entire calls. The trouble starts when it's your turn to speak, with someone waiting on the other end and silence counting against you.

This isn't a grammar article. It's about having something ready to say in the first three seconds.

How to use these answers

First things first: don't memorise them. A memorised answer falls apart at the first follow-up question, and an experienced interviewer spots it in ten seconds.

Use them like this:

1. Read the script.
2. Swap the examples for your own.
3. Say it out loud three times. Not in your head, out loud.
4. Record yourself once on your phone and listen back.

Step 4 is the one almost nobody does and the one that changes the outcome most. You'll hear exactly where you stumbled, and it's always in fewer places than it felt like.

1. Tell me about yourself

The question that opens 90% of interviews, and the one most people answer badly. It isn't an invitation to your life story. It's an invitation to 90 seconds of professional context.

Three parts: where you are now, what you've done that matters for this role, why you're in this conversation.

"I'm a product designer with six years of experience, currently at a fintech where I lead design for our payments product. Over the last two years I've focused on onboarding flows, and the redesign I led cut our drop-off by about thirty percent. I'm looking for a role with a fully remote team and a bigger international user base, which is exactly what caught my attention about this position."

Three sentences. Present, evidence, direction.

2. Why do you want to work here?

Research one concrete thing about the company. One. The difference between a generic answer and a good one is specificity.

"Two things. First, I've been following your work on [specific product or feature] and it's solving a problem I've dealt with directly in my last role. Second, I want to work in a distributed team, and from what I've read about how you run engineering, that's something you've clearly invested in rather than just tolerated."

3. Why are you leaving your current job?

Never speak badly of your current employer. It isn't about loyalty, it's about what it signals: if you talk about them that way today, you'll talk about the next one that way tomorrow.

Turn it forward.

"I've learned a lot there and I'm still on good terms with the team. But the company is focused on the domestic market, and I want to work on products with an international user base. That's not something I can get where I am."

4. What are your strengths?

Pick one strength and prove it with an example. A list of adjectives convinces nobody.

"I'm good at making complicated things simple for people who aren't technical. In my last project I was the person translating between the engineering team and the client's operations team. Nobody asked me to do it, it just needed doing, and it ended up saving us a lot of rework."

5. What is your biggest weakness?

The classic trap. "I work too hard" fools no one and "I'm a perfectionist" has been worn out.

The answer that works has three parts: a real but not fatal weakness, what you're doing about it, and evidence of progress.

"I used to take on too much instead of asking for help, because I didn't want to look like I was struggling. It caught up with me on a project two years ago when I missed a deadline I could have saved by speaking up earlier. Now I flag things in my weekly one-on-one before they become a problem, and honestly it's made me faster, not slower."

6. Tell me about a project you're proud of

Use STAR: situation, task, action, result. It's formulaic, and it's formulaic because it works.

"We were losing users in the first week and nobody knew why. (Situation) I was asked to figure it out and propose a fix. (Task) I ran twelve user interviews, found that people didn't understand what to do after signing up, and redesigned the first session around a single action. (Action) Week-one retention went from forty-one to fifty-eight percent over the next quarter." (Result)

End on the number. If you don't have a number, end on the consequence: someone got promoted, the team stopped doing something by hand, the client renewed.

7. Tell me about a mistake you made

They aren't asking whether you make mistakes. Everyone does. They're asking what you do afterwards.

"I shipped a change without checking how it affected a smaller customer segment, and it broke a workflow for about two hundred users. I found out from support, not from my own monitoring, which was the actual problem. I rolled it back within the hour, wrote up what happened, and we added that segment to our release checklist. It hasn't happened again."

Own it. Fix it. Show the system that stops it recurring. Don't blame anyone.

8. Tell me about a conflict with a colleague

Describe the disagreement, not the person.

"A colleague and I disagreed about whether to rebuild a feature or patch it. I wanted to rebuild, he thought it was over-engineering. We were both partly right. We agreed to timebox a patch for two weeks and revisit, and the patch held up better than I expected. I was wrong about the scale of the problem, and I'd rather find that out in two weeks than after two months of rebuilding."

Admitting you were wrong inside a conflict answer is strong. Very few people do it.

9. How do you prioritise your work?

What they're really asking is: will someone need to organise your day for you?

"I start the week by writing down what actually has to move, not everything on my list. Usually two or three things. Anything urgent that comes in gets checked against those. If it's genuinely more important, I move something and tell whoever's affected. If it isn't, it waits."

10. How do you work with a remote team?

If the role is remote and international, this question matters more than it looks. They want to know whether you disappear.

"I over-communicate in writing. If I'm blocked, I say so the same day rather than waiting for standup. I keep two hours of overlap with the team, and outside that I work async and leave enough context that nobody has to wait for me to wake up to make a decision."

11. What are your salary expectations?

The hardest answer if you're moving between currencies, because the temptation is to convert your current salary and ask for a little more. Don't. You'll anchor far too low.

Research the range for the role in the company's market first. Then:

"Based on what I've seen for similar roles in this market, I'd expect somewhere between X and Y. But I'd rather understand the full picture first. Do you have a range budgeted for this position?"

Turning the question back is normal and expected. It isn't rude.

12. Do you have any questions for us?

Never answer "no, I think you covered everything". It reads as a lack of interest, even when it isn't.

Keep three ready:

"What does the first ninety days look like for whoever takes this role?"

>

"How does the team handle disagreement about priorities?"

>

"What's something about working here that surprised you when you joined?"

The third almost always gets an honest answer, and it's the one that teaches you the most about the place.

What if you don't understand the question?

It will happen. An unfamiliar accent, a bad connection, an expression you've never heard. The problem isn't not understanding. It's pretending you did and answering something else.

Have these ready, and say them naturally:

"Sorry, could you say that again?"

>

"I want to make sure I understood: are you asking about X, or about Y?"

>

"Could you rephrase that? I want to give you a proper answer."

The last one is good because it signals care rather than confusion. Asking someone to repeat themselves once in an interview does not count against you. Answering the wrong question does.

Where these answers stop working

It's worth being honest about the limit here.

A script solves the opening, not the conversation. The first two or three questions in an interview are predictable, and that's exactly why it's worth preparing: they set your emotional state for everything after. But after "tell me about yourself" comes the follow-up, and then another, and none of those are on this list.

What carries you through a whole interview isn't having the answers ready. It's having spoken English out loud often enough that the sentence arrives while you're still thinking about the next one. It's a motor skill, closer to driving than to studying.

So use this article for the first fifteen minutes. For the rest, speak out loud to someone before the day itself, even if that someone is you in the car.