Tell Me About Yourself

What they are actually asking

They are not asking for your life story and they are not making conversation. The question is doing a specific job: it hands you ninety seconds of uninterrupted time and watches what you choose to put in it.

What you select is the answer. A candidate who spends forty seconds on where they grew up and studied has told the interviewer that they think chronology is the point. A candidate who opens with what they do now and why it connects to this role has told them something else.

The other thing it does is set the agenda. Whatever you claim here is what gets probed for the next twenty minutes, so every sentence you say is a sentence you are volunteering to defend.

That cuts both ways, and the candidates who understand it treat this question as the most controllable moment in the interview. If you name a specific project in your opening, you have made it likely that the next question is about that project, which you have prepared. If you make a vague claim about being a strong communicator, you have invited somebody to go looking for evidence you have not chosen. Steering the interview toward your best material is a legitimate move and this is where it happens.

The structure that works

Three moves, in this order.

Present. What you do now, in one sentence, without qualifiers. I am a support lead at a fifteen-person company. Not I am currently working as, which wastes three words before it says anything.

Past. How you got here, compressed to the two or three moves that explain the present. Skip anything that does not lead to where you are sitting today, including qualifications that predate your current field and jobs you held briefly. Two sentences. If your history genuinely needs more than two sentences, you are probably explaining rather than selecting, and the interviewer will ask if they want the detail.

Why here. What connects your history to this role, ending with something specific about their company or the job. Two sentences.

Then stop. Ninety seconds, roughly 150 to 180 words. The most common failure is failing to stop, because silence after an answer feels like it needs filling, and everything you add past the ninety seconds is unprepared material you have volunteered to defend.

If the silence is genuinely uncomfortable, end on a question. Asking whether they want more detail on any part of that hands the turn back deliberately, and it gives the interviewer a chance to steer you toward what they care about rather than what you guessed.

Put one number somewhere in the middle. It is the thing that survives into the interviewer's notes.

Sample answer: no experience

For a first job, with no professional history to draw on.

I finished my business degree in June and I have spent the last two years running the events side of our student union, which is where I learned most of what I know about working to a deadline with other people's money. The biggest thing I did was our careers fair. Sixty employers, about a thousand students, and a budget of four thousand pounds that I had to account for line by line to a committee. I have applied here because the coordinator role is the same shape of work, and because I want to do it somewhere the events have consequences beyond a student budget.

It works because it treats unpaid work as work. Sixty employers and four thousand pounds is evidence, and neither number needed a salary attached to be real. Nothing in it apologises for a lack of experience, which is the single most common mistake candidates make in this position.

The apology usually arrives as a qualifier: although it was only a student role, I know it is not the same as real experience. Interviewers are not fooled into thinking a student union is a corporation, and they were not going to be. What the qualifier does is tell them you rate your own evidence as weak, which is a judgement they will then adopt.

Sample answer: fresh graduate

For a graduate role where the degree is relevant and there is some work history.

I graduated in computer science last summer and I have been doing back-end work at a fintech startup since, mostly on their payments reconciliation. The specific thing I have got good at is the unglamorous part, tracing why two systems disagree about a number, which I did not expect to enjoy. Before that I spent a placement year at a bank doing something similar at a much larger scale. I am here because your job description talks about data quality as an engineering problem rather than an operations one, and that matches what I have actually been doing.

The last sentence does the work. It quotes something specific from their material, which almost nobody does, and it demonstrates the application was not sent to forty companies unchanged.

Notice also the admission in the middle, that he did not expect to enjoy reconciliation work. Small unflattering details make the rest of an answer more believable, because nobody invents them. A ninety-second answer with one honest edge in it lands better than a ninety-second answer that is uniformly impressive.

Sample answer: experienced hire

For a mid-level or senior move where the history is the asset.

I run support for a fifteen-person company and I have been there four years, which is long enough to have taken first response time from eleven hours to about three and a half and to have kept it there. Before that I was at a much bigger organisation doing a narrow slice of the same thing, and the reason I left was that I wanted to own the whole function rather than one queue of it. I am talking to you because you are at the size where support stops being a queue and becomes a system, and that transition is the part of the job I am best at.

One number, one reason for leaving that is about scope rather than grievance, and a claim about their situation specific enough to be wrong. That last part is what makes it memorable.

Most candidates say something safe about the company here, which is forgettable by design. Saying that support stops being a queue and becomes a system at a particular size is a real assertion about their business. If the interviewer disagrees, you have a conversation rather than a monologue, and conversations are what people remember from a day of interviews.

Sample answer: career changer

The hardest version, and the one candidates handle worst.

I spent six years as a secondary school teacher and I moved into instructional design about eighteen months ago. The bridge was that the part of teaching I was best at was working out why a particular explanation was not landing and rebuilding it, which turns out to be most of what instructional design is. Since I switched I have built onboarding material for two software companies, and the most useful thing I brought with me is that I test explanations on people before I ship them, which is not standard practice in this field. I am here because your product has the same problem my last one did, which is that it is powerful and the first hour is confusing.

Career changers usually apologise for the change or over-explain it. This does neither. It names the transferable skill precisely, which is a specific competence rather than a vague claim about people skills, and moves on.

The precision is the whole trick. Everybody claims teaching gave them communication skills, and it means nothing because it could be said by any teacher about any job. Working out why a particular explanation is not landing and rebuilding it is a specific mechanical skill, it is obviously what the new job requires, and it could only be claimed by somebody who has actually done the old one.

The other move worth stealing is the last sentence, which asserts something about the interviewer's product. It converts a career change from a liability that needs explaining into a perspective the candidate brought with them.

Where a rehearsed answer breaks

This is the most rehearsed question in interviewing, which means it is also the one interviewers have the most calibrated ear for. They are listening for the seam between the part you wrote and the part you did not.

The follow-up that finds it is usually a request to expand on a claim you made in passing:

You said you took first response time from eleven hours to three and a half. What did you personally change, and what did your team change?

Now the ninety seconds is over and you are in unprepared territory, talking about a number you cited as a credential rather than as a story. Candidates who have only memorised the paragraph fall apart here, because the paragraph was written to sound good rather than to be interrogated.

The second break is more subtle. If your answer contains a claim about why you left a previous role, expect that to come back within ten minutes, phrased slightly differently to see whether the account stays consistent. Answers written to be impressive tend to drift, because there is no memory of an actual event underneath them.

The repair is to build the ninety seconds out of things that happened, then check that every claim in it has two more minutes of detail behind it. If a sentence has nothing behind it, cut it. The polished version that collapses under one question is worse than a plainer version that holds.

For the longer treatment of this and the closely related opener, see what do you do. For the format that structures the answers that come afterwards, see the STAR method, and for the questions that follow, behavioral interview questions.