It is the first question in most UK interviews, it is not really a question, and it is where a surprising number of otherwise strong candidates lose the room. "Tell me about yourself" sounds like small talk. It is not. It is the interviewer deciding, in the first two minutes, what kind of candidate they are dealing with.
The good news is that it is entirely predictable, which makes it the single highest-return thing to prepare. Here is a structure that works, and what interviewers are actually listening for underneath it.
What they are really asking
Not "recite your CV" — they have your CV. They are asking three things at once: can you communicate clearly under mild pressure, do you understand which parts of your experience are relevant here, and does your account of yourself line up with the role you have applied for.
That last one matters more than people realise. If you spend two minutes on the operational side of your last job and then apply for a strategy role, you have quietly told them you might be a mismatch — without ever being asked about it.
The structure: now, then, next
Now (about 30 seconds)
Start with where you are and what you do. One or two sentences, present tense, with enough concrete detail to be real. "I am a customer operations lead at a mid-sized insurance broker, where I run a team of six handling renewals and complaints."
Then (about 45 seconds)
Now the relevant history — not all of it, the relevant part. Pick the two or three things from your background that most directly support the role you are sitting in front of, and connect them. This is a selection exercise, not a chronology, and doing the selecting is itself part of what impresses.
If you are changing direction, this is where you frame the pivot rather than hiding it. "I came into operations from a frontline service background, which is why process changes I make tend to survive contact with the people who have to use them" turns a non-linear history into an argument.
Next (about 20 seconds)
Land on why you are here — why this role, now. This is what turns your answer from a summary into a reason to keep talking to you. Keep it short and make it about the work rather than about needing a job.
A worked example
"I am a customer operations lead at an insurance broker in Leeds, running a team of six on renewals and complaints. I came into operations sideways — I spent four years on the phones first, which is probably why the process changes I have made have actually stuck; I knew where the workarounds were. The one I am most pleased with was rebuilding how we triage complaints, which took our average resolution time down by about a third over six months. I have got as far as I can go in a team of that size, and your role is the version of the job I have been growing towards — same work, bigger operation, and a team that is actually being built rather than maintained."
That is roughly 100 seconds spoken. Notice what it does not contain: no adjectives about being passionate or hard-working, no walk through 2011, no apology for the non-linear route.
The four common ways it goes wrong
- The full chronology. Starting at university and working forwards. By the time you reach the present, three minutes have gone and the interviewer has stopped following.
- The CV read aloud. Accurate, complete, and adds nothing they did not have.
- The apology. Leading with what you lack — "I know I do not have direct experience in..." Nobody asked yet. Do not do their objecting for them.
- The under-answer. Two sentences and a shrug. It reads as unprepared, and it wastes the one question you knew was coming.
Practise it out loud, once
Not memorised — memorised answers sound memorised, and the small stumbles of real speech are part of sounding credible. But say it aloud once or twice before the interview, because the gap between an answer that reads well and one that speaks well is bigger than most people expect. You will find sentences that looked fine on paper and turn out to be unsayable.
Once you have this answer working, most of the rest of the interview gets easier, because you have set the frame: you have already told them which version of your history is the relevant one, and later questions tend to follow the shape you established. The other high-frequency questions are worth the same treatment — the STAR method covers the competency ones, and salary expectations covers the one people dread most.
Prepare against the roles you are actually going for.
Generic interview prep gets you generic answers. The useful version is rehearsing against the specific role in front of you — which means knowing what that employer is weighting and which parts of your history speak to it. Valiown reads your CV, builds a picture of how you actually work, matches you against real current UK vacancies with the reasoning shown, and prepares you for the interviews you are genuinely chasing rather than a generic list. Free preview on Google Play.
Common questions
How long should my answer be?
Around 90 seconds to two minutes. Short enough to hold attention, long enough to say something. If you are past three minutes you have moved from answering into narrating, and interviewers stop listening well before they stop you.
Should I talk about my personal life?
A sentence at most, and only if it genuinely says something about you. This is a professional question with a friendly surface. Interviewers are trying to work out who you are at work; a two-minute account of your hobbies answers a question nobody asked.
Where do I start — the beginning of my career?
No. Start close to now. Walking through every role since 2009 in order is the single most common way this answer goes wrong. Give the present, then the relevant history, then where you are heading.