How to Answer "Tell Me About Yourself" in a Technical Interview

"Tell me about yourself" is the first question in almost every technical interview and the one candidates prepare for least, on the theory that it is small talk. It is not. It is the only ninety seconds in the entire loop where you decide what the interview is about, and most engineers spend it reciting a CV that the interviewer is already holding.

Why the first answer sets the whole round

Interviewers form follow-up questions from what you volunteer. Mention that you rewrote a payments reconciliation job and you will spend the next ten minutes on a system you know intimately. Recite your job titles in order and the interviewer has nothing to grab, so they fall back on generic questions you have no particular advantage answering.

That is the whole mechanism. You are not being tested on this question. You are being handed the steering wheel and most people give it straight back.

A structure that works: now, then, why here

Eighty seconds. Not four minutes. The most common failure is length: past roughly two minutes the interviewer stops listening and starts waiting, and everything after that point is wasted regardless of how good it is.

Plant exactly one hook

Somewhere in the "now" section, name one specific technical problem you own. Not a technology, a problem. "I work on the search service" is a technology. "I spend most of my time on why our search latency spikes when the index rebuilds" is a hook, and it is almost impossible for an interviewer not to ask about it.

What to cut

"Any fool can write code that a computer can understand. Good programmers write code that humans can understand."
- Martin Fowler, Refactoring (1999)

The same standard applies to the answer. Anyone can list what they have done. The skill is selecting the two percent that makes the listener want to hear more, and leaving out the rest without feeling that you have undersold yourself.

The "why here" that is not flattery

Good reasons are concrete and slightly self-interested: the scale is larger than anything you have worked on, the problem domain is one you have been circling for years, the team owns something end to end rather than a slice. Those are checkable and they explain why you would stay.

Bad reasons are compliments. "You are doing amazing work" tells the interviewer nothing about whether the role fits you, which is the only thing they can act on.

Rehearse it once, then stop

Say it out loud with a timer, twice, and then leave it alone. Over-rehearsed introductions develop a recited cadence that is audible immediately and undermines everything after it. You want the shape memorised and the sentences fresh, which is exactly what two run-throughs produce and ten do not.

If you practise with a mock interview, use the transcript rather than your memory. Almost everyone runs twice as long as they think, and the recording is the only thing that will convince you.