Tell me about yourself: the answer structure that works (with 8 examples)

The best answer to "tell me about yourself" follows a present-past-future structure in about 50 words: start with who you are professionally right now, give one or two lines on the path that got you here, then land on why that path points at this specific role. Keep it to 60 to 90 seconds and end on the job you are interviewing for, not a full career history.

That structure works because it does one thing most answers fail to do: it ends with relevance instead of trailing off after a chronological recap. The rest of this guide covers why the question gets asked, how to time and tailor the structure, eight worked examples, and the delivery mistakes that undercut an otherwise good answer.

Key takeaways

• The present-past-future structure answers the real question in three moves: where you are now, how you got here, why that leads to this role.
• Target 60 to 90 seconds. Shorter reads as underprepared, longer starts losing the interviewer's attention before you reach the point.
• Tailor the "future" line to the specific job description, the same grounding logic used when tailoring a CV rather than sending one generic version everywhere.
• The 8 examples below cover distinct situations, graduate, career switcher, senior IC, manager, gap, layoff, internal move, contractor going permanent, because the right emphasis changes with your situation.
• The most common failure is reciting your CV chronologically. The interviewer already has your CV. This answer is for judgement about relevance, not a repeat of the document.

What the interviewer is actually asking

"Tell me about yourself" is rarely a genuine request for your life story, and treating it as one is the first mistake most candidates make. It does two jobs at once: orienting the interviewer, since even a well-prepared one has often only skimmed your CV minutes before the call, and testing your judgement about relevance, your ability to select which parts of a long career actually matter for the room you are in.

That second part is the real test. Anyone can recite a chronological list of jobs. Far fewer people can identify, in real time, which two or three threads are worth pulling on for this specific interviewer. An answer that treats every job with equal weight signals that you have not thought about what this role needs from you. An answer that clearly prioritises the parts most relevant to the job in front of you signals the opposite, a genuinely useful signal, since prioritising relevance under time pressure is a skill the job itself will require constantly.

There is also a practical function: this is almost always the opening question, and it sets the frame for the next 45 minutes. A sharp, well-structured answer buys you credibility before a single other question has been asked. A rambling one puts the interviewer on the back foot.

The present-past-future structure, with timing

The structure has three parts, delivered in order, and the order matters because it front-loads the most useful information rather than building up to it.

Present (about 15 seconds). State who you are professionally, right now, in one sentence: your current title, the kind of work you do, and, if it is a strong hook, the scale or domain you operate in. This is not the place for a personality description or a hobby.

Past (about 30 to 45 seconds). One or two sentences on how you got here, hitting the two or three moves that actually explain your current strengths, not every job you have held. This is where most people over-include. The test for each detail: does it make the "future" line land harder, or is it just there because it happened.

Future (about 15 to 20 seconds). Land on why this background points directly at the role you are interviewing for. This is the line that should change most for every interview, since it does the actual work of connecting your past to their specific need.

Total: 60 to 90 seconds. Under a minute usually means you have not given the interviewer enough to work with. Over 90 seconds and you risk losing their attention before the "future" section lands, which defeats the entire structure.

Tailoring the answer to the job description

The "future" line only works if it is specific to the actual job description in front of you, not a generic statement that could close any answer for any role in your field. Read the posting for the two or three things it emphasises most: is this a scaling-stage role that wants someone who has built process from scratch, or an established team that wants steady execution within existing systems. Your "future" line should name that specific thing, not a vague "I'm looking for my next challenge."

This is the same grounding logic used when tailoring a CV to a job description rather than sending one static version everywhere: the underlying facts about you do not change, but which facts you surface should change every time. A candidate with 8 years of experience might lead with team leadership for a management-track role and hands-on technical depth for a senior IC role at the same company, because the relevant slice of an identical career depends on what the room needs to hear.

8 example answers by situation

Graduate. "I'm a recent computer science graduate who spent my final year building a course-scheduling tool that's still used by about 200 students at my university. Before that, two internships gave me production experience with the stack this team uses. I'm looking for a first role where I can keep building things people actually use, which is exactly what this position offers." Annotation: leans on one concrete project instead of GPA or coursework, since a graduate's "past" section has to work harder to earn credibility.

Career switcher. "I currently work in operations management, where I spent the last three years automating reporting processes that used to take my team a full day a week. That work pulled me toward data analytics, I kept finding myself more interested in building the tool than running the process it replaced. I'm now looking to make that the actual job, which is why this analytics role caught my attention." Annotation: names the pivot moment explicitly, since career switches need an explicit "why" or they read as unexplained.

Senior individual contributor. "I'm a staff engineer focused on distributed systems, currently leading the reliability work for a platform handling several million requests a day. Over the last seven years I've moved from generalist backend work into specialising in the kind of infrastructure problems that only show up at scale. I'm looking for a role where that specialisation is the actual job, not a side project, which is what drew me to this posting." Annotation: signals seniority through scope and specialisation rather than years of experience alone.

Manager. "I currently lead a team of six product designers, and the part of the job I've grown into most is making the team's output consistently strong, not just my own. I moved into management two years ago after leading design on a project that made the case for a dedicated design function, and I've stayed because I'm better at multiplying a team's output than at being the sole strong contributor. I'm looking for a team at a similar stage to the one I lead now, which is what makes this role interesting." Annotation: addresses the individual-contributor-to-manager transition head-on instead of skipping it.

Post-gap return. "I'm a marketing professional with six years of B2B experience, most recently focused on lifecycle campaigns. I took just over a year away from full-time work for a family health situation, during which I kept my skills current through a few contract projects. I'm now ready to return full-time, and this role's focus on lifecycle marketing is a direct match for where I left off." Annotation: states the gap plainly, in one sentence, without over-explaining or apologising, then moves straight back to relevance. For more on framing a gap across the rest of your materials, see employment gaps on a resume.

Post-layoff. "I'm a supply chain analyst who spent four years at a logistics company that went through a company-wide restructuring earlier this year, which is how I ended up in this search. Before that, I built forecasting models that cut stockouts meaningfully across two product lines. I'm looking for a company with a stable growth trajectory where that kind of forecasting work is core to the business, which is what stood out to me about this role." Annotation: states the layoff as a fact, once, with no defensiveness, then pivots immediately back to strength.

Internal move. "I've been at this company for three years, starting in customer support and moving into a customer success role about a year ago. That path has given me a level of product knowledge that's hard to get from outside, and it's what makes me confident I could ramp quickly into this account management role. I know the product, the customers, and where the gaps are in how we currently support them." Annotation: leans on internal knowledge as the differentiator, since that is the actual advantage an internal candidate has over external ones.

Contractor going permanent. "I've spent the last four years as an independent UX consultant, working with early-stage startups on product design from the ground up. I've built a strong, varied portfolio that way, but I'm looking to go back to a permanent role because I want to go deep on one product over a longer timeline rather than starting fresh every few months, and that's exactly the kind of role this is." Annotation: answers the unasked question, why leave contracting, before the interviewer has to ask it.

Delivery mistakes

Reciting the CV chronologically. The interviewer has your CV. An answer that walks through every job in order, with equal weight given to each, wastes the one chance in the interview to demonstrate judgement about what matters. If your answer would sound the same in front of any interviewer for any role, it needs tightening.

Over-sharing personal detail. A brief, factual mention of a gap or a relocation is fine and sometimes necessary. A multi-minute detour into personal history is not, and it shifts the tone away from professional judgement toward something the interviewer did not ask for.

Running past two minutes. The longer the answer runs, the more it feels like the interviewer has lost control of the conversation. If you notice yourself adding a fourth or fifth job to the "past" section, that is the signal to cut, not to keep going and land the future line eventually.

Practising out loud and iterating with an interview coach

A present-past-future answer that reads well on paper does not always come out cleanly the first time you say it aloud, since writing and speaking use different muscles, and that gap is exactly where interview answers fall apart under real pressure. Say your answer out loud, timed, before the interview, more than once. The first pass usually reveals which line is doing too much work.

RecastCV's interview prep coach is built for this kind of iteration. It has read your CV and the job description you are preparing for, so it can push on whether your "future" line is actually specific to this role or just a plausible-sounding closer, and it can run the question as part of a fuller mock interview, closer to how it will actually land on the day. For the standard questions you are likely to face right after this one, 50 common interview questions covers the families and what each is really probing.