How to Answer "Tell Me About Yourself"

how-to-answer-tell-me-about-yourself.jpg

Almost every interview in India opens with this line, and almost nobody prepares for it properly. Candidates either recite their CV from the top or drift into family details for two minutes. The first ninety seconds set the tone for everything after, so this is the one answer worth rehearsing out loud.

What the interviewer is actually asking

They are not asking for your life story. They are asking three things at once: can you speak clearly, what is the short version of your professional background, and why are you sitting in this chair. An interviewer who has five candidates lined up is also using the answer to decide which part of your CV to question first. That means your introduction is a menu. Whatever you emphasise is what you will be asked about, so mention only the work you can defend.

Use present, past, then future

The structure that works in nearly every round is three blocks, roughly sixty to ninety seconds in total.

  • Present: what you do now, in one sentence, including your role, your company and the scope of your work.
  • Past: how you got here. Two or three highlights only, chosen because they support this particular role.
  • Future: what you are looking for now and why this opening fits.

The future block is the one candidates skip, and it is the most valuable, because it turns an introduction into a reason for the conversation.

Two sample answers you can adapt

A fresher, hired through campus placement

Kavya, a 2026 B.Tech graduate from a college in Coimbatore, interviewing for a junior developer role through campus placement:

I completed my B.Tech in Computer Science this year with a 7.8 CGPA. For the last year I have been working mostly in Java and SQL. My final year project was a hostel mess billing system that my department is still using, where I handled the backend and the database design for about two hundred student records. Before that I did a two-month internship at a small firm in Coimbatore doing manual testing, which is where I first understood how requirements actually reach a developer. I am looking for a role where I can work on backend development in a structured team, and your training programme followed by a project allocation is exactly the kind of start I want.

Notice what she does not say: school marks, hobbies, family background, or a list of every technology she has heard of.

An experienced candidate moving laterally

Sandeep, four years in a service company in Bengaluru, interviewing laterally for a product company:

I am currently a Senior Software Engineer at an IT services firm in Bengaluru, working for a European retail client. For the last two years I have owned their order management APIs, which handle roughly a few thousand orders a day, and I also run the on-call rotation for that module. Before this I spent about eighteen months on the migration of their legacy reporting system, which is where I learned most of what I know about database performance. What I want now is to work on a product where I see the same system evolve over years rather than hand it over at the end of a contract, and that is why this role interested me.

A weak answer and its rewrite

Weak: Good morning sir. Myself Rohit Verma. I am from Lucknow. I did my schooling from City Montessori School and then my BCA. My father is a government employee and my mother is a housewife. I have two sisters. My hobbies are cricket and listening to music. I am hardworking and a quick learner.

This is the most common introduction in Indian interviews and it says nothing about the job. The rewrite: Good morning. I am Rohit Verma. I finished my BCA last year and since then I have been working as a data entry and MIS executive at a logistics company in Lucknow, handling daily delivery reports for around forty vehicles. I taught myself Excel formulas and pivot tables on the job because the reports were taking me four hours a day, and I got that down to about one. I want to move into a proper MIS or analyst role, which is why I applied here.

Same person, same background, completely different impression, and the second version invites a useful follow-up question.

Adjust for the round you are in

In a technical round, spend more of your ninety seconds on tools, modules and what you personally built rather than what the team built. In an HR round, spend more on stability, reason for change and what you want next. In a panel interview, address the first sentence to whoever asked, then move your eyes across the panel naturally. In a walk-in, where the interviewer is tired and running through many candidates, shorten it to forty-five seconds and make the future block sharp.

Common mistakes

Do not read from a paper. Do not start with myself followed by your name. Do not repeat your CV line by line, since the interviewer is holding it. Do not run past two minutes; if they want more, they will ask. And do not memorise it word for word, because a recited answer sounds recited. Learn the three blocks and let the words change each time.

Write your version today, say it aloud to a friend or into your phone recorder, and listen back once. That single exercise improves this answer more than any amount of reading about it.