How long should my answer be?

About 60 to 90 seconds — roughly 150 to 200 spoken words. Long enough to give them something to ask about, short enough that you are not still talking when their attention moves on. If it runs past two minutes, it is too long.

Should I memorise my answer word for word?

No. Memorised answers sound memorised, and if you lose your place you have nothing to fall back on. Learn the shape instead — where you are now, the experience that got you here, why you are in this room — and let the words come out slightly differently each time.

What if I am changing careers?

Name the change directly rather than hoping they will not notice, then make the through-line explicit: the skills you built that this role actually needs. A career change is only a weakness if you leave the connection for them to guess.

What if I am early in my career, or have a gap?

Use what you genuinely have — a project, an internship, coursework, something you built or ran. Specific beats senior. If there is a gap, state it briefly and without apology, then move to what you did with the time or what you are ready to do now.

Is this the same as “walk me through your résumé”?

No. “Walk me through your résumé” invites chronology — start earlier and move forward. “Tell me about yourself” invites selection: you choose what matters for this role. Answering the second as if it were the first is the most common mistake.

How to Answer “Tell Me About Yourself” (Structure + Examples)

The short answer

In about 60 to 90 seconds, say where you are now, the experience that got you here, and why you’re in this room. Not your life story — the part of it that matters for this role.

What this question is actually asking

It is almost always the first question, and it is rarely a request for your biography. What the interviewer is really asking is simpler: why are you here, and why should I keep listening?

They are handing you the first word. Whatever you say becomes the frame everyone uses for the rest of the conversation — including you. That is worth preparing for.

Why interviewers ask it

Three reasons, and none of them is “to get to know you” in a general sense:

It settles the room. An easy opener lets both of you find your footing.
It shows them how you decide what matters. What you include — and leave out — says more about your judgement than the facts do.
It gives them threads to pull. A good answer hands the interviewer two or three things worth asking about next.

So the goal is not to cover everything. It is to be relevant, easy to follow, and to leave them something they want to ask about.

The structure that works: Present → Past → Future

The most reliable shape is three beats, in this order, totalling about 60 to 90 seconds.

Present~20 seconds

Where you are now: your current role, plus one thing you are genuinely known for. Give them somewhere to place you.

Past~40 seconds

The experience that got you here: two moments — not a career history — that built exactly what this role needs. Be specific about what the situation was, what you did, and what changed.

Future~20 seconds

Why this role, now: the honest reason you are in this conversation. Not flattery — the actual reason.

It works because it answers the real question in the order a listener needs it: here is where I am, here is how I got here, here is why I am sitting across from you.

Why most people struggle

Most people do not struggle with this question because they lack good material. They struggle because they cannot reach it under pressure.

Your career already contains the answer — the project you turned around, the team you steadied, the decision that was harder than it looked. But in the moment, with adrenaline up and a stranger watching, the mind reaches for the résumé instead of the memory. So people recite a job history the interviewer could have read off a page, and the specific, convincing detail — the one that would actually have landed — arrives on the drive home.

That is not a storytelling problem. It is a recall problem. And recall is a preparation problem, which means it is solvable.

How to build your answer

Do this now. It takes about fifteen minutes, and you will end up with something you can actually use.

1
Start with the role, not with you.
Read the job description once and write down the two or three things this role genuinely needs. Everything that follows is selected against that list.
2
Write your “now” line.
One sentence: your current role, plus one thing you are genuinely known for. Not a title recital — something true and specific.
3
Choose two moments from your past.
Not a career history. The two experiences that most directly built what this role needs. For each: what the situation was, what you did, and what changed because of it.
4
Find the through-line.
What connects those moments to this role? Write it as one sentence. If you cannot, you have probably chosen the wrong moments.
5
Land the “why here, why now.”
One or two honest sentences. Interviewers can tell a real reason from flattery instantly.
6
Cut.
Read it back and remove any sentence that does not help them understand why you fit. Most first drafts lose about a third.

Then read the whole thing out loud once. If it runs past ninety seconds, it is still too long.

Three worked examples

These are illustrations, not templates. The specifics are what make them work — and your specifics will be different.

Mid-career · program manager

I’m a program manager at [company], where I run delivery for our hardware launches — most recently a programme that had slipped twice before I picked it up, and shipped on the revised date. Before that I spent four years in manufacturing operations, which is where I learned to spot a schedule quietly falling apart before it shows up in a status report. The thread through all of it is that I like the messy, cross-functional programmes where nobody quite owns the outcome yet. That is exactly what this role is, which is why I’m here.

Career changer · teaching → customer success

I spent six years teaching secondary maths, and for the last two I ran our department’s intervention programme — which in practice meant owning a set of outcomes for 200 students and reporting on them every term. Last year I moved into customer success at [company], looking after 40 accounts, and the work turned out to be remarkably similar: work out why someone is stuck, build a plan, follow it through, show the results. I’m here because this role is that same work at a larger scale, with a product I actually use.

Early career · first or second role

I’m a data analyst at [company], about eighteen months in, and what I’ve become the go-to person for is fixing reporting nobody trusts — I rebuilt our weekly sales dashboard after we found two of the numbers were wrong, and it is now what the leadership team actually opens on Mondays. Before that I did a placement year in finance, which is where I got comfortable with people questioning my numbers. I’m looking for more ownership of the analysis itself, and that is what this role looked like from the description.

Common mistakes

Reciting your résumé in order.
Instead: Select. They already have the résumé — they want to know what you think matters.
Starting too far back.
Instead: Start where you are now. Nobody needs your degree unless it is genuinely relevant.
Going too long.
Instead: Ninety seconds. If you are still talking after two minutes, you have already lost the room.
Memorising it word for word.
Instead: Rehearse the shape, not a script. Memorised answers sound memorised — and leave you nothing to fall back on if you lose your place.
Leading with what you want.
Instead: Lead with what you bring. Get to what you want at the end, briefly.
Being vague — “I’m passionate about…”
Instead: Use one specific, verifiable detail. Specificity is what makes people believe you.
Never connecting it to the role.
Instead: Say the through-line out loud. Do not leave them to infer it.

How to practice it

The goal is not a perfect performance. It is that the words are available to you when you need them.

Say it out loud. Reading it silently is not practice — your mouth has not done the work.
Practice the shape, not the script. You want three landmarks — now, how I got here, why here — not sentences to recall.
Record it once and listen back. You will hear the padding immediately. Nothing else gives you that.
Three or four passes, not thirty. Over-rehearsal is exactly what makes people sound recited.
Then leave it alone. You are not memorising, you are becoming familiar — and familiar is what comes back under pressure.

How to Answer “Tell Me About Yourself”