HOTSEAT.
How it worksBlogPricing
Sign inStart free interview
Start
Blog/Interview answers

How to Answer ‘Tell Me About Yourself’

How to give a short, natural introduction that connects your background to the job, with examples for freshers, career changers and experienced candidates.

HotSeat team

Updated November 2026 · 3 min read

In this article

  • Present, past, future
  • What it sounds like
  • If your background is less straightforward
  • Where it usually goes wrong
  • Be ready for what comes next

It's usually the first thing they ask, and it sounds like the easiest. Then you open your mouth and hear yourself saying ‘so, I was born in…’ or reading your resume aloud to someone holding your resume.

Treat it as a short pitch for why you're in this room. In a minute or two, the interviewer should know what you do, what you've done that's relevant, and why you want this job. And because it opens the conversation, whatever you mention is probably what they'll ask about next, so you get to choose where the interview goes.

In this article
  • Present, past, future
  • What it sounds like
  • If your background is less straightforward
  • Where it usually goes wrong
  • Be ready for what comes next

Present, past, future

This three-part order works for almost everyone:

  1. Present. Say what you do now, what you recently studied or the kind of work you're moving towards.
  2. Relevant past. Pick one or two experiences that show a skill this job needs, and skip the rest. That summer job can stay on the resume.
  3. Future. Finish with what you want next and why this role gives you that. This is the part people forget, and it's what makes the answer about this interview.

What it sounds like

An invented example for a backend developer:

Could be anyone
“I have five years of experience in software and have worked on many projects with different technologies. I am hardworking and always ready to learn.”

Nothing here is wrong, but an interviewer will have forgotten it by the next sentence.

Could only be you
“I'm a backend developer, and for the last five years I've mostly worked on payment and support systems. In my current role, I helped redesign a slow refund process and cut the average processing time from two days to four hours. Now I'm looking for larger systems and more say in the technical decisions, which is what drew me to this role.”

Notice the bait: an interviewer will almost certainly ask about that refund process, so make sure it's a story you want to tell.

If your background is less straightforward

If you're a fresher, lead with what you studied and one project you can talk about in depth, then say what kind of work you want. Don't list your subjects. They'll assume you attended the classes.

If you're changing careers, don't apologise for your old one. Say why you're switching and what you've already done about it, like a course or a side project, then name what carries over.

If you're coming back after a gap, you don't have to explain it in your opening or share anything private. Talk about your experience, mention anything relevant you did during that time if you want to, and say you're ready for this role.

Where it usually goes wrong

The most common mistake is starting too far back. Your school science fair may be a lovely story, but you've got about two minutes and it's eaten thirty seconds of them.

The next is relying on labels. ‘Passionate’, ‘hardworking’ and ‘team player’ don't mean much until there's an example attached, and once you have the example you won't need the label.

The last is memorising it word for word. A script sounds fine until the interviewer cuts in with ‘sorry, which company was that?’ and you lose your place. Learn the three points and say them a little differently each time you practise.

Be ready for what comes next

A good introduction invites follow-ups. These are the likely ones:

What was your contribution to that project?

Why they ask: They want to separate your work from the team's.

  • Name what you were responsible for
  • Describe one decision you made
  • Connect it to the result

Why are you looking to move now?

Why they ask: They're checking that you're moving towards something, rather than just running away.

  • Stay respectful about your current job
  • Say what you want more of
  • Link that to this role

Why did you change fields?

Why they ask: They want to know the change is thought through and likely to last.

  • Explain what drew you in
  • Show what you've already done
  • Name the skills that transfer

Say your introduction out loud, then take the next question

A live practice interview shows you whether your opening holds up, and where it leads.

Practise your introduction

Sources and further reading

  1. Interviewing (Harvard FAS Mignone Center for Career Success)
  2. Interview tips (UK National Careers Service)

Keep reading

Interview answers

10 Common Interview Questions and How to Answer

4 min read

Interview answers

How to Stop Rambling in an Interview

3 min read

Interview answers

How to Answer ‘Why Should We Hire You?’

2 min read

HOTSEAT.

AI mock interviews under pressure, with feedback connected to what you actually said.

Follow HotSeat

InstagramYouTubeThreads

Product

  • AI mock interview
  • Live interview
  • Text-based interview
  • Knowledge tests
  • Pricing

Practice by role

  • Software engineer
  • Frontend developer
  • Data analyst
  • Product manager
  • Freshers
  • View all roles

Resources

  • Behavioral questions
  • HR questions
  • Blog
  • How it works
  • FAQ

Legal & help

  • About HotSeat
  • Privacy policy
  • Refund & cancellation
  • Contact

© 2026 Marsaze SYP Solutions Private Limited. HotSeat is a product of Marsaze.

Made with ♥ in India