How to answer “Tell me about yourself”
The most common opening question is also the one people prepare for least. A simple structure, three worked examples and a way to practise it.
Answers
In this article
Many interviews begin with the same request: “Tell me about yourself.” It sounds like small talk, so people either improvise or recite their CV from the first job to the last. Both waste the best opening of the whole conversation. The question is not a test of memory. It is an invitation to choose what the interviewer should know about you, before they start choosing for themselves.
What the interviewer is really asking
They have your CV open already, so they do not need it read aloud. What they want is a short, confident summary that answers three quiet questions: who are you professionally, why does that fit this role, and can you organise your thoughts and talk about yourself clearly? It also gives them something to follow up on, so the first minute often decides where the next twenty go.
That is good news. It means the question is one of the few you can fully prepare, because you know it is coming and the material is entirely yours.
A simple structure: present, past, future
Present: what you do now
One or two sentences on your current role, or your current situation if you are between jobs or studying. Include the scope, such as the kind of work, the kind of team or the main area you are responsible for. Start here, not with your birth town or your first job.
Past: the experience that matters most
Pick one to three moments from your history that support this particular role, and say what you did and what came of it. This is where you leave things out. A career has far more material than a minute can hold, and the skill is in the choosing.
Future: why this role
End by connecting the two. Say what you are looking for next and why this job, this team or this kind of problem is the logical next step. A good closing sentence hands the conversation back to the interviewer, because it finishes on something they can respond to.
The order matters. Present first gives the listener a frame, the past supplies evidence, and the future explains why you are in the room. If you finish on your history, the answer sounds like a goodbye to your old job rather than a reason to hire you for the new one.
Three worked examples
These answers are invented for illustration. Do not copy them; notice how each one follows the same three steps and still sounds like a different person. Read them aloud, and each takes roughly a minute.
Example 1: a junior candidate
Little work history is not a problem if you use the past step for projects, studies and volunteering, which are real evidence too.
I have just finished a degree in statistics and I am looking for my first role as a data analyst. During my final year I built a project on public transport data, cleaning three years of delay records and showing which lines were late most often. I presented it to a small group of students and teachers, and I learned how much of the work is explaining the result clearly. I also spent two summers working in a shop, which taught me to stay calm with people who are in a hurry. I am looking for a team where I can learn from experienced analysts and where the data is used for real decisions, which is why this role interested me.
Example 2: a career changer
For a changer, the past step is a bridge. Name the skills that carry over, and say plainly why you are changing.
For the last six years I have been a secondary school teacher, and for the past year I have been training as a UX designer in the evenings. Teaching gave me the skills this role depends on: explaining something complicated to people with very different needs, noticing quickly when something is not working, and changing my approach. Last year I redesigned the way our school collects homework, working with students and parents, and I turned that into the first piece in my portfolio. I want to move into product design because I enjoy solving problems for real users, and your team's focus on education tools is the place where my two backgrounds meet.
Example 3: a senior candidate
Seniority means more to choose from, so the answer must be tighter, not longer. Lead with scope and one result, not a list of employers.
I am an engineering manager. For the last five years I have led a group of twelve engineers who run the payment systems of a mid-sized retailer. Earlier I worked as a developer and a tech lead, so I know the work from the inside. The thing I am proudest of is rebuilding our release process, so that a deployment that once needed a full day of preparation became a routine event, and the team took on larger projects with less stress. I am now looking for a bigger scope, ideally a company where engineering leads are involved in product decisions, and that is what I understood about this role.
NoteNotice what all three have in common
Each starts with the present, picks one or two strands of evidence, mentions a result or a lesson, and ends with a reason for this job. None of them mentions age, family or health. You are not required to offer any of that, and it is fine to keep the answer about work.
How long it should be
Aim for 60 to 90 seconds. That is roughly 150 to 220 words at a calm speaking pace. It is a practical rule of thumb, not a law. Under 45 seconds can sound like you have nothing to say, and beyond two minutes the listener starts to lose the thread. If the interviewer wants more, they will ask, and that is the best possible outcome, because you then talk about what they chose.
Time yourself the first time. Most people are surprised twice: how long a two-minute answer feels from the inside, and how short ninety seconds is on paper.
Common mistakes
- Reciting the CV. The interviewer can read it. Add what the page does not say: the reason behind your choices and what you are proud of.
- Starting too early. “I was born in…” or a school you attended fifteen years ago uses your minute on the least relevant material.
- Getting personal by accident. A short, human detail is fine, for example a hobby that shows curiosity. Family situation, health or politics are not needed and are best left out.
- Apologising in advance. “I do not have much experience, but…” tells the listener what to think. Say what you have done instead.
- Giving the same answer to every employer. A reusable answer sounds reusable. Change the final third at least.
- Speaking in generalities. “I am a hard-working team player” could describe anyone. A specific detail, such as the project or the result, is what makes the answer yours.
- Memorising it word for word. A script breaks at the first interruption. Know the three beats and the key facts, and let the sentences vary.
Tailor it to the job posting
The present and past stay mostly the same; the choice of evidence and the future part change with the role. Read the posting the way described in how to prepare for one specific job posting: find the two or three things it asks for most often, then check which of your own experiences prove them.
- Write down the top two or three priorities of the role, in the posting's own words.
- Pick the one or two experiences from your history that best prove them.
- Use those as the past step and leave out anything that does not help.
- Finish with a reason that refers to something real about the job, such as the kind of problem, the product or the team. Do not praise the company in general terms.
Keep one core version of the answer and three or four interchangeable endings. That is faster than writing a new answer for each application, and it keeps your facts consistent.
TipLeave a thread to pull
Mention one result or story in a single sentence and do not explain it fully. A good interviewer will often ask about it, and you can then answer with a prepared example, for instance in the STAR format.
How to practise it
This is one of the best questions to practise aloud, because it is short, certain and the same every time. Reading it silently tells you very little; the sentences only reveal their problems when you say them. The routine in how to practise interview answers out loud fits it well:
- Write the three parts as short bullet points, not as a script.
- Set a timer for 90 seconds and say the answer out loud while recording yourself.
- Listen back and write down one thing to change: a slow start, a long middle, a vague ending.
- Say it again with only that change. Then stop.
- Repeat on another day, and once with a friend who will tell you where they lost the thread.
After the answer, the interviewer often turns to you. Having a few good questions ready helps there too, and questions to ask the recruiter is a good place to start.
A final thought: the answer is not meant to impress with polish. It is meant to be clear, true and about you. If you can say, in a minute and a half, what you do, what you have done and why you want this job, the first question has already gone well.
