“Tell me about yourself” opens most interviews, and it's almost always the answer people have rehearsed least — because it feels too obvious to practise. So they improvise, and improvising under adrenaline is how a 60-second answer becomes a three-minute autobiography.
The good news: it's the most controllable moment in the whole interview. You know it's coming. You can build one answer that works for almost any version of the question.
What they're actually asking
They are not asking for your life story. They're asking one quiet question: “Why are you a sensible person to be sitting in this chair, for this role, right now?” Answer that in about 60–90 seconds and you're done. Everything that doesn't serve that question is noise.
The formula: now, then, why you're here
Three beats, in order: what you do now, the move or two that got you here, and why this role is the obvious next step. It's almost impossible to ramble inside a structure that has a built-in ending.
Right now I'm a [role] at [company], where I [one concrete thing you own]. Before that, [one move that shows range, growth, or a turning point]. I'm looking at this role because [specific, honest reason tied to the job].
Notice the last line. Ending on why this job hands the conversation back and signals you're finished — no awkward trailing-off. If you want to go deeper on that beat, it's the whole of answering “why do you want this job?”.
Sample answers by level
Same formula, different weight. Junior candidates lean on trajectory and hunger; senior candidates lead with ownership and scope.
“I'm a recent CS grad — I've spent the last year building small web apps, including a booking tool that a local gym actually uses day to day. That project is where I realised I like the backend more than the UI. I'm looking for a first proper engineering role on a team I can learn fast from, and yours ships the kind of product I've been building for fun.”
“I'm a backend engineer at a fintech, where I own our payments service — about 40 requests a second at peak. I moved into payments after our billing kept breaking on my old team and I was the one who kept fixing it. This role is more of that reliability work, at a bigger scale, which is exactly the direction I want to grow.”
“I lead a team of six on platform infrastructure — we run the deploy tooling every other team depends on. Before that I spent five years going deep on distributed systems, and I've spent the last two learning how to make other engineers effective rather than just shipping myself. I'm drawn to this role because you're at the stage where that platform-and-people mix is the whole job.”
Tailor it to your kind of role
The three beats stay; the emphasis shifts with who's listening.
- Technical roles: name a concrete system you own and one measurable outcome. Specifics read as competence; adjectives don't.
- Non-technical roles: lead with the outcome you drive (revenue, retention, a launch, a happier team), not the tools you touched. “I grew the mid-market pipeline” beats “I used Salesforce and HubSpot.”
- Career-switchers: use the “then” beat to make the switch make sense, not to apologise for it. Frame the pivot as a decision, not a detour: “I spent four years in teaching, which is where I learned to explain hard things to sceptical rooms — I'm bringing that into product now.”
Weak answer → better answer
CV recital
“So I graduated in 2018, then I joined Acme as a junior, then I got promoted to mid, then I moved to Globex, then I did some frontend, then some backend, then…”
Framed
“I'm a backend engineer at Globex — I own our checkout service. I got into reliability work after a launch fell over on my old team and I fixed the root cause. This role is more of that, which is why I applied.”
Why it works: the better version answers “why you, why here” in three sentences. The weak one makes the interviewer do the filtering — reciting a timeline forces them to guess which parts matter, and a tired interviewer won't bother.
Treating it as an icebreaker and going personal — hobbies, hometown, the dog. It's not small talk; it's the first scored question. Keep it about the work until they signal otherwise.
Why it still trips people up
Most people have “prepared” this answer in their head, once, on the drive over. Then they say it out loud for the first time in the actual room, the nerves hit, and the tidy version evaporates. The fix isn't a better script — it's reps. Saying it out loud enough times that it survives contact with adrenaline is a blanking problem, not a writing one. And keeping it to 90 seconds is really a rambling problem in disguise.
Write your three beats, then say them out loud on a timer. Under 60 seconds, no notes. If you can't finish in time, the middle beat is too long — cut it to a single sentence and try again.
Once your opener is solid, the same discipline — structure, specifics, land the plane — carries into the harder questions, especially the “tell me about a time…” behavioural ones.
Say your opener out loud before it counts
Run a realistic voice mock interview, get your “tell me about yourself” scored, and see the model answer a strong candidate would give. Free to start — no credit card.
Start freeFrequently asked questions
How long should 'tell me about yourself' take?
About 60 to 90 seconds. Long enough to cover now, then and why-this-role; short enough that you don't ramble or recite your whole CV.
What should you not say in 'tell me about yourself'?
Skip your life story, personal details unrelated to the job, and a flat chronological list of every role. Lead with who you are now and keep everything tied to the job you're interviewing for.
Should the answer be the same for every interview?
The now-then-why structure stays the same, but tune the final 'why this role' beat and your emphasis to each job. One rehearsed core, lightly re-pointed each time.