"Tell me about yourself" is the first real question in most interviews — and the one most candidates fumble. It feels casual, so people answer casually: a stream-of-consciousness career walkthrough, or a recitation of the resume, or worse, the life story. None of these work.
The interviewer is asking for a 90-second pitch. They want to know: what you do now, what you've done that's relevant to this role, and what you want to do next. That's it. The version most candidates give — the chronological walkthrough starting with "I grew up in..." — buries the relevant signal under 4 minutes of irrelevant background.
The formula that consistently works, especially for experienced candidates, is Present-Past-Future:
- Present (15-20 seconds): What you do right now — role, company, scope.
- Past (30-45 seconds): One or two highlights from your background that map directly to this role. Not a full timeline — just the relevant parts.
- Future (15-20 seconds): What you want to do next, and why this role fits.
Total: 60-90 seconds. Practice it once out loud, time it, and trim.
Below: the formula in detail, what to avoid, and 12 sample answers for experienced professionals, career changers, recent grads, and specific roles you can adapt.
The Present-Past-Future formula in detail
Present
Open with what you do now. One sentence. Role + company + one number or scope detail that signals seniority.
- "I'm a senior backend engineer at Stripe, where I own the billing platform for a team of seven."
- "I'm a marketing manager at a Series B fintech, running demand generation for the SMB segment."
- "I'm a charge nurse on a 30-bed med-surg floor at a Level II trauma center in Houston."
Bad version: "I currently work at [Company]." That's the resume. Add the scope detail that makes the role concrete.
Past
Pull one or two highlights from your background that map directly to the role you're interviewing for. The selection matters more than the breadth.
If you're interviewing for a role that wants experience scaling infrastructure, talk about the scaling work — not the early-career front-end role you had. If you're interviewing for a role that wants industry experience, talk about the relevant industry chunk.
A good highlight has three things:
- A specific accomplishment, not a job description
- A measurable result if possible
- A clear connection to the job you're interviewing for
Example: *"Before Stripe I spent four years at a Series A startup as one of the first three engineers, where I built the original payments integration that supports the company's $40M ARR. That's the work that pulled me toward billing as a specialization."*
Skip jobs that don't connect. Two strong highlights beat five thin ones.
Future
Close with what you want to do next, and why this role specifically fits. This is the bridge to the rest of the interview.
- "I'm looking for my next role to be at a company that's doing billing at much higher scale and complexity. That's why this role caught my attention."
- "I want my next move to be from individual contributor to leading a team. The JD said this role has three direct reports — that's the step I'm trying to take."
- "I want to spend the next few years deepening my expertise in healthcare specifically — and this role is on the team building exactly that."
This part also signals that you've actually thought about why this role, not just "I need a job."
What to leave out
A few patterns that derail the answer:
Personal background. Where you grew up, your hobbies, your family. None of it is what the interviewer asked. Unless you're explicitly being asked, save it.
Full chronological resume. "After graduating in 2014, I joined Company A, then in 2017 I moved to Company B, then..." The interviewer has your resume. They want signal, not a recap.
Your weaknesses or what you didn't like about past jobs. Save these for the questions designed for them.
Long-winded explanations of career pivots. A one-sentence acknowledgment is fine; a 2-minute justification isn't.
Filler openers. "That's a great question." "Where should I start?" "Well, let me think..." Skip them. Start with the answer.
Your education unless it's recent. If you've been working for 5+ years, lead with the work. Education comes up if it's relevant.
12 sample answers
Use the structure, swap in your real details, don't memorize the words.
1. Experienced software engineer
> *"I'm a senior backend engineer at Stripe, where I've been for two years owning the core billing platform — I lead a team of seven that handles roughly $X billion in invoice volume. Before Stripe I spent four years at a Series A startup as one of the first three engineers, where I built the original payments stack that grew with the company from zero to $40M ARR. That early-stage work is where I learned to build for scale before it arrives. I want my next role to be at a company operating billing at much higher complexity than I've seen — multi-currency, multi-product, with the kind of regulatory environment you have. That's why this role got my attention."*
2. Mid-level product manager
> *"I'm a senior PM at Notion, where I own the templates and starter content surface — about three engineers and two designers on the team. Before Notion I was at Figma for three years on the community products team, where I led the launch of one of their fastest-growing surfaces. The thread across both has been working on the part of the product where users decide whether to stay — onboarding, activation, and what they see in their first week. That's the work I want to keep doing, which is why this growth PM role at your stage of company is the right next move."*
3. Marketing manager
> *"I'm a marketing manager at a Series B B2B SaaS company, where I lead demand generation for the SMB segment — paid acquisition, lifecycle, conversion. Over the last two years I scaled monthly paid spend from $20K to $400K with a CAC that beats our target. Before this role I was at HubSpot on the inbound team for three years, where I learned how to build a content engine. I want my next role to be on the enterprise side — bigger deals, longer cycles, more multi-touch attribution complexity — which is the segment your team is focused on."*
4. Sales (account executive)
> *"I'm an AE at Datadog, where I cover the mid-market for the East region. Hit 130% of quota last year on $1.4M attainment. Before Datadog I spent two years at Cloudflare in the same segment. The throughline of my career has been technical sales — selling infrastructure to engineering buyers, where the deal cycle hinges on whether the technical evaluation lands. I want my next role to be at a company that's pushing into enterprise after years of mid-market success, because that's the deal motion I think I'm best at — and that's exactly what your team is doing this year."*
5. Designer (product designer)
> *"I'm a senior product designer at Linear, where I've been for three years working primarily on the project planning and sprint surfaces. Before Linear I was at Asana for four years, also on planning products — which means I've spent most of my career on the part of a product that wears the user's mental model for how their team works. The work I want next is on a smaller team, working across more product surfaces, at a company that takes design-engineering collaboration as seriously as you do. That's why this role caught my eye."*
6. Nurse (RN, hospital)
> *"I'm a charge nurse on a 30-bed med-surg floor at a Level II trauma center here in Houston. I've been an RN for six years — three on the same floor I'm charging now. Before nursing I worked as an EMT for two years, which is where I got pulled toward the higher-acuity work. I'm looking to move to a step-down or telemetry unit — same acuity instincts, more cardiac focus — which is what this role is. I also want to be at a Magnet hospital with real shared governance, which I read your unit has."*
7. Teacher (elementary)
> *"I teach 2nd grade at a Title I elementary school in Atlanta. I've been teaching for five years, all at the same school, mostly K-2. My focus has been literacy — I led the move from basal reading to the workshop model on our grade team two years ago, and our DIBELS scores improved meaningfully across the grade. I want my next role to be at a school that uses the workshop model district-wide and that has a strong literacy coach, which is what your school is. That's the next step in my growth as a literacy teacher."*
8. Career changer (consulting → product management)
> *"I'm a senior associate at Bain, where I've spent three years covering B2B SaaS clients — pricing, go-to-market strategy, product portfolio decisions. The part of the work I keep gravitating toward is the product strategy side: defining what to build, sizing markets, talking to users. The operational consulting work I'm less excited about. I want to move from advising on these decisions to making them, full-time, inside a product team — which is what this PM role is. The skills overlap is real: customer research, market sizing, exec communication. The new skill I'm leaning into is shipping software, which I've been building toward through side projects."*
9. Career changer (military → project management)
> *"I'm transitioning out of the Army after eight years as a logistics officer. Most recently I led a 40-person team responsible for moving people, equipment, and supplies across a multi-base operation. The translation to civilian project management is direct — I've been running stakeholder-coordinated, cross-functional, deadline-driven projects my entire career. I have my PMP. I'm looking for my next role to be in commercial construction or manufacturing project management, because those industries match the operational tempo I'm used to — which is why I applied here."*
10. Returning to work (parent re-entering after a break)
> *"Before I took time out to be at home with my kids, I spent six years as a marketing manager at a B2B SaaS company, leading demand gen across SMB and mid-market. I've been out for four years and stayed current through freelance copywriting, two paid certifications, and following the major shifts in martech. I'm coming back into a marketing manager role specifically because that's the work I know best — and your stage of company, where the function is being built rather than scaled, is the right re-entry point. I'd contribute from day one rather than spending six months catching up to an established machine."*
11. Entry-level (recent grad, general)
> *"I just graduated from [School] with a degree in [Field]. The work I'm most proud of from college was [specific project] — I [what you did], and the thing I learned was [what you took from it]. Before college I [internship / job / activity], which is where I [related skill]. I'm looking for my first full-time role to be at a company where the role wears multiple hats — not narrow specialization — and where I can learn from senior people who are doing the work I want to be doing in five years. That's why this role is at the top of my list."*
12. Senior leader (VP / Director)
> *"I'm VP of Engineering at a Series C fintech, where I've built the team from 12 to 60 engineers over the last three years. We ship to 30 enterprise customers in regulated industries, so most of my time is split between scaling the org and partnering with the security and compliance functions. Before this role I was a senior engineering manager at Square, where I learned to operate at much higher scale and complexity than my current company. I want my next role to be at a company that's earlier than my current employer but where the eventual ceiling is much higher — which is what this Head of Platform role would be."*
Specific situations
When you're under-qualified on paper
Lead with the work, not the years. "I've been doing X for two years" can be more compelling than "I've been doing X for five years" if your X is better. Quantify outputs, not tenure.
When you have a gap in your work history
Acknowledge it in one sentence, then move on. Don't over-explain. "I took 18 months out for [reason] and used the time to [thing relevant to your search]" is enough. Most interviewers don't care nearly as much as candidates fear they do.
When you're switching industries
Frame the transition as a deliberate choice driven by skill or interest, not as escape. "I want to spend the next few years working in healthcare specifically" beats "I needed to get out of finance."
When you've had many short jobs
Don't enumerate them all. Bundle: "Over the last five years I've worked at three early-stage startups, which has given me deep experience in [transferable thing]." Pick the through-line and lead with it.
How to practice
The single biggest mistake is winging it. Record yourself answering the question and time it. The version in your head is always shorter than the version that comes out of your mouth.
A workflow that works:
- Write the answer down in full. Edit it to 90 seconds when read aloud.
- Record yourself saying it. Listen back. Cut filler.
- Practice in three different framings: "Tell me about yourself," "Walk me through your background," "Can you give me a quick overview of your experience?" Same answer fits all three.
- Practice answering immediately. Real interviews don't give you a 10-second pause to gather yourself.
You don't want to memorize a script — interviewers can hear it. You want to internalize the structure so the answer feels natural even when the framing or the moment is slightly different.
Use the question to set up the rest of the interview
A subtle thing the best candidates do: they end the answer in a way that *invites the next question*. By closing on the future ("which is why this role caught my attention"), you naturally hand the interviewer the opening for "tell me more about why this role specifically" or "what about this role appeals to you?"
This gives you control over which topic gets the next 5-10 minutes of attention — and lets you steer toward the parts of the conversation you're best prepared for.
The bigger interview problem this question signals
If you're getting through "Tell me about yourself" cleanly but struggling in the rest of the interview, the issue often isn't the question — it's that you're talking to the wrong company, the wrong role, or you don't have enough context about the team to land the specifics. The candidates who interview consistently well are usually the ones who've talked to someone inside the company before the formal interview.
If you don't have a contact, searching for the actual hiring manager or a peer on the team and asking for a 15-minute call is the highest-leverage move. From there, a personalized message that asks for a short conversation typically gets replies at 40-60% versus the 5-8% baseline for cold applications — and the conversation itself gives you the specifics that make every interview answer land harder, not just this one. For more on what to say once you're actually in the interview, the same framing also helps you nail why you're interested in this position and why you want this job specifically.
FAQ
How long should "Tell me about yourself" be?
60-90 seconds is the sweet spot. Under 45 seconds reads as unprepared; over 2 minutes loses the interviewer.
Should I start with my personal background?
No. The interviewer is asking for a professional summary. Personal background (where you grew up, hobbies, family) doesn't belong unless you're explicitly asked.
What's the best structure for the answer?
Present-Past-Future: 15-20 seconds on what you do now, 30-45 seconds on the relevant highlights from your past, 15-20 seconds on what you want next and why this role fits.
How is "Tell me about yourself" different from "Walk me through your resume"?
They're functionally the same question. "Walk me through your resume" sometimes invites slightly more chronology, but the same Present-Past-Future structure works for both.
Can I look at notes?
In a phone screen, sure — interviewers can't see. In a video or in-person interview, glancing at notes briefly is fine; reading a script verbatim isn't.
How do I answer this question as a recent graduate?
Lead with what you studied and one specific accomplishment from school (project, internship, leadership role), then bridge to what you want in your first job and why this role fits. Don't dwell on lack of work experience — name what you do have.
Should I mention salary expectations or compensation?
No. Save compensation for the explicit comp conversation later in the process.