Interviews · 7 min read

How to answer "tell me about yourself"

The short answer

Answer "tell me about yourself" with a 60 to 90 second professional summary in three parts: what you do now and at what level, the past experience that makes you relevant to this role, and why this particular role is your logical next step. Keep it focused on work, choose details that match the job, and end in a way that invites the next question.

By Chanuka Jeewantha · Published · Updated

"So, tell me about yourself" is often the first question in an interview, and it is deceptively open. Candidates who treat it as small talk tend to recite their CV from the beginning, or drift into personal history that the interviewer did not need. Candidates who prepare it properly use it to set the agenda for the whole conversation. It is the one question you can be almost certain will come up in some form, which makes it the most worthwhile two minutes of preparation you can do.

What the question is really asking

The interviewer is not asking for your life story, and they are usually not testing whether you remember your own CV. They are asking you to explain, in your own words, who you are professionally and why you are sitting in front of them. They are also listening to how you communicate: whether you can summarise, prioritise and speak with some confidence about your own work.

There is a practical purpose too. Your answer gives the interviewer threads to pull on. Whatever you mention first, and with the most energy, is often what they ask about next. That means a well-planned answer does more than make a good first impression. It steers the next part of the interview towards your strongest ground.

It is also the moment the interviewer settles into the conversation. They may still be glancing at your CV or finishing notes from the previous candidate. A clear, well-paced opening helps them tune in, and a strong first minute tends to colour how the rest of the interview is heard.

A structure that works: present, past, future

The simplest reliable structure has three parts, delivered in about 60 to 90 seconds. Longer than two minutes and most interviewers start to lose the thread.

Some people prefer to start with a brief past and then move to the present and future. That works too, especially for shorter careers. What matters is that the answer moves in one direction and finishes on why you are in this room, rather than trailing off after a description of your current job.

  • Present: what you do now, at what level and in what kind of organisation. One or two sentences, ideally with a concrete detail about scope or focus.
  • Past: the experience that led you here and that is most relevant to this role. Choose two or three highlights, not every job, and include one achievement with a result.
  • Future: why this role, at this organisation, is the logical next step. Connect what you have done to what they need, so the answer ends on the job rather than on you.

Example answers for different situations

An experienced professional might say: "I am a finance manager at a mid-sized logistics company, where I run the monthly close and the budgeting process for four business units. Before that I spent five years in audit, which is where I learned to find problems in numbers quickly. In my current role, the change I am proudest of is rebuilding the close process, which brought our reporting forward by several days. What draws me to this role is the chance to do that kind of work at a larger scale, with the systems migration you mentioned in the posting."

A graduate might say: "I have just finished a degree in computer science, where I focused on data and backend development. My final-year project was a booking system for a local sports club that is still in use, and last summer I interned at a software consultancy, mainly writing and testing APIs. I enjoy the part of the work where you make something reliable for real users, which is why a junior backend role on a product team like yours appeals to me."

A career changer might say: "For the past eight years I have been a secondary school teacher, and for the last three I also led training for new staff across the school. That part of the job, designing programmes and seeing adults build skills, turned out to be what I enjoyed most. I completed a certificate in learning design this year and have built two e-learning modules for a charity as a volunteer. I am applying for this learning and development role because it is the work I have been moving towards deliberately, not a leap away from teaching."

Each of these is short, each contains at least one concrete detail, and each ends on the role. None of them starts with where the person was born or went to school.

What to leave out

The fastest way to improve most answers is to remove things. These are the elements that most often weaken an otherwise sound answer:

Removing filler also makes room for one thing many candidates avoid: naming what you are good at. A sentence such as "my strength is turning messy data into reporting that managers actually use" is not boasting if the rest of the answer backs it up. It gives the interviewer a clear idea to remember you by.

  • A chronological walk through your entire CV, starting with your first job.
  • Personal details such as family, age, hometown or hobbies, unless they genuinely connect to the role and you choose to share them.
  • Generic self-descriptions like "hard-working, passionate and a great team player", which every candidate uses and nobody remembers.
  • Complaints about your current employer or reasons you are unhappy there.
  • Salary, benefits or flexibility. These are legitimate topics, but not in your opening answer.
  • Anything you would not be comfortable being asked about in detail, because the interviewer may well follow up on it.

Adjusting for the interviewer and the format

The same core answer should flex depending on who is asking. A recruiter or HR screen is often checking basic fit: level, motivation, salary range and notice period in later questions. Keep your answer clear and slightly broader. A hiring manager wants to know whether you can do the job, so lean further into relevant results and the specific problems you have solved. A panel may include people from different functions; a line that shows you understand how your work affects other teams tends to land well there.

Video interviews reward brevity even more than face-to-face ones, because it is harder to read the interviewer's reactions and easier to talk past the point where they have heard enough. Aim for the shorter end of the range and look at the camera rather than your own image. If you are interviewing in a second language, keep your sentences short and prepare the key phrases carefully; clarity matters far more than sophisticated vocabulary.

Variants of the question need the same treatment. "Walk me through your CV" invites a slightly more chronological answer, but still with emphasis on the relevant parts. "Why are you interested in this role?" is essentially the future section expanded. Prepare the core once and you can adapt it to all of them.

Practising without sounding rehearsed

Write your answer out once, in full, to get the content right. Then reduce it to a few bullet points: the present sentence, two or three past highlights and the link to this role. Practise speaking from those notes rather than from the full text. The aim is to know what you will say without knowing exactly how you will phrase it, which keeps it natural.

Record yourself once and listen back. Most people find their first version is longer than they thought, and that they bury the most interesting point in the middle. Move the strongest detail earlier. Cut any sentence that does not help the interviewer understand why you fit this role. If nerves tend to make you speed up, plan a natural pause after the present section. It gives the interviewer a moment to absorb who you are before you explain how you got there.

Finally, make sure your answer and your CV tell the same story. If your CV profile describes you as a data analyst focused on commercial reporting and your spoken answer describes you as a general IT professional, the interviewer notices the mismatch. The best answers sound like a spoken, more personal version of the top third of your CV, which is exactly what they should be.

The short version

  • Treat "tell me about yourself" as a 60 to 90 second professional summary, not a life story.
  • Use present, past, future: what you do now, what makes you relevant, why this role is next.
  • Include at least one concrete achievement and end the answer on the role.
  • Leave out personal details, generic adjectives and complaints about your employer.
  • Practise from notes, not a script, and keep the answer consistent with your CV.

FAQ

Frequently asked questions

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

Aim for 60 to 90 seconds, and no more than two minutes. That is long enough to cover what you do now, the most relevant parts of your background and why you want this role. Longer answers tend to drift into a full CV recital, and interviewers often stop listening closely once they have the main picture.

Should I talk about personal life when asked to tell me about yourself?

Usually no, or only briefly. The question is about you professionally, so focus on your work, your relevant experience and why you are applying. A short personal detail can work if it connects to the role or you are comfortable sharing it, but family, age and hometown are generally better left out of an opening interview answer.

How do I answer "tell me about yourself" as a graduate with no experience?

Use the same present, past, future structure with the experience you do have. Start with your degree and focus, highlight one or two projects, internships, part-time jobs or society roles with a concrete outcome, and finish by explaining why this role is the natural next step. Specific academic or project work is more convincing than general enthusiasm.

Is "walk me through your CV" the same as "tell me about yourself"?

They are closely related. "Walk me through your CV" invites a slightly more chronological answer, but you should still emphasise the roles and achievements most relevant to the job and move quickly through the rest. Use the same prepared core, keep it to around two minutes, and finish by explaining why this position is your logical next step.

Rather have it written for you?

Build your package, choose your level and delivery speed, and see the price before you commit.

Build Package