Walk into any campus placement drive and ask ten candidates how they'd answer "Tell me about yourself." You'll hear roughly the same thing ten times over.
It goes like this: "I'm a final year B.Tech student from [college name], specialising in [branch]. I have a CGPA of [number] and I've done projects in [technologies]. I also did an internship at [company]. My hobbies are reading and cricket. I am a quick learner and a team player."
The interviewer has heard this 40 times that day. They stopped listening after the second sentence.
Why the standard answer fails you
Here's the thing — the information isn't wrong. It's that you're leading with the least interesting part. Your CGPA and branch are on your resume sitting right there in front of them. You're just reading it back.
What the interviewer actually wants from this question is to understand who you are professionally and whether there's a thread connecting your past choices to this role. They want a person, not a résumé recitation.
And honestly? Most candidates miss this because nobody tells them. You've been prepped to have answers, not to have a story.
The structure that actually works
Forget the generic "present-past-future" framework for a second. The version that lands looks more like this:
The whole thing should take 60–90 seconds out loud. Not 3 minutes. Not 30 seconds.
Let's see the difference
Here's the standard version most candidates give:
"My name is Arjun and I'm from ABC College, ECE branch, CGPA 7.8. I've done projects in Python and machine learning. I interned at XYZ for two months. I'm a team player and I learn fast. I'm excited to work at your company."
Now here's the same candidate, same background, different approach:
"I've spent the last four years trying to figure out how to make machine learning actually work outside of Jupyter notebooks — which turned out to be harder than any of my coursework suggested. My final year project was a real-time inventory system for a local textile shop, and half the challenge was dealing with data that didn't behave like Kaggle datasets do. That experience made me obsessed with deployment and reliability, which is why I'm particularly interested in your ML platform team — I saw you shipped a feature for handling sparse input last quarter that I've been reading about."
Same person. Same degree. One version made the interviewer put down their pen. The other made them lean in.
The most common mistake: the everything dump
When candidates are nervous, they try to include everything — every project, every internship, every skill they've ever touched. The logic is: if I mention it, they can't disqualify me for not having it.
This backfires. It sounds unconfident. It also makes it impossible to remember you.
One good hook beats six mediocre bullets every time. Interviewers are pattern-matching for people who know what they're about. Specificity signals that.
For candidates switching from service companies to product roles
If you've spent three years at a service company and you're now applying to a product startup, the "tell me about yourself" moment is where you reframe your narrative — or where you lose the room.
Don't apologise for being at a services firm. Instead, pick the one thing from that work that is genuinely relevant and lead with it. "I spent two years supporting enterprise clients, but I spent most of my evenings building side projects because I wanted to work on something I'd actually use." That's honest. That's interesting. That moves the conversation forward.
Practise out loud, not in your head
This sounds obvious. Nobody does it.
Reading your answer silently feels like practising. It isn't. The version in your head always sounds better than the version that comes out of your mouth. Record yourself once. You'll immediately hear the "ums", the rushing, the flat spots.
Practising with an AI interviewer helps here too — not because AI feedback is perfect, but because hearing the question spoken at you (instead of reading it) more closely replicates the actual experience. The pressure is different. The brain works differently.
Two or three practice runs with spoken answers will do more for your confidence than an hour of silent preparation.
One last thing
Your introduction is not a performance. The goal isn't to sound impressive. It's to make the interviewer want to ask the next question. If you can do that — if they're curious by the end of the 90 seconds — you've done the job.
The interview is a conversation. Your intro is just the first sentence of it. Make it one worth continuing.