Job interview in English: questions and answers
Most interviews in English are built from the same questions. Below are the most common ones, what each is really asking and a sample answer for an IT professional. The samples show a structure: put your own experience in.
What an interview usually includes
Usually there is first a call with a recruiter: your story, your motivation and your salary expectations. Then a technical interview, where you explain decisions and write code while talking. At the end comes a conversation about how you work in a team: conflicts, mistakes, difficult projects.
At every stage they judge not only the answer but how you explain it. So you prepare not a text but the ability to say it out loud.
Common questions and sample answers
Numbers in the samples are placeholders: use your own.
1. Tell me about yourself.
What they want to hear: A short story of one or two minutes: who you are now, your main project and why this job interests you. Don’t retell your CV in order.
I’m a backend developer with five years of experience, mostly in Python and Go. For the last two years I’ve worked on payments at a fintech company, where I led the move to a new payment provider. Now I’d like to work on a product for an international market, which is why this role caught my attention.
2. Why do you want to work here?
What they want to hear: What you know about the company and how your experience connects to its work. Name something specific: the product, the stack, the market.
I’ve used your product myself, and I like how fast you ship new features. You’re also moving to an event-driven architecture, and that’s exactly what I worked on in my last project.
3. Tell me about a project you’re proud of.
What they want to hear: Your part and the result. A handy structure is STAR: situation, task, action, result.
Our checkout was timing out during sales, and I was asked to find the cause. I profiled the service, found an N+1 query and replaced it with a single join and a cache. Checkout time went down from four seconds to under one, and the next sale went through without incidents.
4. Tell me about a time you disagreed with a colleague.
What they want to hear: Whether you can argue calmly and to the point. Show how you reached agreement, not how you won.
A colleague wanted to rewrite a service from scratch, and I thought it was too risky before the release. We agreed to try both approaches on one small module first. Refactoring took two days instead of two weeks, so the team went with it.
5. Describe a difficult problem you solved.
What they want to hear: How you think: hypotheses, checks, conclusion. Detail matters more than scale.
We had a memory leak that only happened in production. I added metrics, narrowed it down to one background job and found that it kept references to old sessions. After the fix, memory stayed flat for a month.
6. What are your strengths and weaknesses?
What they want to hear: A strength with an example. A weakness that is real but not critical for the role, and what you do about it.
I’m good at getting to the root of messy bugs. As for weaknesses, I used to take on too much myself instead of asking for help. Now I flag risks early in stand-ups, and our planning has become more accurate.
7. Why are you leaving your current job?
What they want to hear: Talk about what you’re moving towards, not what you’re running from. Don’t criticise your current employer.
I’ve learned a lot there, but the product is mostly in maintenance now. I want to work on something that’s growing and to use English every day.
8. Where do you see yourself in a few years?
What they want to hear: Whether you have a plan and whether it fits the role.
I’d like to grow into a senior role where I own a part of the system end to end and help newer developers on the team.
9. What are your salary expectations?
What they want to hear: Whether you can name a figure. Give a range you have checked against the market and say you’re discussing the whole package.
Based on my experience and the market for this role, I’m looking for something in the range of 4,000 to 5,000 dollars a month. I’m open to discussing the whole package.
10. Do you have any questions for us?
What they want to hear: Always say yes. Your questions show interest and help you decide whether the job suits you.
Yes. What would success look like in the first three months in this role?
Phrases that buy you time and clarify the question
- That’s a good question. Let me think for a second.
- Could you repeat the question, please?
- Just to make sure I understand: you’re asking about…
- Do you mean… or…?
- I haven’t worked with that directly, but here’s how I would approach it.
- Let me walk you through my thinking.
Questions to ask the employer
- What does a typical week look like for this role?
- How is the team structured, and who would I work with most?
- How do you measure success in the first three months?
- What are the biggest challenges for the team right now?
- What are the next steps in the process?
How to prepare
- Pick three or four stories from your experience: a project you’re proud of, a hard problem, a conflict, a mistake. Almost any behavioural question leads to one of them.
- Say your answers out loud, don’t only write them. Text in your head and text out loud are different skills.
- Record yourself on your phone and listen: where you pause and which words you repeat.
- Do a mock interview with someone who will ask follow-up questions. You can do one with Yeltay in a free lesson.
Updated 2026-10-10