The best answer to "tell me about yourself" is about 60 to 90 seconds, covers where you are now, one or two things you've actually done that matter for this role, and why you're in this conversation, delivered in that order. It is not your life story, not a walk through your CV from university onward, and not a list of adjectives about yourself.
Nearly every interview opens with it. It's the one question you can be certain you'll be asked, which makes it the highest-return thing you can prepare, and yet it's the answer most people improvise. That mismatch is why so many interviews start flat and never quite recover.
Key takeaways
- Aim for 60 to 90 seconds. Under 30 seconds reads as disengaged; past two minutes you've lost them.
- Use present, then proof, then why here. It works for every role and every level.
- Pick evidence that is relevant to this job, not your most impressive story in general.
- End on the role. Your closing sentence should hand the interviewer their next question.
- Don't recite your CV chronologically. They have it, and the first job you ever had is the least interesting thing about you.
- Prepare the shape, not the script. Memorised answers sound memorised, and they break under follow-ups.
What the interviewer is actually doing
This question looks like small talk. It isn't. In the first 90 seconds the interviewer is making three quick judgements: can you organize a thought under mild pressure, do you understand what this job is, and are you going to be tiring to talk to for the next hour.
That's why rambling hurts so much more than a slightly thin answer. A candidate who talks for four minutes without landing anywhere has answered the first question badly before they've said anything technically wrong. And it's why "I'm a hard-working team player who's passionate about learning" fails: it's a list of claims with no evidence, and it could be said by literally anyone in the pipeline.
They're also, quietly, setting the agenda. Whatever you mention, they'll probably ask about next. That's leverage, and almost nobody uses it deliberately.
The structure: present, proof, why here
Present. One or two sentences on what you do now and the scope of it. Not your title alone, the shape of the work.
"I'm a support lead at a mid-size fintech, where I run a team of six covering escalations for our business customers."
Proof. One or two specifics that matter for the role you're interviewing for. Something you did, and what happened. This is where most answers collapse into adjectives, so be concrete.
"The thing I've spent the last year on is our escalation backlog. We were resolving urgent tickets in about four days; I rebuilt how they were triaged and got that under a day, and complaint volume dropped with it."
Why here. Close by connecting yourself to this specific job. This is the sentence that turns an introduction into a conversation.
"That's why this role stood out: it's the same problem at a much bigger scale, and the technical side of it is where I want to go next."
Read end to end, that's around 45 seconds. Add one more proof point if the role is senior or the interview is long, and you're at 75. That's the target.
Worked example: career changer
"I spent six years teaching secondary maths, and the part I got known for was data. I built the tracking our department used to spot which students were slipping, which pulled our pass rate up two years running. About a year ago I started doing that work seriously outside the classroom, finished a data analytics certification, and did a project rebuilding a local charity's donor reporting so they could actually see retention. I'm looking for an analyst role now because that's the part of my old job I never wanted to put down. This one caught my eye because the team sits close to the people using the numbers, which is exactly how I like to work."
Note what it does not do: apologize. There's no "I know my background is unusual" or "I don't have formal experience." The evidence carries the change; the disclaimer would only invite doubt.
Worked example: little or no experience
"I finished my degree in June, and the most useful thing I did during it wasn't the coursework, it was running the student marketing society. I took over when we had about forty members and no real program, ran a term of workshops with people from local agencies, and we finished the year at a hundred and thirty. I did the campaigns for it myself, which is where I learned the parts I actually enjoy. I'm applying here because it's a small team where I'd be doing the whole loop rather than one slice of it, and that's the way I want to learn this properly."
If your background is thin on paid work, the principle is the same: find real evidence in the places you have it. There's more on this in what to say when you have no experience.
The four openings that lose the room
| Opening | Why it fails |
|---|---|
| "Well, I was born in..." | Chronology from the beginning; you'll run out of time before you reach anything relevant |
| "I'm a passionate, hard-working team player" | Adjectives with no evidence; indistinguishable from every other candidate |
| "It's all on my CV, really" | Reads as disengaged and wastes the one question you knew was coming |
| "Sorry, I'm not great at these..." | Trains the interviewer to discount everything after it |
That last one is more common than you'd think, and it's usually nerves talking rather than genuine self-assessment. If that's the pattern you fall into, work on the nerves themselves rather than trying to out-write them.
Tailor the proof, keep the shape
You do not need a new answer for every company. You need one structure and a small set of interchangeable proof points, which is exactly what a story bank gives you. Before each interview, pick the one or two stories closest to what this job actually needs and slot them into the middle.
A rough guide to picking: read the first three bullets of the job description. Those are usually the real job. Your proof should map onto at least one of them. If your best story is impressive but has nothing to do with those bullets, it's the wrong story for this room, however good it is.
Rehearse the shape, not the words
Here's the trap. This question is so predictable that people write out a script and learn it by heart, then deliver it in the slightly flat, slightly fast register that word-for-word recall always produces. Interviewers hear it immediately. Worse, a memorised answer has no give in it: the moment they interrupt with "sorry, which team was that?", the thread is gone and the rest comes out scrambled.
Prepare the three beats and the specific facts inside them, then let the sentences come out differently every time. There's a fuller version of this argument in how to memorise interview answers, and the short version is that you want the structure automatic and the wording live.
Practically: say it out loud six or seven times, in different words each time, ideally to something that can interrupt you. If you can be cut off mid-answer and still land the "why here" sentence, you're ready. That's also the difference between an answer that survives a phone screen, where you can lean on notes, and one that survives a panel, where you can't.
FAQ
How do you answer "tell me about yourself" in an interview?
Use three beats in order: what you do now and its scope, one or two concrete things you've done that matter for this specific role, and why you're interviewing here. Keep it to 60 to 90 seconds and finish on the role, so your last sentence points the interviewer toward their next question.
How long should my answer to "tell me about yourself" be?
About 60 to 90 seconds. Much shorter and you seem disengaged or unprepared; past two minutes and you've usually lost the room. If you can say your answer comfortably in under a minute, add one more piece of concrete evidence rather than padding the sentences you have.
Should I talk about my personal life?
One brief, genuine detail at the end is fine and can make you memorable, but it shouldn't be the substance of your answer. The question is professional in intent, and interviewers are assessing relevance and clarity. Lead with the work, and keep anything personal to a single sentence.
How do I answer if I have no work experience?
Use the same structure and take your evidence from wherever it genuinely exists: coursework, a society you ran, freelance or volunteer work, a side project. Describe what you did and what changed as a result. Avoid opening with an apology for the gap, since a disclaimer invites more doubt than the gap itself does.
Should I memorise my answer word for word?
No. Memorised answers sound memorised, and they fall apart when the interviewer interrupts. Learn the three beats and the specific facts inside them, then rehearse out loud in different words each time. You want the structure automatic and the phrasing live.
What should I not say when asked to tell them about myself?
Skip the chronological life story, strings of adjectives with no evidence behind them, "it's all on my CV," and any opening apology about being bad at interviews. Also avoid negative commentary about a current or former employer, since it's the first impression and it colours everything after it.
Is "tell me about yourself" the same as "walk me through your CV"?
They're close but not identical. "Walk me through your CV" invites a chronological path through your roles and the transitions between them. "Tell me about yourself" is broader and should be selective, leading with where you are now and the evidence that matters for this role rather than starting at the beginning.