Tell Me About Yourself" as a Fresher

It's almost always the first question, and it's the one people prepare for the least. Many candidates think it's small talk. Others recite their resume line by line, starting with their Class 10 marks. Neither works well.

The interviewer isn't asking for your life story. They want to know three things: who you are professionally, whether you can talk clearly about yourself, and what they should ask you next. That last point matters most. Your answer sets the direction for the rest of the interview, so you get to choose what you'd like to be asked about.

A structure that works: present, past, future

Keep it simple.

1. Present. Who you are right now, in one or two sentences. Your degree, branch and college, or your current role if you've started working.
2. Past. One or two things you've done that are relevant to this job. A project, an internship, a competition, a part-time job or a responsibility you took on. Pick the strongest, not all of them.
3. Future. Why you're interested in this role or company, in a sentence or two.

That's it. Aim for roughly a minute, and certainly no more than two. If the interviewer wants more, they'll ask.

Example: engineering fresher applying for a software role

"I'm a final-year computer science student at [college], graduating this year. Over the last two years I've become most interested in backend development. My final-year project is a booking system for our college library, built with Java and Spring Boot and a MySQL database. It's being used by a few departments now, and the most useful part for me was dealing with real feedback, like fixing slow queries once more people started using it. I also did a two-month internship at [company], where I wrote APIs for an internal tool. I'm applying here because I'd like to work on backend systems at a larger scale, and this role is focused on exactly that."

Notice what this answer does. It doesn't list every subject or certificate. It picks one project and one internship, and it gives the interviewer an obvious next question: "Tell me about those slow queries." That's a question this candidate can answer well, because it's their own work.

Example: commerce graduate applying for an analyst role

"I recently finished my B.Com from [college]. During my degree, I realised I enjoyed working with numbers more than with theory, so I learned Excel properly and later some SQL. For a college project, I analysed two years of sales data for a family friend's retail shop and found that a few product lines were taking up shelf space without making much money. They changed their stock based on it. I'd like to do that kind of work full-time, which is why this analyst role caught my attention."

Example: someone switching fields

"I studied mechanical engineering and worked for a year as a quality engineer at a manufacturing plant. A lot of that job involved tracking defect data in spreadsheets, and I found I liked that part more than anything else. So for the last eight months I've been learning Python and data analysis, and I built a small dashboard that tracks defect trends, which my team started using. I'm now looking for a role where data is the main job, not a side task."

A career switcher doesn't need to apologise for the switch. Explain what pulled you towards the new field and show something concrete you've done about it.

Common mistakes

Repeating the resume. The interviewer has it in front of them. Use your answer to add context the resume can't, such as why you picked a project or what you learned from it.

Starting with personal details. Your hometown, your parents' professions and your hobbies usually aren't what they're looking for in this question. A hobby is worth mentioning only if it says something relevant about you, like running a college club or building things in your spare time.

Using empty adjectives. "I'm hard-working, passionate and a quick learner" tells the interviewer nothing, because everyone says it. Show it instead. "I taught myself SQL in a month so I could finish my project" says "quick learner" without the cliché.

Memorising word for word. Know your structure and your key points, but don't learn a script. A memorised answer sounds flat, and if you lose your place, it's hard to recover. Practise saying it out loud a few times, slightly differently each time.

Mentioning things you can't defend. If you bring up a technology, a project or an achievement, expect follow-up questions on it. Don't mention a skill you've only watched one video about.

Adjust it for each interview

The structure stays the same, but the details should change with the job. For a testing role, lead with the time you found and fixed bugs in a project. For a client-facing role, mention the event you organised or the customers you dealt with in a part-time job. Read the job description, pick the two things from your background that match it best, and build your answer around those.

The same applies to HR rounds versus technical rounds. In an HR round, you can talk a bit more about why you chose this career and what you want from it. In a technical round, keep the focus on projects and skills.

Say it out loud before the interview

Write down your three parts in bullet points, not full sentences. Then say your answer out loud, ideally while recording yourself on your phone. Listen back once. You'll notice where you ramble, where you rush and where you say "basically" too often. Two or three rounds of this is usually enough.

A good answer doesn't need to be impressive. It needs to be clear, honest and relevant, and it should leave the interviewer curious about something you're happy to talk about.