How to answer "tell me about yourself"

"Tell me about yourself" is not an invitation to narrate your CV. It is a test of whether you can decide what matters, in under two minutes.

Almost everyone fails it the same way: they start at university and walk forward chronologically, run out of time somewhere around the second job, and finish with "and then I applied here". Nothing in that answer was chosen. The interviewer learns that you can remember your own history.

The good version is three parts and lasts ninety seconds.

Part one — where you are now, in one line

Start at the present, not the beginning. "I'm a backend engineer, mostly payments, four years, currently at a fintech doing about a million transactions a month."

That single sentence gives them scale, domain, and seniority. It is the anchor for everything after it, and it stops you narrating forwards from 2019.

Part two — the one thing you want them to remember

Pick a single piece of evidence that matches the job you are interviewing for. Not your favourite project — the relevant one.

Thirty seconds: what the problem was, what you decided, what happened. If you find yourself explaining the company's org chart, you have chosen a story that needs too much setup. Choose another.

This is the part almost nobody prepares, and it is the only part they will repeat to a colleague afterwards.

Part three — why this role, honestly

Two sentences connecting what you just described to what they advertised. "I want to keep working on payments infrastructure, and your posting is the first I've seen that's explicitly about reliability rather than new features."

Specific is the whole game here. Anything that could be said to any company — growth, great team, exciting mission — reads as filler, because it is.

Ninety seconds, not four minutes

Time it out loud once. Most people are astonished by how long ninety seconds actually is, and equally astonished that their unprepared answer ran past three minutes.

If you run over, cut from part one. Nobody ever lost an interview because the opening line was too short.

What to do when it comes at the end

Sometimes it arrives after the technical questions, as a wind-down. Same structure, but lean harder on part three, because at that point they are deciding whether you actually want the job rather than whether you can do it.

The mistake that costs most

Reciting the resume they are holding. They have read it. Repeating it in paragraph form tells them nothing new and burns the one moment in the interview where you fully control the framing.

Your answer should make them ask a follow-up you would enjoy answering. That is the actual goal — not to be complete, but to be interesting in a specific direction.

What this cannot do

It cannot make you fit a role you do not fit. If part three is hard to write honestly, that is worth noticing before the interview rather than during it.

Prepare this one answer properly and the rest of the interview gets easier, because you have already told them what to look for. If you want the whole week structured around that, here is a realistic seven-day plan — and KyzenX will run the mock out loud and tell you where the ninety seconds went.