All interview questions
Opening questionFor job seekers60-90 seconds (roughly 150-200 spoken words)

How to Answer "Tell Me About Yourself" in an Interview

The short answer

Answer in 60 to 90 seconds using present, past, future. Say what you do now, name the two or three experiences that got you here, then explain why this specific role is your next step. Keep it professional rather than personal, and finish by pointing at the job you are interviewing for.

It is the first question in almost every interview, and the one most candidates waste. Here is the structure, three full example answers, and a way to practise yours out loud right now.

Or skip ahead and have your answer scored — free, no account needed.

Why interviewers ask “Tell me about yourself”

This is not small talk, and it is not a request for your life story. The interviewer has usually skimmed your CV minutes before the call. They are using the first ninety seconds to work out which version of your background you think matters, and whether you can hold a clear thought out loud under mild pressure. Everything that follows in the interview gets filtered through the impression you set here.

What they are actually listening for

  • Can you be concise? An answer that runs past two minutes signals you will ramble through the technical questions too.
  • Did you read the job description? A strong answer quietly maps your background onto the role they are hiring for.
  • What do you choose to lead with? What you put first tells them what you think your strongest card is.
  • Do you have a narrative? Interviewers want a career that makes sense as a story, not a list of employers.
  • Are you actually interested in this job, or any job? The last ten seconds usually give it away.

The structure to use: Present - Past - Future

Almost every good answer to this question follows the same three-beat shape. It works because it is chronologically easy to follow, it ends on the role you want, and it fits comfortably inside ninety seconds. Build your answer in this order and you will never be caught improvising.

  1. Open with a one-line headline

    ~10 seconds

    Start with a single sentence that says who you are professionally right now: your role, your years of experience, and your area of focus.

    Think of it as the sentence a colleague would use to introduce you. "I am a backend engineer with about six years of experience, mostly on high-traffic payments systems." That is enough. Do not open with where you were born, what you studied at eighteen, or a joke about how you are terrible at talking about yourself.

  2. Give the past that explains the present

    ~40 seconds

    Pick the two or three experiences that most directly built the skills this job needs, and say what you actually did and what changed as a result.

    The filter is relevance, not chronology. You are allowed to skip whole jobs. For each one, land a concrete outcome: a number, a launch, a migration, a team you grew. Two well-chosen examples beat six vague ones, and they give the interviewer obvious follow-up questions to ask, which puts you on ground you have already prepared.

  3. Land on why this role, now

    ~15 seconds

    Close by connecting your background to this specific role at this specific company, and say plainly what you are looking for next.

    This is the part almost everyone leaves out, and it is the part that makes the answer feel deliberate instead of recited. Name something real about the role or the company: the product, the stage, the technical problem, the scope of the position. One sentence is enough, but it has to be a sentence you could not have said to any other employer.

  4. Stop talking and hand it back

    ~5 seconds

    Finish on a clean full stop, or one short question that invites them to steer.

    Most answers do not end, they fade out into "so, yeah, that is pretty much me". Decide your final sentence in advance and stop there. If you want to hand over the reins, "Happy to go deeper on any part of that" works well and takes two seconds.

Example answers to “Tell me about yourself”

These are written to be spoken, not read. Do not memorise them — take the shape and put your own experience through it.

Example 1

Software engineer, 6 years experience

Interviewing for a senior backend role at a payments company

I am a backend engineer with about six years of experience, mostly on systems where being wrong is expensive: payments, ledgers, and billing.

I started at a logistics startup where I was the third engineer, which meant I learned the hard way what happens when you do not think about idempotency. I spent the last three years at Wise on the payouts platform. The project I am proudest of was replacing a nightly batch reconciliation job with an event-driven one, which took our settlement lag from about nine hours down to under three minutes and removed the class of support ticket that used to eat a day a week of the team.

I am looking for a role where payments are the product rather than a supporting system, which is why this one caught my eye. The scale you are operating at is where the interesting correctness problems live, and I would like to be closer to them. Happy to go deeper on any part of that.

Why it works

  • The first sentence is a headline, not a life story, and it already signals domain fit.
  • One specific outcome with real numbers (nine hours to three minutes) invites an obvious follow-up the candidate is ready for.
  • The close names something true about this employer that would not fit another one.
  • It runs about 85 seconds spoken, comfortably inside the window.

Example 2

Product manager, 4 years experience

Interviewing for a PM role on a B2B analytics product

I am a product manager focused on B2B tools, currently owning the reporting area at a mid-size HR software company.

I came into product from support, which I think is the most useful accident of my career, because I spent two years listening to customers describe problems before I ever had to prioritise anything. In my current role I own reporting and integrations. The change I am most pleased with was killing a feature: our custom report builder had a two per cent adoption rate and a disproportionate support load, so I replaced it with fifteen templates built from the most common queries, and weekly report usage roughly tripled.

What draws me to this role is that analytics is the whole product here rather than a tab in someone else's. I want to work somewhere the depth of the data model is the differentiator, and where I get to talk to the people who actually run on the numbers.

Why it works

  • The unusual entry point (support) is framed as an advantage rather than apologised for.
  • The example shows judgement, not just delivery, which is what PM interviewers are listening for.
  • It quantifies the result without pretending the number was the whole story.
  • The close is specific to a company whose product is analytics, not generic enthusiasm.

Example 3

Career switcher, teacher moving into UX design

Interviewing for a junior product designer role

I am a product designer, and before that I spent seven years teaching secondary school science.

I moved across deliberately rather than suddenly. Teaching is largely a design job: you are figuring out where someone gets stuck and rebuilding the explanation until they do not. I started redesigning our department's assessment tracker because staff were avoiding it, ran proper interviews with twelve teachers, and cut the weekly data entry from about forty minutes to ten. That project is what made me retrain. Since finishing my course I have shipped two freelance projects, including an onboarding flow for a small accounting tool where we halved drop-off on the first screen.

I am looking for a first in-house role on a team that will push my craft, and specifically somewhere with real users to talk to rather than personas on a wall. That is what stood out about this position.

Why it works

  • It names the switch in the first sentence instead of hiding it, which removes the interviewer's main question immediately.
  • It reframes the old career as directly relevant evidence rather than as lost time.
  • It includes design work done before the retraining, which proves the motivation is old, not opportunistic.
  • It is honest about being early-career while still leading with outcomes.

Common mistakes (and the fix)

Starting at the beginning of your life

Answers that open with where you grew up or what you studied at eighteen spend the most valuable thirty seconds of the interview on the least relevant material, and often run out of time before reaching anything the job cares about.

Fix: Start with your current role and work backwards only as far as the job needs. If the interviewer wants the earlier chapters, they will ask.

Reciting your CV in order

The interviewer already has your CV in front of them. Reading it aloud adds no information and wastes the one moment where you get to choose the framing.

Fix: Pick two or three experiences and say what changed because of you. Skip the rest without apology.

Running past two minutes

Length is the single most common failure here. A four-minute answer tells the interviewer that every later answer will need to be cut short, and it usually means you have not decided what matters.

Fix: Time yourself out loud. If you are over ninety seconds, cut an example rather than speaking faster.

Answering with your personal life

"Tell me about yourself" sounds like a personal question but is asked in a professional context. Hobbies, family, and travel plans use up the window without making the case for hiring you.

Fix: Keep it professional. If you want a human touch, one short clause is plenty, and it belongs at the end.

Giving the same answer to every company

A generic close ("I am looking for a new challenge") is instantly recognisable and quietly tells the interviewer you are running a numbers game.

Fix: Change the last two sentences for every application. Name the product, the stage, or the specific problem this team is working on.

Memorising it word for word

A fully scripted answer sounds scripted, and if you lose your place you have nothing to fall back on. Interviewers notice the shift in delivery immediately.

Fix: Memorise the three beats and the first sentence only. Say the rest fresh each time, which is exactly what practising out loud trains you to do.

Free · no account needed

Say your answer out loud. Get it scored.

Reading about the structure is not the same as saying it. Answer “Tell me about yourself” the way you would in the room, and get a score plus three specific fixes. Aim for 60-90 seconds (roughly 150-200 spoken words).

This browser cannot record audio. .

Practise the other nineteen questions too

“Tell me about yourself” is one question. Paste the actual job posting and your CV and prepare.fyi generates the twenty questions that company is most likely to ask, then lets you answer them out loud — with a live AI interviewer and a scored breakdown of every answer.

One free project every month. Credits are one-off and never expire — no subscription.

“Tell me about yourself”: frequently asked questions

How long should my answer to "tell me about yourself" be?
Between 60 and 90 seconds, which is roughly 150 to 200 spoken words. Under 30 seconds reads as disengaged and gives the interviewer nothing to follow up on. Over two minutes is the most common mistake and makes the rest of your answers feel like a time risk.
Should I mention personal details or hobbies?
Generally no. Despite how the question sounds, it is asked in a professional context and your ninety seconds are better spent on relevant experience. If you want a human note, keep it to a single clause at the very end, and only if it genuinely connects to the role.
What if I am changing careers and my background does not match?
Name the switch in your first sentence rather than hiding it, then reframe your previous career as evidence. Pick the parts of it that used the same underlying skills, add any work you did in the new field before committing to it, and be direct about what you are looking for now. Interviewers are far more comfortable with a clearly explained change than with a gap they have to guess at.
Is "tell me about yourself" different from "walk me through your CV"?
Yes, though people use them interchangeably. "Walk me through your CV" is an explicit invitation to go chronologically, so follow the order but keep moving quickly through the early roles. "Tell me about yourself" leaves the framing to you, which is an opportunity: lead with what is most relevant, not with what came first.
Should I write my answer out and memorise it?
Write it out once to find the shape, then throw the script away. Memorise the three beats and your opening sentence, and speak the rest fresh. Fully memorised answers are audible, and they collapse if you lose your place. Practising out loud several times is what makes it sound natural.
Does the answer change for a phone screen versus an onsite?
Keep the structure and shorten it slightly for a recruiter screen, where 45 to 60 seconds is plenty and the recruiter is mainly checking for relevance and communication. For a hiring manager or onsite panel, use the full 90 seconds and pick the experiences closest to what that specific interviewer owns.

Practise the next question

Motivation

“Why do you want to work here?”

This is the question that separates candidates who researched the company from candidates who applied to forty of them. Here is how to answer it without flattery.

Self-awareness

“What is your greatest weakness?”

Everyone knows "I am a perfectionist" is a non-answer, including you. Here is how to give a real one without damaging your candidacy.

Behavioral

“Tell me about a time you failed”

The trap is choosing a failure so small it proves nothing. Here is how to pick one that is real, tell it in ninety seconds, and come out of it looking better.

Compensation

“What are your salary expectations?”

The first person to name a number usually loses a little ground. Here is how to deflect without sounding evasive, and what to say when deflecting stops working.

How this question lands at specific companies

amazon interview guidegoogle interview guidemeta interview guideapple interview guidemicrosoft interview guidenetflix interview guide

Go deeper