Clear the rounds

Tell Me About Yourself: Builder + 5 Full Answers

Priya opens the call, looks at Aarav's resume for the first time in her day, and says the five words she says forty times a week: "So, tell me about yourself." She is not making conversation. She is deciding what to ask for the next twenty minutes.

11 min readFree, no email neededUpdated 11 September 2026

Before you write a word

What they are actually testing

💼

Priya opens the call, looks at Aarav's resume for the first time in her day, and says the five words she says forty times a week: "So, tell me about yourself." She is not making conversation. She is deciding what to ask for the next twenty minutes.

It is the only question where you choose the topic. Four things are being checked while you talk:

Can you organise a thought under mild pressure?Not your English. Your order. A clear beginning, middle and end in one minute.
Do you actually know what you built?Specifics survive. Adjectives ("passionate", "hardworking") tell her nothing and cost you ten seconds.
Have you read where you are applying?One accurate line about the role or the company separates you from the other 200 in that drive.
Is this a person I can sit next to for a year?Pace, warmth, and knowing when to stop talking. Rambling is the single most common fail.

Whatever you name last is what she asks next. So plant it on purpose.

The 60-second map

Four parts. Roughly 150 words. Under 90 seconds, always.

0 – 15sPresentWho you are right now, in one sentence, plus one piece of proof.

15 – 35sPastOne thing you built, what it did, one number, one thing it taught you.

35 – 50sWhy thisWhy this role and this company, named specifically, tied to what you just said.

50 – 60sCloseOne line that hands them the next question, then stop talking.

Three rules that hold the whole thing up

Never recite the resume top to bottom.They have it open. Repeating it is the fastest way to lose the room.
One project, not four.Depth is the answer. Breadth is what the resume is for.
End on a full stop, out loud.Trailing off into "…yeah, that's it" undoes a good minute.

Where the minute usually goes: most students spend 45 seconds on Present — name, college, family, school, marks — and then rush the project in eight seconds. Flip it. Present is the shortest part of the four.

Present

0 – 15 secWho you are now

One sentence for who you are, one sentence of proof. Proof is a number, a live link, a rank or a shipped thing. Not an adjective.

Say this

Final year, branch, college — in six words.

What you build, in your own words: "I build backend APIs", "I work mostly in React".

One proof, said flatly: 40 users, 300 downloads, a live link, a hackathon place, a rank.

Never say

"Myself Aarav Sharma." Say "I'm Aarav."

Family, hometown, school, date of birth, father's occupation.

"I am a hardworking person, quick learner and good team player." Zero information.

Your 10th and 12th percentages.

Fill this in

I'm name, final-year branch at college.
I mostly build what you build — right now with your main stack.
The one I'd point at is project, which what it does for number users.

If your first fifteen seconds contain no noun a recruiter can search for, start again.

Past

15 – 35 secWhat you built

The longest part, and still only twenty seconds. Pick one project or internship — your strongest — and give it a problem, a stack, a number, and one thing that went wrong.

Say this

The problem first: "hostel students kept arguing over shared bills".

What you made and with what: one line, name the stack.

One number: users, records, seconds saved, percent.

One hard part and how you fixed it. This is the line that gets you the follow-up.

Never say

A list of every project you have ever touched.

"I have knowledge of C, C++, Java, Python, HTML, CSS, JavaScript, SQL…"

"We" for everything. They are hiring you, not your group.

Anything you cannot answer a follow-up question on.

Fill this in

I built project because the problem.
It's stack, and number who used it use it.
The hard part was what broke, which I solved by what you did.

No number anywhere? Count something true today: users, rows, files, minutes saved.

Why this

35 – 50 secRole and company

Fifteen seconds that ninety percent of candidates waste. One true, specific line about the role, connected to the project you just described.

Say this

Name the role as written in the posting: "the Software Engineer, Backend role".

One real fact: a product they ship, the tech in the JD, the scale, the client work, the training programme.

Then join it: "that is the same thing I was doing on a smaller scale."

Never say

"It is a reputed company with a good work culture."

"For my career growth and to enhance my skills."

"My seniors told me it is good."

Anything about package, or about it being your backup.

Service-based (TCS, Infosys, Wipro, Cognizant, Accenture): the honest specific is the training and the breadth — many clients, many domains, structured onboarding. Say that. Product-based: name the actual product and one thing you noticed using it or reading about it.

Fill this in

I'm applying for the exact role name role because one true, specific fact,
and that is close to the thing you just described.

Close

50 – 60 secThe handover

One sentence that names the thing you most want to be asked about — then silence. The silence is part of the answer.

Say this

"That's me in short — happy to go deeper into the payment-split logic, that was the interesting bit."

"Short version done. The part I'd enjoy talking about is how I got the API down from 4 seconds to 1."

"That's the summary — I can walk through the database design whenever you want."

Never say

"Yeah… so… that's it about me." Trailing off.

"That's all about myself, thank you sir."

"Do you want to know anything else?" You are handing them work.

Nothing at all, then filling the pause with more talking.

Aarav, mock interview 1

"…and I also did a weather app, and a portfolio, and I'm learning ML also, so yeah, that's it about me."

Aarav, mock interview 4

"That's me in short. Happy to go deeper into the split logic — that's the part I'd redo differently today."

Choose the hook on purpose. Name the one thing you could talk about for five minutes with no notes. That is where the interview goes next, and you just picked it.

Five answers, written out

01B.Tech CSE, one internship58 sec

"I'm Aarav, final-year CSE at VIT Bhopal, and I work mostly on the backend — Node and PostgreSQL. Last summer I interned at a 20-person logistics startup in Pune, where I owned the driver-tracking API. It was taking about four seconds to return a route; I added indexes on two columns and cached the repeated lookups, and it came down to just under one second. That change went to production and is still running. Before that I built a bill-splitting app that about forty hostel students use, which is where I first learned that a feature nobody uses is not a feature. I'm applying for the Backend Engineer role here because the JD is Node and Postgres, which is exactly the stack I've been shipping on. That's me in short — happy to go deeper into the caching part, that's the bit I'd do differently now."

Why it works: one internship, one number, one honest lesson, and the stack named twice so she remembers it.

02No internship, three projects60 sec

"I'm Riya, final year IT at MIT Aurangabad. I haven't done an internship — I spent those months building instead, and three projects came out of it. The one I'd point at is a college notice-board bot on Telegram: notices used to go up on a board nobody checked, so I scraped the portal and pushed them to a channel. About 300 students are on it and nobody's missed a notice in five months. It's Python, and the hard part was the portal logging me out every hour, which I fixed with a session refresh. I'm here for the SDE role because the work you've described is internal tooling, and that's exactly what I've been doing on my own. That's the short version — I can show you the bot running on my phone if that's useful."

Why it works: names the gap in half a second, then never mentions it again. Proof replaces the title.

Answers 3 and 4

03Branch change: Mechanical to software60 sec

"I'm Karan, final-year Mechanical at COEP. I moved to software in my second year and I've been consistent about it since — around 500 problems on LeetCode and two projects that are live. The main one is a workshop inventory tracker I built for our department: they were tracking 1,200 tools on paper and losing about ten a semester. It's a React front end with a Node API and Postgres, and it cut the monthly stock-check from two days to about an hour. The hard part was designing the schema for tools that get issued and returned, which taught me more about databases than any course did. I'm applying here because the role is full-stack product work and my degree is not the thing I want to be judged on — the code is. That's me — happy to walk through the schema."

Why it works: owns the switch in one clause, gives a date, then buries it under evidence. Never apologises for the branch.

04A cleared backlog58 sec

"I'm Aditya, final-year CSE at a Pune college, CGPA 6.9. I had one backlog in third semester in Engineering Maths, and I cleared it in the next attempt — that year I was also handling something at home, and after it I fixed how I study rather than how much. Since then I've built two things I'm proud of: an attendance app our class of 68 actually uses, and a REST API for a local gym with login and billing. Both are Java and Spring Boot, both are on GitHub with the commit history to show. I'm applying here because the training programme is structured and the work is Java, which is what I've spent two years on. That's the short version — the API is the one I'd like to talk through."

Why it works: states the backlog before they find it, one line of context with no excuse, then "cleared" and forward.

Answer 5, then yours

05Targeting service-based (TCS, Infosys, Wipro)60 sec

"I'm Sneha, final-year IT at SRM, CGPA 8.1, no live backlogs. I'm comfortable in Java and SQL, and I've built two projects end to end. The stronger one is a library management system for our department — 4,000 book records, issue and return, fine calculation. Java, MySQL, and I wrote about 30 queries for it, which is where I actually learned joins properly rather than from a textbook. The hard part was handling two people issuing the same copy at once, which I solved with a transaction. I'm interested in this role because the first year is structured training across real client projects — I want to see several domains before I decide what I'm good at, and that's hard to get anywhere else. I'm also fine relocating anywhere in India. That's me — happy to go into the query side."

Why it works: CGPA and backlog status stated up front (they will ask), a real reason for wanting service-based, and relocation answered before it is asked.

Make it yours in 20 minutes

5 minPick the closest answer above. Swap in your name, college, project and stack.

10 minReplace every number with a true one. Estimate honestly if you must.

5 minRead it aloud with a timer. Over 90 seconds, cut the second project.

The part everyone skips

How to say it out loud

A perfect answer said at 200 words a minute sounds memorised. Memorised sounds like hiding.

Aim for 140 words a minute. 60 seconds is about 150 words.Paste your answer into any word counter. Over 200 words, cut — do not speed up.
Breathe in three places, on purpose.After your opening line. After the number. Before "I'm applying here because". It sounds like thinking, not stalling.
Slow down on numbers and names."Four seconds to under one second" and the company name are the two bits she writes down. Give them room.

Memorise three lines. Keep the rest loose.

Line 1Your opening sentence, word for word. It kills the first-ten-seconds panic.

The numberThe one metric in your project line, exactly as you will say it.

The closeYour last sentence, word for word, so you always land instead of trailing off.

The drill: record it on your phone three times, listen once, fix the one word you stumble on. Ten minutes a day for three days. If you blank: say "Let me start with what I'm working on right now" and go to the project. Never apologise, never restart.

Want this on your phone?

Everything above, as a PDF built to read on a phone the morning of the interview. It costs nothing — we ask for an email so we can send it, and that is all.

Get the PDF, free See every guide