How to answer the first interview question in ninety seconds

"Tell me about yourself" is the question you're most likely to be asked and least likely to have prepared. It gets treated as a warm-up. It isn't. It's the moment you decide what the next forty minutes are about.

Answer it well and the interviewer spends the rest of the hour asking you about the work you're proudest of. Answer it badly and they spend the hour digging for something to hold on to, and you spend it defending a résumé you didn't get to explain.

Ninety seconds. Rehearsed, timed, said out loud before the day. That's the whole skill.

What they're actually asking

They're not asking for your life story, and they're not being polite. Three things are going on behind that question.

They want to know if you can organise a thought under mild pressure. Half the jobs you'll ever apply for involve explaining something to somebody who's busy. This is a live sample.

They want a map. An interviewer has your résumé and no narrative. Six jobs, two industries, a gap in 2021. The question is an invitation to tell them which parts matter and in what order.

And they want to know whether you've thought about this job, or whether you're doing the rounds.

The four ways people lose it

• The life story. "So I grew up in Ohio, and I studied biology because my dad was a vet…" You're ninety seconds in and still in secondary school.
• The résumé recital. Reading the document they're already holding, in chronological order, with no reason attached to any of it.
• The adjective pile. "I'm a hard worker, I'm passionate, I'm a people person." Nobody has ever said the opposite. It's noise.
• The handback. "What would you like to know?" It sounds collaborative. It reads as unprepared, and now they're doing your work.

There's a fifth, quieter failure: a perfectly good answer that runs four minutes. Length is a message. It says you can't tell what matters.

Start with the job, not with you

Before you write a word about your own history, read the posting again with a pen.

Pick out the two or three things the role genuinely turns on. Not the boilerplate. The parts that would be hard to replace. A posting for an operations manager might list fifteen bullets, but the job is really about keeping a plant running with a thin team and a difficult supplier. That's the thing.

Then look at who's interviewing you. A hiring manager wants to know you can do the work. An HR screener wants to know you're a credible, stable, pleasant human who'll pass the next round. A founder wants to know you'll take ownership. Same story, different emphasis.

Now you know what your answer has to prove. Everything in it earns its place by proving one of those things or it goes.

Build it backwards

Write the last sentence first.

The last sentence is why you're in the room. "And that's why the maintenance lead role here caught my attention — it's the same problem I've been solving, with a bigger plant behind it." It should be specific enough that it couldn't be pasted into an application for a different company.

Write the first sentence second. Present tense, current role, one line of scope. "I'm a project manager at a mid-sized civil contractor, running three to four sites at a time, mostly public infrastructure." No wind-up. No "well, I suppose I'd start by saying".

Now you've got both ends. The middle is the bridge between them, and it's short.

The middle is two moves, with reasons

Pick the two or three moments in your working life that explain how you got from the first sentence to the last one. Each one gets a sentence for what you did and a sentence for why you moved.

The why is the part people skip, and it's the part that does the work. "I moved from field to office because I kept seeing the same scheduling mistakes made upstream and wanted to be where they were made." That's a person with judgement. Compare it to "then in 2019 I joined Hendricks as a scheduler", which is a date.

Include one concrete result if you have one you can state plainly and honestly. A number you actually know. A crew size, a budget, a delivery you turned around. If you don't have a number you're sure of, describe the outcome instead. Never invent one. Interviewers follow up on numbers, and a vague answer to a follow-up undoes the whole thing.

Leave the interesting loose thread hanging. If you mention that you rebuilt the handover process, don't explain it all. You want to be asked.

Cut it, then say it out loud

Written out, ninety seconds is about 200 to 220 words. Most first drafts come in at double that.

Cut every job that doesn't support the through-line. You're allowed to skip nine years. "I spent my twenties in retail management, which is where I learned to run a shift" covers three employers in one clause. If they want the detail, they'll ask.

Then say it out loud, standing up, with a timer. Not in your head. Reading it in your head is how people discover on the day that their opening sentence has four clauses in it and no air.

Do it five or six times over a couple of days until the shape is memorised but the wording isn't. You want to know the four beats cold and improvise the sentences. A word-perfect recitation sounds like a recitation.

In the room

Slow down. Nerves speed you up by roughly a third, so what feels sluggish to you sounds normal to them.

Stop at the end. Fully stop. The urge to keep talking into the silence is what turns ninety seconds into three minutes, and the silence is usually just someone typing a note. Let it sit.

The question comes in disguises. "Walk me through your résumé" wants the same answer with slightly more chronology. "So, what's your story?" wants the same answer, warmer. "What brings you here today?" wants the same answer with the last sentence moved to the front. One prepared answer covers all of them.

When the story has a gap

If you were laid off, say it in four words and move on. "The site closed in March." Restructures, redundancies and closures are ordinary and everyone in the room knows it. The only thing that makes them awkward is a candidate treating them as shameful.

If you were out for caring, illness or family, a plain sentence is enough. "I took eighteen months out when my father got ill, and I came back last spring." No apology, no over-explanation. Then keep going to the part about the job.

If you're changing careers, your through-line isn't your job titles. It's the skill. Say what the skill is, then show it showing up in both places.

If you fumble it

You will, sometimes. You'll start in the wrong place or trail off.

Say so and reset. "Let me start that again, more usefully." It costs you nothing. Interviewers see nervous people all day; what they remember is whether you recovered.

The thing to understand is that you're not being graded on this answer. You're setting an agenda. Somewhere around minute thirty, when they say "you mentioned you rebuilt the handover process — tell me about that," you'll realise you chose that question yourself, three days earlier, standing in your kitchen with a timer running.