The classic three-part structure works:
- Where you've been — 2-3 sentences on your career so far.
- Where you are now — 2-3 sentences on your current role and what you're known for.
- Why you want this role — 1-2 sentences on the connection to the role you're interviewing for.
90 seconds total.
Template
"I started my career [where, doing what — 1 sentence]. After that, I spent [time period] at [Company] focused on [main area / outcome]. For the last [time period], I've been at [Company] working on [current role / focus]. I'm known for [one specific strength]. I'm interested in this role because [connection to the role you're interviewing for]."
Example
"I started my career at GammaTech as a backend engineer, mostly working on data infra. After three years there, I moved to Acme to lead a small team rebuilding their pricing engine — that's where I learned how to ship distributed systems under real-time SLAs. For the last two years, I've been at BetaCo, where I'm a tech lead on the platform team. I'm known for shipping reliable systems under tight deadlines. I'm interested in this role because the work you've described in the JD — building a real-time event processing system at scale — is the same kind of problem I've been working on for the last five years."
That's about 90 seconds. Concrete, scoped, ends with a connection to the role.
What to skip
- Childhood / where you went to high school. Save it for casual chat.
- Resume recitation. They have the resume.
- Long personal backstory. Brief is fine; long is filler.
- Negativity about your current role. "I'm leaving because they don't appreciate me" — never.
- Hedging language. "I'm not sure if you want me to start with..." — just start.
What to include
- A through-line. Your career should sound like a story, not a list.
- One specific strength. "I'm known for X" — concrete.
- A connection to this role. End with why this role specifically.
Adapting per company
You don't need 5 different versions, but lightly tune the through-line:
- Tech: lead with technical scope and projects.
- Finance: lead with quantitative results and rigor.
- Sales: lead with quota attainment and deal sizes.
- Marketing: lead with metrics moved (CAC, ROAS, growth).
Common mistakes
- Going over 2 minutes. Pad-detector goes off.
- Using "passionate" 4 times. Cut all of them.
- Listing every job. Pick the throughline.
- Forgetting to end with the role. The connection is the point.
Practice this one
"Tell me about yourself" gets asked at every first-round interview. Practice it out loud until you can deliver it cleanly without notes. Time yourself.
The bigger pattern
A clean 90-second answer to "tell me about yourself" sets the tone for the whole interview. It's worth practicing.
Sorce gets you the interviews — 40 free swipes a day, AI agent applies.
For more: how to ace an interview, how to prepare for a job interview, STAR method for interviews.
Frequently Asked Questions
- How long should the answer be?
- 90 seconds. Long enough to set up your story; short enough that the interviewer can ask a follow-up.
- Should I cover personal stuff?
- Mostly no — keep it professional. A brief personal note at the start is fine ('I'm based in [city] and originally from [place]') but the bulk should be career.
- What's the biggest mistake here?
- Reciting the resume. The interviewer has the resume; they're asking for a story, not a list.
- Should I mention why I'm leaving my current role?
- Optional and usually save it for the 'why are you looking?' question. Don't anchor your answer in negativity about the current role.