How to Answer: Tell Me About Yourself in an Interview (with Examples)
The first 90 seconds set your hire/no-hire signal. Interviewers decide whether to lean in or wait you out before you finish your opening sentence, and most candidates give them a reason to wait.
Practice this out loud. Get scored in 30 seconds.
Voice mock interview with AI scoring — built because ChatGPT can chat, but can't pressure-test you or grade you.
Try the demo →Why this matters
This question is almost always the first thing you hear, which makes it the moment where your credibility is either established or damaged. Interviewers use your answer to calibrate how well you understand the role, how clearly you communicate under low pressure, and whether you have prepared at all. A scattered answer makes every follow-up harder because you have already created doubt. A crisp, structured answer does the opposite: it builds credibility before you answer a single hard question. Candidates who nail this question consistently report that the rest of the interview feels easier because the interviewer is already leaning forward.
What to think about
- I currently lead a six-person analytics team at a mid-size logistics company, where I built the real-time dashboard that reduced shipment delays by 18 percent last quarter. Before that I spent four years in consulting, which gave me a cross-industry view of operations problems. I am now looking to move into a product role where I can own the roadmap end-to-end rather than advising from the outside.
- I have been a senior account executive in B2B SaaS for five years, most recently closing deals between $80k and $300k ARR. My background in customer success before sales means I sell with a long-term retention lens, not just a close-first mindset. This role appeals to me because your average contract size and enterprise focus match exactly where I have been performing.
- I spent the first eight years of my career as an ER nurse, then transitioned into healthcare operations consulting. I now help hospital networks redesign triage workflows. I am applying here because your operations director role sits at exactly that intersection of clinical expertise and process redesign.
- I am a product designer with seven years of experience, currently at a fintech startup where I own the end-to-end design system used by three product teams. I reduced onboarding drop-off by 24 percent last year through a series of usability studies and targeted redesigns. I am looking for a larger canvas and a team that ships at higher velocity.
- My background is in corporate finance. I spent three years in investment banking and the past two years as an FP&A lead at a healthcare company, building the models that supported two acquisitions. I am making this move because I want to be on the operating side of the table, where the decisions I model actually get made.
The framework
Use the Past-Present-Future structure. Spend roughly 20 percent on your past: a single sentence or two that provides just enough context to explain how you arrived at your current role. Spend 60 percent on your present: your current scope (team size, budget, or customer base), one quantified achievement from the last 12 to 18 months, and one sentence explaining why that experience is directly relevant to this specific role. Spend 20 percent on your future: what you want to do next and why this particular job is the logical next step, not just a step. The whole answer should run 60 to 90 seconds when spoken aloud. Write it out first, then rehearse it until it sounds natural and conversational rather than recited. The goal is a clear narrative arc that ends with a direct, specific bridge to the job you are interviewing for, so the interviewer immediately understands why you are sitting in that chair.
Common mistakes
- Reciting your resume in chronological order. The interviewer has your resume. They want synthesis and narrative, not a spoken timeline.
- Starting with childhood, college, or anything before your professional life. Jump straight to relevant professional experience unless explicitly asked otherwise.
- Ending with no forward hook. Many candidates summarize the past and present but never explain why this specific role is the logical next step. That missing bridge leaves the interviewer doing extra work.
- Being vague about scope and impact. Saying 'I worked on a team' or 'I improved performance' is much weaker than 'I led a team of five' or 'I reduced processing time by 30 percent.'
- Going over two minutes. Longer is not more impressive. It signals poor judgment about what matters and makes the interviewer feel trapped.
Bad answer vs strong answer (scored)
Weak answer
Sure, so I graduated with a business degree and then joined a consulting firm where I did a lot of different projects. After that I moved into an analyst role and have been doing that for a while. I am really passionate about problem-solving and enjoy working with data and helping teams succeed. I am excited about this opportunity and think my background is a strong fit.
What's wrong
- No specifics whatsoever — no team size, no measurable outcomes, no industry context. 'A lot of different projects' and 'for a while' are vague to the point of being meaningless.
- The passion statement ('I am really passionate about problem-solving') is a cliche that every candidate uses and adds zero signal.
- No forward hook. The answer does not explain what the candidate wants to do next or why this particular role is the right move, so the interviewer has to ask a follow-up just to get basic context.
Stronger answer
I am currently a senior data analyst at a mid-size e-commerce company, where I own the forecasting models that inform $40M in annual inventory decisions. Over the past year I rebuilt the demand forecasting pipeline from scratch, which cut overstock write-offs by 22 percent. Before this role I spent three years in management consulting, which gave me a strong foundation in translating messy data into executive-ready recommendations. I am making this move because I want to step into a decision-making role rather than an advisory one, and your head of analytics position gives me the scope, the data infrastructure, and the cross-functional ownership I have been building toward.
Related practice
Quick answers
How long should my answer to 'tell me about yourself' be?
Aim for 60 to 90 seconds when spoken aloud. That is roughly 150 to 225 words in written form. Any shorter and you have not given the interviewer enough to work with. Any longer and you are eating into their time and signaling poor judgment about what matters most.
Should I mention personal interests or hobbies in my answer?
Only if they are directly relevant to the role or reveal something meaningful about your work style. A software engineer mentioning open-source contributions is relevant. Mentioning that you enjoy hiking is not, unless the company is in the outdoor industry. Default to keeping your answer professional. Personal details can come up naturally in small talk or when the interviewer explicitly asks, and they land better there because they feel organic rather than rehearsed.
What if I am changing careers and my background does not directly match the role?
Lead with the transferable skills and measurable outcomes, not the job titles. Focus the present section on the work you have done that is most relevant to what this role requires, even if the industry or function was different. Then use your future hook to explicitly bridge the gap: explain what capability you are bringing from your prior path and why that non-traditional background makes you stronger, not weaker, for this particular job. Career changers who own their narrative confidently tend to do far better than those who apologize for their path.
My answer feels good on paper but falls flat when I say it out loud — what is wrong?
Written answers almost always sound more polished than spoken ones. The real problem is that most people have never heard themselves give this answer under any pressure at all. Odin runs a live mock interview where you answer out loud and receive a scored breakdown across specificity, structure, and delivery. The scored feedback shows you exactly which sentences are vague, which land, and where you lose the listener — before it happens in a real interview.