"Tell me about yourself" is the first question in almost every round, and it is the only one you can script completely. A good answer takes 60 to 120 seconds, states your level before anyone has to guess it, and plants two or three hooks the interviewer will pull on for the next half hour. This chapter gives you the structure, a worked example taken apart line by line, a full pitch drafted in both lengths for you to adapt, and the three questions that travel with it: why this company, why are you leaving, and what are you looking for.
What the question is doing
Interviewers do not ask it to hear your life story. They ask it for four reasons, and each one changes what you should say.
| Reason | What the interviewer does with your answer | What that means for you |
|---|---|---|
| Calibrate level | Writes a first guess: "mid", "senior", "maybe staff". Recruiters use it to pick which loop to book. | Say your scope in the first 15 seconds: what you own, how many people or teams depend on it. |
| Find follow-up material | Picks the most interesting thing you said and asks about it next. | Mention only things you want to be asked about. Every noun is an invitation. |
| Check communication | Notices whether you can summarise without rambling. | Stop on time. A crisp 60 seconds beats a thorough four minutes. |
| Warm up | Lets both of you settle before the real questions. | Sound like a person, not a résumé. One sentence of why you like the work is enough. |
The same question has a different job in each round. In a recruiter screen it decides which loop you get. In a behavioural round it chooses the first story. In a technical round it is a 30-second courtesy before the problem. In a team-match call it is most of the conversation. The section on tailoring gives the length and emphasis for each.
The structure: present, past, future
Chronological answers ("I graduated in 2020, then I joined…") put your least impressive work first and your current scope last, often after the interviewer has stopped listening. Start with now instead.
PRESENT ── who you are today, what you own, at what scale
│ ~40% of the time. Level is decided here.
▼
PROOF ── one or two results with numbers, told in a sentence each
│ ~30%. These are the hooks for follow-ups.
▼
PAST ── how you got here, compressed to the thread that explains you
│ ~15%. One or two sentences.
▼
FUTURE ── what you want next, and why this role fits it
~15%. Ends on them, so the next question is easy.
Present-past-future is the common name. The "proof" beat is the part most people skip, and it is the part that makes the answer score. A proof is a specific outcome you caused: "cut reconciliation breaks from about 40 a day to under 5" is proof; "worked on reconciliation" is not.
Two other shapes, and when they fit
Headline, proof, bridge
One sentence that names you ("I'm a backend lead who works where mistakes cost money"), two proofs, one bridge to the role. Best for the 30-second version in a technical round, or when the interviewer says "briefly".
Theme thread
Pick one theme that runs through your career ("I keep ending up on the systems where correctness matters more than speed") and hang every beat on it. Best for hiring-manager and team-match calls, where they are judging fit as much as level. It costs you breadth: anything off-theme gets cut.
Timing in words
Most people speak somewhere between 130 and 160 words a minute in an interview; nerves push it up. Measure your own pace once by reading a paragraph aloud for a minute. Assuming about 140 words a minute:
version target time words (at ~140 wpm) use it in ───────── ─────────── ─────────────────── ───────────────────────── short 30 s ~70 coding / design rounds standard 60 s ~140 recruiter, most onsite rounds long 2 min ~280 hiring manager, team match
Do not memorise word for word. Memorise the beats and the numbers. A recited answer sounds recited, and if you are interrupted you lose your place. Practise it enough times that it comes out a little differently each time with the same skeleton.
A worked example, weak to strong
Meera (fictional) is a backend engineer with seven years' experience, now leading the payments-retry service at a food-delivery company. Here is her first draft, for a Senior role.
Weak (about 90 seconds, chronological): "So I did my B.Tech in computer science from a college in Pune, graduated in 2018. I joined a services company where I worked on a Java project for a bank client, mostly on APIs. Then in 2020 I moved to my current company. I've worked on a lot of things there: the order service, some payments work, and now I'm on the payments team. We use Kotlin, Postgres, Kafka, AWS. I like solving problems and learning new technologies. I'm looking for a new challenge."
What is wrong with it, beat by beat:
- Starts in 2018. The interviewer learns her current scope only at the end, and even then it is "on the payments team", which is a location, not a scope.
- No proof. Not one outcome. "Worked on a lot of things" invites the interviewer to guess, and they will guess low.
- The stack list is wasted time. It is on the résumé. Mention technology only when it explains a decision.
- "New challenge" says nothing. Everyone wants one. It gives the interviewer no reason to believe she wants this role.
Strong (about 60 seconds, ~145 words): "I'm a senior backend engineer at a food-delivery company, where I lead the payment-retry service: four engineers, and every failed card or UPI payment in the app goes through us, about two million a month. The thing I'm proudest of is the retry redesign last year. We were retrying on a fixed schedule and double-charging a few hundred customers a month; I moved us to idempotency keys per payment attempt and a state machine the support team could read, and double charges went to zero for two quarters running. Before this I spent two years building banking APIs at a services firm, which is where I learnt to care about audit trails. I'm looking for a team where money movement is the core product rather than a side feature, which is why your payouts team stood out."
Notice what changed. Scope (team size, volume) arrives in the first sentence. One proof is told with a before, an action and an after. The past is one sentence, chosen because it explains her. The ending names this team, which hands the interviewer an obvious next question. The stack disappeared.
"…which is why your payouts team stood out. Happy to go deeper on the retry redesign or anything else on my résumé."
That closing line is optional. It tells the interviewer you are done and offers a direction, which is useful in rounds where they have no plan for the next question.