The first 90 seconds set the direction of the entire interview. Here is a structure that works, and what to leave out of it.
Quick answer
How should a fresher introduce themselves in an interview?
Use a present-past-future structure in 60–90 seconds: what you are studying and where, two or three relevant things you have done (a project, an internship, a role of responsibility), and what you want to do next and why this role fits. Do not narrate your schooling, your family background or your entire resume — the introduction should set up the questions you want to be asked.
The self-introduction is the only part of an interview you fully control, and most candidates waste it. The usual version is a chronological recap that starts at Class 10 and ends with hobbies — which tells the interviewer nothing and hands them no thread to pull on.
A good introduction does two jobs: it establishes that you can organise information, and it plants the two or three topics you most want to be questioned about.
| Part | Roughly | What goes in it |
|---|---|---|
| Present | 15 seconds | Name, degree, branch, college, year |
| Past | 45 seconds | Two or three things you have done that are relevant to this role |
| Future | 20 seconds | What kind of work you want, and why this role fits it |
The proportions matter. Most weak introductions spend forty seconds on the "present" section — where you studied, what your percentage was — which is already on the resume in front of the interviewer.
Engineering fresher, product company
"I am Ananya, a final-year Computer Science student at [college]. Over the last year I have worked on two things I would call substantial: a campus event management app that around 400 students used during our tech fest, where I built the backend and the notification system, and a two-month internship at a logistics startup where I worked on their internal dashboard. The internship was the first time I saw how much of the work is understanding what someone actually needs before writing anything. I am looking for a backend-leaning role where I can keep working on systems that real users depend on, which is why this role interested me."
Notice what it does: it names two concrete things, quantifies one, states what was learned rather than just what was built, and closes with a direction that connects to the role. It also deliberately leaves several threads — the notification system, the dashboard, the startup — for the interviewer to pull on.
Before your drive
60–90 seconds. Past two minutes you are talking over the interviewer's attention, and the questions they wanted to ask start getting cut for time.
No, unless directly asked. It is not relevant to the role and it uses seconds you need for things that are.
Use whatever you genuinely owned — a college committee role, a competition, a self-taught skill with something built to show for it. Interviewers care about what you did with an opportunity, not how prestigious the opportunity was.
Slightly. For a technical round, weight the "past" section toward what you built and the decisions you made. For HR, weight it toward motivation and fit.
Say your introduction out loud to someone who will tell you the truth about it.
Book a live mock interview →The questions that come up in almost every fresher interview — what each one is actually testing, and how to build an answer that sounds like you rather than a script.
Interview PreparationThe most commonly asked HR questions, why they're asked, and a structure for answering each one honestly and specifically.
Skills & LearningCommunication feedback is the vaguest rejection reason there is. Here is what it actually refers to, and how to fix each part of it.
InternshipsThe preparation process, not just the question list — what to do in the days before, and how to walk in ready.