How to Answer "Tell Me About Yourself" in an Interview

"Tell me about yourself" sounds casual, but it is usually the first real question, and it sets the tone. Interviewers are not asking for your life story. They want a short, relevant introduction that shows how you communicate and why you fit the role.

What the interviewer is really asking

In most cases the question means: who are you professionally, what have you done that is relevant, and why are you here? A focused answer of 60 to 90 seconds is usually enough.

The present, past, future structure

A reliable structure has three parts.

1. Present: who you are now. Your course, year and main area of interest.
2. Past: two or three relevant things you have done. Projects, an internship, a competition, or a skill you built.
3. Future: what you want next and why this role or company is a good step.

A sample answer

"I am a final-year Computer Science student, and over the last two years I have focused on backend development. I built a library management system in Java with a MySQL database, and more recently a small REST API with Spring Boot that handles user accounts and book records, where I learned a lot about validation and error handling. I also completed a summer internship where I fixed bugs in a small internal tool and wrote a few tests. I am looking for an entry-level backend role where I can keep learning from experienced engineers, which is why this position at your company interested me."

Notice what it does: it is specific, it mentions relevant work in plain language, and it ends by linking to the role. It does not recite the resume.

Tailor it in ten minutes

Before each interview, adjust the middle part. Read the job description and choose the two or three experiences that best match what they need. A front-end role should hear about your React or CSS work. A data role should hear about your SQL or analysis project. If you would like a stronger set of project descriptions to draw from, read how to write projects on your resume.

Mistakes to avoid

• Reading your resume aloud. They have it in front of them. Add context instead.
• Starting with childhood or unrelated details. Keep it professional.
• Being too long or too short. Under 30 seconds feels unprepared, and over two minutes loses attention.
• Vague claims such as "I am a hard worker". Show it with an example instead.
• Listing technologies without context. Say what you built with them.

Practise, but do not memorise

Write your answer, read it aloud, and record yourself once. You should sound natural, not scripted. Memorise the three parts and a few key facts, not every word. If you get nervous, breathe and start with the first part.

Key takeaways

• Use present, past and future, in about a minute.
• Choose examples relevant to the specific role.
• Be specific and honest, and end with why this role.
• Practise aloud until it sounds like you.
• Next, plan the rest of your preparation with the technical interview preparation plan.