Tell Me About Yourself

It is the first question and the one people prepare least, which is backwards. This answer sets the tone for everything after it. Done well, it tells the interviewer what to ask about next. Done badly, it is a rambling life story that burns three minutes and lands nothing.

What they're really testing

This is not one of the deep signal probes. It is a softer screen: can you communicate clearly, do you know what is relevant about yourself for this role, and can you be concise under no pressure at all. If you cannot, it is a bad omen for the harder questions.

The mental model for this question

Two ideas. First, structure it Present → Past → Why here:

PRESENT     who you are now, in one line
              "I'm a frontend engineer focused on design systems."
  PAST        the 2–3 experiences that built you toward this role
              (only the relevant ones — skip the rest)
  WHY HERE    why this company, this role, now

Second, treat it as a trailer, not the movie. Ninety seconds, maybe two minutes. Deliberately drop one or two hooks, a project or a result you mention but do not fully explain, so the interviewer leans in and asks about it. Now you are steering the interview toward the stories you prepared.

How to structure your answer

Skip the childhood and the full résumé walk. Open with what you do today, pull the two or three past steps that are relevant to this job, and close on why you are sitting in this specific room. End with a slight upward inflection, not a trail-off, so they know it is their turn.

A strong sample answer

I am a frontend engineer with about five years of experience, mostly building component libraries and design systems. Right now I lead the design-system work at a fintech, where I own the shared React component library that around forty engineers build on.

I got here a bit sideways. I started in full-stack roles at a small agency, which taught me to ship fast across the whole stack, but I kept gravitating to the frontend and especially to the systems side, making other engineers faster. At my last company I rebuilt our component library and cut new-feature setup time roughly in half, which is when I realised this was the work I wanted to specialise in.

I am talking to you because this role is design systems at a much larger scale than I have worked at, and the part of the job I care most about, raising the floor for a whole engineering org, is exactly what this team does. Happy to go deeper on any of that.

Why this answer works

It opens with one clean line of who I am today, so the interviewer immediately knows how to slot me. The past is two steps, not a timeline, and each step earns its place by pointing at this job. There is a number ("roughly half") dropped as a hook, not explained, so a curious interviewer will ask me to unpack it later, which puts me back on a story I have prepared. And it ends on a clear "why here" with an upward inflection, handing the turn back.

Pitfalls

• The full chronological life story. Nobody asked for the timeline since college.
• Going over two minutes. Length here predicts length everywhere, and they notice.
• Pure résumé recital. They have your CV. Tell them what it does not say.
• No "why here." Without it, you sound like you would take any job, anywhere.
• Reciting it word for word. Memorise the three beats and the hooks, not a script. A script delivered from memory sounds like one, and it falls apart the second they interrupt.

Recap

Present, then the two or three relevant past steps, then why this room. Ninety seconds. Plant one hook. End up, not down.

Now write yours

Draft your 90-second version. Use the four CARL fields loosely: Situation = present, Action = the relevant past, Result = a standout outcome, Learning = why this role now.

Sources

• Crafting the perfect self-introduction — Tech Interview Handbook
• Tell Me About Yourself: software engineer answers — Indeed
• Tackling "tell me about yourself" — Formation