How to answer “Tell me about yourself” in an English interview

What is the interviewer really checking with “Tell me about yourself”?

It sounds like small talk. It is not. This is usually the first real question, and it sets the frame for the rest of the interview. The interviewer is checking three things at once.

• Relevance: can you pick, from everything you have done, the parts that matter for this job?
• Clarity: can you organise your thoughts and speak in a way that is easy to follow?
• Fit and motivation: do you know why you are in this room, for this role?

In an English interview there is a fourth check that nobody says out loud: how comfortable you are speaking. The first 90 seconds give the interviewer a strong impression of your spoken English. A calm, structured answer here buys you goodwill for every question that follows.

What structure should you use?

Use present, past, future. It is simple enough to remember under pressure and it keeps you away from a chronological walk through your CV.

1. Present: your current role and the kind of problem you work on. “I’m a backend engineer at a payments startup, and I work on the systems that move money between banks.”
2. Past: one or two results or experiences that show you are good at it. “Before that, I spent four years at a logistics company, where I rebuilt the tracking service that handled every delivery update.”
3. Future: why this role, at this company, is the next step. “I’m looking for a team where reliability is the product, and that’s why this role caught my attention.”

Aim for 60 to 90 seconds. That is roughly 150 to 220 words at a calm speaking pace. If the interviewer wants more, they will ask. A short answer that invites a follow-up question is better than a long one that leaves nothing to ask.

What does a weak answer sound like compared with a strong one?

The pattern is the same in every row. Strong answers name a role, a type of problem, and a concrete result. Weak answers use adjectives, history, or apologies.

What are some good model answers for different profiles?

These are written to be spoken, not read. Short sentences, contractions, and a clear end. Change the details to match your own work, and keep the shape.

Software engineer: “I’m a backend engineer, and right now I work at a payments startup on the services that handle transfers between banks. My focus is reliability: last year I led the work that cut our failed payments by about a third. Before that, I spent four years at a logistics company building the tracking system for deliveries. So I’ve worked on two products where an outage costs real money. What I want next is a bigger platform with more traffic and a team that takes on-call seriously. That’s what drew me to this role.”

Project or product manager: “I’m a product manager at a mid-size insurance company. I own the claims app, which is the part of the product customers use when something has gone wrong, so the bar for clarity is high. In the last year we redesigned the claim flow and cut the average time to submit a claim from twenty minutes to about eight. Before product, I worked as a business analyst, which is why I’m comfortable with data and with talking to engineers. I’m now looking for a role where I can own a product from zero to one, and your team is building exactly that.”

Career changer moving from teaching into customer success: “For the last seven years I’ve been a secondary school teacher, mostly maths. A big part of that job is explaining something complex to people who don’t want to hear it, and then checking they actually understood. Two years ago I started helping our school roll out a new learning platform, and I found I really enjoyed the training and support side. I did a certification in customer success and I’ve been doing onboarding calls for an education software company on a part-time contract. Now I want to do it full-time, and your product is used by schools, so my background is a direct fit.”

What mistakes do non-native speakers make with this question?

• Sounding memorised. A perfect paragraph recited at speed sounds like a file being read. Learn three points, not three hundred words, so the sentences come out slightly different each time.
• Apologising for your English. Opening with “Sorry for my English” tells the interviewer to listen for mistakes. Say nothing about it. Your English will be judged on how you communicate, not on a disclaimer.
• Speaking too fast. Nerves push the pace up, and fast speech hides your pronunciation and your structure. Pause between the three parts. A pause sounds confident in English.
• Over-hedging. “I think maybe I’m kind of good at…” makes a real result sound uncertain. State results plainly: “I led”, “I cut”, “I built”.
• Translating idioms. Expressions that work in your first language often sound odd in English. Use plain verbs instead.
• Filler at the start of every sentence. “So, basically, actually…” eats time. One “So” at the start is fine. After that, start sentences with the subject.

How do you rehearse it out loud?

Reading your answer silently does not prepare you to say it. Your mouth needs the practice, and so does your timing.

1. Write three bullet points: present, past, future. One line each.
2. Say the answer out loud from the bullets only, with a timer. Stop at 90 seconds even if you are not finished.
3. Record yourself on your phone. Listen once for length and once for filler words. Count the “basically” and “you know”.
4. Apply the one-breath test: each of the three parts should fit in one or two breaths. If a sentence needs a third breath, split it.
5. Say it five times on different days, from the bullets. If the wording is identical every time, you have memorised it. Loosen it.
6. Practise the follow-ups too: “Why did you leave?”, “Tell me more about that project.” Your opener will create them.

If you want a counterpart, Eloquent lets you set up a custom roleplay with the role, the company, and the kind of interviewer, then answer out loud in real time. After the session, the debrief quotes the exact words you used and suggests a better line, which makes it easy to see where you over-explained or hedged.

How should you end your answer?

End on the future part, then stop. Many candidates trail off with “…and yeah, that’s it” or keep adding details because the silence feels awkward. A clean final line hands the conversation back.

• “…and that’s why I applied for this role.”
• “…so this position is a natural next step for me.”
• “Happy to go deeper into any of that.”

Frequently asked questions