"Tell me about yourself" is the most predictable question in interviewing and the one most candidates handle worst. It gets asked in some form in the majority of first-round interviews, and it arrives before you have any read on the room.

The reason it goes wrong is a mismatch of expectations. You hear an open question and reach for autobiography. The interviewer is asking something much narrower: why are you in this room, and should I keep listening?

What the interviewer is actually asking

Three things, in order:

Are you relevant? Does your background map onto this job?
Can you communicate? If you can't structure 90 seconds about your favourite subject — you — the interviewer starts worrying about how you'll handle a stakeholder meeting.
What should I ask next? A good answer plants hooks. The interviewer follows them, and you end up steering the interview toward the work you most want to discuss.

That third point is the one people miss. This question is the only moment in the interview where you have unilateral control over the agenda. Spend it well.

The 90-second structure

Aim for 60 to 90 seconds. Under 30 reads as disengaged; past two minutes you can watch attention drain out of the room.

Present (20 seconds). What you do now, and the scope of it. Scope means numbers: team size, system scale, budget, customer count.

"I'm a backend engineer at Datafold, where I own the ingestion pipeline that processes about 40 million events a day."

Past (30 seconds). The one or two steps that explain how you got here. Not a chronology — a throughline. You are arguing that your history makes you the obvious person for this job.

"I came at it from data engineering. My first two years were in analytics at a healthcare startup, which is where I learned how much downstream damage bad pipeline design does. That pushed me toward infrastructure."

Future (20 seconds). Why this role, this company, now. Be specific enough that the sentence could not be copy-pasted to another company.

"I'm looking for a place where the ingestion problem is the core product rather than a supporting system, which is exactly what your platform team is doing."

Hook (10 seconds). Hand them the next question.

"Happy to go deeper on the pipeline rewrite — it's the project I learned the most from."

Five scripts by career stage

New graduate

"I finished my CS degree at Georgia Tech in May, where I concentrated in distributed systems. The work I'm proudest of is my capstone — a fault-tolerant key-value store that four of us built and load-tested to about 10,000 writes a second. Last summer I interned at Stripe on the payments reliability team, and that was the first time I saw production systems at real scale, which is what got me interested in this kind of role. I'm looking for a first job where I'll be close to infrastructure with engineers who are further along than me. Your platform team seems like exactly that."

Note what is doing the work: a number, a named company, a specific interest, and a reason this job follows from it. No GPA, no coursework list, no hobbies.

Career switcher

"I've spent six years in commercial real estate analysis, and the last two of those turned into a de facto data role — I built the models our acquisitions team used to price deals, which meant a lot of Python and SQL. About eighteen months ago I started formalising it, finished the Google Data Analytics certificate, and moved into a hybrid role where I now own our reporting stack end to end. I'm making the switch complete because the analysis is the part I'm good at and the part I want to do all day. Real estate also means I read financial data fluently, which I know matters for this team."

Switchers usually apologise for the pivot. Don't. Frame the old career as an asset the other candidates don't have.

Mid-level, currently employed

"I'm a product manager at Klarna, where I run the merchant onboarding experience — about 200,000 merchants and a team of six engineers and a designer. Before that I was at a much smaller company where I did a bit of everything, and that contrast taught me the thing I care about most: I'm good at reducing a messy process into something a user can complete in one sitting. Onboarding time-to-first-transaction is down 40% since I took the area over. I'm interested in this role because the same problem exists at a bigger scale here, and the ownership is broader than what I have now."

Returning after a gap

"I took eighteen months out to care for a family member, and I came back to work in February. Before the break I was a senior QA engineer at Cisco for four years, mostly on test automation for networking gear. During the gap I kept my hands in it — I did the ISTQB Advanced cert and contributed to a couple of open-source test frameworks. Since February I've been contracting, which has been a fast way to see how much the tooling has moved. I'm looking for a permanent team now, and this role is a close match to what I was doing at Cisco with more emphasis on CI, which is the part I want to grow."

State the gap plainly in one sentence and move on. Candidates who circle it make it interesting; candidates who name it make it boring, which is what you want.

Senior / leadership

"I lead a platform organisation of 24 across three teams at Twilio. The mandate when I took it over two years ago was to consolidate four internal deployment tools into one, which we did — deploy frequency roughly tripled and we retired two on-call rotations. Before Twilio I was at AWS for five years, ending as a senior manager on ECS. The thread through both is that I like taking infrastructure that grew by accident and giving it an intentional shape. That's why this role interests me — from the outside it looks like you're at the point where that consolidation has to happen."

The five mistakes

Starting at birth. "So I grew up in Ohio…" No interviewer has ever needed this.

Reciting the résumé. They have it. Repeating it wastes your only uncontested airtime and signals you have nothing to add beyond the document.

No numbers. "I improved our reporting process" is unfalsifiable and forgettable. "I cut the monthly close from nine days to four" is neither.

A generic future. "I'm looking for a challenging role at a great company" tells the interviewer you'd take any job, which makes them wonder why they should fight for you.

Winging it. This is the one question you can be certain is coming. Not preparing it is a choice.

How to practise it properly

Reading your answer silently is not practice. The gap between what reads well and what sounds natural out loud is large, and you only discover it by speaking.

Three passes is usually enough:

Write it, then cut it by a third. The first draft is always padded.
Say it out loud and time it. If you're past 100 seconds, cut again. Listen for sentences you stumble on — those are usually written-English constructions that don't survive being spoken.
Deliver it cold. Not reading, not from memory word for word — from the four-part structure. Memorised answers sound memorised; structured answers sound fluent.

If you want feedback rather than self-assessment, Terview's mock interview runs the question in a real interview flow and scores the answer on structure, specificity and pacing. It's the same loop as practising with a friend, minus the scheduling.

One last thing

Tailor the past section to the job. The present and future sections change little between applications, but the two career steps you choose to highlight should change every time. Applying to an infrastructure role? Foreground the infrastructure work. Applying to a customer-facing role? Foreground the customer work. Same career, different argument.

You are not describing your history. You are making a case.

How to Answer "Tell Me About Yourself" (With 5 Scripts That Work)