Tell me about yourself — walk me through your resume.

What the recruiter is actually doing

The recruiter has a requisition with a shortlist of must-haves, a hiring manager who will read one paragraph about you, and a queue of other calls that afternoon. Asking you to introduce yourself tests three things at once: whether your background maps onto the requisition, whether you can be summarised compactly enough to pass along, and whether you are coherent enough to put in front of an engineering panel.

That third one is not a formality. A recruiter's credibility depends on who they forward, so they are listening for anything that would embarrass them in a technical loop: rambling, defensiveness about a past employer, or an inability to say plainly what you do all day. This is not an icebreaker, because everything the hiring manager reads about you before the interview is a paraphrase of what you say here.

The structure: present, path, why this role

Start with the present: your current role, the scope of what you own, and one detail that establishes level. "I am a senior backend engineer on the order-routing service, which handles about a million shipments a month, mostly Java and Postgres, and I have led the last two releases." That one sentence gives the recruiter your title, stack, scale and seniority.

Then the path — only the relevant part of it. Pick the two or three steps that explain how you acquired what this requisition asks for, and say what each gave you rather than what the title was. If the role emphasises payments, the payments work goes here even if it was three years ago; if it emphasises platform work, your CRUD years are one clause, not a chapter.

Close with why this role. Name something specific about the company, product or problem, and connect it to a direction you are already moving in. This is the sentence the recruiter will reuse, because it answers what the hiring manager cares about: why would this person say yes.

Ninety seconds, and how to hit it

Ninety seconds is roughly two hundred words at an unhurried pace. That is short: one sentence of present, three or four of path, one of closing. Practise it aloud against a clock so the length is in your body, but do not memorise it word for word — memorised text is audible and it collapses the moment the recruiter interrupts. Learn the three landmarks and improvise between them.

Then stop cleanly. A final sentence followed by silence reads as more confident than tapering off with "so, yeah, that is basically me," the commonest tell that a candidate has run out of structure rather than finished a thought.

The failure modes

The chronological life story starts at college and works forward at even pace. By the time it reaches anything relevant the recruiter has stopped listening. Recency and relevance both argue for the reverse: now first, then only the history that earns its place.

The resume recital lists employers and dates in the order they appear on the document the recruiter is already reading. It adds nothing and wastes your one chance to say which parts of that document matter. The resume is the data; you are the interpretation of it.

The jump to logistics goes from "hi" to notice period, expected package, or whether the role is remote. The recruiter will raise those later in the same call anyway. Raising them first reads as though fit is already settled and only terms remain, and it spends your introduction on the part of the conversation that has no bearing on whether you get forwarded.

A worked example

A pattern to adapt, not a script to reuse. The shape transfers; the content has to be yours.

"Right now I am a backend engineer at a mid-sized fintech, where I own the reconciliation service — it settles around forty thousand transactions a day against three payment providers. Mostly Java and Kafka, and I am on call for it.

Two steps got me here. I started on an internal reporting product, where I learned to work with messy data and to care about correctness over cleverness. Then I moved onto the payments team during a migration off a monolith, and that is where I picked up event-driven design and learned how much of the difficulty lives in the failure cases rather than the happy path.

I am talking to you because this role is on the settlement platform rather than a feature team, and the platform layer is the direction I have been pushing towards. I would rather own the thing other teams depend on."

Notice what it omits: no graduation year, no list of six employers, no adjectives about being passionate and detail-oriented, no mention of money. It still hands over a level, a stack, a scale, a trajectory and a reason, which is a complete forwarding paragraph.

The trap

The trap is answering the question that was asked instead of the question that was meant. "Tell me about yourself" is grammatically an invitation to talk about yourself, so candidates take it literally and give a biography or a personality sketch. The real question is "why should I put you forward for this specific requisition," and every sentence spent not answering it is spent for nothing. So the answer cannot be generic: if you can deliver the same ninety seconds to two different companies without changing a word, you have an introduction rather than a pitch, and the closing sentence — the only one the recruiter will quote — will be its weakest part.

Write the two sentences you want the recruiter to send the hiring manager, then work backwards: your answer is whatever makes those two sentences the obvious summary of it.