How to Introduce Yourself in an Interview

The question “Tell me about yourself” opens most HR interviews, and how you answer it in the first 90 seconds sets the frame for everything that follows.

Most students either over-prepare (memorised, robotic) or under-prepare (rambling, unfocused). Neither creates the impression that gets you to the next round. This article covers a four-part structure that works for engineering freshers at Indian IT companies, three sample scripts you can adapt, and the mistakes that undermine otherwise strong answers.

What Interviewers Actually Want From This Question

HR interviewers are not asking you to narrate your life. They are running a quick calibration: Is this person self-aware? Can they communicate clearly? Does their background connect to this role?

The question is open-ended because interviewers want to see what you choose to say. A student who leads with a relevant project signals something different from one who opens with their school history. The selection reveals priorities.

Spending 20 minutes on AmbitionBox before an interview, reviewing experiences at your target company, tells you what topics come up early in their HR rounds. That context helps you decide which part of your background to lead with.

The self-introduction is also a filter. Everything the interviewer hears in the next 30 minutes gets processed through the picture you painted in the first 90 seconds. A strong introduction sets a frame that works in your favour throughout the conversation.

The 90-Second Structure That Works

Four components, in order:

1. Academic background: your degree, branch, and college. One sentence.
2. What you have done: one project or internship with one specific detail. One to two sentences.
3. What you are good at: one skill, supported by the same project as evidence. One sentence.
4. Why you are here: the role or function you are applying for, and a one-sentence connection to your background.

At a calm, conversational pace, those four components take about 90 seconds. Not 30 seconds (reads as unprepared) and not 3 minutes (reads as unfocused).

A note on “Good morning, my name is…”: skip it. The interviewer already has your name from your resume. That greeting consumes your first sentence without adding information. Go directly to content.

Sample Introductions You Can Adapt

Fresher With No Internship (B.E. CSE, Tier-2 College)

Applicable for a software developer role at a mid-size IT services company:

• Academic: “I am completing a B.E. in CSE this May at a college in Tamil Nadu.”
• Project: “For my final-year project, I built a text summarisation tool using Python and NLTK. It condenses a 1,000-word article into a 100-word summary and runs as a Flask web application.”
• Skill: “Python is my strongest language and I have used it across three projects, including this one.”
• Direction: “I am looking for a developer role where I can build production-grade applications. This opening fits that direction.”

Fresher With an Internship (B.E. ECE, Applying for a Testing Role)

• Academic: “I am in my final year of B.E. ECE at a college in Coimbatore.”
• Internship: “Last semester I did a six-week internship at a local automation firm. I wrote test cases for a PLC-based conveyor system and identified two defects in the monitoring dashboard.”
• Skill: “I came away comfortable with both hardware validation and bug documentation, and I can work across the hardware-software boundary.”
• Direction: “I want to move into embedded or hardware testing after graduation. This role is the natural starting point.”

Off-Branch Student (ECE Applying for a Software Role)

The key shift here: lead with the software work, not the ECE degree.

• “I am in ECE, but most of my project work has been on the software side. My final-year project is a Python data pipeline that pulls sensor readings from an IoT device and stores them in a PostgreSQL database. Python and SQL are my working languages. I want to move into backend or data engineering, which is why I applied for this role.”

For product-oriented companies with deeper technical rounds, the project detail in component two carries even more weight. The Intel interview guide covers how the HR opener connects to the technical discussion that follows.

Common Mistakes That Hurt First Impressions

Starting With Personal Details

Family background, hometown, school history, and hobbies unrelated to the role add words without adding signal. The HR interviewer has 30 to 45 minutes total. Every sentence about your native place is a sentence that is not about your fit for the job.

Reciting Your Resume Chronologically

Running through your life from school to present is the most common mistake. Interviewers have your resume in front of them. They do not need you to read it aloud. The introduction should be a curated argument, not a timeline.

Memorising Word for Word

A memorised script is hard to recover from when the interviewer interrupts, asks a follow-up mid-sentence, or the connection drops on a virtual call. Know the four components well enough to speak to them in any order. Practise the meaning, not the exact phrasing.

Generic Introductions That Apply to Any Company

“I am a hard-working, team-oriented person who wants to grow in a dynamic organisation” could describe any of 500 applicants in the room. The introduction that works references the specific role or something you found when you researched the company. Use LinkedIn to look at the team you would be joining and the problems the company solves. One relevant detail is worth more than three generic sentences.

Delivering It Well

Structure handles the content. Delivery handles the impression.

Four specifics:

• Pace: speak at conversation speed, not presentation speed. If you normally speak quickly, slow down deliberately. Fast delivery reads as nervousness.
• Eye contact: sustained but natural. For virtual calls, look at the camera lens, not at the interviewer’s face on screen.
• Recovery: when you stumble, pause, take a breath, and pick up at the next component. Recovering cleanly is better than pushing through a muddled sentence.
• The closing sentence matters disproportionately: end with the direction statement, not with “…and that’s about me.” Close with a forward-facing sentence that names the role or function you are applying for.

A single timed practice aloud the evening before the interview will do more for your delivery than an hour of silent re-reading.

If your placement process includes a group discussion round before the HR interview, the communication clarity you build for your introduction transfers directly. The traits GD moderators actually assess overlap with what interviewers look for in an opening 90 seconds.

The four-part structure above has a load-bearing component: the project reference. There is a real difference between citing a deployed project and citing a course certificate. The first holds up when the interviewer asks one follow-up question. If that project gap is what you are facing before your placement window, TinkerLLM is a hands-on environment for building real LLM-based tools. At ₹299, you walk away with a deployed project you can name in the “what you have done” component of your introduction.

FACE Prep’s guide to the most frequently asked HR questions covers the questions that follow your introduction in most HR rounds, with sample answers framed for engineering freshers.