Blog · Interview answers · 9 October 2026 · 7 min read

How to answer "Tell me about yourself" (formula + 4 examples)

It's the first question in almost every interview, and the one most people improvise. A good answer takes 60–90 seconds, sounds natural, and makes the interviewer want to ask a follow-up. Here's a formula that works for any role, what to leave out, and four example answers you can adapt.

What the interviewer actually wants to know

"Tell me about yourself" isn't a request for your life story. The interviewer is really asking three things:

• Are you relevant? Does your background fit this role?
• Can you communicate? Can you give a clear, structured answer without rambling?
• Why are you here? Does moving to this job make sense for you?

Your answer also sets the agenda for the rest of the interview. Whatever you mention, they'll probably ask about next, so mention the things you want to talk about.

The formula: present → past → future

1. Present (20–30 seconds). What you do now, and one concrete result. "I'm a backend engineer at a fintech company, where I own the payments API that handles about 2 million transactions a month."
2. Past (20–30 seconds). How you got here: one or two experiences that explain your strengths. Pick the parts that are relevant to this job and skip the rest.
3. Future (15–20 seconds). Why this role, why now. Connect what you've done to what they need. "…which is why your role on the platform team caught my eye."

Some people prefer to start with the past and go in order (past → present → future). That works too, especially for fresh graduates. The point is to have a clear structure and to finish with the future: end on why you're a good fit for this job, not on a random detail from five years ago.

What to leave out

• Your full CV, line by line. They have it already. Pick highlights.
• Personal details that don't help. Age, marital status, where you grew up — unless it's clearly relevant.
• Complaints about your current job. "I want to grow" works; "my manager is terrible" doesn't.
• Vague adjectives with no proof. "I'm hardworking and passionate" means nothing on its own. A number or a short example does the job better.
• A memorised speech. Learn the structure and two or three key points, not a script. Recited answers sound recited.

Example answers

1. Software engineer (3–5 years' experience)

"I'm a backend engineer at a fintech start-up, where I've spent the last three years on our payments platform. Most recently I led the move from a monolith to services for card payments, which cut our checkout errors by about 40%. Before that I started as a full-stack developer at an agency, building e-commerce sites for clients — that's where I learned to ship fast and talk to non-technical people. I'm now looking for a team where reliability really matters at scale, and your work on real-time payments is exactly the kind of problem I want to spend the next few years on."

Why it works: one strong, measurable result up front, a short "how I got here", and a specific reason for this company.

2. Fresh graduate

"I just finished my degree in information systems. The part I enjoyed most was data — for my final project I built a dashboard that helped a local clinic track patient wait times, and they still use it. During my internship at a logistics company I cleaned and analysed delivery data in SQL and Python and presented the findings to the operations team every week. I'm applying for this junior data analyst role because I want to keep doing exactly that — turning messy data into decisions — in a team where I can learn from experienced analysts."

Why it works: no work history needed — projects and internships count. It shows the skills the job asks for and ends with clear motivation.

3. Career changer

"For the last six years I've been a secondary-school maths teacher. Over time the part I loved most became building tools for my students — I taught myself Python and JavaScript to make practice apps, and one of them is now used by teachers across our district. Last year I completed a web development bootcamp and built three full projects, including a booking system for a tutoring centre. I'm looking for my first developer role, and an ed-tech company like yours is where my teaching background is an advantage rather than a gap."

Why it works: it tells a story that explains the switch, shows proof of the new skills, and turns the "old" career into a strength.

4. Sales / account manager

"I'm an account manager at a B2B software company, looking after around 40 mid-size customers. Last year I hit 125% of my renewal target and grew our biggest account from one team to company-wide. I started in inside sales, which taught me to handle a lot of conversations and a lot of rejection, and moved to account management because I like long-term relationships more than one-off deals. I'm interested in this role because you're moving up-market, and that's the kind of customer I've been working with."

Why it works: numbers, a clear career story, and a link to where the company is going.

Variations of the same question

The same formula answers all of these:

• "Walk me through your CV / résumé."
• "Tell me a bit about your background."
• "Introduce yourself."
• "How would you describe yourself?" — here, lead with two or three traits and back each one with a quick example.

How to prepare in 15 minutes

1. Read the job description and highlight the 3 skills they mention most.
2. Find one achievement from your CV for each — ideally with a number.
3. Write one sentence each for present, past and future.
4. Say it out loud and time it. Over 2 minutes? Cut the past section.
5. Practise until you can say it in your own words, slightly differently each time.

FAQ