How to Answer "Tell Me About Yourself" as a Fresher
It is the first question in almost every interview and the one most candidates handle worst — either a ninety-second life story or a nervous restatement of the resume. It is really an opening statement, and you get to choose what the next ten minutes are about.
What is actually being tested
- Can you be concise? If you cannot summarise yourself in 90 seconds, an interviewer will doubt you can summarise a project.
- Do you know what matters? What you choose to include shows your judgement about relevance.
- Can you steer? A good answer plants the topics you want to be asked about next.
- Do you sound rehearsed or present? Structured is good; recited is not.
A structure that works
- Present (about 20 seconds). Who you are right now — course, year, focus area.
- Proof (about 40 seconds). One or two concrete things you built or did, with a result attached.
- Purpose (about 20 seconds). Why this role, at this company, now.
Plant your hooks
Name the project you most want to discuss. Interviewers routinely follow up on whatever you mention last — so end on the thing you can talk about for ten minutes without effort.
A worked example
Final-year CSE student, backend role
"I am a final-year Computer Science student at Pune Institute of Technology, and most of my work over the last year has been backend — mainly Java and Spring Boot.
The project I have learned the most from is a campus event-booking system I built for our college fest. It handled about 2,000 registrations across three days, and the interesting part was concurrency: two people could book the last seat at the same time. I ended up using database-level locking to make the booking atomic, after my first optimistic version double-booked under load testing.
That is also why this role interests me — you are hiring for backend work on systems with real transaction volume, and that is the direction I want to go deeper in."
Roughly 75 seconds. It is specific, it admits a first attempt that failed and what fixed it, and it hands the interviewer an obvious next question about concurrency and locking — which is exactly the question the candidate is prepared for.
What loses the room
Starting from school
"I was born in Nashik, I did my tenth at..." — the interviewer has already stopped listening. Start from where you are now.
Reading the resume aloud
They have it open in front of them. Add the context that is not on the page: why you built the thing, what went wrong, what you would do differently.
Listing every technology you have touched
Naming fourteen technologies invites a question about the one you know least. Name three you can defend in depth.
Key takeaways
- Answer in 60 to 90 seconds: present, proof, purpose.
- Use one concrete project with a number and a real problem attached.
- End on the topic you most want to be asked about next.
- Do not narrate your resume or your school history.
Frequently asked questions
How long should the answer to 'tell me about yourself' be?
Sixty to ninety seconds. Long enough for a structure and one concrete example, short enough that the interviewer stays engaged and can follow up.
Should a fresher talk about personal interests?
One line at most, and only if it connects to the role or is genuinely distinctive. The rest of the time is better spent on a project you can defend under questioning.
Is it fine to prepare this answer in advance?
Yes — prepare the structure and the example, not a word-for-word script. Recited answers sound recited, and they collapse as soon as the interviewer interrupts with a question.
Test yourself on HR Interview
Reading is not recall. Take a timed quiz on this topic solo, or share a room code and battle friends on it.
⚡ Start the HR Interview quiz