Tell me about yourself: a 90-second answer for engineers

Why the first question matters

"Tell me about yourself" is the most common first question in an interview, and most engineers treat it as small talk. It is not. The interviewer takes notes on your answer and picks the next questions from it. Whatever you mention in the first 90 seconds, you will probably be asked about in the next 40 minutes.

That makes it the one part of the interview you can steer. Below is a three-part structure that fits in about 90 seconds, four example answers for different situations, and the mistakes that cost people the rest of the conversation.

The structure: now, proof, next

1. 1

   Now (about 20 seconds)

   What you do today in one or two sentences: role, domain, scale. "I am a backend engineer at a payments company, on the team that runs refunds for about 40,000 transactions a day."

2. 2

   Proof (about 50 seconds)

   One or two things you did that are relevant to this job, each with a number. This is the part the interviewer will dig into, so choose the story you most want to talk about.

3. 3

   Next (about 20 seconds)

   Why this role, in terms of what you want to do next, not what is wrong with your current job. Tie it to something specific about the team or product.

About 200 to 250 spoken words. Practise with a timer: most people run long on the first part and short on the last.

Four example answers

Backend engineer, five years of experience

"I am a backend engineer at a payments company, on the refunds team: Kotlin, Postgres, Kafka, about 40,000 refunds a day. The work I am proudest of is moving refunds from a nightly batch to near-real-time; customers now see the money in minutes instead of a day, and support tickets about refunds dropped by roughly a third. Before that I spent two years at an agency building APIs for retail clients, which is where I learned to ship fast. I am looking for a team where the system is bigger than one service, and your post about splitting the ledger caught my attention."

Career switcher, from QA to development

"I have been a QA engineer for three years at a logistics startup, and for the last year I have written most of our test automation in TypeScript and Playwright. Last quarter I fixed the bugs I was finding instead of only filing them, about 30 merged pull requests in our API. That convinced my lead, and me, that I want to build features full time. This junior backend role is the step I am aiming for, and your stack is close to what I already use."

New graduate

"I finished a computer science degree in June. My final project was a scheduling tool for our university's lab rooms, now used by about 300 students; I built the backend in Python and owned the database design. Over the summer I interned at a fintech, where I wrote the export service for monthly statements. I want my first full-time role to be on a product with real users, which is why your internal tools team stood out."

Non-native English speaker

"I am a frontend engineer in Warsaw, working on a React dashboard for a logistics company. My main result this year: I cut the load time of our heaviest page from 6 seconds to under 2. English is my second language, so I will sometimes take a second to choose a word. I am applying because I want to work in an international team, and this role uses the same stack."

The last example does something worth copying: it names the language issue once, calmly, and moves on. Interviewers relax when they know a pause is a pause and not a gap in knowledge.

Mistakes that cost the next 40 minutes

• The CV read aloud. Every job in order, with dates. The interviewer has the CV already; they want the parts that matter for this role.
• No numbers. "I worked on performance" gives nothing to ask about. "I cut p95 from 900 to 240 ms" gives a whole conversation.
• The complaint. "My current company is a mess" in the first minute colours every answer after it.
• Mentioning something you cannot discuss. If you name Kubernetes, expect a Kubernetes question. Only mention what you can defend for ten minutes.
• Running past two minutes. After two minutes the interviewer is waiting for you to stop. Leave them wanting the follow-up instead.

How to practise it this week

Memorize the three anchor sentences, not the whole text. Say the answer to three different people; the wording will change each time, the structure will not, and that is exactly what makes it sound natural.

The short version

Now, proof, next, in about 90 seconds. One sentence on what you do, one or two results with numbers, one reason this role is your next step. Mention only what you are ready to discuss, because that is what the next questions will be about.

Related: 15 STAR stories for senior engineers, stop memorizing STAR, the last week before an interview.