How to Answer "Tell Me About Yourself" as a Fresher (with Examples)

"Tell me about yourself" is usually the first question in an interview, in both technical and HR rounds. It sets the tone for everything after it, and it's the one question you can prepare almost word for word.

The problem is that most freshers either recite their resume line by line or talk about their hobbies and family. This post gives you a simple structure, two sample answers you can adapt, and the mistakes to avoid.

What the interviewer is actually asking

The interviewer isn't asking for your life story. They want to know three things in about a minute:

• Who you are professionally: your degree and what you're good at.
• Proof: one or two things you've built or done that show it.
• Why you're here: why this role makes sense for you.

They're also listening to *how* you speak: whether you're clear, confident and concise. A structured answer helps with that as much as the content does.

A 4-part structure (60 to 90 seconds)

1. Present: who you are. Your name, degree, college and the year you graduated or will graduate. One sentence.
2. Skills: what you're good at. Two or three skills relevant to *this* job, not everything you've ever touched.
3. Proof: one project or achievement. What you built, what you used, and one concrete result. This is the part that makes you memorable.
4. Future: why this role. One or two sentences connecting your skills to the job you're interviewing for.

Sample answer: Computer Science graduate

Why this works: it's specific (a named project, named technologies, a real use), it stays on topic, and it ends by linking to the role. Replace every detail with your own; an interviewer can tell a memorised template from a real story.

Sample answer: non-CS graduate applying for a tech role

Why this works: it turns the "non-CS" background into a reason, not an excuse, and shows effort through concrete projects.

Mistakes to avoid

• Repeating your resume. The interviewer has it in front of them. Pick the highlights and explain them.
• Starting with personal details. Your family, hometown and hobbies aren't what's being asked, unless they connect to the job.
• Listing every technology. "C, C++, Java, Python, HTML, CSS, JavaScript, React, Angular, SQL..." sounds like a list, not a skill. Pick the ones you can answer questions on.
• Going on too long. Past two minutes, you lose attention. Stop after the "why this role" part.
• Saying something you can't back up. Everything you mention is fair game for the next question. If you say "I'm strong in SQL", expect a SQL question.
• Sounding memorised. Learn the structure and the key points, not a script. It's fine to phrase it slightly differently each time.

Tailor it to the round

• Technical round: spend more time on skills and the project. Mention the technical decisions you made.
• HR round: keep the project short and add a line about how you work: teamwork, learning quickly, handling deadlines, with a small example.
• Managerial round: focus on why this role and this company, and what you want to learn in the first year.

Practise it out loud

Write your answer using the four parts, then say it out loud at least five times. Record yourself on your phone once and listen back: you'll notice filler words ("basically", "actually", "like") and the places you rush. Then practise the follow-up questions your answer invites: "Tell me more about that project", "Why this company?", "What was the hardest part?"

Practise more HR questions

"Tell me about yourself" is usually followed by questions such as "What are your strengths and weaknesses?", "Why should we hire you?" and "Where do you see yourself in five years?". You can read sample answers for free on our HR interview questions page.