Tell me about yourself
In one line
A 60-90 second pitch of present, past and future that explains who you are professionally and why this role is the logical next step.
What it is
'Tell me about yourself' is usually the first question in any interview. It is not a request for your life story or a reading of your CV. It is an invitation to give a short, focused professional pitch.
A good answer covers where you are now, the most relevant parts of your past, and why you want this specific role. It also sets the agenda: whatever you mention, the interviewer will likely ask about next.
Why interviewers ask
First impressions shape the rest of the interview. This question tests whether you can communicate clearly, pick out what is relevant, and connect your experience to the job. A confident, tailored answer makes the interviewer's job easier and steers the conversation toward your strengths.
How it works
- 1Present (about 20 seconds): your current role or situation, what you work on, and one concrete highlight.
- 2Past (about 30 seconds): two or three experiences that led here and are relevant to this job. Pick, do not list everything.
- 3Future (about 20 seconds): what you want next and why this role and company fit that. Mention something specific about them.
- 4Keep it to 60-90 seconds. Use numbers where they help (users, scale, team size).
- 5End with a clear handover, for example 'that is why I am excited about this role', so the interviewer knows you are done.
Worked example · A sample pitch for a backend engineer role at a fintech company
- Present: 'I am a backend engineer with three years of experience, currently at a logistics startup where I own the shipment tracking service. It handles about 2 million events a day, and last quarter I cut its p95 latency from 800 ms to 200 ms.'
- Past: 'I studied computer science and started in a QA automation role, which is where I got strict about testing. I moved to backend after building an internal tool that the whole QA team adopted. Since then I have worked mostly in Python and PostgreSQL on high-volume APIs.'
- Future: 'I am now looking for a team where correctness really matters at scale. Payments is exactly that, and I liked reading your engineering blog post on idempotent payment APIs, which is a problem I have handled on a smaller scale.'
- Handover: 'So that is why I applied, and I am happy to go deeper into any of that.'
- Why it works: about 75 seconds, relevant highlights with numbers, a clear story of growth, and a specific reason for this company. It also invites follow-ups on latency and idempotency, both strong topics for this candidate.
Picture it
It is the trailer for the film that is your interview: short, the best scenes only, and it leaves the audience wanting to see more of the parts you chose.
Key patterns
Present, past, future
When: The default structure for most candidates
How: Current role and highlight, the relevant path that led here, then why this role is next.
Past, present, future
When: Your career has a clear progression that tells the story best in time order
How: Start from where it began, move to now, end with why this role.
Hook first
When: You have one standout achievement relevant to the role
How: Open with it in one sentence, then give the short structured pitch.
Real-world use
Experienced engineer
Lead with your current scope and one impact number, then the career thread that leads to this role (for example, from monolith to microservices to platform work).
Fresh graduate
Present is your degree and strongest project or internship; past is what got you into the field; future is what you want to learn in this role.
Career switcher
Turn the switch into a strength: what your previous field taught you (domain knowledge, client handling) and the concrete steps you took to move into tech.
Returning after a gap
One honest sentence about the gap, then what you did to stay current (courses, projects) and why you are ready now. Do not over-explain.
In a project
You are applying to three different roles (a backend role, a data engineering role and a full-stack startup role) and need a tailored opening for each.
- Write one core pitch (present, past, future) of about 150 words.
- For each role, swap the past highlights to the two most relevant ones and rewrite the future part with something specific about that company.
- Time each version out loud; trim to under 90 seconds.
- Check that every item you mention is something you can talk about in depth for 5 minutes.
- Record yourself once and remove filler phrases and repeated words.
Impact: You open every interview confidently, interviewers follow up on the topics you chose, and you avoid the common failure of a 4-minute life story that loses attention.
Trade-offs
Use it when
- The opening question of almost any interview, including technical ones
- 'Walk me through your CV' or 'introduce yourself'
- Networking or recruiter calls, in an even shorter 30-second form
Avoid it when
- Personal details unrelated to the job (family, hometown) unless asked
- Reading your CV line by line; the interviewer already has it
- Going past 2 minutes; long answers signal poor prioritisation
Common mistakes
- Starting from school or childhood and narrating every job in order.
- Giving a generic pitch that never mentions this role or company.
- Mentioning projects you cannot discuss in depth, then struggling on follow-ups.
- Being too modest: no numbers, no achievements, just job titles.
- Not knowing when to stop and trailing off instead of handing back to the interviewer.
Interview questions
Quick revision
- 60-90 seconds, not a life story.
- Present, past, future: now, how you got here, why this role.
- One or two numbers make it memorable.
- Mention only what you can discuss in depth: it sets the follow-ups.
- Tailor the 'future' part to the company every time.
- End with a clear handover line.
Check yourself
1. What is the ideal length for a 'tell me about yourself' answer?
2. Which opening is strongest for a backend role?
3. Why should you only mention projects you know deeply?
4. What should the 'future' part of the pitch contain?
Saved on this device. Create a free account to keep it on every device.
Practise this with Sam
A real mock interview, out loud, with an honest scorecard. Free to start.