How to Answer 'Tell Me About Yourself'

'Tell me about yourself' is the first real question in almost every interview, and it is the one candidates get most wrong. It is not an invitation to recite your resume. It is a 60 to 90 second pitch that sets the frame for everything the interviewer asks next. Nail it and the rest of the conversation runs downhill. Fumble it and you spend the next 45 minutes clawing back credibility.

This guide gives you the exact formula recruiters at Google, Amazon, Stripe, and top consulting firms want to hear, plus five ready-to-adapt sample answers for different roles and career stages. It also shows how an AI interview assistant can rehearse it with you out loud so you sound confident, not scripted.

Why interviewers ask it (and what they're really scoring)

Interviewers open with this question for three reasons. It warms up the conversation. It tells them whether you can communicate under mild pressure. And it hands them a menu of topics they can drill into later. Your answer is scored on three axes: relevance to the role, clarity of structure, and signal that you have thought about why this specific job fits you now.

What they are not scoring: your birthplace, your childhood, your entire job history in chronological order, or a monologue about hobbies. Every second you spend on those is a second you did not spend proving fit.

The Present, Past, Future formula

The cleanest structure recruiters recommend, and the one that consistently outperforms every other template in mock interviews, is Present, Past, Future. Three beats, roughly 20 seconds each, ending with a bridge to the role you are interviewing for.

1. Present: your current role, one metric, and the type of work you are known for. This anchors the interviewer in who you are today.
2. Past: one or two career moves that led here, each tied to a concrete win. Skip the walk through every job. Pick the arc that matters for this role.
3. Future: why this company, this team, and this role are the logical next step. This is the sentence that tells them you are not spraying resumes.

The interviewer decides in the first 30 seconds whether they are excited to keep talking to you. Present, Past, Future gives you three chances to earn that decision instead of one.

Sample answer: software engineer

'I'm a senior backend engineer at Notion, where I lead the payments reliability squad. Over the last year we cut checkout error rate from 1.8 percent to 0.3 percent and shipped the migration from Stripe Checkout to a custom flow that lifted conversion 12 percent. Before Notion I spent four years at Shopify on the same problem space, which is where I fell in love with high-throughput distributed systems. I'm talking to your team because the infrastructure work on your ledger service is exactly the kind of gnarly correctness problem I want to spend the next five years on.'

Sample answer: product manager

'I'm a product manager at Ramp, currently leading the corporate cards surface. My team owns activation, and we moved 30-day activation from 41 percent to 62 percent this year by rebuilding the first-run experience around a single quick action. Before Ramp I was at Square for three years on the seller side, where I learned to ship into a business that already has real revenue on the line. I want to talk to you because your platform sits at the intersection of finance workflows and AI, and that is exactly the wedge I want to build the next chapter of my career around.'

Sample answer: sales / account executive

'I'm an enterprise AE at Gong covering the US Northeast. I closed 138 percent of quota last year with an average deal size of 92 thousand, and my two largest logos came from cold outbound. Before Gong I sold at Salesloft for three years, which is where I learned how to run a real multithreaded deal cycle. I'm interested in your team because you are selling into a category that is still being defined, and I get most excited when I have to teach the buyer, not just qualify them.'

Sample answer: new grad

'I just finished my computer science degree at the University of Michigan. My favorite project was a semester-long build with three classmates where we shipped a real-time collaborative code editor to 400 students on campus. I owned the operational transform layer, which taught me more about distributed systems than any class did. Before graduation I interned at Datadog on the logs team and shipped a query optimization that trimmed p95 latency by 22 percent. I'm applying here because the internship convinced me I want to spend the first years of my career on infrastructure at a company where reliability is the product.'

Sample answer: career switcher

'For the last six years I was a management consultant at Bain, most recently leading pricing engagements for SaaS clients. Two of those projects put me in the room with the product team every week, and I realized the decisions I cared about most were the ones product managers owned, not the ones on my slides. Over the last nine months I have been shipping side projects, taking Reforge, and running a small paid tool that has 900 users. I'm here because your PM role for the pricing surface is the exact overlap of where I have been and where I want to go.'

What to cut from your answer

• Your birthplace, your degree year, and your parents' jobs. None of it earns you a callback.
• The full chronological walkthrough of every role. Pick the arc, not the timeline.
• 'I'm a hard worker and a fast learner.' Every candidate says it. It reads as filler.
• Long lists of technologies or tools. Save those for the technical section.
• Hobbies, unless one of them is directly relevant to the role or genuinely memorable.

How to answer when you're unemployed or have a gap

Do not apologize and do not over-explain. Name it in one sentence, then pivot to what you did with the time. 'I left my role at Airbnb in March to care for a family member. Over the last five months I've kept shipping side projects and just wrapped a contract build for a fintech startup, which is how I stayed sharp on the problem space I want to come back to.' One sentence on the gap, one on the momentum. Move on.

Practice out loud, not on paper

Reading your answer silently will fool you into thinking it is ready. It is not. Say it out loud into your phone or a mock interview tool. Listen back once. You will hear filler words, run-on sentences, and the exact spot your energy drops. Fix those three things and re-record. Ten minutes of that beats an hour of rewriting the script.

An AI mock interview tool speeds this up because it asks the question in a real voice, times your answer, and gives you targeted feedback on structure, filler words, and pacing. If you have never rehearsed this question out loud, do that before the day of the interview, not during it.

Day-of checklist

1. Keep the answer between 60 and 90 seconds. Time it once the morning of the interview.
2. Open with your current role in one sentence. No preamble, no 'that's a great question'.
3. Include one specific number in the Past beat. Numbers stick, adjectives do not.
4. End with a sentence that names this company and this role. Generic endings kill the effect.
5. Take a breath before you start. The 20 seconds of silence you use to think reads as confidence.

What to do next

• Write your Present, Past, Future draft using one of the samples above as a scaffold.
• Run one AI mock interview with your draft so you feel the rhythm at real interview pace.
• Prepare a 30-second short version for phone screens and a 90-second long version for onsites.