How to answer "tell me about yourself" in a job interview

You've read the job posting. You've ironed your shirt (or at least the part visible on Zoom). You join the call, exchange some small talk about the weather, and then it comes.

"So, tell me about yourself."

And suddenly your brain empties out like a bathtub. You know things about yourself. You've been yourself for decades. But somehow the question turns you into a deer in headlights reciting your LinkedIn summary from memory.

I've sat on both sides of this question hundreds of times, and I can tell you: almost everyone overthinks it. The good news is that a solid answer follows a pretty simple structure. The bad news is that "simple" doesn't mean "easy," because you still have to make choices about what to include and what to leave out. Those choices matter.

What the interviewer actually wants to know

Nobody asks "tell me about yourself" because they're curious about your hobbies or your hometown. (Unless you're interviewing at a surf shop, maybe.) They're doing a few things at once:

• Checking whether you can communicate clearly and concisely under mild pressure


• Getting a sense of how you see your own career arc


• Looking for a thread that connects your background to this specific role


• Buying themselves 90 seconds to finish scanning your resume

That last one is real. Interviewers are busy. Sometimes they pulled up your resume 30 seconds before the call. Your answer gives them a map of your experience so they know which follow up questions to ask.

This means your answer isn't a biography. It's a trailer. You're giving them just enough to get interested, organized in a way that makes the rest of the conversation easier.

The formula that works

I like the present, past, future structure because it's intuitive and hard to mess up.

Present: What you're doing now. Your current role, what you focus on, maybe one thing you're good at.

Past: How you got here. Not your whole career history. Just the one or two moves that are most relevant to this job.

Future: Why you're in this interview. What you're looking for next and why this role caught your attention.

The whole thing should take 60 to 90 seconds. Two minutes max. If you're going longer than that, you're losing them.

A few things to notice about this structure. It starts with the present because that's what's most relevant. It ends with the future because that creates a natural bridge into the conversation ("and that's why I was excited to see this role"). And it skips anything that doesn't serve the story you're telling for this particular job.

That last part trips people up. Your answer should change depending on the role. Not dramatically, but the details you pick should be different when you're interviewing for a product management role versus a marketing role, even if your background touches both.

If you're applying to a bunch of different positions and struggling to keep your story straight for each one, that's a sign your resume might need the same treatment. JobTailor can help you tailor your resume to each job description so the story on paper matches the story you tell in person.

Example answers you can steal

These aren't scripts. Read them, notice the structure, then write your own.

New grad

"I just finished my degree in computer science at UT Austin, where I spent most of my time focused on machine learning coursework and research. Last summer I interned at a fintech startup where I built a recommendation engine for their investment platform. That project got me really interested in applied ML, especially in financial services. When I saw this junior data scientist role at your company, it felt like a natural fit because you're doing similar work but at a much larger scale."

Notice what's not in there: GPA, clubs, the three other internships that aren't relevant. It's focused. One thread.

Mid career

"I'm a product manager at Shopify, where I lead a team working on merchant onboarding. Over the past two years we've cut the time to first sale by about 40%, mostly through simplifying the setup flow. Before Shopify I was at a smaller e-commerce company where I started as a business analyst and moved into product. I've spent the last six years in this space and I've gotten really interested in the payments side of things, which is what drew me to this role on your checkout team."

This one names specific results (40% improvement) and shows a clear trajectory. It also explains the "why here" without being generic about it.

Career changer

"For the past eight years I've been a high school biology teacher, and I'm now transitioning into instructional design. Teaching gave me a lot of experience breaking down complex topics for different audiences, building curriculum from scratch, and using data from assessments to figure out what's actually working. Over the past year I completed a certificate in learning experience design and did a freelance project redesigning onboarding materials for a SaaS company. I'm looking for a full time role where I can apply that mix of teaching instincts and design skills."

Career changers have the hardest version of this question because they need to bridge two worlds. The trick is to frame your past experience in terms that translate. "Building curriculum" becomes "designing learning experiences." "Using assessment data" becomes "measuring learning outcomes." You're not lying. You're translating.

Mistakes I see constantly

The autobiography. "Well, I grew up in Ohio, and I always loved computers, so I studied engineering, and then my first job was at..." Nobody needs your origin story. Start with where you are now, not where you were born.

The resume recital. Reading your resume out loud, in order, is boring and wastes time. They have your resume. They can read. Give them the narrative version, not the bullet point version.

The humble brag sandwich. "My biggest weakness is that I work too hard, but anyway, let me tell you about my three promotions." People can smell this from across the room. Just be direct about what you've done without the false modesty wrapper.

Being too vague. "I'm a passionate professional who loves working with people and solving problems." Cool, that describes every human with a job. Get specific. Name companies, numbers, projects. Specificity is what makes your answer memorable.

Going negative. Don't explain why you're leaving your current job by complaining about your boss. Even if your boss is terrible. Save that for your group chat. In the interview, frame it as moving toward something, not running from something.

Adapting for different contexts

Your answer shouldn't be identical in every interview. The setting matters.

Phone screen with a recruiter. Keep it short. Recruiters are often screening dozens of candidates and they're checking basic fit. Hit the structure cleanly, mention the most relevant experience, and keep it under 60 seconds. They'll dig into details if they want them.

First round with the hiring manager. You can go a little deeper here. Include a specific accomplishment that relates to what this team needs. This is where you show that you understand the role, not just the company.

Final round or panel interview. By this point they've read your resume carefully and talked to you before. You can be more conversational and spend more time on the "future" part. Why this team, why this mission, why now. They already know you're qualified. They're deciding if they want to work with you.

Startup versus corporate. At a startup, lean into adaptability, ownership, and comfort with ambiguity. At a larger company, focus on your ability to work within complex organizations and drive results through collaboration. Same experience, different framing.

The differences are subtle, but they matter. A startup founder interviewing you doesn't care that you "collaborated cross functionally with stakeholders." Just say you worked with the sales team to fix the onboarding flow. Plain language wins.

Make your answer match your resume

Here's something that comes up more than you'd think: candidates tell a great story in the interview, and then the interviewer looks at their resume and can't find any of it. The resume lists completely different projects, different skills, a different emphasis.

This happens because most people have one static resume they send everywhere, while their verbal pitch shifts depending on the role. That disconnect is a problem. When your resume and your spoken answer reinforce each other, the interviewer builds confidence in your story. When they don't match, it feels off, even if both versions are true.

The fix is to tailor your resume for each application so the written version supports the story you plan to tell. Yes, this is tedious. I know. That's exactly why tools like JobTailor exist. You upload your resume, paste the job description, and it adjusts your bullets to match what the role is actually asking for. Then your interview answer and your resume are telling the same story.

Putting it together

Write out your answer. Say it out loud a few times. Not to memorize it word for word (that sounds robotic) but to get comfortable with the structure so you can deliver it naturally even when you're nervous.

Time yourself. If you're over two minutes, cut something. If you're under 30 seconds, you're probably being too vague.

Record yourself on your phone if you can stand it. I know it's painful. But you'll catch verbal tics, rambling, and pacing issues that you can't hear in your own head.

And remember: this question is an opportunity to set the agenda for the interview. Whatever you mention in your answer, expect follow up questions about it. So only bring up things you're happy to discuss in detail. Don't mention that machine learning project if you can't explain what you actually did on it.

One more thing. It's okay to be a little human in your answer. You don't have to be a robot reciting accomplishments. If you genuinely love what you do, let that come through. "I got kind of obsessed with making the checkout flow faster" is more interesting than "I optimized conversion metrics." Both might describe the same work. One sounds like a person, the other sounds like a press release.

You've got this. Prepare the structure, fill it with specifics that matter for this job, practice it until it feels natural, and then go have a conversation. That's all an interview is, anyway.