"Tell me about yourself": a template and four sample answers to practise out loud
The interviewer is not asking for your life story. They are asking: who are you professionally, what have you done that proves it, and why are you here? Answer in four parts, in 60 to 90 seconds, then say it out loud until it sounds like you talking.
What the question is really asking
It is usually the first question, so it sets the tone for everything after it. A good answer gives the interviewer three things: a one-line summary of who you are, one concrete piece of proof, and a reason you want this job in particular. Everything else in your CV can wait for their next question.
The shape that works for almost everyone:
- Present: your role and the one thing you do that matters for this job.
- Proof: one result, with a number if you have one.
- Past, briefly: how you got here, in one or two sentences.
- Future: what you want next and why it is this role.
How long should it be?
Our advice: 60 to 90 seconds. At a conversational 140 words per minute that is about 140 to 210 words. Write yours below and the length updates as you type, at the pace you choose. To time a real run-through, use thespeech timer; to check your pace and filler words after you record, thespeaking speed test.
The template
Replace every [bracket] with your own words. Aim for 60 to 90 seconds.
Opens your answer in the free teleprompter. The text travels in the link and is never uploaded.
Four sample answers
The people and companies in these answers are made up. Use them for the shape and the rhythm, not the facts. Each button opens the answer in ourfree teleprompter, which follows your voice as you read, so you can practise saying it rather than reading it.
Recent graduate, first full-time job
Sure. I finished my degree in business administration this summer, and I spent the last year of it working two days a week at a small logistics company, mostly on the customer support desk. That job taught me more than any module did. I handled about forty tickets a day, and I noticed most of them were the same three questions, so I wrote a short help page for each one. Within a month the ticket volume dropped by roughly a quarter, and my manager asked me to keep going. Alongside that, my final project looked at how small warehouses schedule deliveries, which is where I found out I enjoy turning a messy process into something simple. I'm looking for a first full-time role where I can do that properly, on a team that lets juniors own a problem from start to finish. That's what stood out about this operations coordinator position.Practise this out loud →
Experienced, same field, bigger role
I'm an operations manager with eight years in food manufacturing, the last four at a mid-sized bakery group where I run two production sites and a team of about sixty people. The work I'm proudest of there is the changeover project. Switching a line from one product to another used to take ninety minutes. We mapped every step with the operators, moved the tooling closer to the line and built a simple checklist. Changeovers now take under forty minutes, which gave us back about two production hours a day without new equipment. Before that, I spent four years as a shift supervisor at a dairy plant, where I learned that most quality problems start with a handover nobody wrote down. What I'm looking for now is a role with responsibility across more than one region, and a company that is still growing. This head of operations position is exactly that, and the plan to open two more sites next year is the part I'd most like to be involved in.Practise this out loud →
Career change, teacher to UX designer
I'm a UX designer who came to design after seven years as a secondary school teacher, and I think that background is my biggest asset. Teaching is a design job in disguise. Every lesson is a product for thirty people with different needs, and you find out within minutes whether it works. I ran the school's move to a new online homework platform, and I rewrote the student-facing pages because nobody could find anything. Complaints from parents dropped to almost none within a term. That project is what pushed me to retrain. Over the past eighteen months I've completed a UX certificate and designed three products with real clients, including a booking flow for a community sports centre that cut abandoned bookings by about a third. I'm now looking for my first full-time design role on a team with an education or public-service product, where knowing the users from the inside really counts. That's why I applied here.Practise this out loud →
Student applying for an internship
I'm a second-year computer science student, and the thing I enjoy most is building small tools that people actually use. Last term, our student society kept losing track of who had paid for events, so I built a sign-up and payments page over a weekend. About two hundred students have used it since, and the treasurer told me it saved her a few hours every week. That taught me how different it feels to maintain something real, with bugs reported by people you know, compared with a graded assignment. Outside of that, I'm a teaching assistant for the first-year programming course, which has made me much better at explaining a problem simply. I'm applying for this internship because I'd like to work on software at a scale I can't reach on my own, with engineers who review code properly. The mentoring programme in your description is the part that made me apply.Practise this out loud →
Five mistakes to avoid
- Starting at school. Begin with the present. The past gets one or two sentences, later.
- Reciting the CV. They have it in front of them. Pick one result and tell it properly.
- No number. "Improved the process" is a claim; "cut changeovers from ninety minutes to forty" is proof.
- Leaving out the "why here". Without it, the answer could be for any job. One specific reason is enough.
- Running long. Past two minutes the interviewer is waiting. Practise with the timer until it fits.
How to practise it
- Fill in the template in the words you would actually say. Contractions are fine; that is how you talk.
- Open it in the teleprompter and read it out loud three times. The text waits when you pause, so you can take your time.
- Record one take on your phone or webcam and watch it back once. Notice where you sped up or looked away.
- Close the script and say it from memory. If a line will not come, rewrite it shorter; it was never yours.
Frequently asked questions
How long should "tell me about yourself" be?
Aim for 60 to 90 seconds, which is about 140 to 210 words at a conversational 140 words per minute. Under a minute sounds thin; over two minutes and the interviewer is waiting to ask the next question. Use the length check above to see where your answer lands at your own pace.
Should I memorise my answer word for word?
Memorise the shape (present, proof, past, future) and the one number you want them to remember, not every word. Practise it out loud until you can say it slightly differently each time. If it comes out identical every time, it sounds recited.
Can I read it from a script in a video interview?
Practise with the teleprompter until you no longer need it. In the interview itself, a few bullet points under the camera lens are fine; a full script read aloud is noticeable, because your eyes move and your voice flattens. The teleprompter is for rehearsal, so the answer is in your head on the day.
Is "tell me about yourself" the same as "walk me through your CV"?
Nearly. "Walk me through your CV" asks for the sequence; "tell me about yourself" asks for the story. Both want the same four parts. For the CV version, spend a little longer on the past and keep it in order.