Verbalta blog

English job interview: the 12 questions that always come up

The Verbalta team — Tue, 11 Aug 2026 12:00:00 GMT

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:

Read the script.
Swap the examples for your own.
Say it out loud three times. Not in your head, out loud.
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.

"Tell me about yourself": the 90-second script that works in any interview

The Verbalta team — Tue, 11 Aug 2026 12:00:00 GMT

The answer that works runs about 90 seconds and has three parts: where you are now (one sentence), the achievement most relevant to this role (two sentences, with a number), and why you want this job (one sentence). It isn't your life story, it doesn't start at university, and it doesn't repeat the CV they've already read.

This is the question that opens almost every English-language interview. It's also the one most people lose, because it looks easy.

Why this question decides the rest of the interview

Two things happen in the first 90 seconds.

The first is that the interviewer forms an impression. It isn't final, but everything after gets read through it. Start hesitantly and every pause afterwards sounds like uncertainty. Start solidly and a pause sounds like someone thinking.

The second is internal. If the first answer goes well, your body relaxes and the next ones come more easily. If it goes badly, you spend the next twenty minutes recovering instead of answering.

That's why it's worth rehearsing this answer.

The structure: present, evidence, direction

Forget chronological order. Nobody wants to hear about 2016.

Part 1: present. One sentence. Who you are professionally today.

Part 2: evidence. Two sentences. One thing you did, chosen because it's relevant to this role, ending in a result.

Part 3: direction. One sentence. Why you're in this conversation.

The script, with examples

Part 1: where you are now

Role, years, where. No preamble.

"I'm a backend engineer with seven years of experience, currently at a logistics company where I work on our order processing systems."

"I'm a performance marketer. I've spent the last five years running paid acquisition, most recently for a B2B SaaS company."

"I work in customer success. I'm currently leading a team of four at a health tech company, looking after our enterprise accounts."

Note what isn't there: where you studied, how many jobs you've had, what you were doing in 2019. None of it helps.

Part 2: the evidence

This is the part almost everyone gets wrong. The temptation is to list everything. Don't. Pick one thing, chosen because the role asks for exactly that, and end on a result.

"Over the last two years I've focused on making our API faster under load. We were timing out during peak hours and losing orders. I rewrote how we queue and batch requests, and we went from about four hundred failed orders a week to almost none."

"The project I'd point to is the paid channel restructure I ran last year. We were spending across six channels without knowing which ones worked. I cut it to two, rebuilt the tracking, and we brought cost per acquisition down by roughly forty percent on the same budget."

"The thing I'm most proud of is our renewal rate. When I took over the enterprise accounts we were renewing about seventy percent. We're at ninety-one now, mostly because we changed when we talk to customers rather than what we say."

If you don't have a number, use a concrete consequence: the team stopped doing something by hand, a customer stayed, someone got promoted, something that broke weekly stopped breaking.

Part 3: why this role

One sentence. Connect what you just described to what they need.

"I'm looking for a role where that kind of work is the main thing and not a side project, and from the job description that seems to be exactly what this is."

"What interests me here is that you're doing this at a scale I haven't worked at yet, and with a fully distributed team, which is how I want to work."

How it sounds together

"I'm a backend engineer with seven years of experience, currently at a logistics company where I work on our order processing systems. Over the last two years I've focused on making our API faster under load. We were timing out during peak hours and losing orders, so I rewrote how we queue and batch requests, and we went from about four hundred failed orders a week to almost none. I'm looking for a role where that kind of work is the main thing rather than a side project, and from the job description that seems to be exactly what this is."

Read it out loud and time it. It should land between 55 and 75 seconds at a comfortable pace. If you're past 100, cut part 2.

Five things that weaken the answer

Starting at university. "So, I graduated in 2015 and then..." You've spent ten seconds and said nothing useful.

Reciting the CV. They have it open. You're there to give the context that doesn't fit on it.

Apologising for your English. "Sorry, my English is not very good." You've just told the interviewer to listen for your mistakes instead of your content. If you stumble, simply keep going.

Speaking too fast. It's the natural reflex when you're nervous in another language, and it lands worse than a pause. A two-second pause sounds like thought. A rushed sentence sounds like panic.

Ending without ending. A lot of people close with "...yeah, so, that's basically it, I guess". Finish on part 3 and stop. The silence afterwards belongs to the interviewer, not to you.

If you stall halfway through

It happens to someone, at some point. What saves you isn't grammar, it's having a natural-sounding recovery line ready:

"Sorry, let me start that again."

"How do I put this..."

"Give me a second, I want to say this properly."

All three are things native speakers say constantly. None of them sounds like a language problem. They sound like someone choosing their words, which is exactly what you're doing.

Where rehearsing stops helping

An honest caveat, because nobody writes this part.

Rehearsing this answer works very well for this answer. The risk is the side effect: someone who delivers a polished 90 seconds and then falls apart on the first follow-up looks worse than someone who was merely decent throughout. The contrast gives you away.

So treat this as the opening move. Rehearse it until it comes out without effort, then spend the remaining time speaking unscripted English about your work, out loud. Explain what you do to a wall. Talk through your last project as if to a friend.

The goal isn't to have the answer ready. It's to walk into the interview having already spoken English out loud that week, so your mouth is warm by the time it counts.

How to practice speaking English for work without freezing

The Verbalta team — Fri, 31 Jul 2026 12:00:00 GMT

If you understand English but go quiet in meetings, you are not starting from zero. You're dealing with a specific, fixable gap: you can recognise the language, but you can't retrieve it fast enough while people are waiting.

Here's how to close that gap. You don't have to wait until your English feels "ready."

Why you freeze even when you know the words

Freezing usually isn't a vocabulary problem. It's three things happening at once:

Retrieval under pressure. Finding a word in a quiet moment is easy. Finding it in a second and a half while five people look at you is a different task.
Self-monitoring. You're speaking and grading yourself at the same time, and the grading uses the attention the speaking needs.
Stakes. At work, a clumsy sentence can feel like it says something about your competence. So you pick the safe sentence, or say nothing.

The fix for all three is the same: more repetitions, in conditions close to the real thing, somewhere the cost of a mistake is low.

Practice the situation, not the topic

"Business English" is too big to practice. A situation is small enough to rehearse.

Pick one you'll actually face this month:

introducing yourself and what you do to a new client
explaining why something is late, without over-apologising
disagreeing with a senior colleague politely
asking someone to repeat themselves without embarrassment
answering "Tell me about yourself" in an interview
giving a two-minute project update

Say your answer out loud. A voice note to yourself is enough to start. Then listen back once.

Notice where you slow down

When you listen back, you're not hunting for mistakes. You're looking for friction:

Where did you pause before a word?
Where did you translate from your first language?
Where did you choose a simpler sentence than the one you meant?
Which phrase did you use three times because it was the only one available?

Those moments are your real curriculum. They're far more useful than a generic grammar syllabus, because they're the sentences you personally need.

Keep corrections small enough to use

The most common mistake in speaking practice is trying to fix everything at once.

Given eight corrections, you'll remember none of them in your next conversation. Given one (use for with a length of time, since with a starting point), you can carry it into the very next sentence you say.

A loop that works:

Say the sentence out loud.
Take one correction.
Say it again with the change.

Step three is the one people skip, and it's the one that makes the better phrase available to you later.

Rehearse before it counts, not during

Many people only practice English in the meetings themselves: the worst possible place to experiment, because that's where a mistake actually costs something.

Move the experimenting somewhere cheap:

rehearse tomorrow's update tonight, out loud
practice the interview answer on your commute
run through the difficult sentence twice before the call starts

By the time you're in the room, you're not composing the sentence. You're repeating one you've already said.

Aim for clear, not perfect

Fluency is not the absence of mistakes. Plenty of highly effective speakers make small errors constantly. They simply keep going.

At work the goal is to be understood, to sound like yourself, and to stay in the conversation. Perfect grammar delivered after a long silence serves you worse than natural speech with a few small errors.

A realistic weekly routine

You don't need an hour a day. You need frequency.

Five minutes, most days. One real situation, said out loud.
One correction per session, applied immediately in a second attempt.
One harder rehearsal a week: the meeting or call you're actually nervous about.

Consistency matters more than volume here, because speaking is a habit of nerve as much as knowledge.

Where a coach helps

You can do much of this alone with voice notes. What's hard alone is hearing the pattern you can't hear yourself, and knowing which single correction matters most right now.

That's what Verbalta is built for: real conversations on WhatsApp, one correction at a time, with a coach that remembers what you're working on.

Pick the conversation you're dreading this week, and say the first sentence out loud.

What we're building at Verbalta

The Verbalta team — Wed, 29 Jul 2026 12:00:00 GMT

Most adults learning English don't have a vocabulary problem. They have a speaking problem. You can read the email, follow the meeting, and understand the joke, yet still go quiet when it's your turn to talk.

That gap between what you know and what you can say out loud is what Verbalta is here to close.

The problem with how speaking usually gets taught

Most language apps are built around recognition. You tap the right answer, match the pair, fill in the blank. It feels like progress because it's measurable, and it genuinely does help you build vocabulary.

But recognition is not retrieval. Choosing "have been" from four options is a different skill from producing "I've been living here for three years" while someone waits for your answer.

Speaking is a motor skill as much as a knowledge one. It improves the way most motor skills do: by doing it, getting one useful piece of feedback, and doing it again.

What Verbalta actually is

Verbalta is an AI speaking coach that lives in WhatsApp.

You send a voice note about something real: how your week went, the update you owe your manager, the interview answer you're dreading. Verbalta listens, replies in conversation, and gives you one clear correction while the sentence is still fresh in your mouth. Then it invites you to say it again.

There's no app to download. No timetable. No classroom.

One correction, one next step

This is the rule the whole product is built around.

When something comes out wrong, you don't get a list. You don't get a score, a percentage, or a wall of red. You get:

what worked in what you just said
one honest fix that makes your meaning clearer
an invitation to try the sentence again

A long list of errors is hard to act on and easy to feel bad about. One change is small enough to actually use in your next sentence, and using it is what makes it stick.

Practice for the moments that matter

The point isn't finishing lessons. It's feeling ready for:

a meeting where you want to disagree without sounding rude
an interview question you could answer easily in your own language
a client call where the details matter
the everyday conversations that make a new place start to feel like home

Verbalta pays attention to the patterns that make speaking harder for you specifically, and brings them back naturally in later conversations. Not as a quiz. As a conversation you happen to have again.

Why WhatsApp

Because the hardest part of any practice habit is remembering to start.

WhatsApp is already open. It's already where you talk to people. A voice note to a coach looks and feels like a voice note to a friend, so practice fits into the gaps in your day: the commute, the queue, the ten minutes between calls.

Five focused minutes, often, beats an hour you keep postponing.

Where we are now

We're early, and building in the open. If you've ever understood every word in a meeting and still said nothing, you're who we're building this for.

Start a conversation and say the first sentence out loud. That's the whole thing.