The chairs scrape, someone pours water, and then it comes: “So — tell me about yourself.” You open your mouth and hear yourself say “Well, I studied economics at…” and somewhere behind your own voice a small alarm goes off. You are three words in and already heading for the wrong destination, and you cannot stop, because you have no other route mapped. Two minutes later you are describing a placement year from 2014 and the interviewer’s pen has not moved.
This question gets treated as a warm-up. It isn’t one. It is the only question in the interview where nobody tells you what they want, which is precisely what makes it a test.
What is the interviewer actually asking?
Strip away the politeness and the question means: why are you sitting in this chair? Not who you are as a human being. Not what happened to you, in order. Why you, why this, why now.
That is a question about judgement more than biography. They already have your CV — they are not asking you to read it aloud. What they are watching is whether you can look at a large pile of information about yourself, work out which parts matter to the person in front of you, and deliver those in a shape that ends somewhere useful. If you cannot summarise yourself for a specific audience, there is a fair question about whether you can summarise anything.
Why is it almost always the first question?
Partly logistics; someone has to start. But the consequence matters more than the reason: your answer sets the frame for everything after it.
Whatever you emphasise in the first ninety seconds becomes the map the interviewer navigates by. Say you have spent three years untangling messy data for a team that had outgrown its spreadsheets, and the next twenty minutes bend towards that — what the mess looked like, how you decided what to fix first, what broke. You have chosen the topic of your own interview.
Say instead that you did a degree, then a graduate scheme, then moved to a bigger firm, and you have handed them nothing to pull on. You gave up your one chance to steer, in the first two minutes.
What are the two ways people get this wrong?
Almost every weak answer is one of two failures. They sound nothing alike and fail for the same reason: both answer a question nobody asked.
The chronological CV recital
The common one. It starts at the earliest defensible point and walks forward:
“So I did my degree in business management at a university in the north, graduated in 2013. My first role after that was in a customer service team at a retail company, I was there about eighteen months, mainly inbound queries and some complaints escalation. Then I moved to a slightly bigger firm in a similar role but with a bit more responsibility, I was there two years, and while I was there I got involved in some of the reporting side which I really enjoyed. Then there was a restructure so I moved into operations, that was around 2017 I think, or maybe late 2016…”
Three problems. It takes four minutes minimum. It front-loads the least relevant material — nobody hiring you at thirty-eight cares about your first job — so by the time you reach anything that matters, attention has gone. And it makes no argument. It is a list, and it leaves the interviewer to work out the relevance, which was your job.
The personal answer
Less common, more damaging. This one hears the question literally:
“I’d say I’m a real people person. I’m quite driven, I like a challenge. Outside of work I’m big into travelling — I did three months in South America last year which was amazing. I’m quite sporty, I run a bit, I’ve got two dogs. I think what people say about me is that I’m the one who keeps everyone’s spirits up.”
This is a likeable person answering nothing. The problem isn’t warmth — it is that none of it is checkable and none of it is about the job. “Driven”, “people person”, “likes a challenge” cost nothing to claim and carry no information. The interviewer has learned about your dogs and nothing about whether you can do the work.
What structure actually works?
Three parts, in this order: where you are now, the relevant bits of how you got here, and why this role is the logical next step.
Present first. What you do now and what you are known for in it — one or two sentences. This is your most relevant information, so it goes where attention is highest, and it answers the thing they most want to know immediately rather than four minutes in.
Then the relevant past. Not all of it. The two or three things that explain how you became the person in part one. This is where the argument lives: not “then I did this, then this” but “this is where I learned the thing that matters here.”
Then why this role. One or two sentences pointing forward. What you want next and why this job is that. Brief — you are landing the plane, not making the full case.
The reason this beats chronological order is not that it is a nicer formula. Chronological order optimises for the wrong thing. A timeline is organised around when things happened to you, which is only interesting to you. Present-past-future is organised around what the listener needs, and it has a shape: headline, evidence, implication. That is an argument. A timeline is a sequence.
How long should it be?
Roughly sixty to ninety seconds. Two minutes at the outside, and only if you are genuinely dense with relevant material.
Most people have no feel for that, so: ninety seconds of unhurried speech is around 180 to 220 words. Four or five sentences per section. It is longer than it feels while you are talking and much shorter than a chronological run-through can be. Time yourself once, with a clock, reading aloud at interview pace.
People fail this in two directions and almost never in between. Some stop at fifteen seconds — “I’m a project manager, I’ve been doing it about six years, currently at a software company” — which is true, complete, and hands the interview back with nothing gained. Others run five minutes, which is not an exaggeration; a full account of a fifteen-year career genuinely takes that long, and the person delivering it cannot feel it happening.
How do you decide what to leave out?
This is the actual skill, and it is a skill of subtraction. Fifteen years does not fit into ninety seconds and is not supposed to. You are not compressing your career, you are selecting from it.
One test for anything you are considering: does this help them picture you doing this job? Not “is it true”, not “am I proud of it”. Does it move them towards seeing you in the role.
What usually earns a place:
- What you do now, described as the problem you solve rather than the job title
- One or two specifics with texture — a team size, a scale, a thing you built or fixed
- The pivot that explains why your path looks the way it does, if it needs explaining
- The through-line: what has stayed constant across roles, which is often the real answer
What almost never earns a place:
- Your degree, unless you are recent or it is directly required
- Jobs more than two moves back, unless one is unusually relevant here
- Exact dates and durations — they are on the CV and reciting them eats seconds
- Adjectives about your own personality
- Anything you are including only because leaving it out feels like lying
How much of the personal stuff belongs?
A little. Genuinely a little.
One line of humanity near the end does real work: it makes you a person rather than a summary. The version that works is a single clause attached to something real — you got into this field because you spent a year fixing your own team.s broken process and liked it more than your actual job.
What does not work is the hobby list. “I like running, cooking, and spending time with my family” tells them nothing and matches nine other candidates. Rough proportion: of ninety seconds, personal detail gets five to ten.
What do good answers actually sound like?
Formulas are easy to agree with and hard to use. Four, for genuinely different situations. All fictional. Read them aloud — that is the only way to tell whether an answer works.
Experienced, moving sideways
“Right now I’m an operations manager at a mid-sized logistics firm — about forty people in my part of the business, and my job is essentially making sure the things that have to happen every day actually happen, and finding the ones that quietly stopped working.
I came into operations from the warehouse floor, which I think is the useful part of my background. I spent my first few years actually doing the work, so when I’m looking at a failing process I usually have a decent instinct for whether it’s broken or whether people have just found a faster way around it. The last big thing I did was rebuild how we handled returns — it had grown into about six different informal processes depending on who picked up the phone, and we got it to one that people would actually follow.
What I want now is somewhere the operation is more complex and less settled. My current place is stable, which is fine, but I’ve fixed most of what’s fixable. Yours looked like it has more moving parts, and honestly that’s the bit I enjoy.”
Career changer with an unrelated-looking history
“I’ve spent the last two years in data analysis — currently on a small team at a healthcare charity, mostly turning messy operational data into something the leadership team can act on.
Before that I was a secondary school teacher for eight years, which sounds like a hard left turn and in some ways was. What happened is that I ended up running our attainment data because nobody else wanted it, and I discovered I liked that more than the teaching. So I retrained, took a fairly junior role to get in, and built from there.
The teaching matters more than I expected. A lot of this job is explaining a number to somebody who doesn’t want to hear it and has no stats background, and I did exactly that for eight years with a harder audience. What draws me here is that this role sits much closer to the people making the decisions, which is where I think I’m most useful.”
Recent graduate, little work history
“I finished a marketing degree in the summer, and the part that shaped what I want to do was a placement year at a small consumer brand — about twelve people, so I got handed real things quickly.
I spent most of it on their email programme, which had been running on autopilot for a couple of years. I rebuilt the welcome sequence and set up some basic testing so we could tell what was working instead of guessing. It wasn’t a huge operation, but it was the first time I’d seen a change I made show up in a number, and that’s largely why I’m applying for this kind of role rather than something broader.
Since graduating I’ve been doing freelance social for two local businesses to keep my hands on it. What I want now is a team with people who are better at this than I am — I’ve had a lot of figuring things out alone and I’d like a stretch of learning properly.”
Returning after a gap
“I’m a finance analyst — most recently at a manufacturing company, where I looked after monthly reporting and the forecasting model for two of the business units.
I took eighteen months out from the start of last year for family reasons, and I’ve been back looking properly since the spring. That break was useful in one way: it made me look at what I actually want rather than taking the next rung. I spent a fair bit of it getting properly good with the analysis tooling rather than the version I’d half-learned on the job, so I’m coming back sharper on that side than I left.
What I’m after is a role where the forecasting is used rather than produced — at my last place the model was excellent and the decisions were made in a different room. This position looked like the opposite of that, which is why I applied.”
Why these work
- They open in the present tense. Not one starts with a degree or a date. The most relevant fact is the first fact.
- They contain checkable specifics. Forty people, six informal processes, twelve-person company. None are impressive numbers — they are concrete, and concrete beats impressive because it sounds like someone who was there.
- They argue rather than list. Floor experience makes better operations judgement; teaching makes better data communication. The relevance is done for the listener.
- The awkward bits are stated flatly and left alone. The changer doesn’t apologise for eight years of teaching; the returner gives the gap one clause and moves on.
- They sound spoken. “Honestly, that’s the bit I enjoy.” That texture is the difference between an answer and a recital.
What about “walk me through your CV”?
Several questions are the same question wearing a different hat: “tell me about your background”, “how did you end up here?”, “give me the potted history”, “so, what’s your story?”
All get the answer above. Do not be tricked by “walk me through your CV” into believing they want the chronology — they have just phrased it in a way that makes the trap more inviting. If a chronology was what they wanted, they would be reading, not asking.
What if your history is genuinely messy?
Short stints. A redundancy. A stretch with nothing in it. Plenty of people are in exactly this position, and the standard advice — spin it as a positive — is both useless and audible.
The principle is narrow: state it, place it, move on. Do not apologise and do not over-explain. Those are the same failure: both signal that you think it is a problem, which invites the interviewer to agree.
A redundancy. One clause. “That role ended in a restructure.” No adjectives, no company politics, no justification. Redundancy happens to businesses, not as a verdict on you, and treating it as ordinary is what makes it read as ordinary. If they want more, they will ask, and a calm two sentences is fine.
Short stints. If there are two or three in a row, do not narrate each — that turns your answer into a defence. Give the pattern once and the reason if there is a real one: “I had a couple of short roles in a row — the first was a contract, the second turned out to be a different job to the one advertised, and that’s a large part of why I’ve been slower and more careful about this application.” Then move on. One mention, no revisiting.
A gap. Name it, describe it in the most ordinary terms available, and add one clause about what you did with it if anything is true. “I took a year out for health reasons; that’s fully resolved.” You do not owe anyone the detail. The tone that works is the one you would use to say you moved house.
A role that ended badly. Do not raise it here at all. This answer is a summary, not a disclosure. If it needs addressing, it gets addressed when asked — not smuggled into your opener, where it will consume the frame.
On rehearsal for this specifically: the difficult clause is the one worth saying aloud until it bores you. Not to sound polished, but so your voice does not change when you reach it. Most of what interviewers register is not the awkward fact but the wobble around it. And a reassurance worth stating plainly — an interviewer who read your CV already knows about the gap and the short stints. They invited you anyway. You are not breaking news.
How do you finish it?
Deliberately. This is the part people neglect and it undoes good answers regularly.
The failure is trailing off. You get through your content, you are not sure it was enough, so you keep going — “so yeah, that.s sort of, I mean that.s basically me, um” — and the whole thing deflates. A strong ninety seconds followed by ten seconds of mumbling reads as mumbling, because endings are what people retain.
Have a last sentence and know that it is the last one. The natural choice is your why-this-role line delivered as a full stop: “…which is why this role stood out, and why I’m here.” Then stop. The silence will feel much longer to you than to them, and the interviewer will fill it — that is their job.
Should you rehearse it?
Yes — out loud, and not word for word. Those conditions are the point.
Out loud, because writing it down proves nothing. Sentences that read beautifully collapse when spoken. You find the clause you cannot say without running out of breath, the phrase that sounds written, the transition with no natural pause. Six or seven passes in an empty room or a car is plenty.
Not word for word, because memorised delivery is audible. The rhythm flattens, the eye contact goes, and the person is clearly reading from a script only they can see. It is fragile too: interrupt someone reciting and they lose the thread entirely, because they memorised a sequence of words rather than a set of points.
Memorise the three or four things you want to land, in order. Keep the opening line fairly fixed — first sentences are where nerves do most damage, and a known starting point steadies you. Build everything after it fresh each time. Slightly different words, same content; that is what fluent sounds like.
Rehearse against the specific job, too. The through-line you emphasise for one role is not the one you emphasise for another, and a single universal version is how you end up giving a vaguely relevant answer everywhere. If you want the wider picture, here is how to prepare for an interview more broadly — but this answer deserves its own pass, because it sets up everything else, including the questions you ask at the end.
The other question that opens interviews needs a different kind of answer: why do you want this job is about the role, not your history.
For the rest of the process around this one question, the official job-search guidance is a plain starting point.
The National Careers Service covers the rest of the interview if this is the only part you have rehearsed.
Frequently asked questions
Should I mention my salary or notice period here?
No. Neither belongs in a summary of who you are professionally. Notice period is logistics and gets asked separately. Salary is a negotiation, and you gain nothing by opening it early and unprompted. If your answer drifts towards either, you have wandered out of the question.
What if they’ve clearly read my CV and I’d just be repeating it?
You are not repeating it, you are interpreting it. The CV is facts in date order; your answer is an argument about what those facts add up to and why they point at this job. That is different information — and the fact that they asked despite having read it tells you they want the interpretation, not the data.
Is it different on a phone or video screen?
Slightly shorter — sixty seconds rather than ninety — because you cannot read the other person’s face for signs they have had enough. Same structure otherwise. On a phone screen the interviewer is often checking basic fit against a list, so making your current role and its relevance obvious in the first sentence matters more than usual.
What if I’m asked it twice on the same day?
Give essentially the same answer. Do not invent a fresh version to avoid repeating yourself — the second interviewer has not heard the first one, and improvising a new answer is how you end up with a worse one. If they compare notes, consistency helps you. Shift the emphasis slightly if their role suggests a different angle.
I have three sentences of relevant experience. Isn’t sixty seconds impossible?
You have more than you think; it is just not in paid employment. Placement work, a university project you actually ran, freelance work, a volunteer role with real responsibility. What makes it count is describing it the way you would a job: what the problem was, what you did, what happened. If you are genuinely early on, spend more of the answer on why this role and what you want to get good at.