Practice free

Self Introduction for Interview (2026): Structure, Examples & What to Leave Out

Updated August 2026

This is the most searched interview question by Telugu students, and it is also the one students damage most by preparing it badly. The reason is worth stating plainly: it is the only answer in the entire interview you know in advance. You control every word. Most candidates respond to that by memorising a paragraph, which is exactly the wrong use of the advantage.

The better use is strategic. Whatever you mention in your introduction is what the interviewer asks about next — that is simply how the conversation works. So your introduction is not a summary, it is a menu. Name the project you can defend for ten minutes and they will ask about it; mention a technology you touched once and they will ask about that instead. Most students never realise they are choosing the next five minutes of questions, and hand that choice away by accident.

This page covers the introduction itself: the structure, worked examples for different kinds of student, what to leave out, and how to adapt it per company. For the wider interview basics — English, nerves, not knowing an answer, what to carry — our Telugu interview tips page covers those separately, and our HR set covers the other standard questions.

Frequently asked questions

What is the interviewer actually asking for?

Not your life story. They are asking a practical question — who are you academically, what have you actually done, and why are you sitting here — and they are also using the answer to decide what to ask next. It is a warm-up for them and a steering opportunity for you. Understanding this changes what you include: everything in the answer should be something you are happy to be questioned about, because it will be.

What structure should I use?

Present, past, future — the same skeleton the HR round expects, expanded. Present: your name, your degree, your branch and college, in one sentence. Past: the concrete things you have done — one or two projects or an internship, with what you personally built. Future: what you are looking for and why this role follows from what you have done. About sixty to ninety seconds in total. The mistake is spending forty seconds on the present, which is the least interesting part, and rushing the evidence, which is the part that earns questions.

Entha sepu matladali? How long should it be?

Sixty to ninety seconds is right for a fresher. Under thirty seconds sounds unprepared and gives the interviewer nothing to work with. Beyond two minutes you will see them waiting for you to finish, which is not the impression you want in the first two minutes. Time it once with your phone rather than guessing — most students find their version is either twenty-five seconds or three minutes, rarely in between.

"Myself Rajesh" ani modalupettocha? How should I open?

In a formal interview the standard forms are "My name is Rajesh" or "I am Rajesh". "Myself Rajesh" is extremely common in India and everyone understands it, but it is not standard English and some panels notice, so it is a free thing to fix. Do not over-think the opening beyond that — a plain "Good morning sir, my name is Rajesh" is completely fine. There is no need for a greeting speech, and no need to thank them for the opportunity before you have started.

What should I leave out?

Your birthplace, your family details and what your father does, your school marks, your hobbies unless genuinely relevant, and your full academic history year by year. None of it answers what they asked, and it consumes the seconds you need for evidence. Family background in particular is a very common opening in Indian interviews and it does not help you — the panel is assessing you, not your household. Leave out anything you would not want a follow-up question about.

How do I decide what to include?

Work backwards from the questions you want. If you can talk confidently about your final-year project for ten minutes, name it specifically and say what you built. If you learned SQL properly but only touched React once, mention SQL and leave React out — because whatever you name is what gets asked. This is the single most useful idea on this page: your introduction is a menu you hand the interviewer, and most students hand over the wrong dishes without realising they chose.

Example — CS student with a real project?

"Good morning sir. My name is Sravani, and I am a final-year Computer Science student at Andhra University. During my third year I built a web application that lets our department manage lab bookings — I wrote the backend in Node with a MySQL database, and I handled the part where two students could book the same slot at once, which took me the longest to get right. I have also been practising data structures regularly. I am looking for a software engineering role where I can work on backend systems, which is the part I enjoyed most in that project." That is about sixty-five seconds, names one concrete difficulty, and points the interviewer at concurrency, SQL and Node — all things she can defend.

Example — ECE student targeting core or embedded?

"Good morning sir. I am Karthik, a final-year ECE student at JNTU Kakinada. My main project was a sensor node that reads temperature and humidity and transmits readings over a serial link — I did the embedded C for the microcontroller side and the interrupt handling, which is where most of my time went. I have also done a VLSI elective and worked with Verilog for basic digital design. I am looking for an embedded or firmware role rather than IT services, because the hardware-software boundary is the part I find genuinely interesting." This is a good example of a fresher stating a direction clearly, which is respected rather than penalised when there is evidence behind it.

Example — degree, B.Sc or B.Com student?

"Good morning madam. My name is Divya and I completed my B.Com at Osmania University this year. Alongside my degree I taught myself Excel to a reasonably advanced level and learned basic SQL, and I used both for a small project analysing our college canteen's sales data over one semester — I built the queries and the summary sheets myself. I am comfortable with spoken English and I am looking for a business process or analyst role where those skills are used daily." Non-engineering students are frequently told nothing specific about how to present themselves; the answer is the same as for everyone — name a real thing you did and what you personally built.

Example — my CGPA is low. What do I say?

Nothing about it, unless asked. The introduction is not a confession and volunteering a weakness in the first ninety seconds directs the conversation straight at it. Instead spend those seconds on what you have built, which is the only argument that moves a panel. "My name is Anil, I am a final-year mechanical student at JNTU Anantapur. My project was a small automated sorting mechanism where I did the design and the control logic..." — then, if they ask about your marks later, answer that question directly, briefly and without apology. Two separate conversations, and you should not merge them yourself.

Example — I have a gap year or backlogs?

Same principle: the introduction is for what you offer. If the gap is visible on your resume they will ask, and you answer then — one factual sentence, what changed, and move on. If you feel it would be strange not to mention it at all, a single clause is enough: "I had a break of one year due to a health issue, which is behind me now, and during my final year I focused on..." — then continue into your evidence. What you must not do is spend thirty of your ninety seconds explaining it, because that makes it the topic of the interview.

Example — I have no internship, only college projects?

That describes most students in most colleges, so it is not the disadvantage it feels like, and the fix is to describe the project like real work rather than like an assignment. "My name is Praveen, final-year IT student at CBIT. My final-year project is a bus-tracking app for our college route — I built the Android side and the API that receives location updates. The hardest part was handling patchy network coverage, so I added a queue that stores updates and sends them when the signal returns." Nobody asked whether he was paid. What makes it credible is the specific problem and the specific fix.

Should I change it for different companies?

Change the emphasis, not the content. For a mass service recruiter, lead with your willingness to learn, your core subjects and one solid project, since they are hiring for trainability. For a product company or a coding-heavy recruiter, lead with what you built and the technical difficulty you solved. For a core engineering or embedded role, lead with your branch subjects and hardware work rather than any software you dabbled in. Same facts, different first sentence — and the first sentence is what sets the direction of the questions.

How do I finish it? Ela mugincchali?

With your forward-looking sentence, then stop cleanly. "That is a brief introduction about me, sir" or simply "…and that is why I applied for this role" both work. Do not trail off, do not fill the silence, and do not add "that's all about me, thank you" in a rush. The pause after you finish belongs to the interviewer and it is normal — students often keep talking to fill it and undo a good answer in the last ten seconds.

Battee pattali aa? Should I memorise it word for word?

Memorise the structure and the two or three facts, not the sentences. A recited paragraph has a recognisable rhythm and, more importantly, it collapses when the interviewer interrupts mid-way to ask something — which happens constantly. Practise saying it five different times in slightly different words until the content is automatic and the phrasing is not. That is the version that survives an interruption and sounds like a person rather than a recording.

Telugu lo aalochinchi English lo cheppocha? Can I think in Telugu and translate?

Everyone does this early on, and it is fine, with one caution: do not translate literally, because Telugu sentence structure produces English that sounds odd even when every word is correct. The practical fix is to prepare the English sentences by speaking them aloud rather than by translating written Telugu, so what you rehearse is already English-shaped. Over a few weeks the translation step shortens on its own. Short sentences help enormously here, because a short sentence is much harder to translate into something awkward.

What if they say "tell me something not on your resume"?

They are asking for something real, and this is a genuine opportunity rather than a trap. A specific interest with substance works well — something you taught yourself, something you organised, a responsibility you carried at home or in college. Keep it brief and keep it true. What falls flat is either a rehearsed "I am a hard worker and quick learner" or an over-personal answer. One honest specific thing, delivered in three sentences, is exactly right.

What should a 2027-batch student do about this now?

Build the material first, because a good introduction is downstream of having something to introduce — a project with a real difficulty you solved gives you the middle section that everything else hangs on. Then, closer to your drives, write the ninety-second version once, time it, and rehearse it aloud until the phrasing varies but the facts do not. Doing this a term early rather than the night before is what separates an introduction that sounds prepared from one that sounds recited.

Don't just read Self introduction questions — get asked them

Phiny's AI interviews you on exactly these topics, follows up on weak answers, and tells you what a stronger answer looks like. Text interviews are free and unlimited.

Start a free AI mock interview

How to prepare

Where these questions get asked

Related guides