How to Answer "Tell Me About Yourself" (Examples by Role)
A tell me about yourself answer is a 60-90 second pitch: what you do now, the experience that earned it, and why this role is next. The formula, mistakes to fix, and full sample answers for five roles.
A good tell me about yourself answer is a 60 to 90 second pitch with three parts: what you do now, the experience that got you there, and why this specific role is the logical next step. It is a summary of your resume aimed at the job in front of you, not a life story.
The question sounds like an icebreaker. It is not. It is the interviewer's first chance to see whether you understand the job, whether your experience maps onto it, and whether you can be concise. Most candidates lose it in the first fifteen seconds by starting at the beginning of their career.
What is the present-past-future formula for tell me about yourself?
The present-past-future formula is a three-part structure for a tell me about yourself answer: present is your current role and what you are responsible for, past is the experience that makes you credible for it, and future is why this job is the right next move. Three or four sentences each, in that order.
- Present: your title, the kind of company or team you work on, and the one problem you spend most of your time solving. One or two sentences.
- Past: the earlier role, project or training that built the skill this job needs. Pick the part that matches the posting, not the most impressive part in general.
- Future: what you want to do next and why this role and this company are the place to do it. This is the part that turns a summary into an argument for hiring you.
Present first matters because it tells the interviewer where you are now, so everything after it has a frame. Candidates who start with "I graduated in 2018 and then..." make the listener wait for the point.
A template you can fill in
"I'm a [current role] at [type of company], where I mostly [the main problem you solve]. Before that I [the relevant earlier work or training that built the skill], which is where I learned to [specific capability the job needs]. I'm looking for [the next step], and this role interests me because [specific reason tied to the job, not the brand]".
Fill it in with your own facts and say it out loud. If it runs past 90 seconds, you are explaining rather than summarizing. Cut the setup and keep the result.
How long should a tell me about yourself answer be?
Aim for 60 to 90 seconds, which is roughly 150 to 220 words spoken at a normal pace. Under 60 seconds sounds rehearsed and thin. Over 90 seconds and the interviewer starts planning their next question instead of listening.
That length is a rule of thumb, not a rule. A career changer with an unusual path may need the full 90 seconds to make the connection clear. A fresh graduate may be better at 60, because there is less history to compress. The test is whether every sentence earns its place.
- 60 seconds: about 150 words. Enough for present, one past proof point, and a short future line.
- 75 seconds: about 190 words. The comfortable middle for most experienced candidates.
- 90 seconds: about 220 words. Use it when you need to explain a transition or connect two unrelated backgrounds.
What are the most common mistakes, and how do you fix them?
Almost every weak answer fails in one of six ways: it is too long, it starts too far back, it repeats the resume, it is generic, it hides the transition, or it never mentions the job. Each has a specific fix.
| Mistake | What it sounds like | The fix |
|---|---|---|
| Chronological life story | "I was born in..., went to school in..., then my first job..." | Start with your current role. Move earlier experience later, and only if it supports the job. |
| Reading the resume aloud | "Then in 2021 I joined X, and in 2022 I moved to Y..." | Pick two moments that show the skill in the posting. Leave the rest for follow-up questions. |
| Running past 90 seconds | Four minutes covering every project you have ever shipped | Cut to 150-220 words. One result per section is enough. |
| Generic self-description | "I'm a hard-working team player who is passionate about technology" | Replace adjectives with evidence: the problem you solved, the scope, the outcome. |
| Hiding a transition | "I've always been in marketing" when half your career was in teaching | Name the change and give the bridge: what carried over and why you moved. |
| No connection to the job | A polished summary that could be sent to any company in the industry | End with a reason specific to this role: the problem it owns, the stage of the team, the work you want to do more of. |
One more mistake is worth naming separately: memorizing a script word for word. A memorized answer breaks the moment you are interrupted, and interviewers can hear it. Learn the three parts and two facts per part, then say it differently each time.
Sample answer for a software engineer
For engineering roles, the answer should name the kind of system you work on, one technical result with scope, and the type of problem you want more of.
"I'm a backend engineer at a payments company, where I mostly work on the services that move money between merchants and banks — reliability matters more than speed of shipping. Before that I spent three years at a logistics startup, where I rebuilt the order tracking service and cut its worst-case response time from about four seconds to under one. That's where I got comfortable owning a service end to end, including the on-call rotation. I'm looking for a role where I can work on systems at a bigger scale, and this team's work on real-time settlement is the closest match to what I want to do next."
Notice what it does not do: it does not list every language in the stack, and it does not apologize for the startup years. The number is real and explainable, which is the standard for any metric you put in this answer.
Sample answer for a product manager
For product roles, name the product area you own, the decision you are trusted to make, and one outcome you influenced rather than one you personally built.
"I'm a product manager on the onboarding team at a B2B SaaS company, where I own the first two weeks of a new customer's experience. My job is mostly deciding what to build next from a mix of support tickets, sales calls and usage data. Before this I was a business analyst in the same company, which is how I learned the customer base — I moved into product after running the research that reshaped our trial flow. The change I'm proudest of is a shorter setup sequence that we tested over several months and kept because new accounts reached their first real result faster. I want to keep working on activation problems, and this role's focus on self-serve growth is exactly that."
This answer survives the obvious follow-up — "what did you measure?" — because the claim is about a direction and a method, not a precise figure you would have to invent.
Sample answer for a sales role
In sales, the interviewer wants to hear your segment, your motion, and how you run a deal. Numbers help, but only ones you can break down.
"I'm an account executive selling to mid-market operations teams, mostly inbound leads with a handful of outbound accounts I work myself. My week is discovery calls, building the business case with a champion, and keeping deals moving through legal and procurement. I started in customer support at the same company, which turned out to be useful — I learned the product from the people who were already paying for it, then moved into a sales development role before carrying a quota. Last year I closed a set of renewals and expansions in a segment where the product had no reference customers, which meant writing most of the collateral myself. I'm looking for a role with a more complex sale, and this territory's mix of new logos and expansion is the step I want."
If you have a quota figure you are happy to discuss, put it in. If your number needs three sentences of context to be fair, say the context instead and let them ask.
Sample answer for a fresh graduate
With little work history, the present is your degree or your current project, the past is the piece of coursework, internship or side project that proves the skill, and the future is the specific work you want to start on.
"I'm finishing a degree in information systems, and for the last year I've been building a scheduling tool for a local clinic as a side project — it's small, but it's real users, and I maintain it. Before that I interned for a summer on a data team, where I wrote the queries behind a weekly report that the operations manager used to plan staffing. The part I enjoyed most was sitting with the person who used the report and changing it based on what they said was missing. I'm applying here because this role puts analysts close to the business, and that's the work I want to get better at."
Do not pad this with high school achievements or a list of every course. One real project with a user is stronger than five certificates.
Sample answer for a career changer
A career changer has to do one extra job: name the switch in the first sentence so the interviewer is not quietly confused, then show what carried over and what you have already done to close the gap.
"I spent six years teaching secondary maths, and I'm moving into instructional design — I'm currently freelancing on course materials for a test-prep company. Teaching gave me the part that transfers most directly: breaking a topic into steps for people who are stuck, and rewriting it when the first version doesn't land. Over the last year I completed a certificate in instructional design and rebuilt two of my own classroom units as self-paced modules, which is the work I now show people. I want to do that full time on a team with review and feedback, which is why I'm interested in this role."
The bridge does not need to be dramatic. It needs to be specific: what you did, what you learned, and what evidence exists that the transition is already underway.
How do you practice a tell me about yourself answer out loud?
Practice out loud, timed, and against the actual job description. Reading your answer silently teaches you nothing about pace, filler words or whether the transitions hold when you are nervous.
- Write the three parts in bullet points, not full sentences. Six bullets total is enough.
- Say it once into a recorder without stopping. Do not restart when you stumble.
- Listen back for two things: the length, and the moment your answer stops being about the job.
- Rewrite only the weak section, then say it again the next day without reading.
- Do one full mock interview, because the answer changes when someone asks a follow-up.
A voice mock interview is the closest thing to the real pressure. LiveHint builds one from the job description and your resume, so you practise against the role you are actually applying for instead of a generic question list. You get a scored debrief and the full transcript afterward, which is where you can see whether you drifted past 90 seconds or repeated the same point twice. The AI mock interview practice guide covers how to use the transcript instead of just reading the score, and tailoring your resume for each job makes the two answers consistent.
Before the interview, save the posting in an application tracker so you can see which version of your resume and which version of this answer went to which company.
Rehearse your answer against the real job description and get a transcript of how you actually sounded.
Try a mock interviewThe answer is a summary, not a biography
The candidates who do this well are not more impressive than the ones who ramble. They have simply decided, in advance, which two facts about their work matter for this job, and they say those first. Present, past, future, 90 seconds, then stop talking and let the interviewer ask the question they actually care about.
Frequently asked questions
- How long should a tell me about yourself answer be?
- Between 60 and 90 seconds, which is about 150 to 220 words at a normal speaking pace. That is enough for your current role, one relevant piece of experience and a reason for applying. If you regularly run past 90 seconds, cut the background and keep the results. Record yourself once to check, because most people underestimate their own length.
- Should I memorize my tell me about yourself answer?
- Memorize the structure and the two facts in each part, not the wording. A word-for-word script falls apart when the interviewer interrupts or asks a follow-up, and it sounds recited. Learn six bullet points — two for present, two for past, two for future — and practice saying them differently each time until the order feels automatic.
- What if I have no relevant work experience?
- Use a project, internship, course or volunteer role as your present, and make it concrete: what you built or ran, who used it and what changed. Then connect the skill to the job rather than apologizing for the gap. One real project with a user is more convincing than a list of certificates, and it gives the interviewer something specific to ask about.
- Should I include personal details like hobbies or where I grew up?
- Usually no, unless the detail connects to the role or the company in a real way. Hobbies and hometowns use up seconds you need for evidence, and they invite small talk before you have made your case. A brief personal line at the end can work if it explains a genuine motivation for the job, but it should not replace the future part of the answer.
- How is this question different from 'walk me through your resume'?
- Tell me about yourself is a short pitch with a point of view about why you fit this job. Walk me through your resume is a longer, chronological tour where the interviewer wants to understand the sequence and the choices between roles. For the second one, go role by role and explain transitions; for the first, compress and aim everything at the posting.
- Can I use the same answer for every interview?
- Keep the same skeleton but change the past and future parts for each posting. The present section rarely changes. The experience you highlight should match the problems in that job description, and the closing reason should name something true about that role or team. Reusing a generic ending is the most common reason an otherwise good answer feels flat.