"Tell Me About Yourself": the Only 90 Seconds You Control

"Tell me about yourself" is the most predictable question in interviewing and the one candidates handle worst. Not because it is hard, but because almost everyone misreads what it is for. They hear an invitation to summarise their life, and they deliver a chronology that starts at university and runs out of steam somewhere around their third job.

It is not a biography question. It is a framing question. It is the one moment in the interview where you decide what the conversation is going to be about, because everything you say in the first ninety seconds becomes the material the interviewer draws their next questions from.

That reframing is the whole article. If you want the broad list of what else you will be asked, that is in common interview questions; this goes considerably deeper on the one question that opens almost every interview.

What the interviewer is actually doing

Three things at once, none of them "getting to know you".

Calibrating. They have your CV but not your level. In ninety seconds they are working out whether you operate at the scale the role needs, from how you describe your work rather than from your job titles.

Deciding what to ask next. Most interviewers do not follow their script rigidly. They follow what you give them. Say the words "I rebuilt the reporting after we lost half the team" and there is a very high chance the next question is about that. This is the mechanism you are exploiting.

Checking whether you can be coherent. Almost every job involves explaining something to someone. An answer that rambles for four minutes and never lands is data about how you will brief a client or a colleague.

Notice that none of these needs your childhood, your degree classification, or a complete list of employers. They can read the list. What they cannot read is how you connect it.

The one job the answer has to do

Your answer needs to plant two or three hooks: specific, concrete details that you want to be asked about.

A hook is not a claim. "I am very analytical" is a claim, and nobody follows up on claims. "I spent last year moving our reporting off spreadsheets, which was mostly a political problem rather than a technical one" is a hook, and it is very hard not to ask about it.

Choose your hooks deliberately before the interview: pick the two or three things you most want to talk about, ideally the ones where your evidence is strongest and where your STAR stories are already prepared. The story bank approach and this answer are designed to work together: your opening plants the flags, and the stories are what you tell when the interviewer walks over to them.

This is also why the answer should not be exhaustive. Every extra topic you mention dilutes the chance of being asked about the ones that matter.

Two structures that work

Present, past, future. The standard, and it works for most experienced candidates.

Present: what you do now, in one or two sentences, described by the work rather than the title. Past: how you got here, compressed hard, keeping only the parts that explain the present. Future: why you are in this room, connecting to this specific role.

The discipline is in the compression. Past is the section that swallows people; it should be the shortest of the three, not the longest.

Three chapters and why here. Better when your path is not linear, when you have changed field, or when you have several unrelated blocks of experience. Instead of a chronology, you name two or three chapters with a sentence each, then say what connects them and why it leads here. "There have been three phases to what I do: five years in a lab, three years selling to labs, and the last two building the software labs use. The through line is that I have been on all three sides of the same customer."

Either way, the last sentence should be about them, not about you. That is what turns a monologue into the start of a conversation.

Length

Sixty to ninety seconds. Two minutes is the ceiling.

There is a simple test: say it out loud with a timer. Most people are astonished at how long ninety seconds is when you have prepared and how short it is when you have not. If you routinely run over, the cause is almost always that the past section became a job by job tour.

Under thirty seconds has the opposite problem: it reads as either unprepared or reluctant, and it forces the interviewer to do all the work of finding the next question.

What to leave out

• Where you were born and where you grew up. Unless it connects to the role, it costs seconds and adds nothing.
• Your full education history. One clause at most, and only if it is relevant or genuinely distinctive.
• Every job you have had. Group the early ones: "I spent my first four years in agencies, which is where I learned to work to a brief."
• Personal life. Marital status, children, health. Not relevant, and it invites bias.
• Salary, notice period, logistics. They will come, later, from them.
• Anything negative about your current employer. The opening is the worst possible place for it. If your reason for leaving is difficult, keep it to a neutral clause and be ready for the follow up.
• The phrase "as you can see from my CV". They can. That is not what they asked.

Handing back control

The strongest way to end is a sentence that both explains why you are here and gives the interviewer an obvious next move.

Weak: "...and that is pretty much me." Weak: "...so yes, I think I would be a great fit." Better: "...which is why the operations side of this role interested me, particularly the hub consolidation you mentioned in the ad." Better: "...and I am at the point where I want to do that at a larger scale, which is what brought me here. Happy to go deeper into any part of that."

The second style does two things: it signals you have finished, and it points at the topic you would most like to discuss.

Five worked answers

1. Experienced professional, straightforward move

"I run the reporting function for a 300 person logistics company. Day to day that means the weekly operational pack, the month end numbers for the board, and being the person who gets asked why two systems disagree.

I came into it sideways. I started in the warehouse as an analyst on the inventory side, so I know where the data actually comes from, which is the reason the reporting is trusted now. Before that I did two years in audit, which is where I learned to be suspicious of a number that arrives without a source.

The part I have enjoyed most in the last year has been getting the operations managers to use the numbers themselves rather than asking me. What drew me to this role is that you are earlier in that journey and at a bigger scale, and the ad mentions moving to a single reporting layer, which is exactly the problem I have just been through."

2. Recent graduate

"I finished my degree in statistics in July, and the part of it I actually got hooked on was the applied work rather than the theory.

The clearest example is my final project, which was for a group of community pharmacies who wanted to know why their prescription reminders were being ignored. I cleaned about 14,000 rows of their data, found that a third of the reminders were going to phone numbers that had changed, and gave the manager a one page summary she could act on. I also learned something uncomfortable, which is that my first version of the analysis quietly dropped a whole category of patient and I only caught it because the totals did not match.

Alongside that I have worked weekends in a supermarket for three years, which is less relevant technically but is where I learned to work an entire shift accurately when it is busy.

I applied here because the role is mostly recurring reporting that has to be right, and after that project I have a lot of respect for boring and correct."

3. Career changer

"For eight years I was a secondary school teacher, and for the last two I have been working in learning design for a software company.

The bridge between them was not a plan, it was a project. My school bought a piece of assessment software that nobody could use, and I ended up rewriting the training materials and running the sessions. That is when I realised the part of teaching I liked most was designing how something is explained, not the classroom itself.

Since then I have built onboarding for two products, and the useful part of the teaching background is that I am comfortable being told my explanation did not work, because that used to happen to me thirty times a day.

What interests me here is that your product is used by people who did not choose it, which is the same situation as a classroom, and it is a problem I already know the shape of."

4. With an employment gap

"I am a management accountant, most recently at a manufacturer where I looked after cost accounting across three sites.

I was there four years. I left last autumn to care for a parent full time, which lasted about eight months and finished in the spring, and I have been actively looking since June. I kept my certification current during it and did a short data analysis course, mostly to keep my hand in.

Before the manufacturing role I spent six years in practice, which is where the cost side started for me.

Coming back, I am looking for something with real operational contact rather than a purely head office role, which is why this one interested me: the ad describes the finance business partner working directly with the plant managers."

Note what this does: it names the gap plainly, gives the dates, closes it, and moves on. No apology, no over explanation. The technique is the same as on the document, covered in explaining employment gaps.

5. Internal candidate

"You know most of this, so I will focus on the part that is relevant to the role rather than the history.

I have been in the support team for three years, the last eighteen months as the escalation point for the enterprise accounts. The thing I have ended up owning that is not in my job description is the handover between support and implementation, which used to be an email and is now a proper checklist, mostly because I got tired of the same three problems arriving in week two.

That is also why I applied. The implementation role is the other side of a process I have spent a year and a half fixing from the outside, and I would like to fix the front of it rather than the back."

The same question in different rooms

The answer is not identical everywhere, and adjusting it is a small effort with a large return.

HR or recruiter screen. Usually the first call. They are checking eligibility, level and communication, and they often are not deep specialists in your field. Keep it plainer, avoid jargon, and make sure the answer clearly matches the job you applied for. Slightly shorter, around 60 seconds.

Hiring manager. The version above. This is where the hooks matter most, because this person decides. Be concrete and technical enough to be interesting.

Panel. Slightly more structured, because you cannot read four faces as easily as one. Signpost more clearly, and address the answer to the whole table rather than to whoever asked.

Final round with a senior leader. Shorter and higher. They rarely want detail; they want to know what you are good at and why you are here. Sixty seconds, one hook, and something about direction.

Informal coffee or a networking chat. More conversational, more about motivation, less about credentials. Ending with a question of your own is natural here in a way it is not in a formal interview.

Practising without memorising

Memorising this answer is the single most common preparation mistake. A memorised opening is audible: the pace changes, the eye contact goes, and the moment the interviewer varies the wording ("so, walk me through your background") the recital derails.

What you should fix in advance is the skeleton: the four or five beats you want to hit, in order, and the specific facts inside them. Write those as bullet points, not as sentences. Then say it out loud six or seven times, differently each time. You are trying to reach the point where you could give the answer twice in a row and it would not be word for word identical, but it would hit the same beats.

One more thing worth doing: write the answer down and compare it with your CV's professional summary. They should be saying the same thing in different registers. If they contradict each other, one of them is wrong, and it is usually the summary. Examples of the written version are in professional summary examples.

Common questions

How long should the answer be? Sixty to ninety seconds. Prepare for ninety and you will land near seventy under pressure.

Should I mention hobbies? Only if one of them is genuinely relevant, genuinely unusual, or you are in an interview culture where fit matters heavily. One clause maximum, at the end. It should never replace a hook.

Is it different from "walk me through your CV"? Yes, slightly. That version genuinely does want a chronology, and it grants you longer, two to three minutes. Even then, weight the recent roles heavily and compress the early ones.

What if they interrupt me? Excellent news. That means a hook worked. Answer the interruption fully and let go of the rest of your prepared answer; you can bring the remaining points back later.

Should I ask "would you like the personal or professional version?" No. It reads as stalling. Give the professional version, and if they want something else they will say so.

What if I have had eight jobs? Group them into phases. Three sentences that describe three phases beat eight sentences that describe eight employers, and nobody has ever complained that a candidate summarised too clearly.

Should I say why I am leaving my current job? One clause, if it is naturally part of the "future" section. The full answer belongs to the question they will ask directly.

The short version

Do not summarise your life. Decide what you want the next twenty minutes to be about, plant two or three concrete hooks, spend most of the time on the present rather than the past, land the ending on why you are in this room, and keep it under ninety seconds. Prepare the beats, not the words.

CvLaunch can help you find the hooks: it pulls the achievements out of your CV that are worth building an answer around, and shows you how they read to the person who will be sitting opposite you.