How to answer "Tell me about yourself" without rambling

Almost every interview opens with it, and almost everyone answers it badly. Not because the answer is hard, but because the question sounds like an invitation to talk about yourself, and it isn't.

It is a positioning question. The interviewer is asking: why are you in this room, and should I be interested? They have your CV. They do not need it read back to them.

The shape that works

Ninety seconds, three parts.

Where you are now. One sentence. Your current role, and the thing about it that matters for this job.

"I'm a backend engineer at a payments company, where I've spent the last two years on the settlement pipeline."

The path that got you there — selectively. Two or three sentences, chosen for this role. Not chronological. If you're interviewing for a role that needs someone who can work across teams, the story is about the times you did that. The rest of your career can stay in the CV.

Why this conversation. One or two sentences connecting the two. What about this role is the obvious next step, given the above.

That's it. Ninety seconds, and you have framed everything that follows.

Why most answers drag

Starting at university. Nobody has ever been hired because of what they studied in their second year. Start at the most recent point that still explains something.

Chronology instead of selection. A list of jobs in order is a CV read aloud. A good answer skips entire years because they aren't relevant, and the interviewer will never notice the gap.

No ending. The most common failure is not knowing where to stop, so the answer trails into "...and yeah, that's me." Decide your last sentence in advance. The "why this conversation" part is your ending — when you reach it, stop talking.

Adjectives instead of evidence. "I'm very collaborative" costs nothing to say and is worth nothing to hear. "I spent six months embedded with the fraud team" does the same job and can't be faked.

Tailoring without rewriting

You do not need a new answer for every company. You need one answer with two or three interchangeable middle sections.

Write the middles once:

• the one about technical depth
• the one about working across teams
• the one about owning something end to end

Then read the job description and pick. The opening and the closing barely change. This is the difference between preparing for one interview and preparing for a season of them.

A test before the interview

Say your answer out loud, once, with a timer. Then ask yourself: if the interviewer remembered exactly one sentence from that, which would you want it to be? If you can't identify it, the answer has no shape yet.

Then say it again and cut twenty seconds. Almost every first draft survives it.

What to do if you're interrupted

Sometimes they cut in after twenty seconds with a follow-up. That is a good sign, not a derailment — it means something caught. Answer the follow-up fully and do not try to steer back to your script. The opening did its job.

---

Practising this out loud is the whole exercise. Reading it silently, you will not notice that your second sentence takes forty seconds, or that you have no ending. Rehearse it against the role and listen back.