Skip to content
Job interviews

How to Answer "Tell Me About Yourself" (With Examples by Career Stage)

"Tell me about yourself" is not a request for your life story. It is a 60 to 90 second pitch that tells the interviewer why you are in the room. Here is a three-part formula, six example answers for different career stages, and the mistakes that make this question harder than it needs to be.

By NORDON Team

8 min read

Also in Srpski, Hrvatski, Deutsch, Français, Español, Português

What the interviewer actually wants

This is usually the first question, and interviewers use it for three things: to hear how you talk about your work, to pick topics for the rest of the conversation, and to settle in. They are not testing your memory of your CV. They have it in front of them.

So treat it as a short pitch with one job: connect who you are now to the role you are interviewing for. Everything that does not serve that connection can go.

The formula: present, past, future

  1. Present (20 to 30 seconds). What you do now, at what level, and one concrete thing you are good at or proud of.
  2. Past (20 to 30 seconds). How you got here: one or two earlier steps that explain your skills. Pick only what is relevant to this role.
  3. Future (15 to 20 seconds). Why this role, at this company, is the logical next step. Be specific about what draws you.

Total: 60 to 90 seconds, roughly 150 to 220 spoken words. That is shorter than most people expect. If you go past two minutes, the interviewer starts waiting for you to finish instead of listening.

Template: Fill-in skeleton
PRESENT: I'm a [role] at [company or type of company], where I [main responsibility]. Lately I've been [one specific project or result].

PAST: Before that, I [previous role or study], which is where I learned [skill that matters for this job].

FUTURE: I'm looking for [what you want next], and this role stood out because [specific thing about the team, product or work]. That's why I'm excited to talk today.

Example answers by career stage

These are fictional examples. Use them to see the shape and the level of detail, then build your own from your real experience.

Student or recent graduate

Example: Lena, applying for a junior data analyst role

"I just finished my degree in economics, and the part I enjoyed most was anything with real data. For my final project I analyzed three years of public transport ridership for our city and found that two bus lines were losing riders mainly on weekends, which the city council later asked to see.

Alongside my studies I worked part time in a bike shop, where I set up a simple spreadsheet to track which parts sold out first. It cut the number of rush orders we placed, and it's honestly where I got hooked on using data for everyday decisions.

I'm looking for a first role where I can do that full time with a team that uses SQL and dashboards daily. Your job ad mentions building reports for operations teams, which is exactly the kind of work I want to learn from."

Early career (1 to 4 years)

Example: Marco, frontend developer moving to a product company

"I'm a frontend developer at a digital agency, where for the last two years I've built web apps for clients in retail and travel, mostly in React and TypeScript. The project I'm proudest of is a booking flow I rebuilt for a hotel group, which made the pages load noticeably faster on mobile.

I started in the agency's QA team, so I still think about edge cases and accessibility before I write a line of code.

Agency work means I hand projects over just as they get interesting. I want to stay with one product and improve it over years, and your team's focus on a single design system is a big reason I applied."

Mid-career

Example: Priya, customer success manager

"I manage a portfolio of about 40 mid-market accounts at a logistics software company. My focus is renewals and expansion, and over the last year I've built a quarterly review format that the rest of the team now uses.

I came into customer success from support, where I spent three years on the phone with the same kind of customers. That background means I can usually spot an account at risk from how their tickets change, before it shows in the numbers.

I'm now looking to work with larger accounts and a more technical product. Your platform sells to enterprise operations teams, which is where I want to grow next."

Career changer

Example: Daniel, teacher moving into instructional design

"For the past seven years I've taught high school biology. The part of the job I've loved most is designing lessons: turning a difficult topic into a sequence that a sixteen-year-old can follow, and then fixing it based on where students got stuck.

Over the last two years I took that further. I built our school's online course for remote students and completed a certificate in instructional design, where my capstone was a short onboarding course for a local nonprofit.

I want to do this work full time for adult learners, and your team's focus on onboarding for new hires is a very direct fit with what I've been building."

Returning after a gap

Example: Sara, accountant returning after two years of caregiving

"I'm an accountant with six years of experience in month-end close and reporting, most recently as a senior accountant at a manufacturing company.

Two years ago I stepped away to care for a family member. That's settled now, and over the last few months I've refreshed my skills: I completed an update course on the current reporting standards and I've been doing the books for a local nonprofit as a volunteer.

I'm ready to come back full time, and I'm drawn to this role because it's close to what I did before, with a team that's growing its reporting function."

Mention the gap once, briefly and without apology, then move to what you did to stay current. You do not owe personal details. "Family reasons" or "a health matter that is resolved" is enough.

Senior or manager

Example: Tomas, engineering manager

"I lead a team of eight engineers at a fintech company, responsible for our payments platform. Over the last two years we moved it from a single monolith to separate services without a major outage, and I hired five of the eight people on the team.

I was an engineer for ten years before managing, mostly in backend and infrastructure, so I can still hold a real technical conversation with my team and with architects.

What I want next is a role with more scope across teams. You're building a platform group from scratch, and setting up how several teams work together is the part of my job I've enjoyed most."

At senior level, the interviewer listens for scope (team size, budget, systems) and judgment, not tasks. Lead with the outcome of your leadership and keep the technical history to one sentence.

Adjusting for who is asking

InterviewerWhat to emphasize
Recruiter screenFit with the basic requirements, your motivation, a clean and short story.
Hiring managerOne concrete result that matches the role's main problem.
Peer or technicalThe tools and the kind of work you do day to day.
ExecutiveScope, outcomes and why this company, in fewer words.

Mistakes to cut

  • Reading your CV aloud. The interviewer has it. Pick the two or three facts that matter for this role.
  • Starting at birth. "I grew up in..." is rarely relevant. Start with what you do now unless your background is the point.
  • Personal details nobody asked for. Family, age and hobbies can wait, unless a hobby is directly relevant.
  • No ending. Trailing off with "so, yeah" wastes the best moment. Finish on why this role, then stop.
  • A memorized monologue. Know your three parts and two or three anchor facts. Say it a little differently each time so it sounds like you.
  • Talking for four minutes. Practice with a timer. Under 90 seconds is the target.

How to practice it

  1. Write your answer in bullets using the skeleton above, for this specific job ad.
  2. Say it out loud with a timer. Cut until it fits in 90 seconds.
  3. Record it once and listen. Does the last sentence explain why this role? Do you sound like you are reading?
  4. Prepare the two follow-ups it usually triggers: "Why are you leaving?" and "Why this company?". For your bigger stories, use the STAR method.
  5. Practice the first minute until it feels easy. A calm opening helps with the rest, which we cover in how to calm interview nerves.

If you want feedback on the spoken version, NORDON's Practice mode asks questions for the role you enter, scores each answer you give out loud and suggests a stronger version that only uses what you said and your documents, such as your CV. For role-specific questions that often follow, see the interview question library.

Try it in NORDON

Rehearse your opening with feedback

NORDON's Practice mode asks interview questions for the role and job ad you enter, scores each answer you give out loud from 1 to 10 and shows a stronger version to rehearse.

Questions

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

About 60 to 90 seconds. Two minutes is the upper limit. The interviewer will ask for more on anything that interests them.

Should I mention personal things like hobbies or family?

Usually not. Keep it professional unless a hobby or experience directly supports the role. A one-line personal touch at the end is fine if it feels natural.

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

Almost. It invites a little more chronology, so past, present, future often works better there. Keep it to the steps that matter and still end on why this role.

What if the interviewer cuts me off?

That is fine. It usually means they heard something they want to explore. Answer what they ask and do not try to return to the rest of your pitch.