What the interviewer really wants
"Tell me about yourself" is not a request for your life story or a reading of your resume. The interviewer wants a short, confident summary that answers one hidden question: why are you a good fit for this role? They also use it to choose what to ask next. Whatever you mention, expect a follow-up on it, so mention the things you are happy to talk about.
A good answer does three jobs at once: it shows you can communicate clearly, it highlights the two or three things that match the job, and it ends by connecting you to this opportunity.
A four-part structure that works
- Present: who you are now. Your current role or your degree, in one or two sentences. "I'm a final-year B.Tech student in computer engineering" or "I'm a Java developer with three years of experience".
- Past: what you have done. Two or three experiences relevant to this job: an internship, a project, a responsibility at work.
- Proof: one specific result. A number, an outcome or a moment you are proud of. This is what interviewers remember.
- Future: why this role. One or two sentences connecting your direction to this company or position.
Aim for 60 to 90 seconds. Speak at a comfortable pace, and stop when you reach the end of part four; let the interviewer take it from there.
Sample answer for a fresher
"I'm a final-year computer engineering student from a college in Pune, and I'll graduate this May. Over the last two years I've focused on backend development, mainly Java and Spring Boot with MySQL."
"My final-year project is a hostel complaint system that our college is now testing with about 300 students. I built the backend and the database, and the hardest part was making sure complaints couldn't get lost between wardens, so I added a simple escalation if nobody responds in 48 hours. Before that, I did a two-month internship at a small startup where I wrote APIs and fixed bugs in their admin panel."
"I enjoy building things people actually use, and I'm looking for a role where I can work on real products and learn from experienced engineers. That's why this backend developer role in your team interested me."
Why it works: it is specific (Java, Spring Boot, 300 students, 48 hours), it gives the interviewer two clear things to ask about (the project and the internship), and it ends on the role.
Sample answer for an IT professional
"I'm a software engineer with three years of experience, currently at an IT services company where I work on a retail client's order management system, mainly in Java and Oracle SQL."
"I started on the support team, which taught me how the system behaves in production, and for the last 18 months I've been building new features. The piece of work I'm proudest of is a report that used to take the client's team a full day every week; I rebuilt it with better queries and a scheduled job, and it now runs in about ten minutes."
"I'm now looking to move to a product company where I can own features from design to release and work closer to users. Your role on the checkout team fits that, and it uses the same stack I've been working with."
Why it works: it shows growth (support to development), one measurable result (a day to ten minutes), and a clear, positive reason for the move, without criticising the current employer.
Sample answer for a career switcher
"I'm a mechanical engineer by degree, and for the last two years I've worked in quality control at an automobile parts manufacturer near Chennai. A big part of my job turned out to be data: tracking defect rates across production lines and finding patterns."
"I started using Excel for it, then taught myself SQL and Power BI. I built a dashboard that showed which machines caused most defects, and it helped my team cut rework on one line by about 15 percent. That's when I realised I enjoy the analysis more than the engineering itself, so I completed a data analytics certification this year and built three projects on public datasets."
"I'm applying for this analyst role because it combines what I know about operations with the analysis work I want to do full time."
Why it works: it turns the switch into a story with a reason, shows the new skills were already used in a real job, and links the old experience to the new role instead of hiding it.
A fill-in template
If you are starting from a blank page, fill in the brackets, then rewrite it in your own words:
"I'm a [degree or current role] [with X years of experience in / specialising in] [area]. [One or two sentences on the most relevant work: internship, project or responsibilities.] [One specific result: what changed because of you, with a number if possible.] I'm now looking for [the kind of role], which is why [this company or this position] interests me: [one real reason]."
Read it aloud. If any sentence sounds like something you would never say to a friend, simplify it. "I'm passionate about leveraging technology" becomes "I like building things people use".
Adjust it to the round
- Technical round: spend more of your time on the tools and the hardest technical part of your best project. The interviewer will usually dig into it straight away.
- HR round: keep the technical detail light and add a line about how you work with people, such as leading a college event or helping juniors.
- Managerial or client round: lead with responsibility and results: what you owned, who depended on it, what improved.
- Phone or video interview: the interviewer can't read your body language, so pause briefly between the four parts and keep sentences short. Look at the camera, not your own video.
Other ways the same question is asked
- "Walk me through your resume." Same structure, but follow the order of your resume.
- "Describe yourself in three words." Pick three qualities and give one quick example for each, such as "curious: I taught myself SQL during my internship".
- "What should I know that isn't on your resume?" A good place for a hobby or experience that shows a useful quality, like running a small tuition class or organising a college fest.
Mistakes to avoid
- Reading your resume aloud. They have it in front of them. Tell the story behind it instead.
- Starting with personal details. Long descriptions of your hometown, your parents' jobs or your school marks are common in Indian interviews and almost never help. Start with who you are professionally.
- Going on for five minutes. If you pass two minutes, the interviewer has stopped listening.
- Sounding memorised. Know your four parts, not the exact words. Say it slightly differently each time.
- Ending without a link to the role. The last line should answer "why here?"
Practise it out loud
Write your answer using the four parts, then say it out loud five times. Time yourself, cut anything that doesn't support the role, and record yourself once to hear how it sounds. Then try it with a real interviewer's reaction: a mock interview with an AI interviewer starts with a warm-up question like this one and asks follow-ups when an answer is vague.
Once your introduction is ready, go through the other common HR interview questions, since the next ones usually build on what you just said. Myna can help you rehearse all of them by voice; see the plans and the free trial.