It is often the first question in an interview, and an easy one to ramble through. This guide gives you the three-part shape, a template, 12 sample answers for different situations, and the mistakes that make it fall flat.
“So, tell me about yourself.”
Also asked as: “Walk me through your resume.” or “Introduce yourself.”
Say first: "I'm a [current role] at [company], and most of my day goes into [main work]." Before your first job: "I just finished my [course], and the part I liked most was [area]."
Reading your resume out loud, in date order, starting from school. They already have it. Run past two minutes and you risk losing the listener before you reach the part about this job.
Four short boxes. Write the way you talk. Your answer appears below as you type.
Press Start, say your answer, press Stop. Aim for 45 to 75 seconds. It is only a clock: nothing listens and nothing records.
Your pace shows here when you stop.
You can plan the first answer. The next question is the one you cannot plan, so know these three.
This page helps with the first answer. In a real call the follow-ups are different every time, and that is where people freeze. ClapAssist is a desktop app for Mac and Windows: during the video interview it listens on your computer and shows one line to say first, then the points, written from your own resume.
Try it with 10 free minutesWhat you type stays in this browser. It is saved here as a draft so you can come back, and Clear removes it.
Answer in 60 to 90 seconds with three parts: what you do now, how you got here, and why you want this role. Start with your current job or course, pick the two or three past steps that matter for this job, and end on the role in front of you. Do not tell your life story, and do not read your resume out loud.

If your interviewer says "please introduce yourself" instead, it is the same question; the self introduction guide has the shorter four-line version with samples for freshers, hotel management and teaching. That is the whole method. The rest of this guide shows what the interviewer is listening for, the exact structure, four template answers you can fill in, the mistakes that make people ramble, and how to change the emphasis between an HR round and a technical round.
Key takeaways
On this page
The question sounds casual, but it does a job. It is often the first question (Northwestern's career office notes that many interviews start with some form of it), and many interviewers use it to get a first sense of three things: can you talk about yourself in a clear order, do you know which parts of your past matter for this job, and are you interested in this role or just in any role.
They already have your resume. They do not need the dates again. They want the story between the lines: why you moved, what you got good at, and what you are looking for now. Give them that, and the rest of the interview gets easier, because they will ask follow-up questions about the things you chose to mention.
Length matters too. A very long answer can suggest you find it hard to judge how much detail a listener needs, and that is a work skill. Career centres advise keeping it short: the University of Alabama Career Center says interview answers should be no longer than two minutes.

Interviewers ask this in many ways. Treat each one below as the same question and give the same three parts.
Four wordings come up most. They want the same thing, but the order and length shift a little:
| How it is asked | Where | Order | Length |
|---|---|---|---|
| "Tell me about yourself" | Spoken, usually first | Present, past, future | 60 to 90 seconds |
| "Walk me through your resume" | Spoken, often a hiring manager | Past, present, future, a reason for each move | About the same; do not read every line |
| "Introduce yourself" | Spoken, often a campus or HR round | Present first, shorter | About four lines |
| "A little about me" | Written: forms, profiles, emails | Present, one past step, what you want | Two to four sentences |
Three parts, in this order. Present first: for many people it is the easiest thing to say when nervous, and it tells them where you are today.
Your current role or course, and the one thing you are known for in it. "I am a [role] at [company], where I mostly work on [main responsibility]."
Not everything. The two or three earlier steps that explain how you got the skills this job needs. Each one should carry a reason: why you moved, or what you learned there.
Why this role, right now. Name one thing about the job or the company that you actually want. This is the part most people skip, and it is the part that makes the answer sound like it was written for this interview.
Say: "I'm a [current role] at [company], and most of my day goes into [main responsibility]."
Then: Past: before this I was [earlier role], where I learned [skill the new job needs]. Present: this year I [one concrete project or result]. Future: I'm looking at this role because [one specific reason tied to the job description].
Say the first sentence slowly. If you get that one out cleanly, the rest follows.

This is the same order university career centres teach. Northwestern's career office calls it "Present-Past-Future": introduce yourself, give two or three examples that match the role, then say why you are excited about it or a strong fit. The American College of Financial Services uses the same three steps and says hiring managers look for a concise 60 to 90-second answer. Both are listed in the sources at the end.
Write your answer into these five lines first. Then say it out loud and change any word you would not say in real life.
1. Who you are now: "I'm a [role or student of course] at [company or college], and most of my time goes into [main work]."
2. Proof, part one: "Before this, I [earlier job, project or course], where I learned [skill the job post asks for]."
3. Proof, part two: "Recently I [one thing you did], and [what changed because of it]."
4. Why this job: "I applied here because [one real thing about this role or company]."
5. The stop: "That's the short version. Happy to go into any part of it."

Line 4 is the one to rewrite for every company. Lines 1 to 3 can stay the same across interviews for the same kind of job. The free answer builder fills the same lines in your browser if you would rather type into boxes.
The same three parts work for every job, but the facts you choose should change with the job post. Cornell's career centre suggests reading the job description for the words the employer uses to describe the person they want, and Northwestern's suggests picking two or three experiences that match the role's qualifications. In practice:
Example. A post for a junior data analyst asks for SQL, dashboards and "presenting findings to managers". A weak version says "I am good with data and a team player." A fitted version says "In my final-year project I wrote the SQL behind a sales dashboard and presented it to our department head every week", which covers all three needs in one true sentence.
Fill the brackets with your own facts. Read each one aloud once with a timer. If it passes 90 seconds, cut from the past section, not the future.
Say: "I finished my [degree] in [subject] this year, and the part I enjoyed most was [area]."
Then: Past: during the course I built [project] and did [internship or part-time work], which taught me [skill]. Present: right now I am [what you are doing: practicing, freelancing, a certification]. Future: I want to start in a [role type] job where I can [thing the job offers], and this role matched that.
Do not apologise for having no experience. Projects, internships, college work and part-time jobs all count as evidence.
Say: "I've spent [number] years in [old field], and over the last [period] I've moved my work towards [new field]."
Then: Past: in [old field] I was responsible for [thing], which gave me [skill that transfers]. Present: I've since done [course, project or side work] in [new field], including [one concrete thing you built]. Future: I'm applying here because [reason], and I think my [old-field skill] is useful for [specific problem in the new role].
The switch is the story. Say it early and say it with confidence, so the interviewer does not have to guess why your resume changes direction.
Say: "I'm a [role] with [number] years in [area], currently leading [team or project] at [company]."
Then: Past: I started in [first role] and moved into [second role] when [reason]. Present: this year my main work has been [one project with a plain result]. Future: I'm looking for [what you want next], which is why this role stood out.
With experience, the risk is length. Choose the two moves that explain your direction and leave the rest for follow-up questions.
Say: "I worked as a [role] for [number] years, and then took [period] away from work for [short honest reason]."
Then: Past: before the break I [main responsibility and one result]. Present: during the break I kept up with [skill, course, freelance or volunteer work], and I'm ready to return full time. Future: this role is right for me because [reason tied to the job].
One sentence on the gap, no more. A calm, short reason (family, health, study, relocation) is enough. Then move on to what you did and what you want. Longer explanations sound like apologies.
The templates above show the shape. These show what a finished answer sounds like. The people and companies are made up for this guide; copy the shape, not the facts. Each one takes about a minute to say at an easy pace. Time your own version, because everyone speaks at a different speed.
"I just finished my computer science degree, and the part I enjoyed most was building web apps. For my final-year project, two classmates and I built an attendance app for our college. I wrote the part that saved records, and the hardest bit was making it work when the Wi-Fi dropped, so I learned to save changes on the phone and send them later. Last summer I also did a two-month internship at a small software company, where I fixed bugs in their booking site and learned how a real team reviews code. Right now I'm practicing on small projects every day. I applied here because your job post talks about building features end to end, and that's exactly the work I want to learn first. That's the short version. Happy to go into the project in more detail."
"I've worked in customer service for three years, and right now I handle phone and chat support for an online electronics shop. Most of my day goes into orders that went wrong: late parcels, wrong items, refunds. Before that I worked at the front desk of a hotel, which taught me to stay calm when someone is angry and to fix the problem before I explain the policy. At my current job I wrote a short reply guide for the most common delivery questions, and new team members now use it in their first week. I'm looking for a role where I can keep doing support but also help train people, and your posting mentions a path to team lead. That's what drew me here."
"I'm a marketing manager with about eight years in consumer brands, and today I lead a team of four at a home-goods company. My main job is planning our launches across email, social and search. I started as a social media assistant, moved into email because I liked seeing exactly what each message did, and that's how I ended up managing the whole calendar. This year my team relaunched our weekly newsletter, and it now brings in more repeat orders than any other channel we run. I'm interested in this role because you're building a marketing team from a small base, and setting up how a team plans and measures its work is the part of my job I enjoy most."
Notice what each sample leaves out: school marks, hobbies, every job title. Each one names one result and one reason for wanting this job, then stops.
Nine more finished answers, each for a different kind of interview. As above, the people and places are made up: copy the shape, then put in your own facts. Each takes about a minute at an easy pace. Under each one is the reason it works, so you can check your own version against it.
"I'm a second-year business student, and the subject I keep coming back to is how small companies find their first customers. Last semester my team ran a project for a local bakery: we looked at where their orders came from and suggested two changes to their online menu, and they kept one of them. I also run the social media for our college's entrepreneurship club, so I write and post something every week and look at what people actually click. I'm applying for this internship because your marketing team works with early-stage brands, and I want to see how that work is done properly, with real data, before I graduate."
Why it works: an internship interviewer knows you have no full-time job. They want to see that you can already do small pieces of real work. One class project with a result and one ongoing activity are enough.

"I'm in my final year of school, and the thing I spend most of my free time on is our school's science club. Last year I led a small group that tested the water from three wells near our town, and we presented what we found at the district science fair. That project is why I want to study environmental science: I liked that the numbers meant something to people who live here. Outside the club I tutor two younger students in maths every week. I'm applying to this college because of its field-research programme in the first year. I'd like to start doing real fieldwork early, not just read about it."
Why it works: an admissions interviewer is asking who you are as a student and why this place. One activity told in some detail says more than a list of every club.
"I studied biology for my first degree, and for the last two years I've worked as a healthcare assistant on a busy medical ward. Most of my shifts are spent with patients who are scared or confused, helping them eat, move and understand what happens next. That job is where my interest in medicine became a decision: I watched the doctors explain hard news, and I wanted to be the person who could both understand the illness and explain it well. I've also volunteered at a weekend clinic, where I learned how much a short, clear conversation helps. I'm applying here because of the early patient contact in your first two years."
Why it works: in a medical school interview, the future part is "why medicine". Show it through something you saw and did, not through a statement like "I have always wanted to help people". Keep every fact one you can talk about for five more minutes, because the panel will ask.
"I qualified as a nurse this summer. My final placement was eight weeks on a surgical ward, where I looked after up to four patients a shift under supervision, from admission to discharge. The part I found I was good at was discharge: making sure patients and families knew their medicines and what to watch for at home, and I made a one-page checklist that the ward kept using after I left. Before nursing I worked in a pharmacy, which is where I got used to checking things twice. I'm applying to your surgical unit because I want to build on that placement, and your preceptorship for new nurses was the reason I chose to apply here first."
Why it works: a nursing panel listens for safe, careful practice and how you treat patients. One concrete task you did well, with the habit behind it, covers both.

"I finished school last year, and since then I've been working weekends at a family-run shop while I decide on my next course. At the shop I handle the till, restock shelves and help customers find things, and on busy days I'm often the one left in charge for an hour. I've learned to stay calm when there's a queue and to sort out a problem before it becomes a complaint. I'm applying for this trainee role because it comes with proper training and a clear path, and I want a full-time job where I can keep learning while I work."
Why it works: "no experience" rarely means nothing. A weekend job, volunteering, caring for a relative or helping in a family business all show responsibility. Say what you did and what it taught you.
"I've managed customer operations teams for six years, and today I lead a team of twelve at an online insurance company. My job is making sure claims are answered quickly and correctly, and making sure the people doing that work want to stay. I moved into management from the front line, so I still know what a hard day on the phones feels like. Last year we cut the number of claims that had to be handled twice, mostly by changing how new joiners were trained in their first month. I'm looking at this role because you're growing the team from twenty to fifty, and building how a larger team trains and works together is what I want to do next."
Why it works: for a manager, the present part is about the team, not just you. Name the size of the team, one change you led and what it fixed.

"I've taught maths for four years at a secondary school, mostly to students aged twelve to fifteen. The part of the job I care about most is the students who have decided they are bad at maths. Two years ago I started a short weekly session before school for them, built around games and real prices from local shops, and several students who joined it moved up a set the next year. I also run the school's maths club. I'm applying here because your department teaches in mixed-ability classes, and that is the kind of classroom I want to keep getting better at."
Why it works: a school wants to know what kind of teacher you are. One thing you started for a group of students shows that more clearly than a list of subjects.
"I'm in my third year of business-to-business sales, selling payroll software to small companies. My day is mostly calls with owners who have never thought about payroll software, so a lot of the job is listening first and working out what is costing them time. I started in the same company's support team, which is why I understand the product well and why customers trust my answers. Over the last year I've closed more new accounts than anyone else on my team of eight. I'm interested in this role because you sell to larger companies with longer decisions, and that's the kind of selling I want to learn next."
Why it works: sales interviewers expect a result. Give one, plainly, and add how you get it, because that is what they will ask about next.
"I'm a software tester with seven years in banking software. For the last three years I've owned testing for our mobile app's payments screens, which means I decide what gets tested before every release and I write most of the automated checks. I started in manual testing and moved into automation when I saw how much time the team lost on repeating the same checks by hand. This year I set up tests that run every night, so problems are found the next morning instead of the week before a release. I'm applying here because you're building your first automated testing setup, and that's exactly the part of my work I'd like to do again from the start."
Why it works: with years of experience, the answer is about what you own today and one change you made, not a tour of every job. The future line links your strongest skill to their need.
Sometimes the question arrives in writing: an application form with a "tell us about yourself" box, a LinkedIn "About" section, or an email introducing yourself to a new team. Use the same three parts, but shorter, and in the first person.
"I'm a data analyst with two years of experience turning sales numbers into weekly reports that managers actually use. I work mostly in SQL and Excel, and I like the moment when a messy question becomes one clear chart. I'm now looking for a team where reports feed straight into product decisions."
"Hi everyone, I'm Priya, and I joined this week as the new support lead. Before this I spent four years running customer support for a travel company. Outside work I'm usually cooking something too ambitious. I'm looking forward to meeting you all, so please say hello if you see me."
A written introduction can carry one personal line, like the cooking one above, because the reader is deciding whether you are easy to work with. In a spoken interview answer, keep it to the job. For a LinkedIn "About" section, the LinkedIn summary generator writes a first draft from your own details.
The same three parts work in both rounds. What changes is which part you make longest.

The HR interviewer is checking fit, stability and communication. Make the future part longer: why this company, why now, why you will stay. Keep technical detail to one phrase. If you have a gap or a switch, this is where to name it plainly.
The technical interviewer wants to know what you have built and what you own. Make the present part longer: your current tools, your main project, the part of it you personally did. Keep the future part to one sentence. They will use your answer to choose which problems to ask, so mention the areas you want to be asked about.
Somewhere in between. Lead with the result you are proudest of in your current role, then say why this team. A hiring manager is often filling the role to solve a current problem, so link your past to a problem the job post suggests they have.
In many interviews in India, especially campus placements and HR rounds, the question arrives as "introduce yourself" or "tell me about yourself", sometimes before any other question. The same three parts work. A few habits are worth dropping:
"I completed my B.Tech in electronics this year. In my final year I worked on a project that tracks electricity use in our hostel and shows each room's usage on a phone, and I handled the part that sends the readings to the app. During college I also did a one-month internship at a company that services office networks, where I learned how a support ticket moves from the customer to the engineer. Right now I'm improving my networking basics through an online course. I'm applying for this technical support role because it lets me start with customers and systems together, and your company trains freshers before they take calls."
The same answer works for a BPO or call centre role: keep the project to one sentence, and put more weight on the customer part and on your spoken English, because that is what the HR round listens for.
Read your answer once against this list. If something is missing, fix that line only.
The free tell-me-about-yourself builder asks for your present, past and future in plain boxes and joins them into a short answer you can edit. It runs in your browser; nothing is sent anywhere unless you press its optional "Write it with AI" button. Then say the result out loud with the AI mock interview, timer on.
A note on length. Both builders on this site, the one at the top of this page and the full tool, time your draft against 45 to 75 seconds. That is a starting draft, deliberately on the short side. Once you swap in your real project, result and reason for this job, most answers land between 60 and 90 seconds, the range career centres suggest. Under 45 seconds usually means a part is missing; over two minutes means cut from the past part first.
To make the draft yours: replace every example fact with one of your own, keep only details you can talk about for another minute if asked, and say it out loud three times on different days. Change any word you would not use in conversation. The goal is to know the three parts, not to recite the sentences.
After that, prepare the questions that usually follow: why should we hire you and what is your weakness. All three tend to arrive in the same ten minutes.
The present, past, future order and the 60 to 90-second length come from university career centres (see the sources). That is practical guidance from people who coach job seekers. It is not the result of a controlled study, and we did not find one that tested which answer length gets more job offers.

Prepare the answer with this guide, so it is yours. In the live video interview, ClapAssist listens on your own computer, reads your resume, and shows the shape of the answer: one sentence to say first, then the points. It is there so you do not freeze on the first question. It does not write your career for you, and it stays out of screen share. Some employers do not allow AI help during interviews, so check the rules for your interview and follow them.
Outside pages that back the advice above, opened and checked on the date shown.
ClapAssist is a small desktop app for Mac and Windows. It listens to your video interview on your own computer and shows an answer written from your resume, one short sentence to say first and then the points. It never joins the call and stays out of screen shares and recordings.
Career centres commonly suggest 60 to 90 seconds and no more than two minutes. A much shorter answer can leave out why you fit; a much longer one can lose the listener. If the interviewer gives you a time, use theirs. Time it once at home.
One short clause at most, and only if it links to the job. The question means your professional self.
Start with your degree and the part you enjoyed, then a project or internship as evidence, then the kind of role you want. Projects count as experience.
Almost. It asks for the same story in date order. Keep the same three parts but go past, present, future, and give a reason for each move.
Do not repeat your resume line by line, do not start from school, do not list adjectives without an example, and do not end without saying why this role.
The present and past parts, yes. Rewrite the future part for each company. It is the part that shows you prepared.
Answer their question, then return to the part you were in. That is why you memorise the three parts, not the words.
Yes. Five lines: who you are now, one earlier step and the skill it gave you, one recent result, why this job, then a short stop such as "Happy to go into any part of it." Rewrite the "why this job" line for each company.
Say what you do now in one or two sentences, then one or two past steps that matter for this job, then why you want this role, and stop. Around 60 to 90 seconds. Starting with "Sure" or "Happy to" gives you a second to breathe.
Use present, past, future, pick facts that match the job post, end on why this company, and say it out loud with a timer before the interview. Learn the three parts, not the sentences, so an interruption does not throw you.
Yes. "A little" is a hint to keep it short, so aim for the lower end, about a minute, and let them ask for more.
It is usually the same question. If they add "that is not on your resume", keep the three parts but lead with what the page cannot show: why you made a move, or what you got good at.
Both work. Present first is easier to start when nervous and is what most career centres teach. Past, present, future suits "walk me through your resume". Whichever you use, end on why this job.
It is usually written, not spoken: a form, a profile or an email to a new team. Use the same three parts in two to four sentences. One personal line is fine in writing; in a spoken interview answer, keep it to work and study.
Build the answer with the free tool, then let ClapAssist hold the shape for you in the live call.