Interview guide Tell me about yourself
Tell me about yourself: sample answers for freshers and experienced hires
By Manideep · Updated 26 October 2026 · 10 min read
Answer "tell me about yourself" in about a minute, in four parts: who you are now, the one or two things you have done that matter for this job, why you want this role, and a line that hands the conversation back. It is not your life story and not a reading of your resume. It is a short pitch for why you fit this particular job.
Below is the structure, then sample answers for freshers (including freshers with no internship), experienced hires, career changers and people returning after a break, then the mistakes that quietly cost candidates the round. Every sample is written to be said out loud, so read them aloud too.
What the interviewer is really asking
It is the first question in most interviews in India, from campus placements to senior hiring, and it is rarely small talk. In the first minute the interviewer is checking three things: can you communicate clearly under a little pressure, do you understand what this job is, and is there something in your background worth asking about next.
That last point matters most. Whatever you say here becomes the menu for the rest of the interview. Mention a project and you will probably be asked about it. Mention a tool and you may be tested on it. So only put things on the menu that you are happy to be questioned on for ten minutes.
A four-part structure you can reuse
Use the same four parts every time, and change what goes into them for each job.
| Part | What to say | Time |
|---|---|---|
| 1. Present | Who you are now: your role or your degree, and your main area. | 10–15 seconds |
| 2. Proof | One or two things you did that matter for this job, with a result or a number. | 25–30 seconds |
| 3. Purpose | Why this role, at this company, is the next step. | 10–15 seconds |
| 4. Pass back | One line that ends cleanly and invites the next question. | 5 seconds |
Present, Proof, Purpose, Pass back. If you forget everything else, remember that the answer moves forward in time: where you are, what you have done, where you want to go.
Keep personal details short. In India you will often be asked about your hometown or family, but let the interviewer ask. A one-line mention of where you are from is fine; three sentences about your parents' professions is time taken from your proof.
Sample answer for a fresher (B.Tech, campus placement)
Freshers usually have less to say, which makes choosing harder, not easier. Pick the one project or internship closest to the job, and say what you built and what happened.
I'm Priya, and I'm finishing my B.Tech in computer science at a college in Pune, graduating this year with an 8.2 CGPA.
The work I'm proudest of is my final-year project: a timetable app for our department that replaced a shared spreadsheet. I built the backend in Java with Spring Boot and a MySQL database, and about 400 students used it in the last semester. The hardest part was handling clashes when two faculty members edited the same slot, and fixing that taught me more about databases than any course did. I also did a two-month internship where I wrote test cases for a payments API.
I'm applying here because I want to work on backend systems that real users depend on, and your graduate programme puts freshers on client projects early.
That's me in short. Happy to go into the project in more detail.
Notice what it leaves out: school marks, every course taken, every certificate. If the interviewer wants those, they are on the resume in front of them.
Sample answer for a fresher (non-technical role)
I'm Arjun, and I recently completed my B.Com from Delhi University.
Alongside college I worked part-time for eight months at a small accounting firm, where I handled GST invoice entries for about thirty clients and reconciled their bank statements every month. One thing I changed there was the way we tracked pending documents: I set up a simple shared sheet with due dates, and late filings for our clients dropped noticeably that quarter.
I'm applying for this operations role because it's the same kind of work at a much bigger scale, and I like work where accuracy matters and you can see the result.
That's a quick summary. I'm happy to talk about any part of it.
Tell me about yourself for freshers with no internship
No internship is common, and it is not a problem if you fill the Proof part with something you actually did: a college project, a hackathon, a club you ran, a part-time job, or something you taught yourself and built. What matters is that you can say what you did and what came of it.
I'm Kavya, and I've just completed my BCA from a college in Coimbatore with a CGPA of 7.9.
I didn't get an internship, so in my final year I built things on my own. The one I'm proudest of is a website for my father's tuition centre, where students can see their batch timings and download notes. I built it with HTML, JavaScript and a small Node.js backend, and about 120 students use it every week. I also led the coding club in my final year and ran four workshops for juniors.
I'm applying for this trainee developer role because I want to learn to build software properly, with code reviews and real users, and your training programme is designed for that.
That's me in brief. I'm happy to show you the website.
If the interviewer asks for a more formal, ordered introduction, with your education and a personal line, use the format in our guide to self introduction for interview instead.
Sample answer for an experienced hire
With experience the problem flips: you have too much to say. Pick the one achievement that best matches this job description, and leave the rest for later questions.
I'm a backend engineer with about four years of experience, currently at a fintech company in Bengaluru where I work on our loan processing platform.
The piece of work most relevant to this role is a migration I led last year. Our loan approval service was a single large application that took around forty minutes to deploy, so releases happened once a week. I split it into three services, set up the deployment pipeline, and brought deploys down to under ten minutes. We now release several times a week, and incidents after releases went down because each change is smaller.
I'm looking for a role where I can do more of that kind of platform work at a larger scale, and your team's move towards event-driven systems is exactly that.
So that's where I am now. I can go deeper into the migration if that's useful.
I've spent seven years in B2B sales, the last three leading a team of six at a SaaS company that sells to manufacturing firms.
Last year my team was asked to open the Gujarat market from scratch. I hired two people from the industry rather than from sales, because our buyers trusted people who understood their factories, and we closed eighteen new accounts in the first year against a target of twelve.
I'm interested in this role because you're expanding into mid-sized manufacturers, which is the segment I know best, and I'd like to build that playbook for a bigger team.
That's the short version.
Sample answer for a career changer
If you are changing fields, the interviewer's silent question is: why should we trust someone without the usual background? Answer it before they ask, by connecting what you did before to what this job needs, and showing what you have already done to make the switch.
I'm a mechanical engineer by training, and for the last three years I've worked in quality control at an auto-parts plant.
The part of that job I enjoyed most was the data. I started analysing our defect reports in Excel and then in Python, and found that most rejections came from one machine during night shifts. Fixing its calibration schedule cut rejections by about a fifth. That's when I decided to move into analytics full time, and since then I've completed a SQL and Power BI course and built two dashboards on public datasets, which are on my GitHub.
I'm applying for this analyst role because it's in manufacturing, so I can bring the domain knowledge most analysts have to learn on the job.
That's my background in brief.
Sample answer after a career break
Mention the break once, plainly, and move on to what you are ready to do now. Interviewers rarely mind a break; they mind an answer that hides it.
I'm a business analyst with five years of experience in insurance, most recently at a large private insurer, where I wrote requirements for their claims system.
I took a two-year break to care for a family member, and over the last few months I've been getting back up to speed. I completed an agile certification and I've been volunteering as an analyst for a small NGO, mapping how they handle donor records.
I'm applying here because your claims modernisation project is close to the work I did before, and I'm ready to take that on full time again.
That's where I am.
Mistakes that cost you the first impression
- Reading your resume aloud, line by line. They have it in front of them; tell them what it does not say.
- Starting from school. "I did my schooling from…" spends your best seconds on the least relevant facts.
- Going past two minutes. Long answers sound unprepared, not thorough.
- Listing qualities without proof. "I am hard-working and a team player" is what everyone says; one specific result says more.
- Mentioning things you cannot discuss. If you name a technology, expect a question on it.
- Ending on silence. A clear last line, such as "Happy to go deeper into any of that", tells them you have finished.
- Memorising word for word. A recited answer sounds recited. Memorise the four points, not the sentences.
Build your own answer in fifteen minutes
- Open the job description and underline the two or three things it asks for most.
- Write one sentence for Present: your current role or degree, and your main area.
- Pick the one achievement that best matches what you underlined. Write it as what you did and what changed, with a number if you have one. That is your Proof.
- Write one sentence for Purpose that names something specific about this company or team.
- Add your Pass back line.
- Say it out loud with a timer. If it runs over ninety seconds, cut from Proof first.
- Say it again to someone else, or record yourself. The third time is when it starts to sound like you.
If the next question tends to be about your project, prepare that story as well: the STAR method gives it a shape. And because "tell me about yourself" usually opens an HR round, it helps to prepare the common HR interview questions that come after it, including where do you see yourself in 5 years.
A few more answers
Frequently asked questions
How should a fresher answer "tell me about yourself"?
In the same four parts: your degree and main area, one project, internship or thing you built with what came of it, why you want this role, and a closing line. If you have no internship, a college project, a club you ran or something you taught yourself is enough, as long as you can say what you did.
How long should my answer to "tell me about yourself" be?
About one minute, and never more than two. That is roughly 120 to 200 words spoken at a normal pace. Long enough to give one strong example, short enough that the interviewer stays curious.
Should I mention my family or hometown?
Only briefly, and only if it is natural. Interviewers in India often ask about family as a follow-up, so you do not need to cover it in your opening. Spend your minute on what makes you right for the job.
Can I answer "tell me about yourself" in Hindi?
If the interview is in Hindi, yes, and the same four-part structure works. Our guide to [Hindi interview questions](/guides/hindi-interview-questions) has a sample answer in Hindi and English.
Should I memorise my answer?
Memorise the structure and the key facts, not the exact words. A word-for-word answer sounds recited, and one forgotten line can throw you. Practise it aloud until the order comes naturally.
Is "walk me through your resume" the same question?
Nearly. It invites a little more chronology, so move through your roles in order, but still spend most of the time on the one or two achievements that matter for this job.
Should I mention hobbies?
Only if they say something useful about you for this role, such as a coding competition, a sport you captained or a blog you write. One line at most.