How to Answer "Tell Me About Yourself" in a Job Interview

"Tell me about yourself" opens almost every interview, and almost everyone answers it badly — either by reciting their resume top to bottom or freezing because the question is so open-ended. It doesn't have to be either. This guide gives you one repeatable structure, a comparison table for five different situations, five full worked-answer scripts you can adapt, and a clear list of what to cut.

Quick Answer: Use the present-past-future structure: where you are now, the 1-2 past experiences that got you there, and why this specific role is the logical next step. Keep it to roughly 60-90 seconds (under two minutes, always). Tailor the emphasis — not the structure — to your situation: new grad, career changer, employment gap, experienced IC, or remote/AI interview.

How Do You Answer "Tell Me About Yourself" in a Job Interview?

The most reliable approach is the present-past-future formula: describe your current role and what you do now, briefly cover the past experience that shaped your relevant skills, then finish by connecting it to why you want this role. Keep the whole thing under two minutes — most career-coaching guides put the ideal range at roughly 60-90 seconds.

This works because it mirrors how an interviewer is already thinking about you: who are you now, is there proof you can do the job, and why do you actually want it. It also gives you a natural, memorable shape instead of a wandering list of jobs and dates. What hiring managers really think about this question confirms the same pattern — they're listening for relevance and clarity, not a complete biography.

What's the Best Structure for a "Tell Me About Yourself" Answer?

Present-past-future is the structure to default to, but the proportions should shift with your situation. Someone with 10 years of experience should spend most of their time on "present" and pick only the 1-2 most relevant past roles; a new grad has almost no "present" to speak of and should lean on relevant coursework, internships, or projects instead.

Whatever order you use, always end on the future — the part where you connect your background to why you want this specific role at this specific company. Ending on the past (your old job) leaves the interviewer to do the connecting work themselves, and they usually won't bother.

Worked Example Answers for 5 Common Situations

These are full scripts, not templates — swap in your own details, but the shape and pacing are what to keep.

New Grad

"I just graduated with a degree in marketing from State University. During my final year I interned at a mid-size e-commerce company, where I ran A/B tests on email campaigns and helped grow open rates by working closely with the design and copy teams. That internship is what got me excited about growth marketing specifically — I like that it's equal parts creative and analytical. I'm looking for a first full-time role where I can keep building that skill set, and this position's focus on lifecycle marketing is exactly the kind of work I want to be doing."

Career Changer

"For the past six years I've been a high school teacher, most recently teaching biology. What I've realized is that the part of the job I love most is breaking down complex material so it clicks for people — which is a big part of why I've spent the last year building a portfolio in instructional design and completing a UX writing certificate on the side. I've already done freelance course-content work for two small edtech companies. I'm making the move to instructional design full-time now, and this role's focus on onboarding content is a direct match for what I've been building toward."

Employment Gap

"I stepped away from full-time work for about a year and a half to care for a family member — that situation has resolved and I'm ready to return to full-time project management. Before the gap, I spent four years managing cross-functional software rollouts at a logistics company, including one project that came in two months ahead of schedule by restructuring how we handled vendor dependencies. I kept my PMP certification current during the gap and did some part-time consulting, so I'm not starting from zero. I'm excited about this role because it's the same kind of complex, cross-team coordination I'm good at."

Experienced Individual Contributor

"I'm currently a senior backend engineer at a fintech company, where I own our payments infrastructure team's core services and mentor two junior engineers. Before that, I spent three years at a smaller startup where I was the first backend hire and built our API from scratch — that's where I learned to move fast without breaking things, which I still lean on today. I'm looking to move into a role with more architectural ownership, and this position's focus on scaling a platform from the ground up is exactly the kind of problem I want to be solving next."

Remote Interview or AI-Screened Interview

"Sure — happy to start there. I'm currently a customer success manager at a SaaS company, managing a book of mid-market accounts and running quarterly business reviews. Before this I was in account management at an agency, which is where I built the relationship-management skills I use daily now. I'm looking for a role with more strategic account ownership, and what drew me to this opportunity is the emphasis on expansion revenue — that's the part of the job I'm strongest at and want to keep growing in." If you're talking to AI job interviews in 2026, pause for a beat before you start speaking so the platform doesn't clip your first few words, and slow your pace slightly since there's no human nodding along to confirm you're on track.

What Should You NOT Say in a "Tell Me About Yourself" Answer?

Don't turn this into a full resume readout — listing every job, date, and title in order is the single most common mistake, and it's boring to listen to. Also avoid unrelated personal details (marital status, hobbies unless directly relevant, health information), any negative comments about a former employer or manager, and going past the two-minute mark.

A few more specifics to cut:

• Generic filler like "I'm a hard worker and a team player" with no evidence behind it
• Apologizing repeatedly for an employment gap instead of stating it once and moving on
• Starting with "well, umm, so..." — pause silently for a beat instead, it reads as more confident
• Ending on your past job instead of on why you want this one

How Do You Answer "Why Do You Want to Work Here?"

Answer with something specific to the company — a product, a recent initiative, a team you'd be joining — connected to your own goals, not a generic compliment. "I want to work here because I've used your product and noticed X, and I'm looking for a role where I can help solve problems like that" lands far better than "you're a great company with great culture."

Do a few minutes of real research before the interview: the company's recent product launches, its mission page, or a recent piece of news about the team. Vague answers here are one of the fastest ways to signal you didn't prepare.

How Do You Answer "Where Do You See Yourself in 5 Years?"

Describe a growth trajectory that's realistic and plausible within this company, not a specific job title you're locked into. Something like "I'd like to have grown into a role with more ownership over X, ideally staying somewhere I can keep building deep expertise" shows ambition without boxing you into a promise you may not want to keep.

Avoid two extremes: naming a hyper-specific title that doesn't exist at that company (raises doubt you understand the org), and saying "I don't know" or "wherever the company needs me," which reads as a lack of direction.

How Do You Answer "What Is Your Weakness?" in an Interview

Pick a real, moderate weakness — not a disguised strength like "I work too hard" — and pair it with the concrete steps you're taking to improve it. For example: "I've historically been slow to delegate because I wanted to make sure things were done a specific way; I've been deliberately handing off more ownership to my team this year and it's improved both my bandwidth and their growth."

The weakness itself matters less than showing self-awareness and an active improvement plan. Avoid anything that's actually a hard requirement of the job (don't say "public speaking" for a role built around presentations).

How Do You Answer Behavioral Interview Questions Using the STAR Method?

Behavioral questions ("tell me about a time when...") are answered with the STAR method: Situation (the context), Task (your responsibility), Action (what you specifically did), Result (the outcome), a framework described in detail by Indeed's STAR interview guide. Keep Action as the longest part — that's where you prove what you did, not the team.

Prepare 4-5 STAR stories in advance covering common themes (a conflict you resolved, a deadline you hit, a mistake you recovered from, a project you led) so you're not building one from scratch under pressure. If the role involves a technical round too, our guide on how to prepare for a technical interview covers the coding- and systems-specific prep on top of behavioral questions.

How Do You Answer a Question About Salary Expectations?

Give a realistic range based on your own research into the role, location, and your experience level, rather than a single fixed number — and if you genuinely don't have enough information yet, it's fair to ask what the budgeted range is for the role before committing to a figure. Framing it as "based on my research and experience, I'd expect somewhere in the range of X to Y, but I'm open to discussing based on the full compensation package" keeps you flexible without underselling yourself.

Avoid naming a number far below market just to seem agreeable — it's hard to correct later — and avoid refusing to answer entirely, which can read as evasive. If you're unsure what "market" looks like for the role, spend time researching comparable postings before the interview rather than guessing live.

Practice It Out Loud Before the Real Thing

Write your present-past-future answer once, then say it out loud — not silently in your head — at least three times before the interview. Most people who write a script that reads as "about a minute" find it actually runs closer to two and a half when spoken, so timing yourself out loud is the only way to know where you actually land.

For structured practice, our guide to AI prompts for interview prep walks through prompting an AI tool to run mock rounds of this exact question and give you feedback on pacing and content before you're in the room.