Why this question matters
Tell me about yourself is the first question in nearly every interview. Interviewers use it to set tempo, check your communication range, and see whether you can self-edit. Get it right and the next 45 minutes feel friendly. Get it wrong with a 3-minute autobiography and you spend the rest of the round winning back attention you already lost.
The answer is a signal, not a monologue. A strong one tells the interviewer in about 90 seconds: where you are now, what you have done that matters, and why you are in this room specifically. Everything else you could say is better saved for a follow-up question, because the interviewer will ask if they are curious.
The 3-part present-past-future formula
Order matters. Starting with Past drags the energy down. Starting with Present and pivoting back to Past keeps momentum. Starting with Future feels forced. The interviewer should finish listening and think: this person knows where they are, what they have done, and why they are here.
How long should your answer be?
Target 60 to 90 seconds. Under 45 seconds reads as low-effort. Over 120 seconds reads as poorly edited. At 150 seconds most interviewers have stopped tracking and are waiting for you to finish. Practise with a phone voice-recorder. Time yourself. Cut anything that is not directly earning your next follow-up question.
One exception: if the interviewer says "take your time, I want the full picture", you have permission to go 2 to 3 minutes. Default to 90 seconds unless invited to expand.
10 examples by career stage
Each shows a weak version first (what most candidates default to), then a strong rewrite using the 3-part formula. Read the strong version aloud. Time it. Note where the momentum lives.
Fresher / Entry-level
Weak
I am a recent CSE graduate from VIT. I am hardworking, a team player, and eager to learn new technologies. I have done projects in Java and Python and I am looking for an opportunity to grow.
Strong
I am a CSE graduate from VIT Vellore, class of 2025, with a 8.6 CGPA. For my final-year project I built a face-recognition attendance system in Python that hit 94 percent accuracy across a 60-student class, and it ended up winning the Best Project award in our department. My summer internship at a Bangalore fintech had me shipping a REST API that now handles 12k daily requests. I am here today because the Backend Engineer role pairs exactly with what I already enjoy building, and the team you described runs the stack I know best.
Early career (1 to 3 years)
Weak
I have 2 years of experience as a software engineer at TCS. I work on Java backend services and have good communication skills. I am looking for a change for better opportunities.
Strong
I am a backend engineer 2.5 years into my first role at TCS, working on a Java Spring Boot service inside a large retail-banking client. My biggest ship this year was a reconciliation job that used to run 45 minutes every night and now runs in under 6 after I moved it to parallel batches. I am at the point where I want to move from client services to product-scale problems, which is why your Staff Backend role caught my attention, especially the line about payments reconciliation.
Mid-career (4 to 7 years)
Weak
I have 6 years of experience in marketing. I have worked in both B2B and B2C sectors. I have handled campaigns, SEO, and performance marketing. I am looking for a leadership role.
Strong
I am a growth marketer 6 years in, currently running paid acquisition at FinEdge where I scaled monthly spend from 4 lakhs to 42 lakhs at a steady 4.8x ROAS and contributed 2.4 crore in pipeline. Before this I ran lifecycle at a D2C brand through their Series A. The reason I am interviewing is that I am hitting the ceiling of what solo contribution can drive; I want to build and mentor a team, which is exactly the charter of this Head of Growth role.
Senior IC (8 to 12 years)
Weak
I am a Staff Engineer with over 10 years of experience. I have worked at large companies and startups. I have strong technical skills and mentoring abilities.
Strong
I am a Staff Backend Engineer at Razorpay, 10 years in, and I own payments reconciliation across our 18 million merchants. The ship I am proudest of this year was moving our monolithic settlement service into 14 services on EKS, which cut deploy time from 45 minutes to 4. Beyond the code I have been mentoring 5 Senior Engineers through promotion cycles. I am exploring staff-plus roles in climate tech because I want my next 10 years of compounding to land on a problem that matters.
Manager
Weak
I have 8 years of experience including 4 as an Engineering Manager. I have managed teams of 10 to 15 engineers. I believe in coaching and driving outcomes.
Strong
I am an Engineering Manager at Flipkart Grocery, 4 years into people-management after 4 years as an IC. Today I run a 32-person org across 5 squads. The metric I am proudest of is Q4 OKR completion; we landed 91 percent on-time after I restructured our planning cadence from a 61 percent baseline. I hired 17 engineers and promoted 8 in that time. I am here because your Director role takes this same problem one layer up, and the org chart you walked me through feels like the right stretch.
Career changer
Weak
I was working in investment banking for 5 years. Now I am transitioning to machine learning. I have been learning online and doing some projects.
Strong
I spent the first 5 years of my career at Morgan Stanley on the M&A desk, and 14 months ago I pivoted full-time into machine learning. Since then I have shipped 3 production ML models on AWS SageMaker, one for fraud detection and two for KYC risk scoring, while consulting for two fintech startups. I am targeting MLE roles where my finance-domain knowledge is a plus, not baggage, and your risk-modelling team is the exact intersection I have been aiming for.
Returning after career break
Weak
I took a 2-year break for family reasons. Before that I was a product manager at Swiggy. I am now ready to return to work.
Strong
I am a senior product manager returning after a 22-month caregiving break. Before the break I ran the reorder flow at Swiggy Instamart and took it from 14 to 32 percent reorder rate. During the break I used my bandwidth to complete Reforge Growth, ship 2 side projects, one of them at 3k DAU, and mentor 4 early-stage founders through YC-style diligence. I picked this role because it pairs the scale I had at Swiggy with the early-stage ambiguity I got good at during my side projects.
Laid-off / between roles
Weak
I was recently laid off from my previous company. I am looking for a new opportunity to utilise my experience and skills.
Strong
I was a Senior Product Designer at Twitter for 4 years, part of the Nov 2023 layoff cohort. My last big ship there was the Spaces post-launch work, where I grew DAU 3.2x over 18 months. Since the layoff, I have been using the time intentionally, shipped a SaaS side project that now has 1,200 signups, and taken 2 consulting engagements. I am ready to go back to a large-scale product challenge, which is exactly what the Principal Designer role is.
Senior executive
Weak
I am a senior executive with 15 years of experience. I have led teams and driven strategic initiatives at multiple companies.
Strong
I spent the last 4 years as COO at Neobank-X scaling the company from 180 to 1,100 people across India, UAE, Singapore, and Indonesia. Revenue grew from 40 crore to 920 crore ARR while we held burn to an 18-month runway. Before that I ran central ops at a publicly listed logistics group. I am exploring CEO and COO roles at Series C+ fintechs because I am at the scale where I want the board and fundraising exposure that comes with the CEO seat.
Student / first internship
Weak
I am a second-year engineering student. I have good grades and I am passionate about technology. I am looking for an internship to learn and grow.
Strong
I am a second-year CSE student at BITS Pilani, currently 8.4 CGPA. I have shipped two full-stack side projects this past summer, one of them is a plagiarism detector for code (Python + Flask) that has been adopted by three CS professors for assignment grading. I am looking for a software engineering internship specifically because I want to see how production code gets reviewed, tested, and deployed, the part I have not yet touched in my personal projects.
6 mistakes that tank the answer
Reciting your resume top to bottom
The interviewer has already read the resume. Pick 3 highlights, not 13 line-items.
Starting with childhood or college admission
Cut to your current role and current work. They did not ask for your life story.
Adjectives instead of evidence
Do not say "I am a passionate developer". Say what you shipped last month and let the passion show through the specificity.
Skipping the future
The Future (why this role) sentence is what closes the answer. Without it, you sound like you are still explaining yourself.
Going over 2 minutes
At 2 minutes 30 seconds the interviewer has stopped listening. 60 to 90 seconds is the sweet spot.
Memorising word-for-word
Memorise 3 beats and hit them. Fresh phrasing on the day sounds human; a rehearsed script sounds robotic.
How the question actually gets asked
The phrasing varies but the question underneath is always the same: give me a 90-second self-pitch. All of these map to the same answer:
- Tell me about yourself.
- Walk me through your background.
- Can you introduce yourself?
- Run me through your resume.
- Give me a quick overview of your career so far.
- What is your story?
- Who are you, outside the resume?
The last one ("outside the resume") does invite a slightly more personal beat, but still hold to the 90-second limit and still end on Future.
How to rehearse without sounding robotic
- Write it out once, fully. Three sentences each for Present, Past, Future. That is the skeleton.
- Now delete 30 percent. The written version is always too long. Cut until every sentence earns its place.
- Rehearse aloud 5 to 10 times, not 50. Over-rehearsed answers sound rehearsed. Stop when the beats come naturally, not the exact words.
- Record yourself once. Play it back. Cut filler (so, basically, I guess). Check your time.
- Adjust per interviewer. Know who you are talking to: recruiter wants the story arc, hiring manager wants the relevance, cross-functional panel wants the range. Same skeleton, different emphasis.
External references
Further reading on this topic from independent sources. All external links open in a new tab.
Frequently asked questions
Should I include personal information?+
What if I have only one relevant role?+
Do I need to mention the company name I am interviewing with?+
Can I use the same answer for every company?+
What if I go blank?+
Is it OK to write notes on a notepad?+
Should the answer change between phone screen and onsite?+
Need a resume that matches your pitch?
Your Tell-Me-About-Yourself answer is easier to deliver when your resume already tells the same story. Build a free, ATS-ready resume in under 10 minutes.