Job Interview English: Get the Question Right Before You Worry About the Answer

You practiced "Tell me about yourself" at home a dozen times, fluent down to every pause. In the interview, the recruiter looks at the screen for a second and says: "So, walk me through your background." You freeze, not quite sure what they just asked, then answer something else entirely. The carefully prepared answer is still sitting in your head, unusable.

Almost every article about English for job interviews teaches you how to answer: sample sentences for strengths, sample sentences for weaknesses, the STAR structure, a list of five hundred questions with answers attached. The hardest part of an English-language interview is somewhere else entirely — in the exact two seconds you have to understand what the other person just asked, when they're speaking fast, in their own personal way, and not using the exact wording from the textbook.

This article goes in the opposite direction from the rest of Google: treat the interview as a listening test first, and a speaking test second. You'll get different ways of asking the same classic question, follow-up questions that nobody prepares answers for, vocabulary for describing your experience and achievements, the small talk before getting down to business, the part about salary, and a real conversation with the spots Vietnamese speakers tend to miss. If you need vocabulary for daily work after you've landed the job, the office English article is a better fit.

• An English interview is a listening test first
• One question, many ways to ask it
• Vocabulary for each stage of the interview
• What a real interview sounds like
• How to practice so you don't miss a question
• Common mistakes in English interviews
• Frequently asked questions

An English interview is a listening test first

A memorized answer to the wrong question is worse than a modest but on-target answer. The interviewer doesn't know how much you studied — all they see is that they asked one thing and you answered another, and they draw one of two conclusions: the candidate isn't listening, or the candidate is dodging.

The problem is the interviewer isn't reading from a script. They rephrase questions in their own habitual way, and everyone's habit is different. For the same idea — "tell me about yourself" — some say "tell me about yourself," some say "walk me through your background," some just toss out something as short as "so, who am I talking to today?" You'd understand all three written on paper, but at real speaking speed, the last two sound nothing like the first one you memorized.

On top of that, an interview is the hardest listening situation an English learner faces. No subtitles, no rewinding, the speaker doesn't slow down for you at all, the accent could be British, American, Indian, or Singaporean, and you're nervous — meaning half the brainpower you'd normally spend on listening is already taken up by anxiety. The audio in test-prep books pronounces every word clearly, while a hiring manager says "whaddya think?" and "dju have any questions?" just like they would to any coworker. This swallowing-of-sounds mechanism is covered in more detail in the connected speech article.

One question, many ways to ask it

The table below groups the classic questions by intent, not by wording. The middle column has the other ways you'll actually hear the question asked; the last column is what the interviewer really wants to know behind the question. Read the middle column more carefully than the first — you already know the first one by heart.

The more dangerous part lies in the follow-up questions. No article prepares answers for these, because they latch onto exactly what you just said. A good interviewer uses one or two of these to check whether your story is real or just a nicely rehearsed line.

Pay special attention to "Can you say more about that?" and "How so?" Plenty of candidates hear these two and immediately assume they just answered wrong, then rush to change their whole argument. Usually it's the opposite: the interviewer found that part interesting and wants to hear more.

Vocabulary for each stage of the interview

An interview has four fairly fixed stages: a bit of small talk at the start, the part where you talk about yourself, the part where you ask questions back, and the part about salary and next steps. Each stage has its own layer of vocabulary, and the first stage is the one people prepare for least.

Small talk before getting down to business

The first thirty seconds set the rhythm for the whole session. Miss something here and you sit down already feeling like you've fallen a beat behind, and that feeling follows you through the rest of the interview.

Describing experience and achievements

This is the layer of vocabulary that decides whether you sound like someone who has actually worked or someone reading off a CV. Pay attention to the verbs: they signal how much you actually owned the work, not just showed up to the project.

Questions to ask the recruiter back

"Do you have any questions for us?" isn't a polite closing formality — it's still being scored. Answering "no, I think you covered everything" throws away your last chance to show you're genuinely weighing this opportunity.

Salary, benefits, and next steps

This part is short but consequential, and also the easiest to mishear because it's full of long nouns. Mixing up "notice period" with "probation period" is a real mistake, and it makes your answer completely wrong.

What a real interview sounds like

Below are the first ten exchanges of an ordinary interview. The italicized column in parentheses shows how that line actually sounds at natural speaking speed, when the function words get swallowed and stick together.

Interviewer: So, thanks for coming in. Did you find us okay? (how it really sounds: thanks fer cummin in. Dju fine us okay?)

Candidate: Yes, no problem at all. Thanks for having me.

Interviewer: Great. Before we dive in, do you want to walk me through your background? (how it really sounds: befor we dive in, dyawanna walkme through yer background?)

Candidate: Sure. I've been working as a data analyst for about three years, mostly in retail.

Interviewer: Got it. And what was your specific role in that migration project? (how it really sounds: gaddit. An whuwuz yer specific role in that migration project?)

Candidate: I took ownership of the reporting side after our team lead left.

Interviewer: Okay. Can you give me a specific example of something that went wrong there? (how it really sounds: kenya gimme a specific example of something that went wrong there?)

Candidate: We lost two weeks because the old data wasn't as clean as we assumed.

Interviewer: And what would you do differently? (how it really sounds: an whuwudja do diffrently?)

Candidate: I'd run a sample check before committing to a timeline.

Interviewer: Alright. Anything you'd like to ask me before we wrap up? (how it really sounds: enything yood like ta ask me before we rap up?)

Here's where Vietnamese speakers commonly miss things in exactly those ten exchanges above:

• "Did you" becomes "dju" or "didja." The whole opening chunk disappears — you only catch "find us okay," and sometimes end up answering about researching the company instead.
• "walk me through" sounds like "work me through." The /ɔː/ sound in walk and the /ɜːr/ sound in work are very close to a Vietnamese ear. Since "work me through" doesn't make sense, you freeze for two seconds.
• "Got it" becomes "gaddit." The /t/ sound between two vowels in an American accent turns into a soft /d/ sound, sounding like an unfamiliar word, and you sit waiting for the second half of a sentence that already ended.
• "what was your" sticks together into one block, "whuwuzyer." You only catch "specific role" — enough to guess the gist but not enough to know which project they're asking about.
• "Can you" becomes "kenya." Many learners write down the actual word Kenya, the name of a country, and drop the rest of the sentence entirely.
• "would you" becomes "wudja." Losing the word "would" means losing the conditional tense — the question "what would you do differently" gets understood as "what did you do," and you retell the same old story again.
• "wrap up" sounds like "rap up." The silent w makes a first-time listener think it's related to rap music, and you lose focus right when you're invited to ask questions.
• "you'd" in "anything you'd like" is nearly invisible. The sentence sounds like "anything like to ask me," which is grammatically wrong, so you doubt your own ears instead of answering.

How to practice so you don't miss a question

Reading through all the tables above once isn't enough, and you know it. Recognizing "walk me through" on paper is one thing; recognizing it in a seven-word sentence spoken in a second and a half is an entirely different thing. That gap between the two is exactly what wrecks an interview.

The way to close that gap isn't more reading — it's mishearing something and then getting corrected. A word you read in a table gives your brain no reason to hold onto it, because it never actually caused you trouble. A word you mishear, mistranscribe, and then look at the transcript and realize where you went wrong — that one sticks, because it came with a real stumble and an immediate explanation right on the spot.

Take the exact sentence "Can you give me a specific example?" as an example. At real speed, two things collapse at once: "can you" sticks together into "kenya," "give me" shrinks to "gimme." Someone who's only ever listened to clearly enunciated recordings will write down "Kenya me a specific example," find it meaningless, and give up. Mistranscribe it once and see the correct transcript, and next time that phrase pops out instantly, with no need to translate through Vietnamese.

That's the entire reason listening dictation works better than memorizing a list of questions. At WELE, every podcast is real speech at real speed — you listen and transcribe it, and wherever you get it wrong, it's pointed out right away. After a few dozen rounds of mistranscribing chunks like "could you," "would you," "what was your," your ear gets used to it, and in the interview room you no longer lose two seconds decoding the question. The 5 steps to effective listening dictation article describes the process for beginners, and the free listening level test tells you where you stand before you start.

To be fair, listening practice doesn't replace practicing your answers. WELE trains the ear, but the speaking part still requires you to practice out loud, record yourself and listen back, or have a friend play interviewer. The two complement each other: practice speaking while your ear isn't solid yet, and you end up with a great answer to a question nobody asked.

Common mistakes in English interviews

The mistakes below have almost nothing to do with grammar level — they come from reflexes under pressure.

• Answering the prepared question instead of the one just asked. Catching a few familiar-sounding words is enough to trigger the whole memorized passage. The interviewer notices right away, and the impression left is worse than a short but on-target answer.
• Not daring to ask for clarification. Many people fear that asking again will cost them points. In fact "Sorry, could you repeat that?" or "Just so I understand, are you asking about the process or the result?" are viewed positively, because that's exactly what a good colleague does in a meeting.
• Answering yes or no to an either/or question. If "Would you rather work alone or with a group?" only gets caught as "work alone," an answer of "yes" sounds very strange. When you hear "or" in the middle of a sentence, pause and pick one side.
• Reading a follow-up question as a sign you got it wrong. "Can you say more about that?" usually means they found that part worth hearing more of. Changing your whole argument at this point wrecks your own good answer.
• Using the present tense for a job you've already left. "I am responsible for the reporting" when you left that job three months ago makes the listener ask where you're currently working. Switch to "I was responsible for."
• Giving a fixed number when asked about salary expectations. Giving a range along with a reason is safer, for example "I'm looking at somewhere in the range of X to Y, depending on the full package."
• Confusing notice period with probation period. One is the notice you must give at your old job, the other is the trial period at the new one. Mishearing these two words means answering wrong about your possible start date.

Frequently asked questions

What should I do if I can't hear a question clearly in an English interview?

Ask for it again, and ask in a way that shows you caught part of it. "Sorry, could you repeat the last part?" is better than a plain "Sorry?", and "Just so I understand, are you asking about X or Y?" is the best option, because it both asks for a repeat and proves you're following along.

Should I memorize English answers before the interview?

Memorizing the ideas — yes. Memorizing word for word — risky. A verbatim memorized answer is obvious right away, and worse, it makes you try to force whatever question you just heard into the mold you prepared. Remembering three or four real stories about yourself and retelling them flexibly holds up much better.

Is an online English interview harder to hear than an in-person one?

Usually harder, because you lose lip movement, the audio gets compressed, and connection lag clips off a few sounds at the start of sentences. On the plus side, you get to sit in a familiar space and can keep a note sheet just out of frame. If the audio cuts out, just say so directly: "you're breaking up a bit."

What level of English do you need to go to an interview?

There's no fixed threshold, since it depends on the position and on what the company actually needs English for. What matters more is your ability to understand natural spoken language, not a score on a certificate. You can estimate your current vocabulary with the free vocabulary test.

How should I tactfully answer a salary question in English?

Give a range instead of a single number, and tie it to the overall package. If you want to ask back first, a safe line is "Could you share the range you have budgeted for this role?" If pressed, "I'd rather understand the full package first" is a polite way to defer.

How long should I practice listening before an interview to be ready in time?

There's no universal number, but a few weeks of short daily dictation practice helps more than one cram session right before the interview, because the ear needs time to get used to the natural rhythm of speech. A schedule for busy people is covered in detail in the 15 minutes of English a day article.

An interview doesn't grade you on perfect pronunciation or rare vocabulary — it grades whether two people understand each other over forty-five minutes. Most of your effort should go into locking down your listening, because that's the part you don't control once you're sitting in the room. If your field also has its own layer of terminology worth reviewing beforehand, the specialized English roundup gathers the core vocabulary for twelve different fields.