Tell me about yourself, in ninety seconds

Ninety seconds is shorter than you think

At a normal speaking pace, ninety seconds is about two hundred and twenty words, roughly three short paragraphs. That's the real budget for "tell me about yourself," and almost every answer that goes wrong goes wrong by running past it. The question is not an invitation to narrate your resume from your first job onward. It's an opening statement, and like any opening statement it works best with a shape: what you do now, the thread that got you here, and why this role is next. Say those three things, in that order, and stop.

The three part shape

Start in the present tense, with your current role and the part of it most relevant to the job you're interviewing for, not your whole title and every duty attached to it. If the posting you applied to is heavy on cross-functional work with Product, open with the version of your current job that leads with that, not the version that leads with team size or tenure.

Move to the past, but only far enough to explain the thread, not the whole timeline. This is where people go wrong most often: they either skip it and jump straight from "here's my current job" to "and that's why I want this role," which sounds thin, or they narrate every job on the resume in order, which spends the whole ninety second budget before the answer gets anywhere. One sentence, sometimes two, connecting two or three roles with a line that shows direction: you moved from execution into ownership, or from a generalist role into a specialty, or from one industry into an adjacent one on purpose.

End in the future, specifically this role. Not "I'm looking for my next challenge," which answers nothing, but a sentence built from the posting's own language. If it says the role owns renewals for a defined book of accounts, say you want to move from influencing renewals to owning them outright. This is the sentence that should make the interviewer's next question obvious, which is the actual goal of the whole answer.

A full example, timed

Here's what that sounds like assembled, for a candidate moving from a generalist customer success role toward the Senior Customer Success Manager posting referenced throughout this prep. Read it out loud once. It runs close to ninety seconds:

"Right now I manage a shared book of accounts on a team of five, and the part of that I've leaned into most is expansion: finding the accounts that are ready to grow and building the case for it with Product and Sales. Before this I spent three years in a support role, which is where I learned to read an account's health before it shows up in a dashboard, and that's carried straight through into how I manage renewals now. What I'm looking for next is a role where I own a defined book end to end rather than sharing one, which is exactly how this position is scoped, and where the roadmap conversations I've been having informally become part of the actual job."

That's three moves, no more, and it ends on a sentence the interviewer can respond to directly.

Adjusting the length for who's asking

The ninety second version is built for a first real interview, but the question shows up earlier too, often in a shorter form. On a recruiter screen, the same three part shape works at closer to thirty seconds: present and future stay almost the same, and the past section shrinks to a half sentence or disappears entirely, since a recruiter is mainly checking that your background is in the right neighborhood, not evaluating the story of how you got there. Save the fuller version for someone who's actually deciding whether to move you forward.

In a panel or group setting, where you might be asked to introduce yourself to three or four people at once, the same ninety seconds still works, but it's worth adding one sentence up front naming what you're covering: "I'll give you the quick version of my background and then I'm happy to go deeper on anything." That sentence does nothing on its own, but it signals to a room that you're aware of their time, which a group interview rewards more than a one on one does.

What doesn't change across any version is the order: present, past, future. Compressing the answer means cutting detail inside each part, not dropping a part entirely or reordering it.

What to cut

Cut anything that doesn't serve one of the three parts. Hobbies, where you grew up, your degree if it isn't doing real work in the answer: all of it belongs in small talk before the call starts, not inside the ninety seconds. Cut apologies too. "Sorry, I'm not great at these questions" or "let me think about how to say this" both spend time you don't have and plant a doubt you didn't need to plant. If you need a second to think, take it silently. A short pause reads as composed. A narrated pause reads as unprepared.

Cut the instinct to cover every job on your resume out of fairness to your own history. The interviewer already has the resume. This answer isn't a summary of it, it's a filter on it: which parts matter for the conversation you're about to have.

Ending on a question, not a period

The best version of this answer ends on a sentence that sets up what you want asked next. End with "...which is why I'm excited about this role" and the interviewer has to invent their own follow up. End with a specific claim, like moving from a shared book to a defined one, and the natural next question is about that exact transition, so now you're talking about something you prepared for on purpose rather than something they picked at random. Treat the last sentence as a lever, not a wrap up.

Practice this out loud, not silently. Silent practice hides the sentences that read fine and sound awkward, and "tell me about yourself" is entirely a spoken performance. Time yourself once. If you're running past two minutes, the past section is almost always the part that's too long, so cut there first.

This answer sets up everything that follows, and a shorter version of it is usually the very first thing asked on a recruiter screen too, so it's worth having ready before that call, not only before the onsite. It's worth revisiting once you've looked closely at the posting itself, and it pairs directly with how you deliver behavioral answers later in the same conversation, since both draw on the same short list of stories.

iapplyai.app drafts a version of this opening answer automatically, built from your actual resume and scored against the specific posting, so the three part shape above starts already filled in rather than blank.