How to Answer "Tell Me About Yourself" (With Examples)
The most common opening question in any interview — and most candidates answer it wrong. Here's how to nail it every time.
Bottom line: "Tell me about yourself" is the highest-leverage question in any interview. Most candidates waste it with a rambling life story. A focused 90-second answer using Present → Past → Future sets the tone for everything that follows — and signals immediately that you know how to communicate.
Why this question trips people up
"Tell me about yourself" sounds open-ended, so candidates treat it like an invitation to give their life story. They start from their first job, work through every role chronologically, and end with "…and that's why I'm here today." The interviewer has stopped listening by sentence three.
The question isn't asking for your biography. It's asking: can you do this job, and will you fit this team? Your answer should address both — concisely, with a clear through-line — in under two minutes.
The Present–Past–Future formula
The most reliable structure for this question is Present → Past → Future. It's simple, chronologically intuitive, and naturally ends with why you're in the room. Each section is 2–3 sentences. The whole answer runs 60–90 seconds.
| Part | What to cover | Length |
|---|---|---|
| Present | Your current role, what you do, and a key recent win | 2–3 sentences |
| Past | 1–2 experiences that built the skills relevant to this role | 2–3 sentences |
| Future | Why you're making this move and why this role/company specifically | 1–2 sentences |
The "Future" section is the most commonly skipped. Without it, your answer hangs in the air. Adding it transforms your response from a summary into a pitch.
Example answers by career stage
Early career / graduate
"I've just completed a BSc in Computer Science at Manchester, where I focused on software engineering and spent my dissertation researching distributed systems performance. During my studies I completed two internships — one at a fintech startup building APIs in Python, and one at a larger software house on a Java microservices team. I'm now looking for a graduate developer role where I can grow quickly in a product-focused environment, and [Company]'s focus on developer tooling stood out immediately."
Mid-career professional
"I'm currently a Senior Product Manager at a Series B SaaS company, leading the core product area with a team of three PMs and 12 engineers. Over the last five years I've moved from data analysis into product — most recently shipping a pricing feature that increased ARR by 18%. I'm now looking for my next step toward a Head of Product role, and [Company]'s current growth stage is exactly the environment I want to do that in."
Career changer
"I've spent eight years in financial services — most recently as a derivatives analyst — and I've been deliberately moving into data science for the past 18 months. I've completed an ML specialisation and built three end-to-end projects using real financial datasets alongside my day job. I'm now looking to combine domain knowledge with technical skills in a finance or fintech context, which is why [Company]'s risk analytics team caught my attention."
What makes the difference: specifics vs generics
| Weak version | Strong version |
|---|---|
| "I'm a hard-working team player" | "I led a team of four through a product relaunch that lifted retention by 22%" |
| "I have lots of experience in marketing" | "I've run paid acquisition across B2B SaaS — most recently managing a £400k annual budget" |
| "I love solving problems" | "I cut our manual reporting time from 4 hours to 20 minutes by automating the data pull" |
| "I'm keen to grow in this area" | "I'm specifically looking for a role where I can own the full product lifecycle — which is what this role does" |
The left column gets forgotten. The right column gets written down.
Common mistakes to avoid
Starting too far back
Begin with who you are now. A-levels, university clubs, and your first job at 18 are almost never relevant. The interviewer has your CV — they don't need a guided tour.
Being too vague
"I'm passionate about technology" is background noise. What technology? What did you build? What problem did it solve? Every claim should be backed by a specific example or number.
Skipping the "why here" section
The final sentence — why you're applying to this company specifically — is the one interviewers remember most. It signals preparation and genuine interest. "I'm looking for a new challenge" is not a reason. "I've followed your product for two years and the way you're approaching the enterprise market is genuinely different" is.
Tailoring for different industries
- Finance/consulting: Lead with impact metrics — deal value, portfolio size, client wins, cost savings
- Technology: Emphasise what you've built, what stack you've used, what scale you've operated at
- Creative/marketing: Lead with notable campaigns, brand names, audience size, or campaign ROI
- Operations/logistics: Focus on efficiency gains, scale, cross-functional coordination
Golden nugget: record yourself and watch it back
Writing your answer is only half the job. Set your phone up and say it to camera. Most people are surprised by how often they rush the ending, trail off, or use filler words — "like", "you know", "kind of". Aim for a pace that feels slightly slower than natural. On playback, it'll sound confident and measured. One practice session in front of a camera is worth five sessions just thinking about the answer.
Use our STAR Generator to build polished answers for the behavioural questions that follow this opener.
Written by Desh Naidoo-Cann · Founder, Apex Assets Group · MBA Finance