Topic: Interviews

How to answer "Tell me about yourself" as a fresher (with examples)

Updated · 5 min read · Interviews

Answer "tell me about yourself" in about 60 to 90 seconds using a present–past–future structure: who you are now (your degree and target role), what you've done that proves you can do this job (one or two projects, an internship or a relevant achievement), and why you want this particular role. Leave out your family details, hobbies and a recital of your marks unless they're relevant. The goal is to give the interviewer a clear, relevant picture and a few good things to ask about next.

Why interviewers ask it

It's usually the first question, and it does several jobs at once:

  • It eases both of you into the conversation
  • It shows how clearly you communicate and whether you can summarise
  • It tells the interviewer what you think is most important about yourself
  • Whatever you mention becomes the material for their next questions

That last point is the secret: you get to steer the interview towards your strongest topics.

The present–past–future structure

  1. Present (1–2 sentences): "I'm a final-year B.Tech student in electronics, focusing on software development, and I'm applying for the associate developer role."
  2. Past (3–4 sentences): your most relevant proof: a project, an internship, a hackathon, a skill you built. Be specific.
  3. Future (1–2 sentences): why this role and company fit what you want to do next.

That's it. Six to eight sentences, spoken calmly, takes about a minute.

Example answers

These are examples of the structure. Use your own details and words; memorised answers sound memorised.

Developer role

"I'm a computer science graduate from the 2026 batch, and I'm looking to start my career as a backend developer.

During college, I built two projects I'm proud of. The first is a placement-drive tracker for our college, built with Spring Boot and MySQL, which our placement coordinators used last semester. The second is an expense-splitting app for hostel rooms where I designed the database and the REST APIs. Building them taught me a lot about database design and debugging slow queries.

I'm applying here because your graduate programme combines training with real client projects, and I want to build strong fundamentals in backend development in a team that works at scale."

QA / testing role

"I'm a 2026 BCA graduate, and I want to build a career in software quality, especially test automation.

In my final year I automated the testing of a demo e-commerce website using Selenium and Java, writing around 35 automated tests for login, cart and checkout, and running them on every code change with GitHub Actions. I also did a two-month internship where I wrote manual test cases and logged bugs for a mobile app, which taught me how to write bug reports that developers can act on.

I'm interested in this role because it combines manual and automation testing, and I'd like to grow into an automation engineer."

Non-CS branch moving into IT

"I graduated in mechanical engineering this year, and over the last year I've moved towards software development.

I started with Python for data analysis in a college project on machine maintenance data, enjoyed it more than design work, and then learned SQL and web basics through online courses. I've since built a small inventory management web app with Flask and SQLite, which I deployed online.

I'm applying because your company hires graduates from all branches and provides training, and I'm ready to build on the fundamentals I've already learned."

What to leave out

  • Family details ("My father is a businessman, my mother is a homemaker") unless directly relevant. This is common in Indian interviews but doesn't help your case for the job.
  • Your full academic history from Class 10 onwards. Your resume already has it.
  • Hobbies, unless they're related (for example, competitive programming or open-source contributions).
  • Generic adjectives like hard-working, dedicated, passionate, without proof.
  • Anything you can't talk about in depth. If you mention machine learning, expect machine learning questions.

Adjust it for the round

  • HR round: include a little more on motivation and why this company
  • Technical round: put more weight on projects and the technologies you used, since that's where the interviewer will dig
  • Online video interview: keep it slightly shorter, look at the camera, and pause briefly between parts

How to practise without sounding rehearsed

  1. Write bullet points, not a script: three for present, three for past, two for future
  2. Say it aloud and time yourself; aim for 60–90 seconds
  3. Record yourself once and listen back for filler words and rushed parts
  4. Practise with a friend and ask what they remember afterwards; that's what the interviewer will remember too
  5. Vary the wording each time so it stays natural

Prepare your projects well too, because follow-up questions will come straight from them. How to write projects on a resume includes the questions interviewers commonly ask about projects.

Common mistakes

  • Talking for three or four minutes
  • Repeating your resume line by line
  • Starting with "As you can see on my resume..."
  • Speaking too fast because of nerves
  • Ending abruptly. Finish with the "future" part so the interviewer knows you've finished

For the rest of the round, see common HR interview questions for freshers.

Frequently asked questions

How long should my answer be?

About 60 to 90 seconds. If the interviewer wants more detail on something, they'll ask.

Should I mention my CGPA?

Only if it's strong or the company emphasises it. Otherwise your projects and skills are a better use of the time.

Is it okay to mention personal interests?

Briefly, if they're relevant or show a useful quality, such as competitive programming or leading a college technical club.

What if I have no projects or internships?

Talk about what you've learned and practised, any college assignments you built, and start one small project now. Even a recent, simple project gives you something concrete to discuss.