Tell Me About Yourself: 90-Second Answer Formula + 3 Examples (2026)

Interview Fundamentals · Updated April 2026 · Reviewed by a former big-tech recruiter (12 years, 4 FAANG-adjacent companies)

"Tell me about yourself" is the most-asked interview question and the most-miswritten answer on the internet. Most candidates read their CV out loud for three minutes and wonder why the interviewer's pen stopped moving. The recruiter screen version, the hiring-manager version, and the onsite version all use the same question — but the scoring rubric is the same in all three.

This guide gives you the 90-second formula, three fully-written scripts at three seniority levels, and the delivery details that separate a candidate who sounds prepared from one who sounds rehearsed. For the STAR answers that come after the intro, read our behavioral interview guide.

Why this is the most-miswritten answer on the internet

Three failure modes dominate:

• The CV read-aloud. "I graduated from X in 2018, then joined Y as a software engineer for two years, then Z for three years, then…" The interviewer has your CV in front of them. They're not asking for it back.
• The life story. "I grew up in Portland and loved math as a kid…" Personal colour is fine in small amounts, but a 90-second answer can't afford it as the spine.
• The humble-ramble. "I'm not sure how to summarize myself, but I guess I'd say I'm passionate about learning…" The answer reveals more about your lack of preparation than about you.

The rubric scores three things: does the candidate sound like a coherent professional, does the answer name one or two specific wins, and does the answer land a reason they specifically want this specific role. All three in 90 seconds.

The present-past-future formula (breakdown)

Structure your answer in three beats. Each beat is roughly 30 seconds spoken — about 75 words.

Present (0:00–0:30). What you do now and what you're known for on the team. One sentence on role, one sentence on scope, one sentence with a single quantified win.

Past (0:30–1:00). The two experiences that shaped the path to today. Skip the laundry list; pick the two that show a coherent arc. One sentence each, each with a specific artifact, number, or outcome.

Future (1:00–1:30). Why this role specifically, and why now. One sentence that names something concrete about the team, product, or company (not "mission"), and one sentence that connects your skills to their gap.

Timing is the critical discipline. Most candidates underestimate how long their spoken answer runs by 40%. Practice with a stopwatch. If your Present beat ends at 0:45, you've lost 15 seconds from Future — and Future is where the answer actually sells you.

Example 1: new graduate (90-second script, annotated)

Context: interviewing for a software engineering new-grad role at a mid-sized B2B SaaS company.

[0:00–0:25] Present. "Hi — I'm Priya. I just finished my CS master's at UT Austin, specialising in distributed systems. Over the last year I've been leading the infra team for our university's student-run fintech, a 12-engineer group that processes small-dollar payments for about 800 students."

[0:25–0:55] Past. "Two experiences stand out on the way here. At my Stripe internship last summer, I shipped a bounded-retry library for our subscription-renewal service — the existing retries were unbounded and had caused a minor outage the month before — and it reduced failed-renewal pages by 40%. Before that, I led a course project on fault-tolerant consensus where we implemented Raft from scratch and demo'd it with a two-node partition test; the professor asked to use our test harness in next year's course."

[0:55–1:25] Future. "The reason I'm focused on B2B SaaS infra specifically is that the retry-library problem — where small primitive fixes compound into real reliability wins — is the shape of engineering I want to spend time on. Your public engineering blog post on the event-streaming migration hit a lot of those notes, which is why your platform team is the one I was most excited to apply to. The gap between 'student project' and 'production scale' is the one I want to close in a new-grad role, and this team looks like a strong place to do it."

[1:25–1:30] Close. "Happy to dig into any of that."

Total: 95 seconds spoken at normal pace. What scores: a specific role (fintech infra), a quantified win (40% reduction), an artifact other people adopted (test harness), a specific reason for the company (named engineering blog post), and a reason for the role (closing a specific skills gap).

Example 2: mid-level engineer (90-second script, annotated)

Context: interviewing for a Senior SWE role at a consumer startup after 4 years as a mid-level at a FAANG.

[0:00–0:25] Present. "I'm Marcus — for the past two years I've been a mid-level engineer on Google's ads-quality team, where I own the offline-evaluation pipeline for ranking model releases. That pipeline serves about 30 engineers across three teams and validated 14 production model launches last quarter."

[0:25–0:55] Past. "Before ads-quality I was on Search Infra at Google for two years — my main contribution there was a caching layer for query-rewriting that cut P99 latency by 22%. And before Google, I spent three years at a health-tech startup where I was one of six engineers and built the patient-record ingestion pipeline from zero to serving four hospital networks. I mention the startup specifically because that's the scope I'm looking to return to."

[0:55–1:25] Future. "Two things brought me to your team. First, your Series B is the scale where a senior engineer can still shape the platform instead of just extending it — the ad-quality pipeline work at Google has given me the evaluation rigor I'd want to bring, but the scope is narrower than what I want next. Second, your engineering leadership wrote publicly about splitting the monolith this year; the migration-at-scale work is exactly the technical problem I'd want to own."

[1:25–1:30] Close. "Glad to walk through any of that in depth."

Total: 95 seconds. Notice the shape: named scope at Google (30 engineers, 14 launches), a specific reason for leaving (narrower than wanted), and a specific reason for this company (monolith split, public write-up). No mission-worship; no generic "I'm excited about the culture."

Example 3: senior/staff or engineering manager (90-second script, annotated)

Context: interviewing for a Staff Engineer role at a Series C company after 10 years at progressively larger companies.

[0:00–0:25] Present. "I'm Dana — currently a Staff Engineer at Figma, where I lead the reliability platform team. We own incident response tooling, the error budget framework, and the new-service launch playbook. Over the last year I drove a rollout-safety programme that moved the company's deploy-incident rate from 1.4% to 0.3%."

[0:25–0:55] Past. "Before Figma I was a Senior at Stripe on the payments platform for three years, where I led the idempotency-layer consolidation — three legacy implementations merged into one. And before Stripe I was at a 20-person startup as employee 8, building the initial billing system. The arc I've been on is reliability engineering at progressively more interesting product surfaces."

[0:55–1:25] Future. "The specific reason I'm interested in your team is the dual-system migration your VP Eng described in the February talk — moving your event pipeline to a log-structured substrate while keeping the legacy system live. The rollout-safety work I've been leading at Figma is the closest thing I've done to that pattern, and the scope — cross-team migration, risk budget, incremental cutover — is exactly the shape of problem I want to spend the next two years on."

[1:25–1:30] Close. "Happy to go deeper on any piece."

Total: 95 seconds. Senior-level cues: named scope (reliability platform, 3 functions owned), a programme outcome (1.4% → 0.3%), a specific external signal (VP Eng's February talk), and a multi-year commitment framing (next two years).

The delivery details (tempo, breaths, where to land)

Beyond content, three delivery details make a visible difference:

• Tempo. Speak at ~150 words per minute. Faster reads as nervous; slower reads as uncertain. If your script is 220 words and you finish in 70 seconds, you're rushing.
• Breaths. Plan two natural breaths — one between Present and Past, one between Past and Future. Candidates who try to speak the full 90 seconds without a breath sound rehearsed and anxious.
• Landing the last sentence. The last sentence of your Future beat should land with finality. Practice ending with a falling pitch, not an upward-tilting "…and yeah". The small silence after you finish is a positive signal, not an awkward one.
• Eye contact and camera. On video interviews, look at the camera for the last sentence of each beat. Drift to the screen is fine during the middle of sentences; the beat-ends should be camera-locked.

What not to say

Eight patterns that tank the answer:

• "So, um, basically…"
• "Let me see, where do I start…"
• "I'm not sure what you want to know, but…"
• A chronological career narration ("Then in 2019 I moved to…")
• Generic mission-worship ("I'm really passionate about your mission to…")
• Personality abstractions without evidence ("I'm a team player, detail-oriented, hardworking")
• Salary, title, or location preferences (save these for the screen's back half)
• Apologies for anything (a career gap, a pivot, a demotion)

The last one matters particularly. If you have a career gap or unconventional path, name it in one sentence in the Past beat, give the reason, and move on. Apologising reads as flagging the issue before the interviewer would have raised it.

Frequently Asked Questions

How long should "Tell me about yourself" be?

90 seconds spoken, roughly 220 words. Under 60 seconds reads as under-prepared; over 120 seconds starts to lose the interviewer. Time yourself with a stopwatch because most candidates underestimate their spoken length by 30–40%.

Should I mention my education?

If you graduated within the last three years, yes — one line. After three years of full-time work, drop it from "Tell me about yourself" and let the CV speak for itself. The interviewer has it in front of them.

Do I use the same answer for a recruiter screen and a hiring manager?

Almost. The recruiter screen version weights the Future beat more heavily — recruiters are screening for fit and motivation. The hiring manager version weights the Past beat more — the manager wants to hear the specific shape of work you've done. Same 90-second shape, with the 10–15 second emphasis shifted.

What if my career path is non-linear?

Name the arc explicitly. "The thread through my roles has been infrastructure reliability — different companies, different stacks, same problem shape." That sentence turns what looks like career wandering into a coherent narrative in 12 words. Use it in the Past beat.

Should I mention hobbies or personal interests?

Only if they're genuinely relevant or memorable. "I also run a 500-person climbing club" can be a fine closer; "I like hiking and reading" is filler. If in doubt, leave it out — the Future beat is where the 15 seconds would be better spent.

Can I memorise the script word-for-word?

Memorise the structure and the three or four specific artifacts (numbers, named wins, named company signal). Don't memorise connecting prose — rehearsed sentences sound rehearsed. The scaffolding is repeatable; the connective tissue should come from you in the moment.

Keep reading

• The Behavioral Interview Guide: STAR, Stories, and How to Actually Win — the pillar guide
• Software Engineer Behavioral Interview: 30 Questions + STAR Examples
• Product Manager Interview Guide 2026
• Amazon Leadership Principles Interview Guide (2026)

Ready to run your Tell-Me-About-Yourself answer out loud with scored feedback on timing, structure, and specificity? Start a free trial — intro-round prompts with 90-second timer, filler-word tracking, and pacing analysis.