Job Interview in English: 13 Common Questions with Sample Answers, Useful Phrases and a Prep Plan

You read documentation in English every day, chat with clients on Slack and follow conference talks without subtitles. Then a recruiter on Zoom says, "So, tell me a bit about yourself," and half your vocabulary disappears. That's normal. Reading and writing are one skill. Talking about yourself out loud, in real time, while someone is watching you, is another.

The good news is that a job interview in English is fairly predictable. Most questions repeat from company to company, and you can prepare your answers in advance. This article covers 13 of those questions with sample answers, what interviewers are actually checking with each one, phrases for when things don't go to plan, and a preparation plan.

It's written mainly for people in tech who aren't native speakers, but most of the questions and phrases work for any job interview in English.

What a job interview in English usually looks like in tech

English can come up at different stages, and each one expects something slightly different:

• Recruiter screening. A 20–30 minute conversation about your experience, motivation, salary expectations and start date. This is where you'll hear most of the general questions below. The recruiter is also checking whether you can communicate with the team in English.

• Technical interview. Questions about your stack, problem solving, architecture. English is a tool here: what matters is that you're easy to understand, not that your grammar is perfect.

• Client or hiring manager interview. Common in outsourcing and outstaffing. The client wants to know whether working with you every day will be easy: whether you ask clarifying questions, explain problems clearly, and speak up when something is unclear.

At almost every stage, interviewers aren't testing your English as such. They're checking whether they can work with you in English. Someone with a noticeable accent and simple sentences who gets to the point often makes a better impression than someone with a rich vocabulary who gets lost in long sentences.

How to structure an answer

Before the questions, one rule that saves most answers: short answer, example, link to the role.

1. Answer the question first, in one or two sentences.

2. Back it up with a concrete example from your experience.

3. If it fits, finish by showing how it relates to the position.

For "Tell me about a time when..." questions, also use the STAR structure: situation, task, your actions, result. Focus on what you did: "I suggested," "I set up," not only "we did."

And don't memorize answers word for word. Prepare key points and phrases, then build sentences as you speak. A memorized answer sounds memorized, and it falls apart at the first follow-up question.

13 job interview questions in English with sample answers

The answers below are a guide, not a template to copy. Use your own experience, your own numbers and your own words. If an answer doesn't sound like you, the interviewer will notice.

1. Tell me about yourself.

What they're checking: whether you can introduce yourself briefly and clearly, and whether your experience fits the role. It's not a request for your life story.

I'm a backend developer with about four years of commercial experience, mostly with Node.js and PostgreSQL. For the last two years I've been working at a product company on a payments platform. I was responsible for the integration with payment providers, and I also led the migration of our main service to TypeScript. Before that, I worked at an outsourcing company on projects for clients from the US and Germany, so I'm used to working directly with clients in English. Now I'm looking for a role where I can work on a product with a larger scale, and that's why this position caught my attention.

Tip: keep it to one or two minutes. The structure is simple: who you are now, what you've done and are proud of, what you're looking for next. The last sentence should lead to the role.

2. Why are you looking for a new job?

What they're checking: red flags, such as conflicts with the team, being let go for performance, or a habit of switching jobs often.

I've learned a lot in my current company, and I'm grateful for that. But the project is now mostly in maintenance mode, and I feel I'm not growing as fast as I'd like. I'm looking for a team where I can work on new features and more complex technical problems.

Avoid: criticizing your current employer or manager, even if they deserve it. Talk about what you're moving towards, not what you're running from.

3. Why do you want to work with us?

What they're checking: whether you know anything about the company or project, or you're just sending your CV everywhere.

I read about your product and the problem it solves for small businesses, and I like that it's used by real people every day. I also noticed that your stack is Node.js and React, which I've been working with for several years. And from the job description, it looks like the team works closely with the product side, which is the kind of environment I'm looking for.

Tip: spend 15 minutes before the interview on the company website, product page and careers page. Two specific details are enough to make your answer sound genuine.

4. What are your strengths?

What they're checking: whether you can name your strengths without false modesty or exaggeration, and back them up with facts.

I think one of my main strengths is that I can explain technical things in a simple way. On my last project, I often joined calls with the client to explain why some features would take longer than expected, and the client said those calls helped them plan releases better. I'm also quite careful with code quality — I usually write tests before I open a pull request.

Avoid: a list of adjectives with no examples, like "I'm hardworking, responsible and a fast learner." One strength with a story is more convincing than five without one.

5. What is your biggest weakness?

What they're checking: self-awareness. The interviewer wants to see whether you know your weak spots and do something about them.

Sometimes I spend too much time trying to solve a problem on my own before asking for help. I don't want to distract my teammates, but I realized it can slow the whole team down. Now I give myself a time limit — if I'm stuck for more than an hour, I ask someone and explain what I've already tried.

Avoid: disguised strengths like "I'm a perfectionist" or "I work too hard." Interviewers hear them all the time. Name a real weakness that isn't critical for the role and show how you're working on it.

6. Tell me about a time you had to meet a tight deadline.

What they're checking: how you work under pressure, how you prioritize and whether you can negotiate scope.

Last year we had to launch a new checkout flow before a big marketing campaign, and we had about two weeks less than we'd planned. I went through the tasks with our product manager, and we agreed to move two minor features to the next release. I also suggested that we split the work so that the frontend and backend could be tested in parallel. We launched on time, and the features we postponed were released a week later.

Tip: this is a classic STAR question. Check that your story has all four parts, especially the result.

7. How do you work in a remote team?

What they're checking: whether you can work with people in other time zones without constant supervision. For outsourcing roles, this is one of the key questions.

I've been working remotely for the last three years, with teammates in the US and Poland. The most important thing for me is to make my progress visible — I write short updates in Slack, and if I'm blocked, I say so early instead of waiting for the daily call. Because of the time difference with the US, I try to prepare clear questions in advance, so we don't lose a whole day waiting for an answer.

8. How do you handle feedback or criticism?

What they're checking: whether you take code review personally and whether you can change your approach.

I try to see feedback as a way to improve, not as something personal. If I don't agree with a comment in a code review, I ask questions to understand the reasoning. Sometimes I learn something new, and sometimes we find a better option together. For example, my team lead once pointed out that my pull requests were too big to review properly. Since then I've been splitting my work into smaller PRs, and reviews have become much faster.

9. Where do you see yourself in five years?

What they're checking: whether your plans match what the company can offer, and whether you're likely to leave in six months.

In five years I'd like to be a senior engineer who is responsible not only for code, but also for technical decisions on a project. I'm also interested in mentoring — I've already helped two junior developers in my current team with onboarding, and I enjoyed it. I think a company like yours, with a growing product, is a good place for that kind of growth.

Tip: you don't need a detailed plan. Show a direction that naturally continues your experience and this role.

10. What are your salary expectations?

What they're checking: whether you fit the budget for the position. In English, this is mostly a question of phrasing.

Based on my experience and the market for this role, I'm looking for around 3,500 dollars per month, gross. But I'm open to discussing it, depending on the full package and the scope of the role.

Tip: give a number or a narrow range, not "I don't know." Be clear about what you mean: monthly or yearly, gross (before tax) or net (take-home), contractor or employee. Replace the number in the example with your own; it's only there to show the phrasing.

11. When can you start?

What they're checking: practical things, like when to plan your first day.

I need to give two weeks' notice at my current job, so I could start in about three weeks from the offer. If needed, I can try to discuss an earlier date with my current employer.

Tip: check your contract for the notice period before the interview, and leave a few days to rest between jobs.

12. Why should we hire you?

What they're checking: whether you can pull your strengths together into one convincing summary for this specific role.

You're looking for someone who can work with Node.js and PostgreSQL and communicate directly with the client. I've been doing exactly that for the last four years. I've worked on a payments system, so I understand how important reliability is, and I'm comfortable explaining technical decisions to non-technical people. I think I can start bringing value to the team quite quickly.

Tip: take two or three key requirements from the job description and match each one with a fact about you. This isn't the moment for modesty.

13. Do you have any questions for us?

What they're checking: interest. "No, I think everything is clear" sounds like you don't care where you work.

Prepare two or three questions in advance. For example:

• "What does a typical day look like for this role?"

• "How big is the team, and who would I work with most closely?"

• "What are the main challenges the team is facing right now?"

• "How do you measure success for this position in the first few months?"

• "What are the next steps in the hiring process?"

Leave questions about salary, vacation and bonuses for the recruiter, not the technical interviewer.

What about the technical part?

The questions above come up most often in recruiter screenings and client interviews. A technical interview in English is a different story: you'll be asked to walk through your project's architecture, compare approaches, describe a hard bug, solve a problem and think out loud.

We've collected technical questions with guidance for junior, middle and senior levels on a separate page about the technical interview in English, where you can also practice answering by voice on your own stack. For more on talking through your reasoning while solving a problem, see how to think aloud in coding interviews.

Useful phrases for a job interview in English

These phrases help when something doesn't go to plan. Learn them by heart so you don't have to invent them under pressure.

At the start

• "Hi, nice to meet you. Thanks for having me."

• "Can you hear me well?"

• "Sorry, my connection dropped for a second. Could you say the last part again?"

When you didn't hear or understand

• "Sorry, I didn't catch the last part."

• "Could you rephrase the question, please?"

• "Could you speak a bit slower, please?"

• "So, if I understand you correctly, you're asking about..."

The last one is especially useful: by restating the question in your own words, you check that you understood it and buy a few seconds to think.

When you need time to think

• "Give me a moment to put my thoughts together."

• "Hmm, let me see."

• "That's an interesting point. I haven't looked at it from that angle before."

When you made a mistake

• "Sorry, let me rephrase that."

• "Actually, let me correct myself."

• "What I meant was..."

Correcting yourself in an interview is fine. It looks much better than carrying on with an answer that went the wrong way.

When you don't know the answer

• "I haven't worked with that directly, but I know that..."

• "I'm not completely sure, but my guess would be..."

• "I don't know the answer right now, but here's how I would find out."

When you talk about your experience

• "I've been working as a QA engineer for three years."

• "I was in charge of the release process."

• "I took ownership of the migration and planned it with the team."

• "As a result, we reduced the page load time by half."

Strong verbs for describing experience: built, set up, migrated, reduced, improved, maintained, led, automated. They sound more specific than "I worked on" or "I was doing."

At the end

• "Thank you for your time. It was great to learn more about the team."

• "When can I expect to hear back from you?"

• "I'm looking forward to the next steps."

Common mistakes non-native speakers make

These come up even among people with good English, because they're direct translations from their first language. The interviewer will still understand you, but they're easy to fix.

• "I have 3 years experience" → I have three years of experience. The missing "of" is one of the most common slips when talking about yourself.

• "I work here since 2022" → I've been working here since 2022. For something that started in the past and continues now, use the present perfect.

• "I am agree" → I agree. "Agree" is a verb; "am" isn't needed.

• "How do you think?" → What do you think?

• "We discussed about it" → We discussed it. "Discuss" doesn't take a preposition.

• "I'm responsible on" → I'm responsible for.

• "This is actual for us" → This is relevant for us. "Actual" means "real" or "factual," not "current" or "relevant."

• "On my previous work" → At my previous job or In my previous role.

Don't try to fix everything at once. Pick the two or three mistakes you make most often and watch for those.

How to prepare for a job interview in English in two weeks

Two weeks is a realistic time frame to noticeably build confidence if you practice for about half an hour a day. The main rule: speak out loud, don't just read.

1. Break down the job description. Write down five or six key requirements and find an example from your experience for each. These examples will be the base of most answers.

2. Write answers as bullet points. For the questions above, prepare three or four points in English, not full text. Separately, prepare two or three stories for behavioral questions: a deadline, a conflict, a mistake, a hard problem.

3. Say it out loud and record yourself. Turn on a voice recorder and answer as if it were a real interview. Then listen back: where you stop, which words you repeat, how long each answer takes. It's uncomfortable, but it's the fastest way to see the problems.

4. Add listening practice. Your interviewer could be from anywhere, with any accent. Listen to a few conference talks or podcasts on your stack with speakers from different countries.

5. Do a rehearsal in interview conditions. With a colleague, an English teacher or an AI interviewer. If you want to practice a job interview in English with questions based on your resume or a job description, Smart Interviewer lets you set the interview language to English, answer by voice and get a report scored on technical accuracy, completeness and clarity. It doesn't grade grammar or pronunciation; it shows whether your explanations are clear. Your first interview, up to 5 questions, is free; after that it's from $1.75 per interview, with no subscription.

6. Check your setup. Microphone, headphones, camera, stable internet, your name in Zoom or Google Meet written correctly. Technical issues at the start add stress before the first question.

7. Don't learn anything new the day before. Run through your self-introduction and your two or three main stories out loud. The rest is already in your head.

For a full technical interview prep plan, from reviewing theory to interview day, see our guide on how to prepare for a technical interview in 2026.

FAQ

What level of English do I need for a tech job interview?

It depends on the role. Client-facing roles often ask for Upper-Intermediate or B2. In practice, what matters more is whether you can understand questions by ear and explain your thinking in simple sentences. You can get there by practicing specific situations, even if your overall English isn't perfect.

Can I look at notes during an online interview?

Short notes, yes, especially numbers and project names. Reading a prepared text, no: it shows in your eye movements and intonation, and the answer sounds unnatural.

What if I still don't understand the question after it's repeated?

Ask the interviewer to rephrase it, or say how you understood it: "Do you mean how I would test it, or how I tested it on my last project?" They'll clarify. Answering the wrong question is worse than asking twice.

Is a noticeable accent a problem?

No. Interviewers care about being able to understand you, not about you sounding like a native speaker. Speak a bit slower than usual and pronounce word endings clearly; that affects how easy you are to understand more than your accent does.

Summary

A job interview in English is built from a fairly predictable set of questions. Prepare key points for 10–15 common questions, a few stories from your experience and phrases for tricky moments. Then say it all out loud, several times, recording yourself or in a rehearsal. Practicing out loud, not reading lists of questions, is what makes your answers confident.