How to answer “Tell me about yourself”

“Tell me about yourself” opens more interviews than any other question, and most candidates burn it in one of two ways: reciting their résumé line by line (the interviewer is holding it), or rambling biographically from school onwards.

The interviewer is really asking: give me a frame for the next forty minutes. Your answer sets what they probe next — which makes it the one answer you can fully control.

The three-part structure

1. Present (one sentence). Who you are professionally, right now, in the language of the role you're interviewing for.

"I'm a backend-leaning engineer with two years on payments systems at a fintech."

2. Proof (two or three sentences). The one or two things you've done that this company should care about — chosen for this job description, not your favourites.

"Most recently I owned our settlement-reconciliation service — I rebuilt it after we kept missing gateway mismatches, and it's caught every discrepancy since."

3. Pull (one sentence). Why this role, said plainly.

"I want to work on payments at a bigger scale than my current org can offer — which is why this role stood out."

Under a minute total. Everything you leave out is something they can ask about — which is the point: you're leaving hooks, not gaps.

Put together, it sounds like this

"I'm a backend-leaning engineer, two years on payments systems at a fintech. Most recently I owned our settlement-reconciliation service — I rebuilt it after we kept missing gateway mismatches, and it's caught every discrepancy since; before that I cut our checkout API's p95 latency by about a third. I'm looking to work on payments at a bigger scale than my current org can offer, which is why this role stood out."

Forty-five seconds, three deliberate hooks — the reconciliation rebuild, the latency work, the scale motivation — and the interviewer will almost always pick one. You've just chosen your first deep-dive topic for them.

If you're a fresher

Same structure, different raw material. Your Present is your degree plus what you build: "I'm a final-year CSE student who ships small products end to end." Your Proof is your strongest project, described like a job — what it does, the stack, one real outcome ("a mess-feedback app about 200 students in my hostel actually use"). Your Pull stays the same: why this company, plainly. What you don't do is narrate your education history — the degree line on your résumé already did that.

The follow-up is the real test

Whatever you put in your opener, the interviewer will pull on it. That's not a risk to manage — it's the mechanism to use. Only include things you can go two levels deeper on: if you mention the reconciliation service, be ready for "what was the hardest edge case?" and then "how did you test for it?" An opener full of things you can't defend is worse than a modest one you can.

The mistakes that cost the most

• Starting from childhood. Nobody hired their school journey. Start from the professional present.
• Listing instead of framing. Five projects in one breath gives the interviewer nothing to grab. One strong thread beats five titles.
• Memorised-essay delivery. Rehearse the structure, not a script. If it sounds recited, the follow-ups will test whether it's real.

Practise it out loud

Reading this is not the skill. Saying it — under mild pressure, to something that talks back — is. Rehearse your opener, then work through the role-specific questions we've decoded, or answer one question free on Renonym and see how your opener scores on clarity, structure and confidence before a human ever hears it.