How to Answer "Tell Me About Yourself" (+ 7 Example Answers)
A 60-to-90-second structure, five worked answers for different career stages, and the specific habits that make an interviewer stop listening.
By James O'Connor · Oct 15, 2026 · 12 min read

By the end of this guide you'll have a spoken answer to "Tell me about yourself" that lasts about a minute and a half, opens with the part of your background that matches the job, and hands the interview back to the person asking. You'll also have five worked examples to borrow the shape from — new graduate, promotion, industry switch, career change and return after a gap.
The question is not small talk with a trap in it. It is the one moment where you choose what the interview is about, so it rewards preparation more than almost any other question you'll be asked.
Why interviewers ask it
Interviewers open with this question for two practical reasons: it eases you into the conversation, and it shows them which parts of your qualifications and experience you think are most relevant to the job (Indeed, 2026-08-04). Some use it purely as an informal warm-up before the formal questions start.
What is being assessed is narrower than it sounds. One career coach describes hiring managers as typically checking four things through this question — professional experience related to the job, the skills to do it well, educational background, and compatibility with the company's culture (Tufts Alumni and Friends, January 2026).
Underneath those sits a competency you'll be judged on all day: prioritisation with no structure given to you. You've had no prompt, no word limit and no told-you-so about what matters. What you lead with, what you leave out and when you stop talking is evidence of how you handle an open brief and how you communicate to someone who doesn't yet know your work.
Other ways you'll hear it
The wording changes; the job the question does stays the same. Expect any of these (the first five are listed as common variations by Indeed, 2026-08-04):
- "I have your resume in front of me, but tell me more about yourself."
- "I'd love to learn more about your professional journey."
- "Tell me a little bit more about your background."
- "Describe yourself."
- "Tell me something about yourself that's not on your resume."
- "Walk me through your resume" or "So, what brings you here?"
Treat the last two in that list slightly differently. "Walk me through your resume" invites a short chronological account rather than a themed pitch, and "something that's not on your resume" is asking you not to repeat the document — so lead with a project, a responsibility or an interest the paperwork doesn't show.
How to build your answer
Use Past, Present, Future. Career coach Becky Farone describes it as the best structure for standard interviews, internal promotions and anyone with a reasonably linear path: Past is the evidence, Present is your value proposition, and Future is the goal that connects the two to the open role (Tufts Alumni and Friends, January 2026). A related source describes the same three beats as giving an interviewer context, proof and direction in under 90 seconds (Extern, 2026).
- Pick the through-line from the job posting. Read the responsibilities and choose the one or two the employer clearly cares most about. Everything in your answer has to point at those. This is the step most people skip, and it's the step the interviewer is actually scoring.
- Past — the evidence. Choose two or three experiences that prove you can do the thing in step one. Pick them by running each through the STAR method — situation, task, action, result — so you know the story has an ending before you tell it (Indeed, 2026-08-04). If you don't have much paid history, this is where internships, student projects, a final-year project, volunteering or community work go (Indeed, 2026-08-04).
- Present — the value proposition. One or two sentences on your current role, your scope and what you're known for right now. Scope matters: team size, budget, number of accounts, the kind of customer. It saves the interviewer from guessing how big your version of the job was.
- Future — the goal. Say plainly why this role is the right next step, in words taken from the posting. Without this, the answer is a history lesson and the interviewer has to work out the relevance themselves.
- Add one number and one pre-empted objection. Quantify at least one accomplishment, and anticipate the question or doubt your background invites — being overqualified, a gap, no industry experience (Tufts Alumni and Friends, January 2026). Saying it first makes it a fact rather than a discovery.
- Cut it to time. Farone's advice is blunt: "You must stick to 60 to 90 seconds max," because an answer that runs long risks losing the interviewer's attention (Tufts Alumni and Friends, January 2026). Two minutes is the outer limit (Indeed, 2026-08-04). Cut adjectives, job titles nobody outside your company understands, and any job more than about ten years old that isn't relevant.
- Rehearse out loud. Record yourself and listen back, then run it past a trusted partner or a career coach; you can also use AI tools to critique a written draft for brevity and impact (Tufts Alumni and Friends, January 2026). Rehearse the shape, not the script — a memorised paragraph sounds memorised.
If your current job is your strongest argument, flip the order to present, past, future. Both orderings are common and cover the same ground (Indeed, 2026-08-04). And customise the Future sentence for every single application — it takes a minute and it is the difference between an answer and a recording.
Example answers
Five answers, five different shapes. Read the one closest to your situation, then steal the structure rather than the words.
New graduate
Maya, statistics graduate, applying for a junior data analyst role at an insurer
I finished a statistics degree in May, and the part that stuck with me was my final-year project: I built a model predicting which bus routes in my city ran late using three years of open transit data, and presented it to the transport authority's planning team. That taught me more about cleaning messy data than any class did — two thirds of the work was fixing broken timestamps. Last summer I interned at a small credit union and rebuilt their weekly membership report in SQL so it ran on a schedule instead of taking someone a whole morning. I also tutored first-year stats for two years, which is where I got comfortable explaining a result to someone who doesn't want the maths. This role is claims analytics, and that's the mix I've been aiming at: real data with a real operational decision at the end of it.
Step up in the same field
Darren, senior support specialist, applying for a support team lead role
I look after enterprise accounts on the support desk at a payroll software company — about forty accounts, including the ones that escalate fastest. Last year our reopened-ticket rate was the team's worst number, so I started a Friday triage where we read every ticket that had been reopened twice. Most of them traced back to three badly written help articles. We rewrote them and reopens on those topics almost stopped. Since then I've run onboarding for four new hires on the desk and covered for my manager when she's out, which is how I learned the hard part of the job is the rota, not the tickets. I've been doing the lead role in pieces for about a year and I'd like to do it properly. Your posting mentions building out a tier-two function — that's the part I most want to own.
Industry switch, same job
Lena, marketing manager, moving from consumer goods into healthcare communications
You'll see I've spent eight years in consumer goods and none in healthcare, so let me deal with that first. What I actually do is lifecycle email and retention. At a household goods brand I owned the post-purchase programme, and rebuilding the welcome series around how people use the product — rather than when we wanted to sell them something — lifted repeat orders enough to pay for a second writer. The regulated side is new to me but not foreign: everything we sent went through legal review for claims language, and I learned to write with the reviewer in mind instead of arguing after the fact. What pulls me towards patient communications is that the message carries a consequence. If someone ignores a refill reminder, something happens. I'd rather spend the next eight years on that than on discount codes.
Career change into a new function
Ray, former restaurant general manager, applying for a facilities coordinator role at a hospital system
For nine years I ran a sixty-seat restaurant — hiring, the schedule, suppliers, health inspections, and whatever broke at seven on a Saturday night. The part I was best at was operations: I cut our produce waste substantially by changing how we ordered and counted stock, and I held a crew of twenty-two together through two kitchen refits. What I didn't want was another decade of nights. So over the past year I finished a facilities management certificate at my community college and shadowed a friend who coordinates work orders for a school district. The vocabulary is new — I had to learn what a CMMS is — but the job isn't: vendors who don't show, a budget that doesn't stretch, and people who need the room ready by nine. A hospital runs harder than a restaurant, and honestly that's the appeal.
Returning after a gap
Nadia, QA engineer, returning after three years out
I'm a QA engineer. I spent six years testing payments software, mostly automation — I owned the regression suite for a checkout product and got the nightly run from four hours to under one, largely by deleting tests that duplicated each other. I then took three years out to care for my father, who had dementia; he died last spring. I've kept current rather than waiting: since January I've been contributing test cases to an open-source scheduling tool and I rebuilt my own automation setup in Playwright, because the tooling moved while I was away and I didn't want to arrive rusty. What I want now is a team with a real suite and someone who can teach me the product domain, on a permanent basis rather than contract. Your posting says the suite is being rebuilt from scratch — that's the work I enjoy most.
Mistakes to avoid
| Mistake | Fix |
|---|---|
| Starting at birth and walking forward through every job you've held | Start at your current or most recent relevant role and go back no further than the job that first proves the skill they're hiring for. |
| Reading your resume back to them line by line — a listed avoidable in Indeed's guidance (2026-08-04) | Pick two or three items and add what the document can't show: the problem, your decision, the result. |
| Spending most of the answer on your personal life, which Indeed also flags as a common error (2026-08-04) | Keep it professional, and allow yourself one personal line at the end only if it genuinely connects to the work. |
| Giving the identical answer to every employer | Rewrite the final sentence for each application so it names a responsibility from that specific posting. |
| Running past two minutes and trailing off without an ending | Write one closing line, rehearse stopping on it, and time yourself against the 60-to-90-second mark (Tufts Alumni and Friends, January 2026). |
| Apologising for a gap, a redundancy or a missing credential | State it in one neutral sentence, then move straight to what you've done most recently. |
| Using internal jargon, product codenames or made-up job titles | Translate everything into words an outsider understands, including your own job title if it's unusual. |
Your answer checklist
Before you walk in, check your answer has all five:
- One opening sentence that says who you are professionally right now — role, field and scope, so the interviewer can place you immediately.
- Two or three pieces of evidence tied to the job's responsibilities, with at least one result you can state in numbers (Tufts Alumni and Friends, January 2026).
- A sentence that answers "why this role, why now", using language from the posting rather than generic enthusiasm.
- The obvious objection handled — the gap, the switch, the seniority — in one calm sentence rather than left hanging.
- A timed runtime of 60 to 90 seconds spoken aloud, with a clear ending line so the interviewer knows it's their turn.
Frequently asked questions
How long should the answer actually be?
Aim for 60 to 90 seconds. Career coach Becky Farone's advice is to stick to 60 to 90 seconds maximum, because a longer answer risks losing the interviewer's attention (Tufts Alumni and Friends, January 2026), and Indeed suggests practising until you can tell a great story about yourself in two minutes or less (2026-08-04). Time it with a stopwatch rather than guessing — most people's silent read is far faster than their nervous speaking voice. If the interviewer leans in, nods or asks a follow-up mid-answer, that's an invitation to say more about that specific point, not licence to restart the tour.
When in the interview does it come, and does that change the answer?
It usually comes first, which is why some interviewers use it to start an informal conversation before the formal questions begin (Indeed, 2026-08-04). The setting changes the emphasis more than the structure. In a short recruiter screening call, keep it tight and factual — availability, scope, why this job — because the screener is matching you to a brief. In a panel or a hiring manager interview, spend more of your 90 seconds on the evidence, since those people can judge the detail. Practice also varies by employer and by country: some interviewers expect a line of personal context, others will think it's padding. In US interviews you are generally safe keeping it professional and volunteering nothing about your personal circumstances.
What follow-up questions usually come next?
Whatever you leave on the table. If you mention a project, expect "tell me more about that one" — so only name examples you can discuss for five minutes. Common follow-ups include why you left or want to leave your current role, why this company specifically, what you'd want to do first in the job, and a request to expand on whichever result you quantified. You can use this. Deliberately leave one interesting detail slightly underexplained — a metric, an unusual project — and you steer the next question towards ground you've prepared.
What if I have almost no work experience, or a long gap?
Use the same structure with different evidence. For students, Indeed suggests talking about your major and educational background, relevant internships or student projects, and your final-year project if it fits the role (2026-08-04); for candidates with no professional experience at all, it suggests accomplishments from community work, volunteering, school and hobbies, particularly where they're relevant to the job (2026-08-04). For a gap, name it in one plain sentence and put the weight of the answer on what is current — recent study, contract work, volunteering, a self-directed project. Interviewers are generally more interested in what you've done in the last six months than in the reason for the two years before that.
Sources
- Indeed — Interview Question: "Tell Me About Yourself" (With Answers) (2026-08-04)
- Tufts Alumni and Friends (Tufts University) — How to Answer the "Tell Me About Yourself" Interview Question (2026-01)



