RezPolish

RezPolish / Resume guides

Interview pitch

How to answer "Tell me about yourself" using your resume

Start with what you do now, go back briefly to how you got there, then say why this job is the next step. Your resume already holds every line you need; below is how to turn it into a 60 to 90 second answer, with eight worked examples.

By The RezPolish teamUpdated November 7, 20269 min read
Polish my resumeShort quiz first, about 2 minutes
A blank cream sheet on a wooden desk with a smooth grey stone on it and a red mug of coffee at one corner

To answer "Tell me about yourself", give a 60 to 90 second summary in three parts: what you do now (with one result), how you got here (one or two relevant steps), and why this job is the logical next one. That order, present, past, future, is a formula career coach Lily Zhang recommends in The Muse's guide to this question, and it works because it puts your strongest, most recent material first.

What most guides skip is where the content comes from. You have already written it: your headline, your summary and your best bullet points are the raw material. This page shows how to turn a resume into the answer, what follow-up questions each line will trigger, and eight worked answers for different kinds of candidate.

then back then forward,to this job 1 PRESENT What you do now plus one result about 25 sec 2 PAST How you got here one or two steps about 25 sec 3 FUTURE Why this role tied to the posting about 20 sec Spoken order 1, 2, 3. Total: 60 to 90 seconds.
You speak in the order 1, 2, 3, which is not the order things happened. Starting in the present means the interviewer hears your most relevant material while they are still paying full attention.

What the interviewer is really asking

It is rarely an invitation to tell your life story. In a first-round screen, the interviewer wants three things in about a minute: whether your background matches the job, whether you can explain yourself clearly, and what to ask next. It also decides what they ask next, which is the real reason to prepare it.

The question comes in several wordings, and they all want the same answer: "Walk me through your resume", "Tell us about your background", "Describe yourself", and in Indian HR rounds, "Introduce yourself" or "Give me your self introduction". The last two sometimes come with an expectation of name, education and family background, which we cover below.

Build your answer from your resume

If your resume is in decent shape, the answer is mostly a matter of reading it in a different order and saying it out loud. Each part of the answer has an obvious source.

Where each line of the answer comes from
Part of the answerTake it fromTurn it into
Present: who you areYour resume headline"I'm a data analyst, two years in e-commerce reporting."
Present: one resultYour best bullet with a number"Last quarter my returns analysis traced a third of complaints to three sellers."
Past: how you got hereEarlier roles, degree, one project"I started in customer support, which is where I learned SQL."
Future: why this jobYour objective plus the posting"Your team does pricing analytics, which is where I want to go next."

Turn your resume into a 60 to 90 second answer

  1. 1

    Rewrite your headline as a spoken sentence

    "Data Analyst | 2 yrs | SQL, Power BI" becomes "I'm a data analyst, I've spent the last two years building reports in SQL and Power BI for an e-commerce team." Spoken language is looser than resume language; that is fine.

  2. 2

    Pick one bullet to tell as a mini story

    Choose the result most related to this job, not the biggest one overall. One sentence of what you did, one of what changed. If your profile summary already leads with a result, use that.

  3. 3

    Choose one or two past steps that explain the path

    Not every job. Only what makes the present make sense: the degree that got you started, the role where you picked up the key skill, the reason you switched fields.

  4. 4

    Connect the ending to the posting

    Read the job description again and pick one thing it emphasises that you want more of. End on that. "Which is why this role caught my eye" is a fine closing line once you have said what "this" is.

  5. 5

    Say it out loud with a timer, then cut

    Most first drafts run over two minutes. Record yourself on your phone, listen once, and cut the sentence you would least miss. Do not memorise it word for word; memorise the three beats and the one number.

A 70-second answer, beat by beat

  1. 0:00

    Present

    "I'm a backend developer, four years in Java and Spring Boot, currently at a fintech in Pune where I work on the UPI payment services."

  2. 0:10

    One result

    "The piece I'm proudest of this year: our API latency was hurting checkout, and I reworked the caching and a few heavy queries, which brought p95 latency from about 900 milliseconds to 250."

  3. 0:30

    Past

    "I got into payments by accident. My first job was at an IT services company on a bank's reconciliation system, and I liked that a bug there had a rupee value attached to it."

  4. 0:50

    Future

    "What I want next is a product team where I own a service end to end, including on-call. Your posting talks about rebuilding the ledger service, which is exactly that kind of work."

  5. 1:10

    Stop

    Stop there. Do not add "So, yeah, that's me." Silence is the interviewer's cue to ask the next question, usually about the latency story.

Tell me about yourself sample answers

Each answer below is written to be spoken, so the sentences are shorter and looser than resume lines. They are examples built around imaginary candidates; swap in your own facts and leave out anything you cannot talk about for five minutes. Several are the same candidates whose written summaries appear on our profile summary examples page, so you can compare the written and spoken versions.

Fresher, engineering (India)
Good morning. I'm [name], I finished my B.Tech in Computer Science this year with a CGPA of 8.1.

Most of my time in the last year has gone into backend development in Java and Spring Boot. In my final year, three of us built a leave-management system for our college. I wrote the APIs and the database design, and it has been in use since January by about 300 students and staff, so I've already had real users find my bugs.

Before that I did a two-month internship at a small logistics company, fixing issues on their order-tracking dashboard. That's where I worked out that I prefer backend work to frontend.

I applied for this role because your team builds the services behind payments, and that's the kind of problem I want to spend the next few years on.

About 140 words. Read it aloud with a timer; if it runs past 90 seconds, cut a sentence. CGPA is mentioned once because campus recruiters often ask; drop it if you are not a recent graduate.

Fresher, commerce (India)
I'm [name], I completed my B.Com from a college in Hyderabad this year.

For the last six months I've been interning at a small CA practice, where I prepare GST returns for about twenty clients and post entries in Tally Prime. During the September audit season I also helped the team with vouching and ledger scrutiny for two companies.

I chose commerce because I liked accounts in school, and the internship confirmed it. I'm happiest when a reconciliation finally matches.

I'm looking for an Accounts Executive role where I can learn the full month-end close, and your posting mentions GST and Tally, which is what I already do every week.
Experienced professional moving up
I'm a data analyst, and for the last two years I've been on the category team at an e-commerce company, building the SQL and Power BI reports that about twenty people use every morning.

The work I'm proudest of is a returns analysis from last quarter. Damaged-item complaints were rising, and when I broke them down by seller, three sellers accounted for about a third of them. That changed how we onboard sellers.

I started in customer support, actually. I learned SQL to answer my own questions about tickets, and my manager moved me to analytics after a year.

I'm now looking for a role where I work closer to pricing decisions, and your team's focus on pricing analytics is why I applied.
Career changer (US or UK)
I've spent the last five years teaching high school math, and for the past year I've been moving into instructional design.

The bridge was remote learning. When our school went online, I recorded about forty short video lessons and rebuilt my units for our learning platform, and I found I enjoyed designing the course more than delivering it. Since then I've built three short courses in Articulate Rise, one of which our district now uses to onboard substitute teachers.

What I bring from the classroom is knowing when a learner is lost, because I've watched it happen thirty times a day.

Your role is about onboarding new sales staff, which is a teaching problem with a different audience.

Spend less time on the past, not more. Name the bridge once and get to what transfers.

Returning after a career break
I'm a software tester with five years of experience, mostly on banking apps.

In my last role I led regression testing for a mobile banking app with around two million users, and I built the team's first API test suite in Postman.

I took eighteen months off to care for my father after his surgery. He's doing well now. While I was away I finished an API testing course and did a few freelance test cycles, so I'm current on tools.

I'm looking for a QA role where API testing is a big part of the job, which is how I read this one.

The break gets two sentences and no apology. If they want more, they will ask. Our employment gap guide has wording for other reasons.

Nursing interview
I'm a registered nurse with five years in a thirty-bed medical ICU.

Most of my patients are ventilated or on dialysis, and for the last two years I've also been the nurse who trains new joiners on our ICU checklist. Last year I led the night shift for about six months while our charge nurse was on leave.

I started on a general medical ward after my B.Sc, and moved to the ICU because I wanted to work with sicker patients and a smaller team.

I'm applying here because your unit is bigger and does cardiac cases, which I want more experience with before I move towards a charge nurse role.
Manager or senior candidate
I run B2B sales for the Western region at a SaaS company that sells to mid-size manufacturers. I have a team of five, and we went from zero to sixty-four paying accounts in three years.

The part of that I'd point to is how we did it. Our early deals were taking nine months, mostly because we were selling to IT. I moved us to selling to plant heads, with a two-week pilot on one production line, and that cut the cycle to about four months.

Before this I spent five years in field sales for an industrial equipment company, which is where I learned how plant managers think about risk.

I'm looking to run a national team, and your plan to expand into the South is the kind of build I've done once and want to do again at a bigger scale.

Senior candidates can take a little longer. Spend the extra seconds on how you did it, not on more history.

Thirty-second version (career fair or phone screen)
I'm a final-year Computer Science student, graduating next May. I've spent the last year on backend work in Python and Django, including a summer internship where I built an internal tool that the support team still uses to search tickets. I'm looking for graduate software roles, and I'd like to hear what your new grad engineers work on in their first year.

Self introduction in an interview (India)

In many Indian interviews, especially campus placements and HR rounds, the question is phrased "Introduce yourself", and some interviewers expect a more formal structure: greeting, name, education, then the rest. That is fine; start with the greeting and name, then move straight into the present-past-future answer. Family details ("my father is a businessman, my mother is a homemaker") and hobbies are worth one short sentence at most, and only if the interviewer seems to want them. They take time away from the part that gets you shortlisted.

Follow-up questions your answer will trigger

Follow-ups to expect
If you sayExpect
"Built an app used by 300 students"How did you handle two people editing the same record? What would you change now?
"I left after a year"Why did you leave? What would your manager say about you?
"I'm interested in your company"What do you know about what we do?
"I took a break for a while"What did you do during it? Are you ready to start full time?
A number ("cut latency to 250 ms")How did you measure it? What was your part and what was the team's?

Mistakes that make the answer drag

  • Starting with where you were born or which school you went to. Start in the present.
  • Reading out your resume in order, job by job. The interviewer has it in front of them.
  • Listing adjectives: hard-working, passionate, quick learner. Show one of them with a story instead.
  • Running past two minutes. Long answers come across as nervous, even when they are well prepared.
  • Ending vaguely ("so that is about me"). End on why this job, then stop talking.
  • Saying something you cannot back up when they ask about it.

Questions people ask

How long should my answer to "Tell me about yourself" be?

Aim for 60 to 90 seconds in most interviews. Time it on your phone rather than counting words, because people speak at very different speeds. A phone screen or career fair needs a 30-second version. Senior candidates can take up to two minutes, but no longer.

Should I talk about my personal life or hobbies?

Keep it to one line, and only if it connects to the job or makes you memorable in a useful way. The question is about your professional story. If the interviewer wants personal detail, they will ask a separate question.

Is "walk me through your resume" the same question?

Nearly. "Walk me through your resume" invites a bit more chronology, so you can give the past part a few more seconds. Still start with the present and end with why you are here.

Should I memorise my answer?

Memorise the structure, the one result and the closing line, not every word. A word-for-word answer sounds recited, and if you lose your place it is harder to recover than if you are working from three beats.

How do I answer as a fresher with no experience?

Use your degree as the present, your best project or internship as the result, and what drew you to the field as the past. The fresher examples above follow exactly that pattern. Freshers in India can also look at our resume format for freshers, since the same project will lead both.

Keep reading