How to Answer 'Tell Me About Yourself' in Interviews

"Tell me about yourself" is usually the first question in an interview, and it is less casual than it sounds. Your answer shapes what the interviewer asks next and frames everything that follows. A good answer is a short, deliberate summary that points at the role you are applying for.

How long to speak

Career services commonly suggest keeping several versions of your introduction for different situations. Harvard's career centre describes a 15-second version for job fairs, 30 seconds for networking events, and 60 to 90 seconds to open an informational meeting (Harvard: building your network). The interview opener is closest to the longest of these: about 60 to 90 seconds, two minutes at most. Long enough to give a picture, short enough that the interviewer can steer.

The present, past, future structure

Present: what you do now

Your current role or study, your main responsibilities, and one result that matters for this job. "I'm a data analyst at a logistics company, where I own the delivery performance reporting. The work I'm proudest of is automating our delay report, so operations see problems the same morning."

Past: how you got here

Only the parts of your background that explain your skills or your direction. "Before that I spent two years in the operations team itself, which is why I understand what the numbers mean on the ground."

Future: why this role

What you want to do next and why this role fits. "I'm looking to move into analytics engineering, building the models behind dashboards rather than only the dashboards, and your team's work on the data platform is exactly that."

Then stop. Let the interviewer choose what to ask about; the follow-up question they pick tells you what interests them most.

Tailor it to the role

Microsoft describes interviews as two-way conversations and advises candidates to research the role and team (Microsoft: interview tips). Use that research here. Choose the result in your "present" and the reason in your "future" to match what the job description emphasises. For a data engineering role, mention a pipeline; for a product analytics role, a decision your analysis changed.

Examples for different starting points

Fresher: "I've just completed a degree in statistics. In my final-year project I built a demand forecast for a local grocery chain using two years of their sales data, and it outperformed their spreadsheet method on the last three months. I also did a two-month internship cleaning customer data for a marketing team. I'm applying for this analyst role because your team works on retail demand, which is the problem I've enjoyed most."

Career switcher: "I've worked for six years in accounts payable. In the last year I started automating our reconciliation with SQL and Python, which now saves my team about a day a month, and I completed a structured analytics course alongside work. I'm applying for this finance analytics role because it combines the accounting knowledge I have with the data work I want to do full time."

Experienced engineer: "I'm a senior data engineer at a payments company, where I led the move of our batch pipelines to a lakehouse and cut daily processing time roughly in half. Before that I built ETL for a retail client in a services company. I'm looking for a role with more ownership of data quality across teams, which is why your platform team's work on data contracts interested me."

Each is under 90 seconds, contains one concrete result, and ends on why this role.

Variations of the question

• "Walk me through your resume." Same structure, but follow the order of the page, briefly, and spend most time on the most recent and relevant role.
• "Why are you interested in this role?" Expand the "future" part with specifics about the team and work.
• "Describe yourself in three words." Choose words you can back with examples, and give one short example for at least one of them.
• "What should I know that isn't on your resume?" A brief story that shows motivation or judgement, such as how you taught yourself a tool to solve a real problem.

Mistakes to avoid

• Reciting your whole life story or your full resume.
• Personal details that are not relevant to the job.
• No result: describing duties without anything you achieved.
• No link to the role, so the interviewer cannot see why you applied.
• A memorised script that sounds rehearsed. Learn the structure, not the words.

Prepare and practise

Write a 150-word version, read it aloud and time it. Cut until it fits in 90 seconds. Practise it with a friend who then asks one follow-up question, because that question is where the real conversation starts. Keep a 30-second version too; crafting an elevator pitch shows how the lengths fit together. Have one or two STAR stories ready for the follow-ups your opener invites; see the STAR method story bank.

Projects that give you a concrete result to mention are part of the Data Analytics course.

Sources

• Harvard Extension School Guide to Building your Network (Harvard Mignone Center for Career Success) — Harvard FAS Mignone Center for Career Success
• Interview tips (Microsoft Careers) — Microsoft