Tell Me About Yourself: Full Sample Answers by Situation

"Tell me about yourself" is the first question in almost every interview in India — technical, HR, telephonic, or walk-in — and most candidates lose the interviewer's attention in the first 20 seconds because they either recite their resume line by line or launch into a life story that starts from Class 10. The fix is a simple structure: Present, Past, Future. Say what you do or study right now, the one or two things in your past that are relevant to this specific role, and where you want to go next. Done well, this takes 60–90 seconds. Below are complete sample answers for four situations, plus the structure and mistakes to avoid.

The structure that actually works: Present, Past, Future

Interviewers ask this question to see if you can organize information about yourself without being prompted — it's a proxy for how you'll explain a project status update or a bug postmortem later. The Present-Past-Future structure solves this in three moves:

• Present: Who you are right now — your course/role, year, and one number that anchors it (CGPA, years of experience, team size).
• Past: The one or two experiences most relevant to the job you're interviewing for — not everything you've ever done.
• Future: What you want next, phrased as something this specific role gives you — never a generic "I want to grow," always tied to the JD.

Keep it under 90 seconds spoken aloud. Practice it out loud with a timer at least five times before the interview — reading it silently in your head will always feel shorter than it actually is when spoken.

Full sample answers for four situations

Situation 1: Fresher with no internship

"I'm a final-year Computer Science student at [college], graduating in 2026 with a CGPA of 8.2. Since I didn't land a formal internship, I used the last two years building things on my own — I built a full-stack college event management system using React and Node that's deployed and used by our department, and I completed a certification in DBMS and SQL where I scored in the top 5% of my batch. I also spent six months as a core member of our coding club, where I ran weekly DSA sessions for juniors, which forced me to get sharper myself. I'm now looking for a role where I can move from building solo projects to contributing to a live codebase with a team, and grow into someone who can own a feature independently within the first year."

Situation 2: Fresher with an internship

"I'm a final-year B.Tech student, and I completed a 3-month internship at [company] as a QA and automation intern, where I wrote over 60 automated test cases using Selenium and reduced manual regression testing time for their release cycle by roughly 40%. Before the internship, I'd already taught myself Python and basic automation through online courses, which is part of why I could start contributing meaningfully by the second week instead of spending the whole internship just learning the tools. I'm now looking for a full-time QA or SDET role where I can go deeper into test architecture rather than just writing individual test cases."

Situation 3: One year of experience, switching jobs

"I've been working as a Software Engineer at [company] for the last 14 months, mainly on their customer-facing dashboard in React and TypeScript. I started by fixing UI bugs and gradually moved to owning a full feature — a notifications center — from wireframe to production, working directly with the design and backend teams. I'm looking to move now because I want to work on a product with a larger user base and more complex state management than what I currently touch, and this role's focus on [specific thing from the JD] is exactly the direction I want to grow in."

Situation 4: Service company to product company switch

"I've spent the last year and a half at [service company], working on a supply chain client's inventory module in Java and Spring. I've delivered four production releases on schedule, and I became the person my team relied on for a tricky legacy integration that nobody else wanted to inherit. I'm moving toward product companies now because I want to own a product over years instead of rotating between client engagements every few months, and get closer to real user feedback instead of a client's change requests. I've been actively closing the gap — I've built a side project using the same stack your team uses, specifically to shorten my ramp-up here."

What to leave out

Common mistake	Why it fails	What to do instead
Starting from school/Class 10	Wastes time on information the interviewer doesn't need	Start from your current course or current job
Listing every project or skill	Sounds like a resume read aloud, not a person talking	Pick 1–2 items most relevant to this specific role
No connection to the job you're applying for	Makes the interviewer do the work of connecting dots	End with a "future" line tied directly to the JD
Going over 2 minutes	Signals poor self-editing and time awareness	Time yourself; cut ruthlessly to under 90 seconds
Memorized, flat delivery	Sounds robotic; invites harder follow-up questions	Know the structure, not a script — vary the wording each time

Handling the follow-up questions

A good "tell me about yourself" answer invites follow-ups — that's the point, it opens doors instead of closing the conversation. Be ready for: "You mentioned X project, walk me through the hardest bug you hit in it." "You said you want to grow into Y — what have you done about that already?" "Why that specific certification and not something else?" If your answer mentions something you can't defend in detail, cut it. Every sentence in your answer should be something you're happy to go three questions deep on.

Common variations of this question

Interviewers rarely ask it in exactly these words, and each variation shifts what you should emphasize:

• "Walk me through your resume" — More chronological than "tell me about yourself." Go in order, but still spend the least time on the oldest, least relevant entries.
• "Introduce yourself in one line" — A stress-test of your ability to compress. Have a single sentence ready: role/course + one standout number or achievement.
• "What should I know about you that's not on your resume?" — Skip the Present-Past-Future structure here; give one specific trait or habit with a quick example, not a summary of your CV.
• "So, tell me something about yourself" (as an opener, informally) — Slightly shorter and more conversational than the formal version; 45–60 seconds is enough, and it's fine to smile and keep it lighter in tone.

Whichever version you get, resist the urge to give the exact same rehearsed paragraph regardless of phrasing — interviewers notice when an answer doesn't actually respond to what they asked.

Why interviewers keep asking this even though everyone prepares for it

Candidates assume this question is a formality now that everyone knows it's coming, so the honest, well-structured answers stand out more than they used to, not less. Most people either over-prepare into a stiff monologue or under-prepare into a rambling one — both are easy to spot in the first 30 seconds. An answer that sounds like you're actually talking, with natural pauses and specific numbers instead of vague adjectives ("passionate," "hardworking," "dedicated"), does more work for you here than in almost any other part of the interview, because it sets the interviewer's first impression of how you'll communicate on the job — in stand-ups, in status updates, in client calls.

How this answer should change based on the company

Don't use one fixed script everywhere. For a service company like TCS or Infosys hiring in bulk, emphasize consistency, adaptability across projects, and willingness to learn a new stack — see how TCS structures its interview rounds and what Infosys looks for across its SP, DSE, and SE tracks for what each actually screens for. For a product company or startup, emphasize ownership, specific technical depth, and impact metrics. The Present-Past-Future skeleton stays the same; only the "future" line and which past experience you lead with should change.

Where this fits in the rest of the interview

This question sets the tone for everything after it. If you lead with a project, expect the next 10 minutes to be technical questions on that project — only mention things you can defend. If you lead with a leadership or team experience, expect behavioral follow-ups. Once you're through this opening, the rest of the round typically moves into the standard set of HR interview questions around strengths, weaknesses, and salary expectations — have those ready before you walk in, not after this question catches you off guard.

FAQ

How long should my "tell me about yourself" answer be?

60–90 seconds spoken aloud. Time yourself with a stopwatch while practicing — most people run 30–40% longer than they think.

Should I memorize my answer word for word?

No. Memorize the structure and the 3–4 key points, but let the exact wording vary slightly each time you say it — word-for-word delivery sounds rehearsed and brittle under follow-up questions.

What if I have nothing impressive to say as a fresher?

You don't need something impressive — you need something specific. A small project you can explain in detail beats a vague claim about "strong communication skills" every time.

Should I mention hobbies or personal interests?

Only if you have time left after the professional part and it's genuinely relevant — one line at most, and only if it adds something (e.g., you run a tech blog, you've placed in a hackathon).

Is it different for a telephonic or video interview?

The content stays the same; keep it slightly shorter for phone screens since attention drops faster without visual cues, and speak a touch slower than feels natural on video.

What should the very last line of my answer be?

A forward-looking line connecting what you want next to what this specific role offers — never end on a flat description of your past.