"Tell me about yourself": the 90-second script that works in any interview

The answer that works runs about 90 seconds and has three parts: where you are now (one sentence), the achievement most relevant to this role (two sentences, with a number), and why you want this job (one sentence). It isn't your life story, it doesn't start at university, and it doesn't repeat the CV they've already read.

This is the question that opens almost every English-language interview. It's also the one most people lose, because it looks easy.

Why this question decides the rest of the interview

Two things happen in the first 90 seconds.

The first is that the interviewer forms an impression. It isn't final, but everything after gets read through it. Start hesitantly and every pause afterwards sounds like uncertainty. Start solidly and a pause sounds like someone thinking.

The second is internal. If the first answer goes well, your body relaxes and the next ones come more easily. If it goes badly, you spend the next twenty minutes recovering instead of answering.

That's why it's worth rehearsing this answer.

The structure: present, evidence, direction

Forget chronological order. Nobody wants to hear about 2016.

Part 1: present. One sentence. Who you are professionally today.

Part 2: evidence. Two sentences. One thing you did, chosen because it's relevant to this role, ending in a result.

Part 3: direction. One sentence. Why you're in this conversation.

The script, with examples

Part 1: where you are now

Role, years, where. No preamble.

"I'm a backend engineer with seven years of experience, currently at a logistics company where I work on our order processing systems."

"I'm a performance marketer. I've spent the last five years running paid acquisition, most recently for a B2B SaaS company."

"I work in customer success. I'm currently leading a team of four at a health tech company, looking after our enterprise accounts."

Note what isn't there: where you studied, how many jobs you've had, what you were doing in 2019. None of it helps.

Part 2: the evidence

This is the part almost everyone gets wrong. The temptation is to list everything. Don't. Pick one thing, chosen because the role asks for exactly that, and end on a result.

"Over the last two years I've focused on making our API faster under load. We were timing out during peak hours and losing orders. I rewrote how we queue and batch requests, and we went from about four hundred failed orders a week to almost none."

"The project I'd point to is the paid channel restructure I ran last year. We were spending across six channels without knowing which ones worked. I cut it to two, rebuilt the tracking, and we brought cost per acquisition down by roughly forty percent on the same budget."

"The thing I'm most proud of is our renewal rate. When I took over the enterprise accounts we were renewing about seventy percent. We're at ninety-one now, mostly because we changed when we talk to customers rather than what we say."

If you don't have a number, use a concrete consequence: the team stopped doing something by hand, a customer stayed, someone got promoted, something that broke weekly stopped breaking.

Part 3: why this role

One sentence. Connect what you just described to what they need.

"I'm looking for a role where that kind of work is the main thing and not a side project, and from the job description that seems to be exactly what this is."

"What interests me here is that you're doing this at a scale I haven't worked at yet, and with a fully distributed team, which is how I want to work."

How it sounds together

"I'm a backend engineer with seven years of experience, currently at a logistics company where I work on our order processing systems. Over the last two years I've focused on making our API faster under load. We were timing out during peak hours and losing orders, so I rewrote how we queue and batch requests, and we went from about four hundred failed orders a week to almost none. I'm looking for a role where that kind of work is the main thing rather than a side project, and from the job description that seems to be exactly what this is."

Read it out loud and time it. It should land between 55 and 75 seconds at a comfortable pace. If you're past 100, cut part 2.

Five things that weaken the answer

Starting at university. "So, I graduated in 2015 and then..." You've spent ten seconds and said nothing useful.

Reciting the CV. They have it open. You're there to give the context that doesn't fit on it.

Apologising for your English. "Sorry, my English is not very good." You've just told the interviewer to listen for your mistakes instead of your content. If you stumble, simply keep going.

Speaking too fast. It's the natural reflex when you're nervous in another language, and it lands worse than a pause. A two-second pause sounds like thought. A rushed sentence sounds like panic.

Ending without ending. A lot of people close with "...yeah, so, that's basically it, I guess". Finish on part 3 and stop. The silence afterwards belongs to the interviewer, not to you.

If you stall halfway through

It happens to someone, at some point. What saves you isn't grammar, it's having a natural-sounding recovery line ready:

"Sorry, let me start that again."

>

"How do I put this..."

>

"Give me a second, I want to say this properly."

All three are things native speakers say constantly. None of them sounds like a language problem. They sound like someone choosing their words, which is exactly what you're doing.

Where rehearsing stops helping

An honest caveat, because nobody writes this part.

Rehearsing this answer works very well for this answer. The risk is the side effect: someone who delivers a polished 90 seconds and then falls apart on the first follow-up looks worse than someone who was merely decent throughout. The contrast gives you away.

So treat this as the opening move. Rehearse it until it comes out without effort, then spend the remaining time speaking unscripted English about your work, out loud. Explain what you do to a wall. Talk through your last project as if to a friend.

The goal isn't to have the answer ready. It's to walk into the interview having already spoken English out loud that week, so your mouth is warm by the time it counts.