How to answer 'tell me about yourself' in a job interview

Why interviewers ask this question

Interviewers use this question to see how you think about your own career, not to hear your life story. They want to know whether your background is relevant, whether you can communicate clearly under mild pressure, and whether you have a reason for wanting this specific role.

A common mistake is treating it as an invitation to summarise your entire resume chronologically. That wastes time and gives the interviewer nothing to work with. A structured answer that connects your past to the role in front of you is far more useful to both sides.

The present-past-future structure explained

Present: start with your current role or situation and the most relevant thing you do in it. This grounds the interviewer immediately.

Past: pick one or two experiences from your background that explain how you developed the skills the role requires. You do not need to go back to the beginning of your career.

Future: close by explaining why this role is the logical next step. This is where you connect your story to the company and show genuine motivation.

• Present: current title, main responsibility, one concrete result
• Past: one or two experiences that built the skills this role needs
• Future: why this role, why this company, what you want to contribute

Examples by experience level

The structure works at every career stage. The examples below show how to adapt it depending on how much experience you have.

1. Entry level (0 to 2 years): 'I recently graduated with a degree in marketing and spent the last eight months as a part-time social media coordinator for a local retailer, where I grew their Instagram following by around 40 percent. Before that I completed a placement at a digital agency, which is where I learned paid search. I am looking for a full-time role where I can develop those skills further, and your focus on performance marketing is exactly the direction I want to go.'
2. Mid level (3 to 8 years): 'I am currently a software engineer at a fintech startup, where I lead backend development for our payments API. Before that I spent three years at a larger bank building internal tooling, which gave me a strong foundation in compliance requirements. I am ready to take on more architectural responsibility, and the scale of the problems your team is working on is what drew me to this role.'
3. Senior level (8 or more years): 'I have spent the last four years as a product director at a SaaS company, where I built the team from four to eighteen people and launched three product lines. Earlier in my career I was an individual contributor in UX, which still shapes how I work with designers today. I am looking for a VP-level role where I can drive strategy across a broader portfolio, and your expansion into enterprise is the kind of challenge I want to be part of'

How long your answer should be

Aim for 90 seconds to two minutes when spoken aloud. That is roughly 200 to 250 words. Anything shorter can seem underprepared; anything longer risks losing the interviewer's attention before the real conversation starts.

Time yourself when you practise. Most people find their first attempt runs three to four minutes because they include too much background. Cut anything that does not directly support why you are a good fit for this specific role.

Phrases to use and phrases to avoid

Specific language makes your answer memorable. Vague language makes it forgettable. The table below shows common swaps.

• Use 'I led a team of five' instead of 'I have leadership experience'
• Use 'I reduced processing time by about 30 percent' instead of 'I improved efficiency'
• Use 'I am looking for a role where I can own the full product cycle' instead of 'I want to grow'
• Avoid 'I am a hard worker', 'I am passionate', and 'I wear many hats' as standalone claims without evidence
• Avoid starting with 'So, um, basically I...' as it signals nerves and wastes your opening seconds

Adapting your answer for different interview formats

In a phone screen, your answer may be the only thing the recruiter uses to decide whether to move you forward. Keep it tight and end with a clear statement of interest in the role.

In a panel interview, make brief eye contact with each person as you move through present, past, and future. This keeps the whole room engaged rather than just the person who asked.

In a video interview, the slight audio delay can make pauses feel longer than they are. Speak a little more slowly than you would in person and do not rush to fill silence at the end of your answer.

Break-In Bad's interview assistant listens to the interviewer's questions in real time and shows you suggested answers on screen that only you can see, including prompts for this opening question. It works even on a shared screen, so it is useful for both in-person and remote formats.

Practising until the answer sounds natural

Reading your answer is not the same as delivering it. Record yourself on your phone and watch it back once. You will notice filler words, rushed sections, and moments where you lose eye contact with the camera.

Practise the structure, not a word-for-word script. If you memorise every sentence, a small interruption can throw you off completely. Know your three beats, present, past, future, and let the exact wording vary slightly each time.