Tell Me About Yourself: How to Answer (8 Sample Answers)

"Tell me about yourself" is almost always the first question in an interview, and the only one you can prepare almost word for word. Yet most candidates improvise it, start from high school, and lose the interviewer within the first minute. This guide breaks it down: what it really tests, a simple structure, a short phone version and a full version, and eight sample answers for different backgrounds. For the behavioral questions that usually follow, see our guide to HR interview questions.

What is the interviewer really testing?

Three things: whether you can summarize yourself clearly, what you choose to highlight when handed a blank page, and whether your story connects to this job. The facts matter less than you think - the interviewer has already read your resume. What they don't know yet is how you connect the dots.

Your answer also feeds the next questions: mention a project and you'll be asked about it. So mention only what you're ready to expand on.

What structure works? Present, past, future

Three parts, in this order: start with today, go back only to explain how you got here, and end by connecting to the role.

• Present, about 20 seconds: what you do now and what you're good at. Role, field and one concrete achievement - "I'm an operations manager at...", "I'm a third-year student in...".
• Past, about 30 seconds: two or three stops that explain the present. Not every job - only the ones that built the skills this role needs. This is also where you explain a career change or a gap, in one sentence.
• Future, about 20 seconds: what you're looking for now and why this role. It's the part that changes from interview to interview, and the part most candidates forget.

If you're just starting out and have no professional "present", your present is your studies, your service or your current job - even if it's in a different field. The structure stays the same.

How long should your answer be?

In person or on video, aim for 60 to 90 seconds. At a relaxed speaking pace that's roughly 150 to 220 words - about half a page. Treat it as a rule of thumb: under 30 seconds sounds evasive, and past two minutes the interviewer starts waiting for you to finish. Write your answer, count the words, then say it out loud against a timer. If it runs long, the part to cut is almost always the past.

What changes between a 30-second phone screen and a 90-second interview?

On a recruiter phone screen, "tell me about yourself" is mostly a check that you meet the basic requirements. Thirty seconds - about 60 to 80 words - is enough: who you are, one sentence of relevant experience, and why you applied. With the hiring manager there's time for the full version, with one achievement and a reason this specific role fits.

Here's the 30-second version of sample answer 5 below: "I'm a full-stack developer with five years of experience, currently on the payments team at an e-commerce company, where I led our move to TypeScript. I want to work long-term on a complex B2B product, which is why your role on the permissions team caught my eye." Same story, without the past or the detail. If the recruiter wants more, they'll ask.

What does a good answer sound like? 8 sample answers

Each answer uses the same structure for a different background. Don't copy them - take the skeleton and fill it with your own details. Specific details are what make an answer memorable.

1. No experience: a student looking for a part-time job

"I'm a second-year economics and accounting student. I've waited tables at the same restaurant for three years, and this past year I'm the one who closes the register and sends the shift report to the manager. Last semester I built an Excel budget model for a nonprofit I volunteer with, and they still use it. Your role means working with financial data from day one, three days a week alongside my studies - and I'm looking for a place I can stay until I graduate."

2. Recently finished military service

"I finished three years of army service two months ago, most of them as a battalion logistics NCO running the equipment warehouse - receiving, issuing, stock counts and orders. Before a major exercise the records didn't match the shelves; I did a full count in three days, found where the records broke, and we switched to a short weekly count. I want to keep doing this as a civilian, and a distribution company like yours is the natural place. I can start right away and work shifts."

3. Career change: from teacher to data analyst

"I taught middle-school math for seven years and coordinated the department for the last three. That's where I started working with data without calling it that: I built a sheet from the whole grade's test scores that showed each teacher which topics their class had missed, and we rebuilt our exam review around it. It became my favorite part of the job, so this year I finished a course in SQL and Power BI and built two projects on open data. Your analyst role includes presenting findings to managers - which I did every week in front of a staff room."

4. Returning to work after a break

"I have six years in procurement, mostly as a buyer at a medical-equipment company managing about twenty suppliers. Two and a half years ago I took a break to care for my father - a decision I'm at peace with. I stayed close to the field by running procurement for our city's food bank as a volunteer, and recently took a refresher course on the ERP system in your posting. I'm back with full availability, looking for a role like yours where you build the supplier base, not just place orders."

5. Experienced developer looking for the next step

"I'm a full-stack developer with five years of experience, the last three on the checkout team at an e-commerce company. I led our front end's move to TypeScript, and this year I'm mentoring two new developers. Before that, two years of short client projects at a software services firm taught me to work out fast what a client really needs. What I'm missing is long-term work on a complex product business customers use all day. Your permissions team is exactly that, and I'd like to grow toward technical leadership there."

6. Customer service to B2B sales

"For three years I've been a retention agent at a telecom company: my job starts when a customer calls to cancel, so every call begins with a no. I've learned to listen for the real reason and offer something that fits it, and this year the team routes the hardest calls to me. Before that I did two years of customer service at an electronics chain. Now I want to move from keeping customers to winning new ones, and B2B sales, like your role, adds what retention lacks: a long relationship with the same customer."

7. Manager: from area manager to operations

"I'm an area manager at a fashion chain, responsible for five stores and about fifty employees. I came up from the floor - sales, then a store of my own, then the area four years ago. I'm proudest of a standard onboarding process I built after noticing each store trained new staff differently; since then fewer new hires leave in their first months. Now I want a broader operations role, designing processes for the whole company instead of running them in the field - and with the distribution centers you're opening, that's exactly the stage where it's needed."

8. First job after graduating

"I graduated a month ago in industrial engineering and management. My final project was with a packaging plant whose line kept stopping for product changeovers: I mapped them for a month, built a model that sequences orders to reduce them, and the plant adopted part of it. I also spent two years as a statistics teaching assistant, which taught me to explain complex things simply. I'm looking for a first role in production planning, and a plant like yours, running shifts with many products, faces exactly the problem I worked on."

What should you include, and what should you leave out?

The rule: every sentence should answer "why does this matter for this job?". If it doesn't, cut it - even if it's true and interesting.

Include

• Your current role or occupation, in the first sentence.
• One achievement with a concrete detail - what you did and what changed.
• Only the past stops that lead to this role.
• A short explanation of a career change or gap, before they ask.
• An explicit link to the role and the company: "which is why this role...".

Leave out

• Childhood and hobbies - unless they relate directly to the job.
• Marital status, age, religion or family plans. You don't have to share them.
• Criticism of your current or past employer, and salary expectations.
• Every job on your resume in order.
• Traits without proof, like "I'm hardworking and dedicated". One story shows it better.

What are the most common mistakes?

• Starting from school when you have ten years of experience.
• Reciting a memorized script - it sounds recorded and falls apart when you're interrupted.
• Using the same answer for every job. The future part has to change with the posting.
• Ending in mid-air, with no link to the role. The last sentence is the one they remember.
• Shrinking yourself - "I don't really have experience, but...". Say what you did.

What if English isn't your first language?

Many candidates interview in English for international companies while thinking in another language. Write the answer directly in English rather than translating it, and keep the grammar simple: present simple for the present, past simple for the past, and "I'm looking for..." for the future. Short sentences are your friend. Because this question comes first and sets the tone, it's the one most worth rehearsing out loud.

How do you practice your answer?

• Write three bullet points per part - present, past, future - not a paragraph. You'll remember points, not sentences.
• Memorize only your first sentence. A confident opening takes the pressure off the rest.
• Record yourself three times and time it. By the third take you'll hear where you ramble.
• Prepare a 30-second version for phone screens, and rewrite the future part for each posting.
• Check that your answer matches your resume - dates, titles and wording.

After this question come follow-ups about what you mentioned, and at the end, "do you have any questions for us?" - for that moment, see our 30 questions to ask the interviewer. If practicing with another person is hard, Custro has an AI mock interview that gives feedback on your answers (part of the Pro plan).