TL;DR: "Tell me about yourself" isn't a request for your life story — it's the interviewer deciding whether to lean in or coast through the rest of the interview on autopilot. A 60-second answer has four parts: who you are in one line, the one project or result you're proudest of, why this role connects to it, and a closing line that hands the turn back. Build it, cut the filler, and practice out loud until it actually takes a minute.
Every campus placement HR round opens with some version of the same line — "tell me about yourself," "walk me through your background," "so, tell us a little about you." It sounds like small talk while the panel settles in. It isn't. It's the first data point they use to decide how closely they listen to everything you say next, and answering it with a resume readout instead of a structure is an easy way to lose that attention before the harder questions even start.
Why Is "Tell Me About Yourself" Asked First?
The panel already has your resume. So this question isn't about information — it's doing three jobs at once. It's a warm-up: your first thirty seconds show how you speak under mild pressure, and that first read colors how the panel hears everything after. It's a structure test: can you organize your own story without being told the format? And it's a filter for what you think matters about yourself — what you lead with tells the panel what you value, and whether that matches what the role needs. A memorized resume readout answers none of those three; a structured sixty-second answer answers all of them.
What Is the 60-Second Shape That Actually Works?
Sixty seconds at a normal pace is roughly 130 to 150 words — not long enough for your whole life story, which is the constraint that makes this easier once you accept it. Four parts, in order:
- Who you are, in one line. Name, branch, year, college, said once. "I'm Ananya, a final-year B.Tech CSE student." That's it — don't pad it.
- The one project or result you're proudest of, and what you did in it. Not "I worked on several projects" — one project, named, with your specific contribution. Specificity makes this land — vague language gives the panel nothing to remember you by.
- Why this role. One sentence connecting that project to what the job actually needs. This is the line that turns a life summary into a pitch.
- A closing line that hands the turn back. Something short — "that's broadly where I am right now" or "happy to go deeper into any part of that." Don't trail off.
That's the whole shape.
What Does a Good 60-Second Answer Actually Sound Like?
Here's the shape filled in for three backgrounds. Each still runs the same four beats.
B.Tech CSE: "Hi, I'm Ananya, a final-year B.Tech Computer Science student. I've spent two years on backend development — Java, Spring Boot, some AWS. The project I'm proudest of is a hostel mess-management app I built with two classmates: it replaced a paper register nobody kept up to date, and students on campus still use it. I led the backend and database design, and debugging what happened when multiple wardens updated stock at once taught me more than any course did. I'm looking at this role because you build for scale from day one."
B.Com: "Hi, I'm Rohit, a final-year B.Com student specializing in accounting and finance. During my internship at a CA firm, I was handed GST reconciliation for eleven small-business clients — work nobody senior wanted, because it was slow and easy to get wrong by hand. I built a spreadsheet template that flagged mismatched invoices automatically, cutting our monthly reconciliation time roughly in half. What I took from it was that "boring" finance work like that still has room for someone willing to fix the process, not just do the task. I'm applying here because you rotate juniors across audit and taxation in year one, and I want that breadth first."
BA English: "Hi, I'm Priya, in my final year of a BA in English Literature. The obvious assumption is that means teaching or writing, but what pulled me toward this internship is the content and communications side. Last year I ran our department's literary magazine — recruiting writers, editing submissions, and printing it within a deadline we'd missed twice before I took over. That taught me how to hold a schedule with people who weren't reporting to me and still get them to deliver. I'm interested in this role because it's the same skill in a different room: shaping how something is said for an audience."
What Should You Cut From Your Answer?
What to cut from your answer:
- Reading your resume aloud. "I did my schooling from X, then joined Y college, then interned at Z..." The panel is holding your resume. Reciting it back wastes your best sixty seconds on what they already have.
- Family history. Where your father works, how many siblings you have — none of it answers "why should we hire you," and it eats time you need for the thing that does.
- "I am a hard-working and sincere person." Naming the trait tells the panel nothing they can check. Show it through the project instead of naming it as an adjective.
- Apologizing for your college. "I know it's not a top-tier college, but..." Nobody asked, and raising it plants a doubt that wasn't there.
- Running past ninety seconds. A self-introduction that keeps going becomes background noise, and you lose the structure — and the panel's attention — with it.
How Do You Practice a 60-Second Answer Until It's Actually Ready?
Writing the answer is the easy part. Getting it to take sixty seconds, out loud, under a little pressure, is what takes practice. A routine that works in one evening:
- Record yourself once, cold, on your phone — the four beats from memory, no script.
- Play it back and count your filler words — "um," "so basically," "like." Write the exact count down; that's the number the next round has to beat.
- Cut one thing — a weak line, a filler-heavy sentence, a detail that isn't pulling its weight.
- Record again, and check the time. Past ninety seconds, cut harder before the third round.
- Do three rounds total. By the third recording, it should feel like something you're saying, not reciting.
If you'd rather not count fillers by hand, practice it now — SpeakUp runs the same drill and counts them automatically.
FAQ
How long should my answer actually be?
Sixty to ninety seconds. Under a minute can feel thin. Past ninety seconds, you're repeating a point instead of adding a new one — that's the signal to stop, not the clock. Time yourself out loud at least once before the interview so you know exactly where you land.
What if I don't have an impressive project to talk about?
You don't need an impressive project — you need a specific one. A college assignment, a small freelance job, a society event: pick the one where you can say exactly what you did and what happened because of it. Specificity reads as substance even when the project is small.
Should I memorize the answer word for word?
Memorize the four beats, not the sentences. Word-for-word memorizing means losing your place can collapse the whole thing. Knowing the shape instead lets you rebuild any sentence on the fly and still sound like you.
A good sixty-second answer doesn't sound rehearsed — it sounds like someone who already knows what matters about their own story. That only happens once the four beats stop feeling like a script. Once this one is solid, HR round questions for freshers breaks down what each of the other HR-round questions is actually testing. And if your recordings keep coming back full of "um" and "basically," filler words Indian English speakers use covers which ones are worth cutting and which ones aren't fillers at all.
Practice the full set free: SpeakUp's placement interview practice.