How to Answer "Tell Me About Yourself" in an Interview (Freshers and Experienced)

"Tell me about yourself" is usually the first question in an interview, and it is also the one people prepare worst. Most candidates either recite their resume line by line or start with where they were born. Neither helps the interviewer. What they actually want, in roughly two minutes, is this: who you are professionally right now, what you have done that is relevant to this job, and why you are sitting in front of them.

If you remember only one thing from this guide, make it that order: present, past, next. Where you are now, what got you here, and why this role is the logical next step.

Why interviewers ask it at all

It is not small talk. A recruiter or hiring manager uses your answer to decide what to ask next. If you mention that you automated a weekly report in Excel, expect a follow-up on how. If you say you handled 60 calls a day in a support process, they will probe how you dealt with angry customers. So in a real sense, you are choosing the direction of the interview. That is the biggest reason to plan this answer instead of winging it.

It also tells them how you communicate. A tight, confident answer suggests you can explain things to a client or a manager. A five-minute ramble suggests the opposite, even if your experience is strong.

A simple structure that works for freshers

If you have no full-time experience, your "present" is your degree and whatever you did around it. Keep family background, hobbies and school marks out unless they connect to the job.

• Present: "I'm a final-year B.Com student at ___, and over the last year I've focused on accounting and Excel-based reporting."
• Proof: one or two concrete things. An internship, a project, a part-time job, a college event you ran. Say what you did, not just that you were "part of" it.
• Next: "That's why this accounts executive role interests me. It's the kind of work I've enjoyed most, and I want to get better at it in a real finance team."

A sample for an IT fresher might sound like this:

"I'm a computer science graduate from ___, batch of 2026. Most of my practical work has been in backend development. My final-year project was a small attendance system built with Python and Django, and I handled the database design and the APIs. I also did a two-month internship where I fixed bugs in an internal tool and wrote test cases. I enjoy the problem-solving side of backend work, which is why this junior developer role stood out to me."

Notice what is missing: no "I am a hard-working, passionate, quick learner." Every candidate says that. Show it through the example instead.

For experienced candidates

With three, five or ten years of work, the risk flips. You have too much to say. Pick the thread that matches the job description and leave the rest for later questions.

Open with your current role and scope in one line ("I'm a senior sales executive at ___, handling B2B accounts in the Pune region"). Then give one or two results that matter for the new role, ideally with numbers you can back up. Close with why you are looking now, in neutral terms. "I'm looking for a role with larger accounts" lands far better than anything about your current manager. If the "why are you leaving" part tends to trip you up, our guide on answering why you're leaving your current job goes deeper.

If you have changed fields, say so early and own it: "I spent four years in mechanical design before moving into software testing two years ago." Interviewers get suspicious when a switch is hidden and only comes out under questioning.

Mistakes that quietly cost people the job

• Reading the resume aloud. They have it in front of them. Add context the resume can't show.
• Going past three minutes. Practise with a timer. Around 90 seconds to two minutes is a comfortable target for most interviews.
• Personal details nobody asked for. Marital status, father's occupation, native village. In most private-sector interviews this adds nothing and can invite bias.
• Memorised word-for-word scripts. They sound flat, and if you lose one line you lose the whole thing. Memorise the three points, not the sentences.
• Mentioning something you can't explain. If "machine learning" is in your answer, be ready for two technical questions on it.

Adjust it for the type of interview

On a short recruiter screening call, a 60-second version is enough. They mostly want to confirm you match the basics, and they will often move on to notice period and expected salary quickly (our guide on recruiter screening calls covers that part). With a hiring manager, spend more of your time on the work itself. In an HR round, a line on how you like to work and what kind of team suits you can fit naturally.

Video interviews and AI-screened rounds are now common at the first stage, and the same structure works there. The only difference is that you can't read the interviewer's reaction, so being concise matters even more. See how to prepare for an AI interview round if that is your situation.

How to prepare in one evening

Open the job description and underline the three things they clearly care about most (see how to read a job description if it's unclear). Pick one example from your experience for each. Write your present-past-next answer in bullet points, not sentences. Say it out loud five or six times, once while recording on your phone. Listen back. Most people are surprised by how long they take and how often they say "basically".

Then prepare a slightly different version for each type of role you apply for. A sales role and an operations role at the same company should not hear the same answer.

It feels like a throwaway question, but it is the one part of the interview you can fully control. Get it right and the rest of the conversation tends to follow your strengths rather than your gaps.