It's the first question in most interviews and the one people prepare least. It isn't small talk. It's the frame the rest of the interview hangs off. A good answer takes about 90 seconds and quietly tells the panel why you're the sensible choice before they've asked anything hard.
What they're really asking
Not your life story. They're asking: can you summarise yourself clearly under mild pressure, and does your path make sense for this job? Interviewers are also using the answer to pick their follow-ups, and whatever you highlight is what they'll dig into next. That means the question is an opportunity to choose the ground the interview gets fought on.
The structure: Present, Past, Future
- 1
Present
Open with what you do now in one sentence: your role, the scale of it, and the part you're known for. No date-of-birth openings, no 'so I grew up in…'.
- 2
Past
Two or three sentences on the path that got you here, chosen only for what's relevant to this job. Include one concrete achievement with a number in it.
- 3
Future
Close by connecting to this role: what you're looking to do next and why this job is the logical next step. This is the sentence that makes it an interview answer rather than a biography.
Keep it to roughly 90 seconds, about 200 words spoken. Present, Past, Future works because it ends on them rather than on you, and it hands the panel a clean hook to follow up on. Practise it out loud until the shape is automatic, but don't memorise it word for word: a recited answer sounds worse than a slightly rough one.
Example answers
Graduate, first professional job
I finished a business degree in June, and the part I got most out of was the final-year project where I ran a live pricing study for a local retailer. I handled the data collection and presented the recommendation to the owner, who ended up using it. Before that I spent two summers in a customer-facing job where I was the one training new starters by the second summer. What I'm after now is a graduate role where I'm working with real data for real decisions rather than case studies, which is exactly what this analyst role looks like.
Experienced candidate, same field
I'm a project manager at a mid-sized fintech, currently running delivery for the payments team, about nine people across engineering and finance. I came into project work from an operations background, which is why I tend to be the one asking about the handover and the support model rather than just the launch date. The piece I'm proudest of is a billing migration we delivered two days early with no incidents. I'm looking to move towards programme-level work now, and this role sits right on that line, which is why I applied.
Career changer
For the last six years I've been a secondary school teacher, and the last two of those I led our department's timetabling and reporting, which is where I discovered I liked the systems side more than the classroom. So I taught myself SQL, did the Google data analytics certificate, and rebuilt our attendance reporting into something the leadership team now uses weekly, and it cut about four hours of manual work a week. I'm making the move into data properly now, and this role appeals because it's analysis with a public-service angle, which is the part of teaching I don't want to lose.
Common mistakes
- Starting at the beginning of your life instead of the present day. The panel switches off before you reach anything relevant.
- Running four minutes long. Anything past two minutes reads as poor judgement about what matters.
- Reciting your CV chronologically. They've read it; they want the version with the reasoning attached.
- Being entirely generic, like 'hard-working, good with people', with nothing specific enough to follow up on.
- Forgetting the Future part, so the answer never connects to the job you're actually sitting in.
- Over-sharing personal circumstances. Keep it professional unless it's genuinely relevant to the role.
Knowing the answer isn't delivering it.
Have the actual conversation with a video AI interviewer that listens, follows up on what you say and pushes back — then writes you an honest coaching report.
Frequently asked questions
How long should "tell me about yourself" take to answer?
About 90 seconds, and no more than two minutes. That's enough for the Present, Past, Future structure with one concrete achievement, without losing the room.
Should I mention personal life when answering "tell me about yourself"?
Only briefly, and only if it's relevant to the role or explains something on your CV. One short human line is fine; a family history is not what the question is asking for.
Is "tell me about yourself" the same as "walk me through your CV"?
No. "Walk me through your CV" invites a chronological account of your roles. "Tell me about yourself" invites a curated summary aimed at this job: start in the present and select only what's relevant.
Should I memorise my answer word for word?
Learn the structure, not the script. Memorised answers sound flat and fall apart when the interviewer interrupts. Practise it out loud a few times so the shape is automatic and the words stay fresh.