"Tell me about yourself" is usually the first question in an interview, and it's also the one candidates prepare for the least. Because it feels open-ended, many people either recite their entire resume chronologically or launch into unrelated personal details. Both approaches waste the minute or two you have to set the tone for the rest of the conversation.

Think of it as a pitch, not a biography

Interviewers aren't asking for your life story. They're asking you to frame your own narrative before they start asking narrower questions. The best answers run 60 to 90 seconds and follow a simple present-past-future structure: where you are now, how you got here, and why you're interested in this specific role.

• Present: Start with your current role and the core skill or responsibility that's most relevant to the job you're interviewing for.
• Past: Briefly trace the one or two experiences that explain how you built that skill — not every job you've held.
• Future: End by connecting your trajectory to why this role, at this company, is the logical next step.

What to leave out

Skip your education history unless it's directly relevant, skip personal details like hobbies or family unless they come up naturally later, and resist the urge to list every tool or technology you've touched. A recruiter would rather hear why you're good at the two things the job actually requires than a complete inventory of your skills.

Tailor it to the role, every time

The same answer should not be used for every interview. If you're applying for a people-management role, emphasize team outcomes. If it's an individual-contributor technical role, lead with the specific problem you solved most recently. Read the job description beforehand and mirror its priorities back in your framing — this is the easiest way to sound prepared without sounding rehearsed.

A quick example

"I currently work as a product analyst at a fintech startup, where I own the dashboards our sales team uses to track conversion. Before that, I spent two years in a data support role, which is where I picked up SQL and started noticing patterns that led to a couple of process changes the team still uses. I'm looking for a role like this one because it would let me move from reporting on decisions to actually owning the analysis that drives them."

Notice what this example does: it's specific, it's under 90 seconds when spoken aloud, and it ends by pointing directly at the role being discussed. Practice your own version out loud a few times before an interview — not to memorize it word for word, but so the structure feels natural when nerves kick in.

Handle follow-ups calmly

A good answer often invites a follow-up question, which is a good sign — it means the interviewer is engaged. If you're asked to go deeper on something you mentioned, treat it as an opportunity rather than a derailment. The goal of this question was never to cover everything; it was to open the door to the parts of your background that matter most for this job.