It's the first question in almost every interview — asked in roughly 95% of job interviews across all roles and seniority levels. You've had your whole life to prepare for it. And yet most people walk in and still get it wrong.
Not because they're nervous. Because they've misunderstood what the question is actually asking.
"Tell me about yourself" is not an invitation to walk the interviewer through your CV. It's a test of one thing: can you figure out what's relevant to this role, and lead with it?
Here's how to do that.
What mistake do most candidates make with this question?
Picture the most common answer to this question. It starts somewhere around childhood, moves through school, hits the first job, the second job, the third — and eventually lands, breathless, in the present.
The interviewer already has your CV. They don't need a verbal re-run of it.
This is what recruiters call autobiography syndrome, and it's the fastest way to sound like every other candidate in the room. You haven't told them what makes you the right fit. You've told them everything, which is the same as telling them nothing.
The fix isn't complicated. It's structural.
What is the best formula for answering "Tell Me About Yourself"?
Your answer needs three things, in this order:
The whole thing should run between 60 and 90 seconds. For senior roles, up to two minutes. If you're going longer, you're including things that don't serve you.
What does a strong "Tell Me About Yourself" answer sound like?
Here's a worked example — a product manager interviewing at a tech company. Notice how every sentence earns its place.
"I'm a product manager currently focused on growth — specifically, how businesses use paid channels to reach new users. In my current role at Google I grew App campaign revenue by 26% over nine months by rebuilding the targeting approach from scratch. Before that I spent five years on the Search side, where I developed strong instincts around data and stakeholder management. I'm interested in this role because of the scale of the distribution problem you're working on — it's exactly the kind of complexity I want to be working on next."
That's it. Under 90 seconds. Three parts, clean landing.
What it does well:
- Opens with professional identity, not job history
- Quantifies the highlight (26%, nine months — not "I improved performance")
- Closes with a specific reason tied to this company's actual challenge
How should career changers answer this question?
Career changers have a specific problem with this question: their most recent experience isn't directly relevant to the role they're applying for.
Don't open with the role you're leaving. Open with who you're becoming.
You need a one-sentence bridge that connects your past to this role — before you say anything else. Something like: "I've spent five years in operations, and what's pulled me toward product is..." Then your highlights should lead with the transferable ones.
Whatever you do, don't pretend the unrelated experience doesn't exist. Acknowledge it, bridge it, and move on. In easedit.co sessions, the autobiography pattern — a chronological career walkthrough starting from the first job after university — shows up in the majority of first attempts. One rehearsal with the three-part formula almost always closes that gap: candidates find that naming the three components out loud makes the filtering instinct automatic.
What should you avoid?
The interviewer doesn't need the origin story unless you're making a specific point. Start with who you are now.
"I'm passionate about customer service" means nothing without a story attached to it. Every claim needs a fact behind it.
If you don't end with "why this role," the interviewer has to guess at your motivation. Don't make them guess.
What separates a good answer from a great one?
Most candidates prepare a single version of this answer and use it for every interview.
That's a mistake.
The "highlights" section should change based on the role. If you're applying for a sales role, your two highlights should be sales-adjacent. If it's operations, pick the accomplishment that shows you can run something at scale. The opening sentence and the closing sentence can stay mostly the same. The middle is where you do the tailoring.
Read the job description before every interview. Pick the two highlights that speak most directly to what they're actually hiring for. That's the difference between an answer that's competent and one that makes the interviewer think: this person actually understands what we need.
Before the interview ends, you'll almost certainly face your greatest weakness and why do you want this job — both follow the same principle: filter through what's relevant to this role, not what's most accurate about your general history.
The formula only works if you've practised saying it out loud. Reading it off the page and delivering it under pressure are two different things. At easedit.co, candidates rehearse this question with a voice AI interviewer that reads their actual CV and job description — so the feedback is specific to their background, not generic advice. Practise your answer — from $39, no data stored.