Tell me about yourself

The interviewer is not asking for your biography. They are opening a scorecard. Google's re:Work hiring research documents that structured interviews, where your answers are scored against a standardized rubric of role-relevant criteria rather than on gut feel, are more predictive of job performance than unstructured ones, which is why serious employers now run them (Google re:Work, accessed July 2026). So treat "tell me about yourself" as your one chance to put the first points on the board yourself, because whoever frames the opener frames the next forty minutes. Lead with two proof points that map to what this role actually needs and you have handed the interviewer evidence for the exact boxes they are there to check. March through your resume in chronological order and you have spent your best airtime on criteria nobody is grading.

Use the present-past-future structure, and keep the whole thing to sixty to ninety seconds. Present: one sentence on who you are professionally right now and what you do well. Past: two or three specific experiences or results that make you credible for this exact role, chosen from the job description, not your favorite memories. Future: why this role, this company, and why now. End by handing the conversation back, something like "so when I saw this opening, it lined up with exactly the kind of work I want to be doing." That closing line signals intent and stops you from trailing off.

Do not open with your employment gap or the fact that you were let go. This is not the question for that, and volunteering it here reads as anxious. If your current status is obvious from your resume and they probe, have one calm, neutral bridge ready, for example "my last role ended when the team was restructured, which is part of why I'm being deliberate about where I go next," and then steer straight back to why you fit. You control what this answer is about, and it should be about the value you bring, not the reason your last job ended. Save the full explanation for its own question, where you can handle it on purpose.

Write it down, then say it out loud and time it. A script that reads well in your head often runs long or sounds stiff spoken. Record a voice memo and score it against the mock-interview scorecard in Resources: did it land in 60 to 90 seconds, how many filler phrases slipped in ("basically," "kind of," "a little bit of everything"), and could a stranger hearing it name the two role criteria you were aiming at. You are not memorizing it word for word, which sounds robotic. You are learning the three beats well enough that you can hit them naturally even when your nerves spike.

• Write one present-tense sentence that names your professional identity: your function, your level, and the one thing you are genuinely good at.
• Open the target job description, pull its top three priorities, and pick one concrete result from your past that maps to each.
• Draft the full present-past-future script and read it aloud with a timer. Cut it until it lands between 60 and 90 seconds.
• Record a voice memo of the answer, listen once, and delete every filler word and hedge you hear.
• Write a single neutral bridge sentence about your current status in case they ask, then rehearse pivoting straight back to fit.

Before, a candidate opens chronologically: "So, I graduated in 2015, started as a coordinator, moved to a bigger team in 2018, and then, well, I was actually let go in March, so I've been looking for a few months now..." Three minutes in, the interviewer has a timeline and a gap but nothing about fit, and none of it maps to a single rubric line. After, three candidates in different functions each lead with two proof points pulled straight from the posting. Sales: "I'm an enterprise AE who's carried a $2M-plus quota, and what I do best is land and expand in healthcare accounts. Last year I closed the two largest new logos on my team and grew one of them threefold on renewal. This role is squarely that motion, which is why I reached out." Software engineer: "I'm a backend engineer focused on payments infrastructure. Most recently I rebuilt a reconciliation service that cut failed transactions by roughly a third and owned it on-call; before that I shipped the rate-limiter our whole platform runs on. Your posting is all about payments reliability at scale, so this lined up immediately." Marketing: "I'm a demand-gen manager who lives in the pipeline, not the brand deck. I built a lifecycle email program that drove about 30 percent of last year's sourced pipeline and ran paid acquisition across three channels. You're hiring for pipeline ownership, which is exactly the work I want to keep doing." Each runs 60 to 75 seconds, none mentions the exit, and every sentence feeds a criterion the interviewer is there to score.

• Starting chronologically at college or your first job and narrating the whole resume, which runs three-plus minutes and buries the point. Start in the present with one sentence about who you are professionally now, then pick only two or three past proof points that match this job description. Time it; cut until it lands between 60 and 90 seconds.
• Volunteering the firing or the gap inside this answer because it feels dishonest to leave it out. This is not the question for that. Prepare a one-line neutral bridge for if they ask directly, and keep this answer entirely about fit. You are choosing emphasis, not hiding anything.
• Memorizing the script word for word, so under nerves it comes out flat and robotic, or falls apart when you lose your place. Memorize the three beats (present, past, future), not the sentences. Rehearse out loud until you can hit the beats in slightly different words every time.