Tell Me About Yourself: Answer Formula and Examples

"Tell me about yourself" is not a request for your life story. It is the interviewer asking for a short, relevant summary of who you are professionally and why you are here. You will be asked it in almost every interview, which makes it the single most worthwhile answer to practice. This page gives you a four-part formula, examples at three career stages, and a software engineer version.

The answer in 60 to 90 seconds: Present, Past, Future

1. Present (15-20 seconds): what you do now and one thing you are good at or proud of.
2. Past (30-40 seconds): two or three steps that led here, chosen because they connect to this role. Skip anything that does not.
3. Future (15-20 seconds): why this role and company are the logical next step.
4. Handoff (5 seconds): end with a clear stop, or a short question like "I would love to hear more about the team."

The most common failures are starting at birth, listing every job, and ending with no point. Treat your resume as the source, not the script.

Example: new graduate

I just finished my degree in statistics at the University of Texas, where I focused on data analysis and a capstone project building a course-scheduling tool with a team of four. I really enjoy the part of the work where messy data turns into a decision someone can act on. I interned at a local retailer, where I automated a weekly sales report and cut the manual work by hours each week. I am looking for a first analyst role where I can learn from experienced people and work on real data, and this role stood out because of the focus on retail analytics.

Why it works: Education is brief, there is one concrete project and one internship result, and the last sentence ties to the role. It stays under a minute.

Example: mid-career professional

I am a product manager with six years of experience, mostly in B2B software. For the last three I have owned the onboarding and billing experience at a mid-size SaaS company, where I led a redesign of checkout that improved self-serve conversion for small teams. Before that I was a business analyst, which is where I learned to ask what a decision actually depends on. I am now looking for a role with more ownership of a full product area, and I was drawn to this one because of how much of your roadmap comes from customer research.

Why it works: A clear identity in the first sentence, one specific accomplishment, a thread through the past ("learned to ask what a decision depends on"), and a reason for this company.

Example: software engineer

I am a backend engineer with about five years of experience, mostly building payment and notification systems in Python and Go. Right now I own the notification service at a fintech startup, which I moved from scheduled jobs to a queue so messages stop getting dropped under load. Before that I was at a consultancy, where I worked on a dozen small projects and learned to get a service from idea to production quickly. I am looking to work on a larger system with more traffic and a stronger code review culture, and your engineering blog on reliability is part of why I applied.

Why it works: Specific technologies and one project the interviewer can ask about. The "past" is selected, not a list. The last line shows research.

Example: career changer

I spent eight years as a high school teacher, and for the last two I have been learning to program in the evenings and building small tools for my school, including a grade-tracking app now used by our department. What carried over from teaching is explaining complicated ideas clearly and working with people who have different levels of knowledge. I am looking for a junior developer role where I can keep building things people use, and I am especially interested in education technology.

Why it works: It turns the change into a thread rather than an apology and offers proof (a tool people use).

What to leave out

• Personal details that are not relevant: age, family, where you grew up (unless the interviewer asks).
• A chronological list of every job.
• Weaknesses or reasons you left a previous job.
• Anything you would not want to be asked a follow-up about.

Adapting it to the role

Keep the structure and change which two or three past steps you mention. For a startup, lean on ownership and range. For a large company, lean on scale and collaboration. Read the job description and make sure at least one of its key requirements shows up in your Past section.

Practice it aloud

Write the answer as bullet points, not a script. Say it out loud three times, record it once, and listen for filler words and anything that sounds like a list. This is the answer worth rehearsing most: you will use it in nearly every interview. A mock interview starts with this question because real interviews do, and the software engineer practice page goes through what comes next.

Frequently asked questions

How long should my answer be?

Sixty to ninety seconds. Shorter than a minute can feel thin; over two minutes loses the listener.

Should I mention my personal life?

Only briefly, and only if it is relevant or the interviewer invites it. A single human detail at the end can help, but the answer is professional.

Is "tell me about yourself" the same as "walk me through your resume"?

Close. A walk-through is more chronological and detailed. For that version, keep the same steps but add one sentence per role about what you accomplished and why you moved.

What if I have gaps or a non-linear career?

Build the Past section around the thread that connects your experience, and address a gap in one honest sentence if it is relevant. Do not apologize for it.

Can I read it from notes on a video call?

Use brief bullet notes if the interview allows notes. Do not read a script aloud; it sounds flat and the interviewer notices.