Tell me about yourself: how to answer, with timed examples

'How to answer "tell me about yourself" in 60 to 90 seconds: the word budget that fits, how to pick from the job posting, and four example answers by situation.'

"Tell me about yourself" sounds like an invitation to talk. It is closer to a word limit. Most advice says to keep the answer between 30 seconds and two minutes, and none of the ranking guides we read converts that into words, so people write 400 words, rehearse them fast, and believe they are under two minutes.

This post does the conversion, then shows what fits inside it: how many of the posting's requirements you can realistically reach, a structure that fits the budget, four complete answers with their word counts, and one weak answer rewritten. It also covers the 30 seconds before the question, and the two variants that interviewers use in its place: "walk me through your resume" and "tell me something that's not on your resume". For the rest of the interview, from research to the thank-you email, see our guide to preparing for a job interview.

How long your answer should be, in words

Aim for 60 to 90 seconds. That is long enough to say who you are, prove one thing and connect it to the job, and short enough that the interviewer gets the conversation back before their attention drifts.

Now the conversion. In a study of thousands of recorded English phone calls between strangers, Yuan, Liberman and Cieri (Interspeech 2006) found that the average speaking rate per conversation topic ran from 152 to nearly 170 words per minute. The same paper reports faster figures when the rate is measured over whole conversations: 193 words per minute on that corpus, and 196 on a second one.

We build the budget on the slow end, the per-topic figures, on purpose. If you talk faster than that, your answer comes in under time, which is the safe side to miss on. At the slow end:

• 60 seconds is about 150 to 170 words.
• 90 seconds is about 230 to 255 words.

For scale, this section up to this sentence is about 125 words, under a minute out loud. In the four example answers further down, the proof takes 50 to 65 words and the opening plus the link to the job take most of the rest. So a 60 to 90 second answer has room for one proof, maybe two. Every extra job, hobby or adjective comes out of that space.

Write your answer down and count it before you rehearse it. If it is past 250 words, it is past 90 seconds at the pace this budget assumes. A fast talker may squeeze it in, but the timer decides that, not how quick it feels when you say it in your head.

Pick two or three requirements from the posting

Nearly every guide says to tailor the answer to the job description. None of them says how much of the description an answer can reach. So we counted.

On 1 October 2026 we pulled 35 postings from the public Greenhouse job boards of seven employers (Airbnb, Stripe, GitLab, Duolingo, Figma, Dropbox and Reddit), five per company, with location duplicates removed. We counted the bullet points listed under qualification headings ("Requirements", "You have", "What you'll bring", "Nice to have") and left out responsibilities and benefits.

The count is conservative. One posting put its qualifications inside "What you'll do", and we counted only the three bullets under its own heading.

Trying to touch all nine produces the answer that sounds like a list of keywords. Choose instead:

1. Mark the requirements that appear in the posting's title, its first paragraph, or more than once. Those are what the hiring manager wrote first.
2. Of those, keep the ones you can prove with something you did, with a number or a named result.
3. Pick two or three. One goes into your proof sentence. The others can be named in one line ("you mention SQL and explaining numbers to non-analysts").

The requirements you leave out are not lost. They are what the rest of the interview is for, and you will prepare STAR stories for them separately.

A structure that fits the budget

The usual formula is present, past, future. It works, but "past" is where answers swell, because it invites a tour of every job. A version that fits 150 to 250 words:

1. Now. Your current role or situation, in one or two sentences.
2. Proof. One achievement that matches a requirement you picked, with a number.
3. Why here. The link between that proof and what this posting asks for, and what you want next.

The past still appears, but only when it explains the present or carries the proof. Graduates and career changers use it more. Senior candidates barely need it. Whatever proof you pick should also be on your resume, in the same words, so the interview confirms the document: see how to write an effective resume.

Example answers by situation

Each answer below was written for this article and counted with wc -w. At 150 to 170 words per minute, the slow end of the range above, each runs about 50 to 65 seconds, which leaves room for a pause or two and for the interviewer to come back in.

Recent graduate (156 words)

An internship counts as "now". The dissertation earns its sentence only because it supports the data requirement. Two requirements from the posting are named back in the interviewer's own words.

Career change (160 words)

A career changer's proof has to come from the old job but look like the new one. Naming the missing tool before the interviewer finds it costs one sentence and removes the obvious follow-up doubt.

Returning after a gap (145 words)

The gap gets three sentences: what, why, and that it is over. It sits in the middle, so the answer opens and closes on the work. The interviewer can ask more if they want to; most will not.

Senior or manager (157 words)

Eleven years of career fit in three sentences. The proof is a decision the candidate made, not only a result, because at this level the interviewer is hiring judgement.

Before and after: rewriting a weak answer

The weak version below is 92 words, so length is not its problem. It spends every one of them on the wrong things: a childhood location, three jobs with no detail, three adjectives, two hobbies, and a reason for applying that would fit any posting.

The rewrite is shorter and says more. "Very organised" became a calendar that cut missed deliveries. "Looked really interesting" became the posting's actual problem. At 69 words it runs under 30 seconds, which leaves room to add a second proof if the posting has a second requirement worth hitting.

The first 30 seconds, before the question

"Tell me about yourself" rarely comes first. There is a greeting, a line or two of small talk, and often a sentence from the interviewer about how the hour will run. Your introduction starts there, and it needs one sentence:

"Hi, I'm Sam Patel. Thanks for making the time. I'm here for the operations coordinator interview."

Say your full name clearly, at the pace you would use to spell it, so the interviewer hears how to pronounce it. Name the role, because a hiring manager with three openings may not know which one you are for. On a video call, say the same sentence when you join, then stop: the interviewer will steer to the first question.

You will read that delivery matters more than content. One ranking guide states that "an estimated 70% of communication is nonverbal", with no source given (BetterUp, checked 2026-10-05). The most quoted split of this kind is Albert Mehrabian's 7% words, 38% voice, 55% face, and Mehrabian's own page limits it: the equations "were derived from experiments dealing with communications of feelings and attitudes (i.e., like-dislike). Unless a communicator is talking about their feelings or attitudes, these equations are not applicable."

An interview answer is mostly facts about your work. So sit up, look at the camera and do not mumble, but do not spend your preparation on posture at the expense of the proof sentence. The interviewer remembers the number in your answer longer than your handshake.

"Walk me through your resume"

This variant asks for the same minute or two, with one difference: the interviewer has asked for the order of events. A thematic answer that jumps between jobs can sound like you are steering around part of the page. Two changes follow.

Tell it forward. Your resume lists the latest job first. Read aloud in that order, each sentence moves backwards and the story ends on your first job, far from the role you want. Start at the job or degree that explains the rest and finish on the current role, so the last thing you say leads straight into why you applied.

Budget per role, not per answer. The two guides we read that give a ceiling disagree. Harvard Business Review says to "deliver your answer in less than two minutes no matter how many jobs you've had", and The Muse quotes a former recruiter: "Avoid spending longer than five minutes responding to this question" (both checked 2026-10-05). Take the shorter one. Two minutes at 150 to 170 words per minute is 300 to 340 words. Keep one sentence to open and two to close on the posting, and three roles get up to about 80 words each, three or four sentences. The example below uses half that and still lands every move. A fourth or fifth role gets one sentence, or joins its neighbour ("before that, four years in retail management").

Here is a walk-through in that shape, 161 words over three roles:

Each role gets a reason for the next one ("that got me moved into"). That is what separates a walk-through from reading the page aloud. If one of your moves was a gap, give it the three sentences from the returning-after-a-gap example above, in its place on the timeline. Our post on explaining resume gaps has longer versions.

"Tell me something that's not on your resume"

This one asks for the part of you a resume has no field for. The test from the rest of this post still applies: pick something that shows a requirement from the posting, and tell it with a detail you could not have invented. A hobby, a side project or the way you work all qualify, as long as it does a job for this role.

There is a second filter that neither of the two ranking guides we read for this question (Indeed and The Muse) mentions. The U.S. Equal Employment Opportunity Commission tells employers what not to ask before an offer. Its guidance on pre-employment inquiries says that "inquiries about organizations, clubs, societies, and lodges of which an applicant may be a member or any other questions, which may indicate the applicant's race, sex, national origin, disability status, age, religion, color or ancestry if answered, should generally be avoided."

An open "tell me something" is exactly where candidates volunteer those facts: the church choir, the children's ages, the year they graduated, a health condition behind a sport. Nothing stops you from sharing them. But the interviewer has been told to steer clear of that information, and it uses up your minute without adding evidence for the job. Usually you can keep the skill and drop the detail:

The rewrite keeps the choir and drops what the EEOC lists. It also does what the first version never did: it names the requirement it answers.

When the interview is structured

Not every interview opens with this question. In a formally structured interview, every candidate gets the same questions in the same order and is rated on the same scale. The U.S. Office of Personnel Management's guide to structured interviews has the interviewer do the opening: a welcome, a short description of the job, an explanation of the process, and a chance for you to ask questions before it starts. There is no self-introduction in that script.

The same guide tells interviewers that documents a candidate brings, a resume included, are for the candidate's reference only and "should not be looked at by the interviewer during the interview". The UK Civil Service works in a similar spirit: its candidate guidance asks you to prepare examples of the behaviours listed in the job advert, because that is what gets assessed.

Two consequences:

• In a structured interview, put your preparation into evidence for the listed competencies. Keep a 60-second introduction ready anyway, in case the panel asks for one, but do not expect it to carry the interview.
• In a less formal interview, your answer may be the only version of your background the interviewer hears in the room. If they have not reread your resume since the screening call, what you say in that minute is what they work from.

What to leave out

A personal detail is fine when it does work. A hobby that shows the skill the job needs (you run a 200-member running club and the role is community management) belongs. A hobby that just makes you likeable is a sentence you could have spent on proof.

Practising without memorising

Recite a script word for word and you will sound like you are reading. Improvise it and you will run long. The middle way:

1. Write the answer out in full once and count the words.
2. Reduce it to three lines of notes: the role, the proof with its number, the link to the posting.
3. Say it out loud from the notes with a timer running. Do it three times, and record the last one.
4. Listen back for the first sentence that adds nothing and cut it.

If the recording comes in past 90 seconds, you have too much past, not too little speed. Cut a job, not your pauses.

Prepare a short version too. Some interviewers ask "briefly, tell me about yourself" or "walk me through your resume in a minute". The rewrite above shows that 70 words with one proof already makes a full answer.

Preparing the answer for a specific posting in HiredFolio

The answer changes with every posting, because the requirements you pick change. HiredFolio keeps each job's saved description in the job's page, next to what you made for it. The application assets panel lists the resumes you tailored from that job, and when a tailoring report exists, it shows how many of the posting's requirements the resume matched (for example "Requirements matched: 7/9"). The ones it matched are your shortlist for the proof sentence.

On the same page, "Prepare for the interview" reads the saved description and a resume you choose, then returns the questions most likely for that role with STAR answers built only from what the resume contains. When the resume has no evidence for a question, it says so and leaves that answer for you to write. It costs one AI action, and it needs a saved job description to run. It does not write your "tell me about yourself" answer for you; it gives you the evidence to build it from.

Save a job and prepare for its interview in HiredFolio

Read next

• Why do you want to work here? How to answer with what the job posting doesn't say

  'How to answer "why do you want to work here": find company details others miss, see a worked example from an annual report, and read five sample answers.'

• Why should we hire you? How to answer, with 5 example answers

  'How to answer "why should we hire you": three proofs from the job posting, a 150-word budget, and example answers based on real job postings.'

• What are your salary expectations? How to answer on the form and the call

  'How to answer "what are your salary expectations" on an application form and a recruiter screen, with scripts, the state laws that apply, and a count of 243 real application forms.'