It's usually the first question of the interview, and it's the one people prepare least. "Tell me about yourself" sounds like small talk, so candidates wing it. They start at university, list every job in order, and trail off with "...and that's me." Two minutes go by and the interviewer still doesn't know why they should care.
This answer sets the frame for everything after it. Get it right and the interviewer starts asking about your strongest material. Get it wrong and you spend the next half hour climbing out of a vague first impression. Here's how to build an answer that works, with examples you can adapt.
What the interviewer is really asking
"Tell me about yourself" is an open question, but it isn't open-ended. Underneath it, the interviewer wants to know three things:
- Who are you professionally, right now? Your current role, level and focus.
- Is your background relevant to this job? Whether your experience lines up with what they need.
- Why are you here? Whether this move makes sense for you, or whether you're applying to anything that's open.
So your hobbies, your hometown and your full employment history mostly don't belong here, unless one of them speaks directly to the role. Treat the question as "Give me the short version of why you fit this job."
The structure: present, past, future
The simplest reliable structure has three parts, in this order.
Present: what you do now
Open with your current role and the core of what you do. One or two sentences. Lead with the part that's most relevant to the job you're interviewing for, not necessarily the part that takes most of your week.
"I'm a customer support lead at a mid-sized SaaS company, where I run a team of six and own our escalation process for enterprise accounts."
Past: the experience that got you here
Next, pick two or three proof points from your background that match the posting. They can be career moves, skills you built or results you delivered. This isn't a chronology. You're choosing the evidence.
To choose, reread the job description and note the requirements it repeats or puts first. Then match each proof point to one of them. If the posting stresses "cross-functional work with product," a story about working with engineers to fix a recurring bug is worth more than a promotion that's already on your résumé.
Use specifics where you have them, like team size, scope, a before-and-after result or a tool you know well. Only use numbers you could explain if asked. They will ask.
Future: why this role, why now
Close by connecting your past to this specific job. It's the part most people skip, and it's the part that makes the answer feel finished.
"I'm looking to move into a customer success role where I own the relationship before problems escalate, and that's exactly what this position focuses on."
Ending here does two things. It tells the interviewer you chose this job on purpose. And it hands them an obvious next question, usually about the experience you just mentioned, which is the ground you want to be on.
How long it should be
Aim for 60 to 90 seconds. That's roughly 150 to 220 words spoken at a normal pace. Under 45 seconds can sound evasive or underprepared. Over two minutes and you're giving a monologue, and the interviewer is waiting for a gap to cut in.
For a quick recruiter screen, go shorter, closer to 60 seconds. With a hiring manager in a longer interview you can use the full 90 and add a bit more detail to the "past" section.
Examples for three common situations
Adapt these. Don't memorize them.
Experienced candidate, same field
"I'm a backend engineer at a logistics company, mostly working on our order-routing services in Go. Over the last three years I've led the migration of our main routing service off a legacy monolith, and I now own on-call for that system. Before that I spent two years at an agency building APIs for clients across very different stacks, which is where I got comfortable picking up new codebases quickly. What drew me to this role is the scale. You're handling far more traffic than we do, and I want to work on reliability problems at that level."
Career changer
"I'm currently a high school science teacher, and for the last two years I've been moving into instructional design. I've rebuilt my school's onboarding course for new teachers in Articulate Rise, and I completed a certificate in learning experience design last spring. Teaching gave me something a lot of designers have to learn on the job: I've spent eight years watching in real time what makes people disengage. I'm applying here because your team builds training for frontline staff, and that's very close to the audience I know best."
For a career change, name the transition up front. Leaving it unsaid makes the interviewer wonder. Saying it plainly lets you frame it.
Recent graduate
"I just finished a degree in economics, and the part I enjoyed most was the applied work. For my final project I built a model of regional housing prices in Python, and I spent last summer interning with a city planning office, where I cleaned and analyzed permit data for their annual report. I'm looking for an analyst role where I can keep working with messy real-world data, and your focus on public sector clients is a big part of why I applied."
Without much work history, coursework, projects and internships count as proof points.
Mistakes that weaken the answer
- Reciting your résumé in order. They have it already. Choose and frame, don't list.
- Starting too far back. Unless it's directly relevant, skip school and early jobs if you have several years of experience.
- Getting personal too soon. A brief human detail is fine if it connects to the role. Family, health and politics are better left out.
- Being negative about your current job. "I'm looking for more ownership" works. "My manager is impossible" doesn't.
- One answer for every company. The present and past sections can stay mostly the same. The future section should change for every interview.
- No ending. Trailing off with "so, yeah" wastes your strongest line. Finish on why this role.
How to prepare it in 20 minutes
- Pull the requirements. List the three or four things the posting cares about most.
- Draft your present line. One sentence about your current role, framed toward those requirements.
- Pick your proof points. Two or three experiences, each tied to a requirement, with one specific detail each.
- Write your future line. Why this role and this company. Make it specific enough that it couldn't be pasted into another application.
- Say it out loud and time it. Cut until it fits in 90 seconds.
- Rehearse the shape, not the script. Memorize the order and the key points, not the exact words, so it sounds like a conversation.
Practicing out loud is the step people skip, and it's where most of the improvement happens. Writing an answer and saying one fluently are different skills. If you'd like a structured place to rehearse, Twin-Seeker's Interview Gym runs mock interviews built from the specific job posting. You can speak or type your answers, and you get a graded debrief afterward. Once your opening is solid, the STAR method covers the behavioral questions that usually come next.
Sources and further reading
On this blog
- How to Prepare for a Job Interview: The 2026 Guide
- The STAR Method: Answer Any Behavioral Interview Question
- How to Tailor Your Resume to a Job Description (Fast)
External
Frequently asked questions
How long should my answer to "tell me about yourself" be?
Aim for 60 to 90 seconds, roughly 150 to 220 spoken words. Go shorter for recruiter phone screens and use the full 90 seconds in longer interviews with hiring managers.
Should I include personal information?
Mostly no. Keep it professional and focused on the role. A short personal detail is fine if it ties directly to the job, but family, health, religion and politics are best left out.
Is "walk me through your résumé" the same question?
Close enough to use the same structure. You might give a little more context on each role, but you should still pick the relevant moves and finish on why this job, not list every position.
Should I memorize my answer word for word?
No. Memorize the structure and the two or three proof points, then practice saying it out loud in slightly different words each time. A memorized script tends to sound recited, and it falls apart if you're interrupted.
Put this playbook on autopilot
Twin-Seeker discovers roles that fit, beats the ATS with a tailored résumé, drills you for interviews, and runs your whole pipeline — so you apply smarter, not harder.
Get started with Twin-Seeker →