Interview English: Talking About Your Work

Interview English is a specific skill. The vocabulary is ordinary; the difficulty is structuring an answer under pressure while keeping your tenses straight.

Structure an answer: situation → action → result

This is the most reliable pattern in English-language interviews.

Situation: We were losing about a day a week to manual reporting.

Action: I built a script that pulled the data automatically and flagged anomalies.

Result: That cut the reporting time to about an hour, and we caught two errors we'd have missed.

Weak answers stop after the action. The result is what interviewers are listening for.

Tense control

• Past simple for what you did: I built, I led, we decided
• Past continuous for background: We were losing a day a week
• Present perfect for overall experience: I've worked on several migrations
• Present simple for what's still true: I work mainly in Python

The classic slip is drifting into present simple while narrating a past project: ❌ So I build the script and it works well. → ✅ So I built the script and it worked well.

What the standard questions are actually asking

Question	What they want to hear
Tell me about yourself.	two minutes on your professional path, ending at why you're here
Why are you leaving?	something you're moving towards, not away from
What's your biggest weakness?	a real one, plus what you do about it
Tell me about a difficult colleague.	that you don't badmouth people
Where do you see yourself in five years?	that this role fits your direction
Why us?	evidence you researched them

The trap in why are you leaving is worth naming: criticising your current employer costs you more than almost anything else you could say. I've learned a lot there, but I'm looking for more technical depth says the same thing safely.

Describing your contribution honestly

Interviewers listen for whether you distinguish I from we.

• I was responsible for the data layer.
• My role was to coordinate between the two teams.
• I led a team of four.
• We delivered it together, but I owned the testing.

Claiming a whole team's work sounds inflated; saying only "we" makes your own contribution invisible.

Talking about difficulty and failure

Expect a question about something that went wrong. The structure: what happened → what you did → what you learned.

• We underestimated the migration by about a month.
• I flagged it early and we re-scoped rather than rushing.
• Since then I always build in a buffer for data cleanup.

Avoid two extremes: blaming others, and claiming you've never failed.

Buying time, and admitting a gap

Two things you will need, and both are fine:

• That's a good question — let me think for a second.
• Could I come back to that at the end?
• I haven't used Kafka in production, but I've done something similar with RabbitMQ — shall I talk about that?

That last pattern is the one that saves interviews: admit the gap, then immediately offer the nearest real experience. Bluffing is caught quickly and costs far more than the gap would have.

Talking about money

• What's the range for this role?
• I'm looking for something in the region of X.
• I'd rather understand the role fully first — could we come back to that?
• Is there flexibility on that?

Give a range rather than a single number, and give it in their currency and their terms (annual, gross).

On a video interview

• Sorry, you cut out — could you repeat the last part?
• Can you see my screen?
• I'll just close the door — one moment.

Technical trouble is not held against you. Pretending you heard the question is.

Asking your own questions

• What does success look like in this role in the first six months?
• How is the team structured?
• What are the biggest challenges the team is facing right now?
• What do you enjoy about working here?

Closing

• Thank you — I've enjoyed this. Is there anything about my background you'd like me to expand on?
• What are the next steps? · When might I hear back?

That first question is worth memorising: it invites the interviewer to raise any doubt while you're still in the room to answer it.

You are being assessed on your English as well as your work. A clear, well-structured answer in simple English beats a sophisticated one you lose control of halfway through. Short sentences, one idea each, and a result at the end — that reads as competence in both dimensions at once.

One answer, done properly

Interviewer: Tell me about a time a project didn't go to plan.

Candidate: Sure. We were migrating about 200 accounts and we'd estimated six weeks. About two weeks in it was clear the data was much messier than we'd assumed.

Interviewer: What did you do?

Candidate: I flagged it that week rather than hoping to catch up. We re-scoped — moved 40 of the messiest accounts to a second phase. The main migration landed a week late instead of a month late.

Interviewer: And looking back?

Candidate: I now always build in time for data cleanup before committing to a date. That's the main thing I took from it.

Background in past continuous, actions in past simple, a number, an honest failure, and a lesson — without blaming anyone.

Try it yourself

The quiz below focuses on structure and tense — the two things that most affect how answers land.