Nobody Wants Your Life Story
"Tell me about yourself" is the question almost every interview starts with, and almost every candidate gets it wrong. Not because they don't know what to say. Because they say too much of the wrong things in the wrong order.
The classic mistake: candidates interpret "about yourself" as an invitation for autobiography. They start with where they grew up, mention their university, walk chronologically through every role since graduation, and land, three minutes later, out of breath and slightly lost, somewhere around their current job. The interviewer has been politely waiting for the point.
Here's what the question actually means: "Give me a 90-second pitch that tells me who you are professionally, why you're good at it, and why you're here." That's it. The personal details — hobbies, family, where you went to school — are almost never relevant unless you're asked directly.
Why This Question Exists
Interviewers don't ask this as a warm-up. They're doing several things at once:
First, they're watching how you structure and communicate information under mild pressure. Can you self-edit? Do you lead with what matters? This previews how you'll communicate in the actual job.
Second, they're checking whether your self-perception matches the role. If the job needs a strategic thinker and you describe yourself exclusively as an executor, that's a misalignment they'll remember.
Third, they're getting calibration data. Your answer to this question frames every follow-up. If you mention a specific achievement early, they'll ask about it. If you mention a career gap, they'll probe it. You have more control over the conversation than you probably realize.
The Present-Past-Future Framework
This is the structure that works consistently across industries and seniority levels. It works because it's logical, it's concise, and it ends in the right place.
Present: Who are you professionally right now? Your current role, your core function, one or two things you're specifically known for. Keep it to two sentences.
Past: Why are you credible? Pick the one or two experiences from your history that most directly support your fit for this role. Not a tour of your career. Highlights selected for this audience.
Future: Why are you here? What do you want to do next, and why does this company or role fit? This is the piece most candidates skip, but it's the piece the interviewer most wants to hear.
A mid-level data engineer going for a staff role might say:
"I'm a data engineer with about seven years of experience, currently at a healthcare technology company where I lead our data pipeline infrastructure for about 40 million patient records. Before that, I spent four years at a consultancy working on data architecture for financial services clients, which gave me a broad view across very different data environments. I'm here because I want to move into a staff-level role where I'm shaping the technical direction, not just executing on it — and from what I've read about what you're building, this seems like the right next step."
Ninety seconds. Present, past, future. Specific enough to be memorable, tight enough to invite follow-up.
What to Include (and What to Cut)
Include:
- Your current role and the scale you operate at (team size, revenue, users, etc.)
- The one or two past experiences that make you specifically credible for this role
- A concrete result or achievement — one is enough
- Why this particular role or company, in one sentence
Cut:
- Education details, unless you're a recent graduate or your degree is directly relevant
- Personal information: family, location, hobbies — unless asked
- Everything pre-2015, unless it's genuinely foundational to your candidacy
- Anything defensive or explanatory ("I left that company because...")
- Superlatives without evidence ("I'm extremely passionate and results-driven")
The editing principle: for each thing you consider including, ask "does this help the interviewer see why I'm the right person for this specific job?" If no, cut it.
Tailoring to the Role
This is where candidates who prepare beat candidates who wing it. Before any interview, identify the two or three qualities the role most requires — not just the generic ones in the job description, but the ones that show up repeatedly or are emphasized as "must-haves."
Then reverse-engineer your answer. If the role emphasizes cross-functional leadership, make sure your present or past sections demonstrate that. If it emphasizes technical depth, lead with that. You're not lying — you're choosing which true things to say.
I once coached a product manager who was interviewing for a senior role at a fintech. Her default answer led with her background in B2C product. The role was enterprise B2B. When she swapped those emphases — leading with her one year of B2B experience rather than her five years of B2C — her callback rate went from one in six to one in three. Same person, different editorial choices.
For Career Changers
The Present-Past-Future framework needs a small adjustment when you're pivoting into a new field. The temptation is to be apologetic about what you're not. Resist it.
Instead, reframe your past as a foundation, not a liability. A teacher moving into corporate training says "I've spent six years designing learning experiences that have to work under real constraints — skeptical audiences, limited time, competing priorities. I'm moving into L&D because that challenge appeals to me at a different scale." The past isn't irrelevant. It's the argument.
Our guide to career change CV strategy covers the written version of this same principle — same logic applies to how you introduce yourself out loud.
The Length Problem
Ninety seconds is the target. Two minutes is the outer limit. Beyond that, you're testing attention and eating into the time they've set aside for substantive questions.
Practice out loud — not in your head, out loud — and time yourself. Most people's internal sense of "about two minutes" is actually three or four minutes when they speak. Your polished version should feel slightly too short when you deliver it. That's how you know it's right.
Common Mistakes
Starting with a job title and company without context. "I'm a senior manager at Accenture" tells an interviewer very little. "I'm a senior manager at Accenture where I lead a team of twelve that delivers digital transformation projects for retail clients" is a sentence.
Ending on the past. Many candidates trail off after describing their work history. The Forward-looking element — "and here's why I'm talking to you" — is the most important sentence for the interviewer. End there.
Using hedging language. "I've been kind of involved in..." or "I sort of work on..." signals uncertainty about your own value. Say what you did directly.
Over-rehearsing to the point of sounding scripted. Memorize the structure and the key facts, not the exact words. An answer that sounds mechanical is almost as bad as one that rambles.
Practice Method That Works
Write your answer out long — three or four paragraphs with everything you might include. Then edit it down to the best 150 words. Practice delivering those 150 words until you can do it conversationally without sounding like you're reading from your brain.
Then practice answering the question when you don't expect it. When your answer only works when you're warmed up and prepared, it's not ready. When you can deliver it clearly after being caught off guard, it's ready.
Before interviews, review the job description against your CV. If you're using MakeMyCV, the match analysis will show you which of your skills and experiences are most relevant to that specific role — useful input for deciding which highlights to lead with in your answer.
Frequently Asked Questions
How long should my answer to "Tell me about yourself" be?
60 to 90 seconds is ideal. Two minutes is the maximum. Beyond that, you're likely including information that doesn't serve the interview. Practice out loud and time it — most people underestimate how long they're speaking.
Should I mention personal details like hobbies or family?
Only if they're directly relevant to the role or specifically asked for. The question is a professional prompt. Personal information, unless it's genuinely unusual or directly relevant, uses up time that should go toward your professional case.
What if I don't have much experience?
Lead with what you do have: academic projects, internships, freelance work, relevant skills. The framework still applies — present what you're bringing now, the past experiences (academic or otherwise) that support your credibility, and why this specific opportunity fits where you want to go. Enthusiasm backed by specific evidence is compelling at any level.
How do I start my answer if I'm nervous?
Begin with a grounding sentence: your current role and where you work. It's factual, it's easy, and it gives you a moment to settle in before you move to the more substantive parts. "I'm currently a [role] at [company], where I..." is a perfectly solid first line.
Should I mention why I'm leaving my current job?
Not unless you're asked. "Tell me about yourself" is not an invitation to discuss your reasons for job searching. Save that for "Why are you looking to leave?" which is a separate question with its own answer.
Is it okay to reference the job description in my answer?
Absolutely. In fact, candidates who demonstrate that they've read the job description carefully — and whose self-description connects directly to what the role requires — stand out. "I noticed you're looking for someone who can own the full commercial relationship with enterprise clients, and that's been my primary focus for the past three years" is a powerful way to connect your answer to their needs.