It's the first question of almost every interview. It sounds open-ended. It looks like a warm-up. It is neither.

"Tell me about yourself" is doing real work: the interviewer is calibrating how clearly you talk about your own work, how long your answers will be, what you choose to emphasize, and which of your experiences you think maps to the role. The answer they hear in the first 90 seconds shapes how they listen to everything you say afterward.

Most candidates ramble for three minutes when they should have spent 90 seconds. This post is the structure that fixes that.

The four moves

A working answer has four parts, in this order: anchor, proof, bridge, handoff. Each one is short. The whole answer lands at 80-100 seconds when you say it out loud at a normal pace.

Anchor (15 seconds). Start with where you are. One sentence: current role, current company, what you focus on. The reason to start here — not with school or your origin story — is that the interviewer has roughly 90 seconds of attention to allocate, and the part they care most about is your most recent work. Don't make them wait.

Proof (35 seconds). Pick one project that maps to the job you're interviewing for. Describe the problem, what you specifically did, and a concrete outcome. This is the texture the interviewer can't get from your resume — the decision you made, the tradeoff, the result. It should be one project, not a tour. Specificity beats coverage.

Bridge (25 seconds). One or two sentences connecting your trajectory to this specific role. "I've been moving from team-scope work toward platform-scope work, which is part of why this role caught my attention." Don't say "I'm passionate about X" — that's the default and it reads as the default.

Handoff (15 seconds). End decisively. "Happy to go deeper on any of that, but those are the headlines." This does two things: it tells the interviewer the answer is over (no awkward "...and yeah, that's me"), and it signals that you know how long the answer should be.

What rambling sounds like

A useful exercise: record yourself answering this question once. Most people are surprised by what they hear.

The common failure modes are predictable. Starting with your origin story ("So I grew up in..."). Walking through every role chronologically. Spending four minutes total and then trailing off. Mentioning six projects without going deep on any of them. Failing to connect back to the role being interviewed.

The structured version is the inverse. It starts with your current role. It picks one project. It lands in the 80-100 second window. It goes deep on one specific decision. And it bridges explicitly to the role.

Why 90 seconds is the right length

The length isn't arbitrary. Under 60 seconds reads as unprepared or evasive. Over 2 minutes reads as undisciplined — the interviewer is implicitly tracking how long you'll talk when given the chance, and a four-minute TMAY tells them every other answer will be twice as long as it should be.

The 90-second window also matches how the interviewer is calibrating their note-taking. They're listening for three to five facts to anchor follow-up questions on. Give them too few and they have nothing to ask about; give them too many and the follow-ups are scattered. The structured answer hands them one strong project to ask about next, which lets you steer the interview onto territory where you have depth.

What this isn't

A few clarifications:

• It's not the same answer for every interview. The proof point and bridge change per role. Practice the structure once, then swap the proof project to match the JD.
• It's not memorized verbatim. Memorizing kills it. The four parts should be internalized as moves, not as a script.
• It's not where your weaknesses go. TMAY is not the time to volunteer that you got fired or have a gap. The interviewer will ask about those separately. See how-to-talk-about-getting-fired for that conversation.

For the larger phone-screen prep, see phone-screen-what-recruiters-evaluate. For the bullet-rewriting work that backs the "proof" section, see achievements-vs-responsibilities.

The short version: anchor, proof, bridge, handoff. 90 seconds. Practice once out loud, not silently. The first answer of the interview is the only one where the interviewer hands you uninterrupted time — don't waste it on chronology.