How to Answer “Tell Me About Yourself” in an Interview

1. How to answer “Tell me about yourself”

The first thing to settle is what the question is not. It is not an invitation to tell your life story, and it is not a request to read your résumé aloud. The interviewer already has the résumé. What they want is the version you would give if you had one minute to explain why your background makes sense for this job.

So treat it as a prioritization exercise. Out of everything you could say, which two or three things would most change the interviewer's view of you as a candidate for this role? Those go in. Everything else — the summer job from a decade ago, the degree that has nothing to do with the work, the detailed org chart of your last employer — stays out unless it comes up later.

A structure that holds up across almost every interview looks like this:

• Present. Who are you professionally right now — your role, your status, the work you own.
• Past. Which experience, skill, or accomplishment best explains why you fit this opportunity.
• Future. Why this role is a logical next step, and what specifically drew you to it.

That order works because it starts where the interviewer's attention already is (what you do now), uses the past as evidence rather than as a timeline, and ends on the thing they most want to know — whether you actually want this job or applied to forty of them.

There is no single perfect script, and you should be suspicious of anyone who says otherwise. A tell me about yourself interview answer that works for a hospital charge nurse will not work for a first-year designer. What transfers is the structure and the discipline of relevance; the content has to be yours.

2. Why interviewers ask this question

Interviewers ask it for practical reasons, and understanding them makes it much easier to aim your answer.

• • To open the conversation. It is an easy first question that lets both sides settle in.
• • To hear your professional story in your words. A résumé is a list; this is the narrative that connects the entries.
• • To identify relevant experience quickly. Interviewers often have limited time and a long posting to cover.
• • To see how you understand your own fit. What you choose to lead with tells them what you think matters.
• • To decide what to explore next. Most follow-up questions come straight out of your answer.

That last point is worth sitting with. Because the question is broad, whatever you mention becomes the agenda for the next few minutes. Say you rebuilt a reporting process and you will probably be asked about it. Say nothing specific and the interviewer has to start from scratch. You have more influence over the direction of an interview in this first answer than almost anywhere else in it.

It is also, quietly, a test of judgment. Anyone can talk for five minutes about themselves. Choosing which ninety seconds matter is a skill, and it is one most jobs actually use — in status updates, in client calls, in handovers. Interviewers notice whether you can do it.

One thing to ignore: confident claims that hiring managers make up their minds in the first eight seconds, or that a fixed percentage of decisions are made during this question. Those numbers circulate widely and are not something you should plan around. Give a clear, relevant answer and let the rest of the interview do its job.

3. The present–past–future formula

Here is the framework in more depth, with what belongs in each part.

Two practical notes. First, the proportions shift with experience: an entry-level candidate spends more time on education and projects, a senior candidate spends more on scope and results. Second, the future part is the one candidates most often skip, and it is the easiest to make specific. “Which is why this role caught my attention” is fine; “which is why the fact that this role owns the documentation rather than reviewing it caught my attention” is better.

Use the template below as scaffolding while you draft. Fill in the brackets with your own details and then rewrite the whole thing in your normal speaking voice — the point is the shape, not the wording.

I'm currently a [role or status] with experience in [relevant area].
In my current role, I [main responsibility], and recently I [one relevant accomplishment].
Before that, [brief relevant background that led here].
I'm now looking for [the next step you want], which is why this [role / team / company] caught my attention.

If you prefer to prepare in bullets rather than sentences — which usually produces a more natural delivery — use this version instead and speak from the notes rather than reading them.

PRESENT
- Job title or status:
- What I own day to day:
- The skill this employer cares most about:

PAST
- Experience that best explains why I fit:
- One accomplishment with a concrete outcome:
- Anything that explains my path (degree, training, earlier field):

FUTURE
- What I want next:
- What specifically drew me to this role:
- The link between my background and this job:

4. What to include in your answer

The candidates for inclusion are fairly short. Work through the list and keep only what supports your fit for this specific job.

• • Your current professional situation — role, field, and what you own.
• • The experience most relevant to what the posting asks for.
• • Two or three skills the employer named, with something behind them.
• • One or two accomplishments with a concrete outcome.
• • Relevant education, training, or certification — heavier weight if you are early-career.
• • A specific reason you are interested in this role.
• • The connecting thread between your background and the opportunity.

Relevance is the filter for all of it. Somebody with ten years of experience does not need to account for each job in order; two or three roles that build toward this one, plus a sentence acknowledging the earlier years, is enough. Interviewers are rarely confused by omission — they will ask if they want the rest.

An early-career candidate has a different problem: less employment history to draw on. The answer is to widen what counts as experience. Coursework where you produced something real, internships, capstone or class projects, volunteer work, military service, campus organizations you actually ran, part-time jobs that required judgment — all of these are legitimate evidence when you describe what you did and what came of it.

One more inclusion worth planning: if there is something in your history the interviewer will visibly wonder about — a career change, a gap, a move across the country — a brief, unbothered sentence here saves an awkward question later. You control the framing when you raise it yourself.

5. What not to say

Most weak answers fail in predictable ways. These are the ones worth checking your draft against.

6. Tell me about yourself examples

The sample answers below are illustrative models, not real people. The names of employers are left out on purpose and the accomplishments are invented to show the shape of a good answer. Read them for structure — where the present ends and the past begins, how much detail a single accomplishment needs, how the ending connects back to the role — and then write yours from your own experience.

Do not borrow an accomplishment you did not achieve. Beyond the obvious problem, a fabricated detail is fragile: the interviewer's next question is usually “tell me more about that,” and there is nothing behind it. A modest true example that you can discuss for five minutes always outperforms an impressive one you cannot.

The examples cover the situations candidates ask about most: entry-level, experienced, career change, internship, management, returning after a gap, stepping up in seniority, remote roles, limited directly relevant experience, and customer-facing work.

7. Entry-level example

A recent graduate applying for a first full-time analyst role. The answer leans on education, an internship, and a project, because that is what exists — and it treats them as real work rather than apologizing for them.

I graduated in May with a degree in business analytics, and most of my hands-on experience comes from a summer internship with a regional logistics company and a capstone project I ran with three classmates.

During the internship I worked in the operations team, cleaning up their delivery-exception reporting. It had been tracked in three separate spreadsheets, and I consolidated it into one dashboard the dispatch supervisors actually opened each morning. My capstone was similar in spirit: we analyzed two years of campus dining transactions and presented staffing recommendations to the dining director.

What I took from both is that I like the part of analysis where you have to explain the numbers to someone who is going to act on them. This analyst role sits with the operations team rather than off to one side, which is exactly the setup I'm looking for in a first full-time job.

Why it works: the present is stated in one line without hedging. The past uses two specific pieces of evidence, each with an outcome someone can picture, rather than a list of coursework. And the ending names something concrete about the role — that the analyst sits with the operations team — which shows the posting was actually read. Notice there is no claim to years of experience the candidate does not have.

8. Experienced professional example

Someone with several years in the field. The temptation here is to cover everything; resist it. Pick the through-line that leads to this job.

I'm a registered nurse with about eight years in acute care, the last four of them in a twenty-eight-bed medical-surgical unit where I also serve as a charge nurse two or three shifts a week.

Most of my day is direct patient care, but the part I've grown into is the coordination side: running handoffs, balancing assignments when we're short, and being the person newer nurses come to when something is going sideways. Last year I helped rework our discharge-education process after we noticed patients were being sent home unclear about their medication changes, and readmission follow-up calls got noticeably easier for the team afterward.

I'm looking for a role where that coordination work is part of the job rather than something I fit around a full assignment, and this position is described that way, which is why I applied.

Why it works: eight years are summarized in one sentence rather than four. The answer then narrows to the specific capability the target role needs — coordination and leadership — and supports it with one accomplishment described in plain terms. There is exactly one loosely quantified detail and no statistics stacked on top of each other, which keeps it credible. The close explains the move without criticizing the current employer.

9. Career-change example

When you are changing fields, the interviewer's real question is whether the switch is considered or impulsive. Answer that directly: transferable skills, the reason for the change, and evidence you have already started.

I spent the last six years managing a restaurant with a staff of about twenty-five, and for the past year and a half I've been moving deliberately into IT support.

Running the restaurant was, in practice, a troubleshooting job: systems went down mid-service, the POS and scheduling software broke in creative ways, and I was the person who either fixed it or found who could. That's what made me look seriously at IT rather than treat it as a hobby. I completed the CompTIA A+ certification last spring, built a home lab where I run Windows and Linux machines, and I've been doing volunteer help-desk work for a local nonprofit about six hours a week.

I know I'm coming in with less formal IT experience than someone who has done it for six years. What I bring alongside the technical foundation is a lot of practice staying calm with frustrated people and documenting fixes so they don't recur, which is most of what a service-desk role asks for.

Why it works: it reframes six years of restaurant management as relevant rather than irrelevant, and it does so with specifics — systems failing mid-service — instead of a vague claim about transferable skills. The preparation is concrete: a certification, a home lab, ongoing volunteer work. And it names the experience gap once, calmly, then immediately says what compensates for it. That is confidence, not apology.

10. Internship example

For an internship, nobody expects professional employment. Interviewers are looking for genuine interest in the field, evidence you can do useful work, and a reason you picked this organization.

I'm a junior at State University studying mechanical engineering, with a minor in materials science.

The coursework that's been most useful so far is my design and CAD sequence — last semester my team designed and printed a modified bracket assembly for the university's solar car project, and I did most of the SolidWorks modeling and the tolerance checks. I've been on the solar car team for two years, and this year I'm one of two students responsible for the chassis subsystem, which means a lot of small practical decisions about what we can actually manufacture in the shop.

I applied for this internship because your team works on production tooling rather than pure design, and the gap I'm most aware of in my own experience is what happens between a drawing and a part that can be made repeatably. A summer in that environment would teach me more than another semester of coursework.

Why it works: the field of study is stated immediately, then the answer moves straight to something the student built with a named tool. The solar car team supplies both practical experience and evidence of commitment over time. Best of all, the ending identifies a specific gap in the candidate's own knowledge that the internship would fill, which is a much stronger reason for applying than enthusiasm alone. A tell me about yourself internship answer does not need to sound senior — it needs to sound genuinely interested and honest about where you are.

11. More sample answers by situation

Five more situations candidates commonly ask about. Each one has a different job to do, so the emphasis moves rather than the job title.

A. Manager or leadership candidate

Lead with the size and shape of what you manage, then show that you have a view about how to run a team, not just that you have held the title.

I currently manage a customer support team of eleven, split across two shifts, for a mid-sized software company.

I moved into management about four years ago after leading the escalations queue, so most of what I know about the work I learned doing it. My focus since taking over the team has been reducing the number of tickets that bounce between people — we rewrote the triage rules and gave frontline agents authority to resolve a wider set of issues, which cut handoffs meaningfully and made the queue less demoralizing to work in.

I'm interested in this role because it's a larger team with a mandate to build the support function properly rather than keep it afloat, and building is the part of management I'd rather spend my time on.

B. Returning after an employment gap

Address the gap in one short, matter-of-fact sentence and move on. You are under no obligation to disclose medical, family, or other private circumstances — “for personal reasons” is a complete answer, and how much more you share is entirely your decision. What helps most is showing your skills stayed current.

I'm a payroll specialist with about nine years of experience, most recently with a manufacturing company running multi-state payroll for roughly four hundred employees.

I stepped away from full-time work for about fourteen months for personal reasons, and I've been actively returning to the field since the spring. During that time I kept my certification current and completed a refresher course on the payroll platform your posting mentions, because I didn't want to come back rusty.

What I'm looking for is a stable payroll role where accuracy and compliance actually matter to the organization, which is how this position reads. I'd be glad to go into any part of my background in more detail.

C. Moving into a more senior role

Show that you have already been operating at the next level. Scope, ownership, and responsibility for other people are the signals a hiring manager is listening for.

I'm a project manager in commercial construction, currently running two mid-size fit-out projects at a time, typically in the two-to-five-million-dollar range.

Over the last couple of years my scope has widened past scheduling and coordination into the parts a senior PM usually owns: budget reforecasting, direct client conversations when something changes, and mentoring the two assistant PMs on our team. On my most recent project I took over midstream after the original PM left, and we closed it within the revised budget and only slightly behind the original schedule despite a long lead-time delay on glazing.

This senior role is the formal version of work I've largely been doing informally, which is why it interested me. I'd rather grow into a title I've been practicing for than change direction.

D. Remote-role candidate

Beyond the work itself, employers want to know you can operate without someone nearby. Say how you communicate and make decisions, not just that you “love remote work.”

I'm a technical writer with five years of experience, and the last three of those have been fully remote with a distributed team across four time zones.

I currently own the documentation for two product areas, which means working from engineering tickets and release notes, interviewing engineers, and keeping a style guide that other contributors actually follow. Remote work suits how I operate: I write detailed updates, I'm comfortable making decisions asynchronously, and I've learned to flag a blocker early rather than wait for a meeting to surface it.

I applied here because the role is documentation ownership rather than ticket-taking, and because your team is remote by design rather than by exception, which in my experience makes a real difference to how the work runs.

E. Limited directly relevant experience

Do not pretend the gap is not there. Name the overlapping parts of your current work in detail, then show what you have done deliberately to close the distance.

I've spent the last four years in retail, the last two as a keyholder, and I'm moving into administrative work.

The parts of my current job that overlap most with this role are the ones customers never see: I do the daily cash reconciliation, build the weekly schedule for eleven people, and handle vendor deliveries and the paperwork that comes with them. I'm the person who catches when the count is off by eleven dollars and goes back through the receipts to find why.

I'm honest that I haven't held an administrative title before. What I have is four years of doing scheduling, reconciliation, and records work accurately under time pressure, plus recent coursework in Excel and QuickBooks that I took specifically to make this move.

F. Customer-facing role

Here the interviewer is partly listening to how you speak, not only to what you say. A short illustration of how you handle a difficult moment does more than any adjective.

I've worked in front-desk and guest services roles for about six years, currently at a hundred-and-forty-room hotel where I handle check-in, complaints, and the overnight audit twice a week.

The part of the job I'm best at is the difficult conversation — an overbooked night, a billing dispute, a guest whose flight arrived at two in the morning. I've found that most of those go well if the guest believes you're actually going to do something, so I try to tell people what I can do before I tell them what I can't.

I'm applying here because this role keeps the guest-facing work but adds ownership of the booking system and staff scheduling, and that mix of people work and process work is where I'd like to keep developing.

12. How to practice your answer

Preparation for this question takes about half an hour, and it is worth doing properly because the same material feeds several other answers.

1. 1. Write bullets, not sentences. Dump everything that might belong: roles, skills, results, reasons for applying. Do not edit yet.
2. 2. Cut to what is relevant. Reread the job posting and delete anything it does not touch. Most people lose half their list here.
3. 3. Say it out loud. Silently rehearsing hides how long an answer really is and which sentences you stumble over.
4. 4. Time it once, as a check. If you are at three minutes, cut. If you finish in twenty seconds, add evidence. Then stop watching the clock.
5. 5. Remove the details nobody needs. Exact dates, former colleagues' names, internal team names, background that sets up a point you never make.
6. 6. Practice until you know the beats. Three or four run-throughs is usually enough to hold the structure without locking in the wording.
7. 7. Swap the ending per employer. The present and past stay largely stable; the final lines should be rewritten for each role you interview for.

Aim for conversational delivery. An answer that sounds slightly unpolished but genuinely spoken lands better than a paragraph delivered from memory, and it survives being interrupted — which happens often, since interviewers frequently jump in on something interesting. If you can be interrupted at any point and pick the thread back up, you have practiced enough.

This question also does not exist in isolation. If you have a full interview to get ready for, work through the broader step-by-step job interview preparation process — company research, matching your experience to the posting, accomplishment examples, and logistics — and use this answer as the opening piece of it.

13. Tell me about yourself checklist

Run your draft against this before the interview.

No answer guarantees an offer. Hiring depends on the other candidates, the budget, the timing, and plenty of factors nobody in the room controls. What a well-prepared opening does reliably do is make sure the interviewer hears the most useful things about you instead of whatever came out first.

Prepare for the compensation questions too

“Tell me about yourself” is one question among several you can prepare for in advance, and compensation is usually not far behind it — sometimes in the same first call. Once your introduction is ready, work out what you will say when the subject of pay comes up, using our guide to answering the salary expectations question. If you are filling in application forms as well, see what to put for desired salary, and once an offer arrives, how to negotiate salary.

Frequently asked questions