"Tell Me About Yourself": How to Answer (With 7 Examples)

"So, tell me about yourself." It is the most common opening line in job interviews, and it is also one of the most frequently fumbled. Candidates either recite their entire CV from school onwards or freeze and say something vague like "I'm a hard worker who loves challenges". Neither answer helps the interviewer, and neither helps you.

The good news is that this question is completely predictable. You know it is coming, which means you can prepare an answer that is clear, relevant and around 60 to 90 seconds long. This guide gives you a simple structure, explains what interviewers are really listening for, and walks through seven example answers you can adapt.

What the interviewer is really asking

The question sounds personal, but it is almost never an invitation to talk about your hobbies or childhood. Interviewers use it for three practical reasons:

• To hear your professional story in your own words. Your CV lists facts; your answer shows which of those facts you think matter.
• To judge how you communicate. Can you summarise something complex without rambling? That skill matters in almost every job, and even more in remote roles where much of the work happens in writing and short calls.
• To find threads for the rest of the interview. Whatever you mention here will often become the next question, so you are partly setting the agenda.

Once you see it that way, the goal becomes obvious: give a short, focused summary that connects your background to this job and invites the next question.

The present–past–future formula

The easiest structure to remember has three parts:

1. Present: what you do now, at what level, and one concrete highlight.
2. Past: how you got here — the one or two experiences that built the skills this role needs.
3. Future: why you are interested in this role and this company specifically.

Keep each part to two or three sentences. If you are an experienced professional, you might start with the past instead ("I started my career in…") — that is fine, as long as you still finish with the future. The future part is the one most candidates forget, and it is the part that makes the answer feel tailored rather than memorised.

Seven example answers

Use these as models, not scripts. Replace every detail with your own, and read your final version out loud to check that it sounds like you.

1. Recent graduate

"I recently graduated in business administration, where I focused on data and operations. During my final year I did a six-month internship at a logistics company, cleaning up their delivery data in Excel and building a weekly dashboard the operations team still uses. That project showed me I enjoy turning messy information into decisions. That's why this junior analyst role caught my eye — your team works on exactly that kind of problem, and I'd get to learn SQL and Power BI properly with people who use them every day."

2. Career changer

"For the past five years I've been a secondary school teacher, and for the last two I've also coordinated our online learning platform. I found that the part of the job I loved most was designing lessons that worked for different learners, so I completed a UX certificate and redesigned our course pages based on student interviews — completion went up noticeably the following term. I'm now looking to do that work full-time, and your education product is a natural fit for someone who has sat on the user's side of the screen."

3. Experienced professional

"I'm a senior accountant with eight years in manufacturing and SaaS. Right now I lead month-end close for a company with entities in three countries, and last year I cut our close from ten days to six by automating reconciliations. Before that I spent four years in audit, which is where I learned to document everything carefully. I'm interested in this role because you're preparing for international expansion, and building a multi-entity finance function is exactly what I've been doing."

4. Manager

"I manage a customer support team of twelve across two time zones. When I took over, response times were slipping, so we rebuilt our help centre and introduced a triage rota — first response time dropped by more than half within a quarter. I started as an agent myself, so I understand the work from the ground up. What attracts me here is the chance to build a support function from an early stage rather than inherit one."

5. Remote role candidate

"I'm a backend developer and I've worked fully remotely for four years with teammates in Europe and the US. Most of my recent work is on payment APIs in Python. Working across time zones taught me to write clear design documents and pull requests so people can review without needing a meeting. I'm applying because your team is async-first and the role is focused on reliability, which is the area I most want to grow in."

For remote roles, it is worth briefly proving you can work independently and communicate in writing. Our guide on how to prove asynchronous communication in an interview goes deeper on this.

6. Returning after a career gap

"I'm a project manager with six years of experience in construction and facilities projects. I took eighteen months out to care for a family member, and during that time I kept my skills current by earning my PMP certification and volunteering as the project lead for a community centre refurbishment. I'm ready to return full-time, and this role's focus on multi-site projects matches what I did before my break."

Keep the gap explanation short and factual, then move forward. See how to explain an employment gap for more wording options.

7. Sales or customer-facing role

"I'm an account executive selling software to mid-sized retailers, and I've hit or exceeded quota in six of the last seven quarters. I moved into sales from a customer success role, so I tend to sell by understanding how the customer actually works rather than pushing features. I'm excited about this role because your product solves a problem I heard about constantly from my current clients."

Common mistakes to avoid

• Reading your CV aloud. The interviewer already has it. Pick highlights and connect them.
• Going over two minutes. Long answers signal that you cannot prioritise. Aim for 60–90 seconds.
• Being too personal. One human detail is fine if it relates to the work; your life story is not.
• Using empty adjectives. "Passionate, motivated, detail-oriented" means little without evidence. Replace adjectives with one specific result.
• Forgetting the "why this job" ending. Without it, your answer could be given in any interview — and the interviewer will notice.
• Sounding memorised. Learn the structure and key points, not every word.

How to prepare your own answer in 20 minutes

1. Reread the job description and highlight the three skills or outcomes that appear most often.
2. Write one sentence about your current role that mentions at least one of those skills.
3. Pick one past achievement with a number or visible result that proves another of those skills.
4. Write two sentences on why this company and role, using something specific from their website or the job ad.
5. Read it aloud, time it, and cut anything that does not support the role.
6. Practise it three or four times — ideally with a friend or by recording yourself on video.

If your CV and your spoken story do not match, fix the CV too. A clear resume summary is essentially the written version of this answer.

Variations of the question

You will hear this question phrased in several ways, and the same structure works for all of them:

• "Walk me through your CV."
• "Tell me a bit about your background."
• "How would you describe yourself?"
• "What brings you here today?"

For "how would you describe yourself", lead with two or three traits and back each up with a quick example, then finish with why those traits fit the role.

Frequently asked questions

How long should my answer be?

Between one and two minutes. If the interviewer wants more detail, they will ask a follow-up — which is exactly what you want.

Should I mention personal information or hobbies?

Only briefly, and only if it adds something relevant, such as a side project connected to the role. Avoid topics like age, marital status or religion.

What if I have very little experience?

Use education, projects, volunteering, part-time work and certifications. Focus on what you did and learned rather than job titles.

Can I use the same answer for every interview?

Keep the same core, but always rewrite the ending (and ideally the highlights) for each company.

Next steps

This question is only the start. Prepare for the classics that usually follow, such as "what is your greatest weakness?" and "why should we hire you?", and browse our interview question guides by profession. When you are ready to put your story to work, browse the latest jobs and apply to roles where your answer fits naturally.