Keep it about the work. Your answer to "Tell me about yourself" is a short professional pitch, not a biography.
Harvard FAS Career Services reports that 93% of hiring managers ask some version of the question, and it usually opens the phone screen, the video call, or the on-site visit. Your job is simple.
Make the next 90 seconds easy for them.
This answer is never about your personal life. University of Arizona career coaches are blunt about scope. It's about who you are as a professional, and most people can cover that ground in 30 to 90 seconds. Even executives should stay under two minutes. Don't improvise the whole thing on the call.
So why do strong candidates still freeze?
They try to recap every job. That sounds unfocused. Pick the through-line that makes this role the obvious next step, then stop.
Build a past, present, future answer
The interviewer can follow it without taking notes if you walk through how you got here, what you do now, and what you want next. Harvard's career office suggests that split. Eller's counselors use it too.
Thing is, the order can flex. Lead with your current work if it maps to the posting. Start with the past that explains the shift if you're changing fields.
One result beats five job titles.
Write it in this order, then trim:
- Anchor in one sentence: your current role or situation, plus the skill this job actually needs.
- Proof in two sentences: one or two relevant experiences, each with a result you can name.
- Fit in one sentence: why this role, tied to the team, product, or problem. Not a vague "I'm excited."
You're listing if you run past 90 seconds. Cut hobbies, childhood, and the full resume chronology. Save the detail for follow-ups, where the real probing happens.
A three-word label can sit in your first line only if you prove it right away. "I'm a collaborative operations lead" means nothing until you say what you shipped.
Four sentences is the whole pitch. Anchor, proof, proof, fit. Stop there.
Sample scripts by career stage
Steal the shape, not the facts. Swap in your numbers.
| Stage | What to emphasize | Sample opening |
|---|---|---|
| Entry-level or new grad | Studies, internships, projects, and why this field | "I just finished a degree in information systems and spent last summer with a hospital IT team during a software rollout. I want a support role where I can keep learning systems that affect daily operations." |
| Mid-level | Recent results and the problem you like solving | "I'm an account executive in B2B software. I've owned mid-market books for several years, and in my current role I manage a large account list and stay above quota. The work I care about is the product users touch every day, which is why your scale stood out." |
| Manager or executive | Scope, team, and a business outcome | "I'm a software engineering manager with eight years in payments. Most recently I led a team of 12 on infrastructure work. The thread in my career has been early-stage and scale-up problems, and that's the work I want to keep doing." |
You'll sound stiff if you read it like a teleprompter.
Entry-level answers should start near graduation, or at the internship that pulled you into the field. Skip high school. It's older history than they need. You undercut yourself if you stretch past two minutes.
Name a layoff in one clause and move straight to the work. Don't hide it. Don't dwell on it either.
Look at what the samples share. Each one names a role, one proof point, and a reason this job is next. None of them tours the whole career. That's the whole trick.
The mid-level sample stays on recent results and the problem the person likes solving. The manager sample stays on scope, team, and a business outcome. Neither one walks the interviewer through every title on the page.
Use STAR when they ask you to prove it
"Tell me about yourself" is just the opener. Behavioral questions come next.
MIT Career Advising & Professional Development treats past behavior as a predictor of future results, which means they want a story, not a trait. Prep 3 to 5 stories. Outline them. Don't memorize a speech.
STAR is simple once you see the proportions. Situation sets context, about 20% of the story, and they don't need every detail. Task is the goal you owned. Action is the bulk, around 60%. Result stays brief, roughly 10%, and concrete.
Say what you did. Use "I," not "we." University of Cincinnati career staff make the same point. Interviewers can't hire your old team.
Rebuild this sketch with your own work. Situation: handoffs were messy and the team kept slipping. Task: raise collaboration before a hard deadline. Action: you ran anonymous feedback, set a weekly working session, and wrote one shared checklist. Result: the project shipped on time.
Fill that skeleton with your facts. A number helps. A before-and-after works too if you don't have a clean percentage.
The situation should be short. The action should carry the story. The result should land and then you should shut up.
Practice until each story has a beginning, middle, and end. Then stop talking. Let them ask the follow-up.
Those 3 to 5 outlines sit behind the pitch. You mention a result in the opener. You tell the STAR story when they ask you to prove it.
What to cut so you don't sound rehearsed
Hometowns, employer-by-employer tours, and the fight you had with a former manager all belong off this answer.
A rambling version sounds like this: "Well, I grew up in Ohio, then I bounced around a bit, and there was this time I disagreed with leadership..." It never lands. Tighten it: "In two and a half years I analyzed large client datasets and proposed a process change that cut cycle time." Then wait.
"Detail-oriented" and "hard-working" vanish unless you attach a result. Generic adjectives are the other trap. If you built a quality check that caught errors, say that. If you didn't, pick a different word.
To be honest, people also, and this is the part that trips folks who otherwise have a strong resume, try to sound impressive by stacking every tool they've ever touched instead of naming the one problem they solved that maps to the posting, which means the interviewer hears a catalog and not a person.
Read the job again. Pull two requirements. Make sure your opener hits both.
They already have your resume. Resist reciting it word for word. The spoken version should add judgment: what you chose to work on, and why it matters here.
U.S. interviews still reward direct, achievement-focused answers. Lead with the work. Save the personal origin story for later, if they ask.
Rehearse out loud, then match it to your resume
You will not get better by rereading notes silently. Say it out loud. You have to say it out loud, not stare at the page. Time it. Record a take on your phone.
Some job seekers use AI interview coaches to catch filler words and pacing. Yoodli is one roleplay option people use for that drill. Treat any score it spits out as practice, not a hiring prediction. Google Interview Warmup is gone; the old Grow with Google pages no longer host the tool. Don't waste a search on it.
Open your resume and your pitch side by side. If the intro claims a result that isn't on the page, either add it to the resume (if it's true) or drop it from the speech. Applicant tracking systems and human screeners both notice when the story and the document disagree. A LinkedIn profile with different dates or titles will undercut you too. Fix that before you apply.
Do this once, in order:
- Highlight two requirements on the job post.
- Write the four-sentence pitch on paper.
- Attach one STAR story to the result you mentioned.
- Say it out loud and cut until it's under 90 seconds.
- Record one take, then answer a follow-up without stopping the camera.
- Watch it once for eye contact and filler, not for perfection.
Keep the pitch and the resume in the same voice. If your resume tools spit out a keyword-stuffed summary, don't read that summary in the interview. Translate it into speech.
The spoken version has to match the document a screener already loaded into an ATS. Dates, titles, and named results need to agree. If they don't, fix the file first.
Remote calls need fewer tricks than people think
Put the camera at eye level. Look at the lens when you hit your result line. Test audio before they join.
Phone screens run shorter, so aim closer to 60 seconds. You don't get nods on a call. Land the fit sentence, then pause.
Turns out the script itself barely changes from video to a conference room. Don't add a childhood tour because you're nervous. Same pitch. Same stop point.
A thank-you note still helps when it's specific. Mention one thing they asked about, not a template paragraph.
FAQ
How long should "Tell me about yourself" be? Thirty to 90 seconds covers most U.S. interviews. Stay under two minutes even for senior roles.
What if they ask for strengths and weaknesses in the same conversation? Reuse a strength you already proved in the opener. For the weakness, name a real one and the system you use now. Skip "I care too much."
Should the pitch change for a remote job? The story doesn't. Delivery does. Camera height, a quiet room, and a tighter 60-second version for phone screens.
Write those four sentences tonight. Time them once. Stop when the timer hits 90 seconds.