How to answer "Tell me about yourself" (with 5 examples by career level)

By Kwasi · 2026-05-16

How to answer "Tell me about yourself" (with 5 examples by career level)

"Tell me about yourself" sounds casual. It is not casual.

This is the first question in roughly 90% of interviews, and most people blow it by doing one of two things: reciting their resume chronologically, or giving a life story that starts with where they grew up. Neither works.

The interviewer is asking one thing: why should I keep talking to you for the next 45 minutes?

Your answer needs to do three things in about 60 seconds:

  1. Establish what you do right now
  2. Give one or two relevant highlights from your background
  3. Connect it to why you're sitting in this particular interview

That is the whole formula. Present, past, future. Let me show you what it sounds like at different career levels.

New grad (0-1 years experience)

"I just graduated from Georgia Tech with a CS degree. During school, I interned at a fintech startup where I built their internal dashboard for tracking customer onboarding metrics. It was a small team, so I got to own the full feature from database to UI. I'm looking for a full-time role where I can keep building real products, and when I saw your posting for a frontend engineer, the focus on customer-facing tools felt like a good fit."

Why it works: Specific project, specific company, specific reason for applying. No filler about "passion for technology."

Early career (2-4 years)

"I'm a product designer at a B2B SaaS company, focused on our onboarding flow. Over the past two years I've redesigned the trial experience, which cut our time-to-value from 12 days to 4. Before that I was at an agency, which gave me exposure to a lot of different industries but not much depth. I wanted to go deeper on one product, which is why I moved in-house. Your team is doing similar work on self-serve onboarding and I have a lot of opinions about what works."

Why it works: Leads with a measurable result. Explains the career move without being defensive about it. Ends with genuine interest, not generic enthusiasm.

Mid-career (5-9 years)

"I've spent the last six years in data engineering, mostly in healthcare. Right now I'm the lead engineer on a team of four at a Series B health-tech company. We built the pipeline that processes about 2 million patient records daily for our analytics product. Before that I was at Deloitte doing similar work but in consulting engagements, which meant I rebuilt the same pipeline patterns for different clients every few months. I'm looking for a company where I can own a system long enough to actually make it good. The scale you're operating at, and the fact that you're hiring for a principal-level role, is what got my attention."

Why it works: The career arc makes sense. The motivation is honest, not aspirational. Mentions scale to show they did their research.

Senior / manager level (10-15 years)

"I run the payments engineering team at a mid-size e-commerce company, about 12 engineers across three squads. We process roughly $400M in transactions annually. The biggest thing we shipped last year was migrating from a legacy payment processor to Stripe, which took eight months and had zero downtime during cutover. Before this role I was an IC at two different fintech companies, so I came into management with a strong technical foundation. I'm exploring this role because your payments challenges are more complex than what I'm solving today, and I want to work on harder problems."

Why it works: Numbers give scale. The migration story shows execution. "Harder problems" is honest and flattering without being sycophantic.

Executive / director level (15+ years)

"I've spent my career in supply chain technology, most recently as VP of Engineering at a logistics company where I grew the team from 15 to 60 engineers over three years. We rebuilt the routing engine that powers about 30% of last-mile delivery for mid-size retailers in the Southeast. The business grew from $20M to $85M ARR during that period. I led the technical side of that growth: hiring, architecture decisions, vendor selection. I'm at a point where I want to do that again at a company with a larger surface area, and your expansion into international markets is exactly the kind of complexity I want to take on."

Why it works: Revenue numbers tie the technical work to business outcomes. The motivation is about challenge, not title.

Common mistakes to avoid

Starting with "Well, I'm originally from..." Nobody cares where you grew up unless you're interviewing at a company in your hometown and it is relevant. Listing every job you've held. Pick the 2-3 that matter for this role. Skip the rest. Saying "I'm passionate about..." This phrase has been drained of all meaning. Replace it with something specific you've done that shows the interest. Going longer than 90 seconds. Time yourself. If you're past 90 seconds, you're rambling and the interviewer has stopped listening. Being too humble. This is not the question for "I'm still learning" energy. State what you've done. You can be thoughtful and specific without being arrogant.

How to practice this

Write your answer down. Read it out loud. Time it. If it is over 90 seconds, cut something. Then practice it again without reading.

The goal is not to memorize a script. The goal is to have the structure so internalized that you can say it naturally, like you're explaining to a friend what you do and why you're job hunting.

If you want to hear how your answer actually sounds under pressure, try MockGenie. The AI asks follow-up questions based on what you say, so you can't just recite a memorized answer. You have to actually think on your feet.

Good luck. This question is your first impression. Get it right and the rest of the interview starts on solid ground.

More interview prep guides · Practice with MockGenie — first session free