Interview guide

How to answer “tell me about yourself”

It is almost always the first question, and most candidates either recite their resume or freeze. Use the present–past–future structure below, keep it under 90 seconds, and finish by pointing at the job.

What the interviewer is actually asking

They are not asking for your life story. They are checking three things in the first minute: can you communicate clearly, is your experience relevant to this job, and do you know why you applied. Every sentence in your answer should serve one of those three.

The three-part structure

  1. Step 1

    Present: who you are right now

    One sentence naming your current role, scope and the kind of problem you own. 'I'm a support lead at a 40-person fintech, running a team of six across two time zones.'

  2. Step 2

    Past: the proof

    Two sentences with results attached. Pick the achievements closest to the job description, and use real numbers you can defend if asked.

  3. Step 3

    Future: why this role

    One sentence linking your track record to what this company is hiring for. Reference something specific from the posting or the product.

Sample answers

Read these for shape, not for wording. Swap in your own roles and numbers — an interviewer can tell the difference between your story and a template.

Software engineer

I'm a backend engineer at a logistics startup, mostly on the payments and billing services. Over the last two years I moved us off a nightly batch job onto event-driven billing, which cut invoice disputes by about 40% and took a full day out of month-end. Before that I was at an agency, so I've shipped in a lot of different codebases. I'm looking at this role because the posting is mostly platform reliability work, which is the part of the job I keep gravitating back to.

Marketing manager

I run demand generation for a B2B SaaS team of four. Last year I rebuilt our paid and content mix around three buyer problems instead of product features, and pipeline from organic went from roughly 15% to 34% of total. Before that I was a content specialist, so I still write. What draws me here is that you're at the stage where content has to carry pipeline, and that's the problem I've just solved once.

Career changer (teacher to customer success)

I spent six years teaching high school, which was really six years of onboarding 120 new people a year and keeping them engaged when they didn't want to be. I moved into customer-facing work last year, took a CS certification, and now handle renewals for 60 mid-market accounts with a 94% retention rate. I'm applying here because your customers are schools, and I've been on the other side of that relationship.

Leave these out

  • Your childhood, school choices or anything before your first relevant role.
  • A chronological list of every job — that is what the resume is for.
  • Salary, notice periods or why you dislike your current manager.
  • Numbers you cannot back up when they follow up on them.

Delivery notes

  • Say it out loud three times and time it. Reading it silently hides the length.
  • End on a clear stop so the interviewer knows it is their turn.
  • Adjust the past section per company — the same story, different evidence.
  • If you are interrupted, answer the interruption and do not restart the script.

Frequently asked questions

How long should my answer be?
60 to 90 seconds. Long enough to cover present, past and why-this-role; short enough that the interviewer still has time for follow-ups.
Should I talk about my personal life?
One short human detail is fine if it connects to the work. The rest of the answer should be about what you do and the results you have produced.
Is it the same as 'walk me through your resume'?
Close, but not identical. 'Walk me through your resume' invites a chronological tour. 'Tell me about yourself' wants a positioning statement that ends pointed at this job.
What if I am changing careers?
Lead with the transferable skill, name the pivot explicitly so it does not look like a gap, then show the evidence you have already built in the new direction.
Should I memorise it word for word?
Memorise the three beats and the numbers, not the sentences. A scripted delivery sounds rehearsed and falls apart when the interviewer interrupts.

Build your answer from your real resume

Hirelu’s Interview Coach drafts model answers grounded in the experience already on your resume and the role you are targeting — no invented achievements.

Start free

Related: common interview questions and answers, resume summary examples, interview coach.