In this article
Before you start
Why interviewers ask this
A weak opening spends the only minute in which you choose the topic, and the interviewer then picks topics for you. The question is open on purpose: it does not say what to include, so the answer shows what you select, how you rank it and how clearly you speak. As the usual first question of a behavioral interview, how it is scored depends on the interview loop.
In a structured interview every candidate gets the same questions and a shared rating scale, which Google describes as "using the uniform methods to assess candidates applying for the same job" (Google re:Work, updated March 2026). In a looser conversation the opener simply steers what follows. A weak answer recites a life story; a strong one is a plan for the next ten minutes.
"Tell me about yourself" from first principles
- Opening pitch
- An opening pitch is a spoken summary of about one minute that tells an interviewer who you are professionally, which past work is relevant to the role, and why you want it, so the conversation starts on your strongest ground.
- Handle
- A handle is a specific, interesting detail left at the end of an answer that invites the interviewer to ask a follow-up about it, which lets you steer the next question.
In plain words
An opening pitch works like a film trailer. A trailer shows the best scenes, in a sensible order, and ends on a question that makes you want the film. Your answer does the same for your career. It is short. It is chosen for this audience. It ends on something to ask about. The analogy breaks in one place: a trailer may exaggerate, and your answer may not, because the interviewer will ask about every claim you make.
Stated precisely, the opening pitch is a present, past, future summary, tailored to the job description, of about one minute, that ends on a handle. A University of Houston career-centre post, republishing AngelList material, teaches the same order: your "present, past, and future career goals", tailored to the job, because "interviewers don't want to know your life story" (University of Houston Bauer career centre, February 2022).
Step 1: Present, say who you are professionally now
The present sentence names your current role, its scope and your strongest skill in one breath. Its input is your job today; its output is a single sentence the interviewer can repeat to a colleague. Include what you own, not only your title: "a backend engineer who owns the service that retries failed card charges" says more than "a software engineer". Leave out where you grew up, where you studied, your hobbies and pay; none of them helps this decision, and salary negotiation comes later in the process. This step takes about 40 words, or roughly 15 seconds. What you now know: the interviewer has a label and a scope for you.
Step 2: Past, choose two proof points that match the role
The past section gives two proof points chosen from your history because the role needs them, not because they are your most recent. The input is the job's top two or three skills from the posting; the output is two short stories of one or two sentences each, with a result in each. Start from the requirement and work backwards to your history, then drop everything that does not match, including impressive work that is irrelevant. A good proof point has an action, a number or an observable outcome, and no jargon the interviewer must decode. This step takes about 80 words, or roughly 30 seconds. What you now know: the interviewer has evidence, not adjectives.
Step 3: Future, and end on a handle
The future sentence says why this role is the next step, and its last clause leaves a handle. The input is something true about the role that you want; the output is one sentence that links your past to this job and points at a topic you can discuss well. Compare "I want to grow and learn" with "this role is about reliability at larger scale, and I would like to talk about how we got duplicate charges to near zero". The second names a reason and offers a question.
Choose a handle you can discuss for five minutes; interviewers often ask about the offered topic, but you cannot count on it. This is the rubric line of the question. A strong answer hands over a success to discuss. A Staff answer hands over a decision or an honest mistake, such as "a limit I set too low and what it cost", because that invites questions about judgement, not luck. What you now know: both levels end on a handle, and the Staff one picks a harder topic.
Step 4: Trim to a time budget
Trimming means cutting the draft until it fits about one minute when spoken aloud. The speaking-rate evidence comes from telephone conversations between strangers, not from interviews. In 2,438 English Switchboard conversations, Yuan, Liberman and Cieri (2006, section 2) measured 196 words per minute over the whole call and 236 once silences are excluded. Their turn-wise figure of 164 is lower because turn segments overlap, and they warn that segment-based rates need care.
One minute is therefore roughly 160 to 200 words, and 160 is the safer end for an answer you will say carefully. A 40, 80 and 40 split of present, past and future gives 160 words, or 49 to 59 seconds, computed in assets/data/tmay-timing.py.1 Read the draft aloud with a timer and cut the weakest sentence first.
Step-by-step description
- One sentence: current role, scope, strongest skill.
- Two proof points matched to the role, each with a result.
- Why this role, ending on a topic to ask about.
- Cut to about 160 words, 49 to 59 seconds.
- The present sentence takes about 40 words, the past section about 80 words and the future sentence about 40 words.
- A 160-word answer takes 49 to 59 seconds at 164 to 196 words per minute.
- The answer ends on a handle: a topic the interviewer can ask about next.
Two answers side by side
The difference between a weak and a strong opening is selection, not polish. Both examples are illustrative composites written for this page, for a backend engineering role: no real person, no named company. The full texts follow the table. The numbers are word counts and speaking time at 164 and 196 words per minute, computed in the script above.1 Read the table first. The strong sample is shorter and carries more evidence: each of its two proof points contains a result, and its last sentence offers a topic. The weak sample contains no result at all, and its last sentence offers nothing.
Text description of the diagram
- The weak sample answer is 255 words, 78 to 93 seconds at 164 to 196 words per minute.
- The strong sample answer is 152 words, 47 to 56 seconds at the same rates.
- One minute is roughly 160 to 200 words.
| Fact | Weak sample | Strong sample |
|---|---|---|
| Words | 255 | 152 |
| Seconds at 164 words per minute | 93 | 56 |
| Seconds at 196 words per minute | 78 | 47 |
| Proof points with a result | 0 | 2 |
| Ends on a handle | No | Yes, a success |
The weak sample, in full
The weak sample recites a life story, lists adjectives and ends without a handle.
The strong sample, in full
The strong sample states a present role, two proof points that fit the role, and a handle.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →The Staff-level answer
A Staff-level answer shows scope and judgement in the same minute, because the interviewer wants to know what you decide, not only what you do. It is still present, past, future, but each part is broader.
Tell me about yourself.
I lead reliability for a payments platform, which means I decide which failures we design out and which we only detect. Over the past six years I moved from building services to setting the standards other teams build to. Two things are relevant here. I introduced a retry policy with explicit limits that removed a whole class of duplicate charges, and I changed how we review incidents so the fix is a design change, not a reminder. I am interested in this role because reliability at larger scale means fewer, more costly trade-offs, and I would like to talk about one I got wrong.
What makes it Staff-level: it names a decision rule instead of a task list, it counts a change in how a team works as a result, and its handle is an honest mistake, which invites a deeper conversation than a success would. The same structure carries into leadership interviews and engineering management interviews, where the proof points are about teams.
The rubric
| Dimension | Weak answer | Strong answer | Staff answer |
|---|---|---|---|
| Selection | Whole career in order | Two role-matched proof points | Proof points chosen by a stated principle |
| Evidence | Adjectives ("hard worker") | An action and an outcome | A decision and its effect on other teams |
| Length | Past ninety seconds | About one minute | About one minute, no padding |
| Ending | "That is basically me" | Why this role, then a success to discuss | Why this role, then a decision or an honest mistake |
| Follow-up readiness | Surprised by questions | Can expand each claim | Has chosen the questions it invites |
Three variants of this question
"Walk me through your background."
The interviewer is asking for the same selection under a different wording, so use the same three parts with slightly more of the past. Keep to two proof points and do not narrate every job in order.
"Introduce yourself in thirty seconds."
Keep the present sentence and one proof point, then the handle. That is about 80 words, which takes 24 to 29 seconds at 164 to 196 words per minute.1 Say first that you can expand any part if asked, so the short version does not sound like a refusal to elaborate.
"What if my background does not match this role?"
Lead with the transferable proof point and say plainly what you are moving towards. Name the gap in one clause instead of hoping it goes unnoticed, because the interviewer has already read your résumé and will notice it.
Common mistakes
- Reciting a life story. (wrong) "I grew up in a small town and always liked computers." It spends time on facts that do not affect the decision. (right) Start from your present role; the behavioral interviews hub explains how openers connect to the questions that follow.
- Listing adjectives. (wrong) "I am a hard worker and a team player." Adjectives cannot be checked. (right) "I redesigned the retry logic and duplicate charges fell to near zero."
- Ending with "that is basically me." (wrong) It hands the next move back to the interviewer without direction. (right) Close on a handle: "I would like to talk about how we cut duplicate charges."
- Reading the same answer to every employer. (wrong) A generic pitch ignores the posting. (right) Swap the two proof points to match the top two requirements each time.
- Running past ninety seconds. (wrong) "Let me also tell you about my side projects, my hobbies and my dog." The weak sample runs 255 words, which is 78 to 93 seconds,1 and most of it is about none of the role's requirements. (right) Time yourself aloud and cut to about 160 words.
Follow-up questions
Tell me about yourself vs introduce yourself?
The two questions ask for the same thing in practice: a short, role-relevant summary. "Introduce yourself" is sometimes meant as only a name, role and one line, so give the present sentence first and offer to say more.
When asked "tell me about yourself" in an interview, what do you say first?
Say your present role and what you own, in one sentence: "I am a backend engineer on a payments team, where I own the service that retries failed card charges." Then move to the two proof points. Do not start with childhood, school or hobbies.
What is the best answer for "Tell me about yourself"?
No single text is best, because the best answer is chosen from this job's top requirements. The pattern that holds across roles is present, past, future, about a minute, ending on a handle; the Staff-level answer above shows one in full.
How can I explain myself in five words?
Five words are the label from your present sentence, for example "Backend engineer owning payments reliability". Use it as the headline of the first sentence, not as a replacement for the answer, because five words carry no proof point.
What if the interviewer asks you to take two minutes?
Two minutes is roughly 330 to 390 words at 164 to 196 words per minute.1 Spend the extra time on a third proof point or a deeper one, not on more history, and still finish on the handle. When the opener is over, the same habit of leaving one open topic is behind the questions you ask the interviewer.
What if the interviewer ignores your handle and asks about something else?
Answer the question that was asked. A handle is an offer, not a script, and nothing is lost: keep the topic ready for a later question such as "what are you proudest of?".
- Present, past, future, in that order, then stop.
- Choose two proof points from the job's requirements, not from your latest work.
- End on a handle you can discuss for five minutes; at Staff level make it a decision or an honest mistake.
- One minute of speech is roughly 160 to 200 words, so plan on about 160.
- Rehearse aloud with a timer; cut the weakest sentence first.
Sources
- A guide to structured interviewing for better hiring practices — Google re:Work, 31 Mar 2026
- Here's how to answer the "Tell me about yourself" interview question (republishing AngelList material) — University of Houston, Bauer College career centre, 22 Feb 2022
- Towards an Integrated Understanding of Speaking Rate in Conversation — Interspeech 2006 (Yuan, Liberman, Cieri; University of Pennsylvania), 17 Sep 2006
