The interviewer asks it as they sit down, almost in the same breath as offering you coffee. It seems harmless. It isn't: it's often the only answer they'll hear in full before they start interrupting, and it frames everything that follows.

What they're actually testing

"Tell me about yourself" isn't an invitation to share your biography. Nobody needs to know where you grew up or why you chose your major. What the interviewer observes is your ability to select: out of everything you could say, what do you choose to highlight for this job?

A candidate who recites a full chronology shows they haven't thought about the posting. A candidate who gives three sentences that all point at the role shows the opposite. The question is a framing test before it's a skills test.

The structure: present, past, future

1. Present (20 seconds). Who you are professionally right now. "I'm a product analyst at a B2B software company, where I own reporting for the sales team."

2. Past (60 seconds). Two or three experiences that prove you can do this job. Choose from the posting's top requirements, and use one number if you have it. "Before that, I built the dashboards that cut report prep time from two days to two hours."

3. Future (20 seconds). Why this role, why now. "I'm looking to work on product decisions directly, and your team is doing exactly that."

Total: about two minutes. Practice until it fits, not until it's memorized.

A before-and-after

Before: "I graduated in 2019 with a degree in economics, then I did an internship, then I joined a startup, then another company, and now I'm looking for something new..."

After: "I'm a data analyst focused on retention. At my current company I built the churn model the customer success team now uses weekly, which helped cut churn by a few points. Before that I spent three years in consulting, which is where I learned to present to executives. I'm interested in your role because it combines the analysis I like with a direct line to product."

The second is shorter, concrete, and every sentence points at the job.

Common mistakes

  • Reading your resume aloud. They've read it. Add what it doesn't say.
  • Going too personal or too long. One brief personal touch is fine; three minutes of backstory is not.
  • Starting with your education when you have ten years of experience.
  • Never mentioning the role. If your answer could be used for any job, it's the wrong answer.
  • Sounding scripted. Know your three beats, not your exact words.

Adapting it

For a phone screen, keep it to ninety seconds. For a hiring manager, spend longer on the past and make it specific to their team's problems. For a career change, make the thread explicit: why your previous experience is an asset here.

Key takeaway: present, past, future, in two minutes, all pointing at the job.

Write your answer once, then adjust the "past" section for each posting. Say it out loud and record it on your phone. The most common issue isn't content, it's length. For the full set of questions this one leads into, see common interview questions. In Prepint, each application keeps the posting and your notes together, so you can rework this answer in a minute before every interview.