The 15 Most Common English Interview Questions, With Answers

Here's some good news if English interviews make you nervous: the questions repeat. The wording changes a little, but the intent is often the same. Once you recognize the patterns, you don't have to translate every word in your head. You just think "this is a motivation question" and reach for the answer you've already prepared.

This guide collects 15 of the questions that come up most often, in four groups. For each one, you'll find what it really means and a short sample answer. Every example uses simple sentences. Swap in your own details.

Group 1: Questions about you

1. "Tell me about yourself."

What it means: tell me about the professional you, as it relates to this job.

I'm a web developer with three years of experience. I mostly build dashboards with React. Last year, I led a project for a logistics client. I'm applying because I want to work on a bigger product.

The full breakdown is in how to answer "Tell me about yourself".

2. "What are your strengths?"

What it means: what are you good at that helps in this job? Include proof.

I'm good at breaking big problems into small steps. For example, I split a large migration into weekly tasks. We finished it without downtime.

3. "What are your weaknesses?"

What it means: are you self-aware, and do you work on yourself?

I sometimes spend too long polishing small details. Now I set a time limit for each task. I ask for feedback earlier.

More on this in how to answer "What are your weaknesses?".

4. "How would your colleagues describe you?"

What it means: what are you like to work with?

They'd probably say I'm calm and reliable. I answer messages quickly. And I'm happy to help when someone is stuck.

Group 2: Questions about your experience

These work best with the STAR method (Situation, Task, Action, Result). See the STAR method for English interviews for sentence patterns.

5. "Tell me about a challenging project."

What it means: how do you handle difficulty?

We had two weeks to move an old system to a new server. I planned the steps and tested each one. We switched over on a weekend with no data loss.

6. "Tell me about a time you made a mistake."

What it means: do you take responsibility and learn?

I once sent a report with wrong numbers. I noticed it the next morning. I told my manager and sent a corrected version. Now I always check totals twice.

7. "Describe a conflict with a teammate."

What it means: how do you handle disagreement?

A teammate and I disagreed on a design choice. We each wrote down the pros and cons. Then we asked our lead to decide. We kept working well together after that.

8. "What's your biggest achievement?"

What it means: what work are you proudest of, and what was your part in it?

I built an internal tool for tracking orders. The team still uses it every day. It replaced a messy spreadsheet.

Group 3: Questions about motivation

9. "Why do you want to work here?"

What it means: do you know anything about us, and does your reason make sense?

I like that your product helps small businesses. I've worked with small business clients before. And I want to grow in a remote team.

10. "Why should we hire you?"

What it means: what makes you a good fit compared to other candidates?

You need someone who can build APIs and talk to clients. I've done both for three years. I can start contributing quickly.

See also how to answer "Why should we hire you?".

11. "Why are you leaving your current job?"

What it means: is there a problem? Stay positive and don't criticize your current employer.

I've learned a lot there. But I want to work on a bigger product. This role gives me that chance.

12. "Where do you see yourself in five years?"

What it means: do your plans line up with this role?

I want to be a senior engineer. I'd like to help design systems and guide newer developers.

Group 4: Practical and wrap-up questions

13. "What are your salary expectations?"

What it means: do your expectations fit our budget?

Based on my research, I'm looking for a range of X to Y. But I'm open to discussing the full package.

Replace X and Y with numbers from your own research for this role and country.

14. "When can you start?"

What it means: when are you available?

I need to give two weeks' notice. So I can start on the first of next month.

15. "Do you have any questions for us?"

What it means: are you genuinely interested? Never just say "No."

Yes. What does a normal week look like for this role?

How does the team give feedback on code?

Different ways to ask the same thing

Interviewers rarely read from a list. They rephrase. Here are some versions that mean the same thing:

Common form	Variations you might hear
Tell me about yourself.	Walk me through your background. / Can you give me a quick intro?
Why do you want to work here?	What attracted you to this role? / What made you apply?
Tell me about a challenge.	What's the hardest problem you've worked on?
What are your strengths?	What do you bring to the team? / What are you best at?
Where do you see yourself in 5 years?	What are your long-term goals?

If you don't catch a question, ask for it again. That's normal and polite:

Sorry, could you repeat the question?

Just to make sure I understand, are you asking about my last project?

Common mistakes with standard questions

1. Answers that are too generic. "I'm hardworking and a team player," with no example, doesn't convince anyone. Always add one short piece of proof.

2. One-word answers. "Yes" or "No," then silence. Add at least one sentence of explanation.

3. Answering a different question. Nerves make people catch one keyword and run with it. If you're unsure, confirm what's being asked first.

4. Making things up to look like a fit. If the job asks for experience you don't have, say so and mention what's close. For example: "I haven't used AWS at work yet. But I've deployed apps on Google Cloud, which is similar."

5. Over-rehearsed answers. Memorized answers freeze easily and sound robotic. Memorize the points, not the sentences.

Prep checklist

• I understand what each of the 15 questions above is really asking.
• I have a core answer of two to four sentences for each.
• Every answer contains real facts from my own experience.
• I have two or three questions ready for the interviewer.
• I've practiced hearing different phrasings of the same question.
• I know how to politely ask for a question to be repeated.

Summary

English interview questions fall into four groups: about you, your experience, your motivation, and wrap-up. Understand the intent behind each one, prepare a short and honest core answer, and practice recognizing the variations. That way, you don't have to translate word by word while the interview is happening.

During a Zoom or Meet interview, Repartee shows the core of each question with an Indonesian translation, then a short answer script built from your own profile. You can try it from the download page.