Guides › Interview prep
"Tell me about yourself": a spoken structure that works
"Tell me about yourself" is often the first question in an interview, and it is deceptively hard. It is so open that people either recite their whole resume or freeze. Because it comes first, it also sets the tone. A clear, confident answer settles your nerves, and a rambling one can follow you through the next twenty minutes.
The good news is that this is the one question you can very likely expect, so it is worth preparing carefully. This guide gives you a spoken structure, an example, the usual mistakes, and a way to adapt your answer to each job description.
What the interviewer is really asking
The question is rarely a request for your life story. Usually the interviewer wants to know three things: who you are professionally, why you are a reasonable fit for this role, and whether you can communicate a clear thought. It is also a low-pressure way for them to begin the conversation and decide where to dig in next.
That means your answer is a short pitch with a point of view, not a chronological tour.
A three-part spoken structure
A structure many candidates find helpful is Present, Past, Future. Here is our own way of framing it for speech.
- Present: what you do now, in one or two sentences. Name your role and the kind of work you are strongest at.
- Past: two or three highlights that explain how you got here. Choose experiences that connect to the role. These are chosen, not complete.
- Future: why this role, and why now. End by pointing toward the job you are interviewing for.
A useful target for a spoken answer is about 60 to 90 seconds. That is roughly the length where you can say something real without losing the listener, though context matters. Some interviewers want a bit more and some want less.
Notice what is missing: your education history, your first job from a decade ago, hobbies (unless they are relevant), and anything that sounds like reading your resume aloud. The interviewer likely has your resume in front of them. Your job is to give them the story behind it.
An example answer
This is an invented example for a hypothetical applicant to a customer support operations role. It is meant to show the shape, not to be copied.
Example: "I'm currently a support team lead at a mid-sized software company, where I manage a team of six and own our escalation process. What I enjoy most is turning repeated customer problems into fixes, so fewer people have to contact us in the first place.
Before that, I started as a support agent, and in that time I noticed we kept answering the same billing questions. I wrote a set of help articles and worked with the product team to clarify two confusing screens. That project got me into process work, and I've been doing more of it since, including building our current escalation guide.
I'm interested in this role because it focuses on support operations rather than only handling tickets, and that's where I've been moving. I'd like to work on a larger system where improving the process helps more customers at once."
Let us break it down:
- Present (first paragraph): A role, a scope, and a theme: turning repeated problems into fixes.
- Past (second paragraph): One concrete story that explains the theme. No list of every employer.
- Future (third paragraph): Connects the trajectory to the target job without flattery.
Read aloud at a normal pace, that is roughly in the range of a minute to a minute and a half.
Adapting it to the job description
The same person might give two different versions of this answer depending on the role. The way to adapt is to read the job description and pick out what it emphasizes.
- Underline the three or four recurring themes. If a posting repeats "stakeholders," "process improvement," and "reporting," those are the themes your answer should touch.
- Choose your highlights to match. From your many experiences, select the two or three that best support those themes.
- Use the posting's vocabulary honestly. If it says "escalation management" and you call it "handling difficult tickets," consider using their term, as long as it truly describes what you did.
- Point the Future part at something specific. A generic "I'm excited about this opportunity" tells them nothing. Naming a real piece of the role does.
Prepare a core version of your answer and a quick swap list: which highlights you would change for which type of role. For more on pulling themes out of a posting, see how to predict interview questions from a job posting and tailoring your resume to a job description.
Common mistakes
- Reciting your resume. If your answer is a list of employers and dates, you are duplicating a document they already have.
- Going too long. Several minutes of backstory is a common trap. If you notice you are two minutes in and still in the past, wrap up.
- Going too short. "I'm a marketing person with five years of experience" leaves the interviewer to do all the work.
- Too much personal detail. A single sentence about something outside work can humanize you, but long personal stories usually pull the answer off-track.
- Apologizing or hedging. Phrases like "I don't really have much to say" or "I guess I'm just..." undermine you before you begin.
- Negativity about a current or past employer. Frame transitions as moving toward something, not escaping something.
- A memorized monologue. A fully scripted answer can sound like a recording. Know your three parts and your key sentences and let the rest vary.
- Skipping the ending. The answer should land on why you want this job. Without that, it feels unfinished.
Handling variations
The question comes in other forms: "Walk me through your resume," "Why don't you start by introducing yourself?" or "What brings you here?" The same three-part structure works for each. For "walk me through your resume," you might take a little longer and go slightly more chronologically, but still choose highlights rather than recite everything.
If you are early in your career or changing fields, lean on projects, coursework, volunteering, or transferable skills instead of job titles. The structure is the same: present focus, relevant past, clear future.
Rehearse the first thirty seconds hardest
The opening is where nerves bite. Many people find it useful to rehearse the first two sentences until they come out smoothly, then trust themselves to improvise the middle. Practicing this out loud, rather than silently, is the only way to find out whether your sentences work when spoken. See practice interview answers out loud for a simple routine. If you are also working on salary conversations later in the process, salary expectations in interviews covers that separate question.
Practice this
Write three bullet points for each of Present, Past, and Future, not a full script. Then say your answer out loud with a timer and record it. Check that you stayed under about 90 seconds, that the Past section had one real story, and that the ending named something specific about the role. Then adjust it for the next job description. A MyPrepGuru voice mock can build its second round from your pasted job description, but you can start with your phone's voice recorder today.