Quick Answer
The English mistakes that cost non-native speakers job offers are rarely grammar errors — they are signals. Vague verb tenses, missing quantification, over-hedging, and filler phrases make technically strong candidates sound junior or uncertain. Each mistake has a specific fix: a reworded sentence, a different structure, a phrase swap. Knowing which ten patterns to correct is the fastest way to close the gap between how good you are and how good you sound.
What interviewers are actually scoring (the hidden rubric)
Most rejections after a strong technical round are not about technical skill — they are about what your language signalled. Interviewers are not consciously grading your grammar. They are forming an impression, and that impression is built from a set of signals that your word choices and sentence structures send automatically, before you finish speaking.
| What the interviewer hears | What they conclude (often unconsciously) | What they are actually scoring |
|---|---|---|
| Vague verbs, passive constructions | This person may not have owned the work | Ownership and seniority |
| No numbers, no outcomes | I can't tell if this actually worked | Impact and results orientation |
| Constant hedging ("maybe", "I think", "sort of") | They're not confident in this area | Confidence and communication clarity |
| Long pauses filled with "um", "uh", "how to say" | They're struggling to express the idea | Fluency under pressure |
| Apologies for English mid-answer | They see their language as a liability | Self-presentation and composure |
| "We did this" with no personal contribution | I don't know what this person actually did | Individual contribution |
| Answer starts with context, ends with the point | I lost the thread — what was the answer? | Communication structure |
| Overly formal or textbook phrasing | They sound rehearsed, not natural | Cultural fit and communication style |
Interviewers score communication as a proxy for how you will perform in meetings, on-calls, and cross-functional work — not just how well you speak English.
Key takeaway
The mistakes below are not grammar mistakes. They are signal mistakes — each one sends a message you did not intend, about ownership, confidence, or seniority. The fix is always a specific rewrite, not a vague instruction to "be more confident."
Before going through each mistake, it is worth bookmarking Mockly's guide on verb tenses for your career timeline — the tense choices in your answers are where several of these mistakes live, and getting them right changes how senior you sound immediately.
Mistake 1: Vague past tense that hides your role
Insight
When you describe past work with passive or impersonal constructions, the interviewer cannot tell whether you led the work, contributed to it, or watched it happen — and they will not ask.
This is the most common mistake, and it is invisible to the person making it. In many languages and engineering cultures, using "we" or passive voice is polite and accurate — the team did do it together. But in a US or UK interview, the interviewer needs to evaluate you specifically. If they cannot tell what you personally did, they will assume the answer is "not much."
| What candidates say | What it signals | Rewritten version |
|---|---|---|
| "The system was redesigned to handle higher load." | Who did this? Were you involved? | "I redesigned the caching layer, which cut p99 latency from 800ms to 120ms." |
| "We migrated everything to Kubernetes." | What did you specifically do? | "I led the Kubernetes migration for our three core services — I wrote the Helm charts and ran the rollout." |
| "There were some performance issues that were resolved." | This person was not involved in solving them. | "I identified a N+1 query pattern causing the slowdown and rewrote the ORM calls — response time dropped by 60%." |
Use "I" for your actions, "we" only for team decisions where your personal role is already established.
Interview tip
Self-check: Read your last three STAR answers out loud. Count how many sentences start with "I" versus "we" or passive constructions. If fewer than half start with "I", rewrite until they do.
Mistake 2: Describing impact without numbers
Insight
An answer without a number is an answer the interviewer cannot verify, compare, or remember — and unverifiable impact is discounted to near zero.
"I improved the performance of the service" and "I reduced API response time by 70%, from 400ms to 120ms" describe the same work. The first sounds like a vague claim. The second sounds like a senior engineer who understands the business impact of their work. Interviewers hear dozens of vague claims per week. A specific number is the fastest way to stand out.
How to add numbers when you don't remember the exact figure
- Use a range: "roughly 60 to 70 percent faster" is credible and honest.
- Use relative scale: "we went from handling 10,000 requests per minute to over 80,000."
- Use business impact if you have it: "that change reduced our cloud spend by around $15,000 a month."
- If you genuinely have no number, name the scope: "this affected all 200,000 active users" or "across 12 microservices."
Watch Out
Do not invent numbers. If you are not sure of the figure, say "roughly" or "around" — that is honest and still far stronger than no number at all. Fabricated metrics collapse instantly under a follow-up question.
Pronouncing numbers confidently also matters — "fifteen percent" and "fifty percent" sound nearly identical under pressure. Mockly's guide on pronouncing numbers and metrics covers the -teen vs -ty distinction and how to say decimals and percentages clearly.
Mistake 3: Over-hedging every claim
Insight
Over-hedging — softening every statement with "maybe", "I think", "sort of", or "I'm not sure but" — reads as uncertainty about the content, not politeness.
In many cultures, hedging is a sign of intellectual honesty and respect for the listener. In a US or UK interview, constant hedging signals that you are not confident in your own experience. The interviewer is not looking for certainty about the future — they are looking for confidence about what you have already done. Hedging past facts is the specific pattern to eliminate.
| Over-hedged version | Clean version |
|---|---|
| "I think maybe we reduced the error rate by something like 30%?" | "We reduced the error rate by around 30%." |
| "I'm not sure if this is the right way to say it, but I kind of led the project." | "I led the project end-to-end — from scoping to production deployment." |
| "It was sort of a distributed system, I suppose." | "It was a distributed system — five services communicating over gRPC." |
| "I might have been the one who suggested the new architecture." | "I proposed the new architecture and presented it to the team." |
Hedge the future and unknowns. Never hedge your own past actions.
Hedges to remove entirely from interview answers
- "I think maybe..." → just state the fact
- "Sort of" / "kind of" → remove; they add nothing
- "I'm not sure but..." → only use this before a genuine guess, not before a fact you know
- "Something like" → replace with "around" or "roughly" when you need to approximate
- "I suppose" → remove entirely; it weakens every sentence it touches
Mistake 4: Filler phrases that signal low confidence
Insight
Filler phrases — "how to say", "what is the word", "you know what I mean" — are not grammar errors, but they interrupt the interviewer's attention and shift focus from your answer to your language.
Every speaker uses fillers. The problem is not having them — it is which fillers you use and how often. "Um" and "uh" are universal and mostly invisible to native-English interviewers. "How to say" and "what is the word" are not — they flag that you are searching for an English word, which draws attention to the language gap rather than the idea you are trying to express.
| Filler to replace | Better alternative | Why it works |
|---|---|---|
| "How to say..." | A one-second pause, then continue | Silence reads as thinking, not struggling |
| "What is the word..." | "The term I'm looking for is..." or just use a synonym and move on | Shows vocabulary range rather than a gap |
| "You know what I mean?" | Remove it; finish the sentence instead | Seeking confirmation mid-answer sounds uncertain |
| "Actually, in my country we call it..." | Just use the English term, or explain the concept directly | Cross-cultural detours lose the interviewer |
| "Etc., etc." at the end of a list | Name one more specific example instead | "Etc." signals you ran out of content |
Replace language-searching fillers with a brief pause. Pauses read as composure; filler phrases read as struggle.
💡 Practice drill for fillers
Record yourself answering one behavioral question. Listen back specifically for filler phrases — not grammar, just fillers. Count them. Do the same answer again, replacing each filler with silence. Most people find the second recording sounds significantly more authoritative, even though it feels uncomfortable to record.
Mistake 5: Using the wrong register (too formal or too casual)
Insight
Register — the level of formality in your language — is one of the hardest things to calibrate in a second language, and getting it wrong in either direction creates friction with the interviewer.
Too formal (common in non-native speakers)
"I am pleased to inform you that during my tenure at the aforementioned organisation, I was responsible for the implementation of a novel caching solution." This sounds like a written report, not a conversation. It creates distance and makes you sound rehearsed rather than competent.
Natural professional register
"At my last company, I built a caching layer that cut our database load by about 40%. The main challenge was cache invalidation — here's how I handled it." This is confident, direct, and sounds like someone who has actually done the work.
Register calibration — what to swap
- "I was responsible for" → "I built" / "I ran" / "I owned"
- "I endeavoured to" → "I tried to" / "I worked to"
- "It was ascertained that" → "We found that" / "I noticed that"
- "In order to achieve" → "To" (shorter is almost always better)
- "I would like to mention" → just say the thing you want to mention
- "As per your question" → just answer the question
Interview tip
UK interviews tend to be slightly more formal than US ones, but both expect conversational professional English — not written-report English. If you learned English in an academic or formal business context, your register is probably one notch too high. Bring it down by using shorter sentences and active verbs.
Mistake 6: Burying the answer at the end
Insight
When you give context before your answer, the interviewer spends the first thirty seconds not knowing where you are going — and that uncertainty reads as poor communication structure.
This is a structural habit, not a language problem. Many engineers are trained to show their reasoning before their conclusion — it is how technical writing works. But in an interview, the interviewer needs to know your answer first so they can follow your reasoning. If they do not know the destination, the context feels like noise.
| Answer-last structure (common) | Answer-first structure (correct for interviews) |
|---|---|
| "So, we had a situation where the database was getting a lot of read traffic, and we tried a few things, like adding indexes, and then we looked at read replicas, and eventually we decided to implement a caching layer, which is what I worked on." | "I built a Redis caching layer to solve a read-traffic bottleneck. We had tried indexes and read replicas first — here's why caching was the right call." |
| "The team was quite large and there were some disagreements about the architecture, and after a few meetings I kind of became the person who was coordinating things." | "I ended up leading the architecture decision for that project. The team had competing proposals, so I ran a structured comparison and got us to a consensus." |
State the outcome or your role in the first sentence. Then explain how you got there. Interviewers follow and remember answers better when they know where the story ends before it starts.
Interview tip
Apply this to every behavioral answer: write your first sentence as if it is the only sentence the interviewer will quote back to you. It should contain your role and the result. Everything else is evidence.
Mistake 7: Saying "we" when the interviewer needs to hear "I"
Insight
"We" is not wrong — it becomes a problem when it replaces "I" in sentences where the interviewer is specifically trying to understand your individual contribution.
This is different from Mistake 1 (passive voice). Here, you are using "we" correctly — the team did do those things together. The issue is that the interviewer is evaluating you, not your team. They will ask follow-up questions to dig out what you personally did, but if every answer is "we", they eventually give up and mark you down for unclear ownership.
How to use "I" and "we" correctly in the same answer
- Use "I" for: decisions you made, code you wrote, proposals you initiated, conversations you led, problems you identified.
- Use "we" for: team agreements, collective outcomes, shared processes — after you have already established your personal role.
- Example: "I proposed moving to an event-driven architecture. We spent two weeks evaluating it as a team, and I wrote the final design doc that got us aligned."
- The word "I" does not sound arrogant in a US or UK interview. It sounds like someone who knows what they did. Overusing "we" sounds like someone who is hiding.
Watch Out
If you find it genuinely uncomfortable to say "I" — because it feels boastful in your culture — practise the sentence out loud ten times before the interview. The discomfort is a cultural reflex, not a language problem, and it fades with repetition.
Mistake 8: False fluency collapse under follow-up questions
Insight
Many candidates prepare polished answers to expected questions and then lose fluency completely when the interviewer asks something unexpected — and that contrast is more damaging than being consistently imperfect throughout.
A prepared answer that sounds fluent followed by a follow-up that sounds like a different, much less confident speaker raises a red flag. The interviewer starts to wonder whether the first answer was memorised rather than genuine. This is the "false fluency collapse" — and it is one of the most damaging patterns in non-native speaker interviews because it undermines the answers that came before it.
How to handle unexpected follow-up questions
- Buy yourself two seconds with a bridging phrase: "That's a good angle — let me think about that for a moment." This is natural and buys you real thinking time without sounding lost.
- If you did not fully understand the question: "Could you say a bit more about what you're looking for there?" — asking for clarification is a sign of precision, not confusion.
- If you genuinely do not know: "I haven't worked with that specific approach, but here's how I'd think through it..." — showing your reasoning process under uncertainty is often what the interviewer is testing.
- Never say "I don't know" and stop. Always follow it with what you do know or how you would find out.
- Practise follow-up drills: after each prepared answer, ask yourself three aggressive follow-up questions and answer those out loud too — unprepared.
Consistent imperfect fluency is far less damaging than polished answers followed by collapse. Interviewers are testing your thinking, not your script.