Answering “tell me about yourself” without rambling

“Tell me about yourself” is not an invitation to tell your life story. It is a request for a thirty-second frame that makes the next twenty minutes make sense.

Most people answer it chronologically, starting from their first job. By the time they reach the relevant part, the interviewer has stopped listening and started guessing.

The thirty-second shape

1. What you do now. Role, domain, the kind of problem you own.
2. One concrete thing you did. A project, a number, a change — selected because it is close to the job you are applying for.
3. Why you are here. The sentence that explains why this role, in a way that is not flattery.

Three sentences. Roughly thirty seconds at a comfortable pace. Then stop.

An example

“I'm a backend engineer working on payments — mostly the reconciliation side, where money has to match across three systems. Last year I led the migration off a batch job that used to fail twice a week; we got it to about once a quarter. I'm here because this role is the same problem at a much larger scale, and I want to work on it with a team that owns the whole path.”

Notice what it does not do: no childhood, no list of technologies, no claim to be “passionate about”. The detail is doing the work that adjectives usually try to do.

Selecting the concrete thing

Pick the example that shares a noun with the job description. If the role is about reliability, talk about the failure rate. If it is about scale, talk about volume. If it is about leading people, talk about a decision you made with other people in the room.

One example, not three. Three examples in thirty seconds is a list; one example with a number is evidence.

Why people ramble here

Two reasons. First, the question is vague, so people try to cover everything in case they guess wrong about what matters. Second, the question often comes first in the interview, when nerves are highest, and filling silence feels safer than pausing.

The fix for both is the same: know the first sentence exactly and the shape of the second. You are not memorising the answer, only the route.

The “why you are here” sentence

This is where most answers either become generic or become honest.

Generic: “I'm really passionate about the company's mission and I think it would be a great fit.”

Honest: “I've spent two years on the reconciliation side and I want to see what it looks like at ten times the volume.”

The honest version is specific, slightly modest, and impossible to say about any other company. It also gives the interviewer something to ask about, which is the real goal of the answer: not to conclude, but to open a conversation you can win.

Delivery details

• Do not start with “So, um, I've been in tech for…” Start with the role. The first five words set the frame.
• Keep sentences short. The whole answer should have three full stops.
• Stop after the third sentence. The pause feels enormous to you and normal to the interviewer, who will now ask a follow-up — which is exactly what you wanted.

Practising it

Record the answer once and listen for two things: where the first filler appears, and whether the answer ended before you wanted it to. Most people find that the fillers cluster at the start (where they are deciding what to say) and that the answer is 50 seconds, not 30.

The 30-second intro tool measures the length and the fillers; the full test adds structure and conciseness scoring, which is where rambling shows up as a number. For behaviour questions that follow, Interview practice scores each answer against STAR.