How to answer "Tell me about yourself" — a simple framework (with examples)

"Tell me about yourself" is the first question in almost every interview — and the one people most often ramble through. It isn't an invitation to recite your life story or your résumé line by line. It's your chance to frame, in 60–90 seconds, why you're the right person for this role. Here's a framework that works, two worked examples, and the mistakes to avoid.

Why interviewers ask "Tell me about yourself"

It's a warm-up, but it's not throwaway. The interviewer is checking three things at once: can you communicate clearly, do you understand what this role needs, and can you connect your background to it without being prompted. A tight, relevant answer sets the tone for everything after it. A rambling one makes them work to find the signal.

The framework: Present → Past → Future

The cleanest structure for this question is three short beats:

1. Present — who you are professionally right now, in one line.
2. Past — the one or two experiences that make you a fit for this role — each with a concrete result.
3. Future — why this role, now. Tie it to what they need.

Present–Past–Future works because it's a story with a direction: here's where I am, here's the proof, here's why I'm here. Keep it to 60–90 seconds — you're opening a conversation, not closing it.

Example 1 — an experienced hire

"I'm a backend engineer with about six years on high-traffic systems, currently on the payments team at TechServe. Over the last two years I led the rebuild of our checkout pipeline — we cut failed transactions from four percent to under one, and shipped it with zero rollbacks. I'm drawn to this role because it's the same problem at a bigger scale: reliability where every failed request costs a customer. That's the work I do best."

Notice: one line of present, one specific past win with a number, one future tie-in. No life story, no résumé recital.

Example 2 — a career changer

"I spent five years in operations before moving into data — so I come at analytics from the side of the people who actually use it. In my last role I built the reporting our regional managers now run their weekly numbers off, which taught me that the best analysis is the one someone will actually act on. I'm looking for a data role on a team that cares about impact, not just dashboards — which is why this one stood out."

A career change isn't a weakness if you frame the throughline. The past beat does the work: it turns "switched fields" into "brings a rare perspective."

Common mistakes to avoid

• The life story. "I was born in…" — start at your professional present.
• The résumé recital. They have your résumé. Pick the two things that matter for this role.
• No result. "I worked on the checkout pipeline" is weaker than "I cut failed transactions to under 1%." A number makes it stick.
• No tie to the role. End on why this job, or the answer floats free of the interview.
• Rambling. Past ~90 seconds, cut. Brevity reads as confidence.

Make it yours

The framework is the easy part; the hard part is picking which past win, for this role, and saying it cleanly under pressure. That's exactly what a tool like Slaydit does — it builds your "Tell me about yourself" from your real résumé and the specific job, so the version you deliver is grounded in what you actually did and matched to what they actually need. But the structure works with or without it: Present, Past, Future, one number, one reason.

The bottom line

"Tell me about yourself" isn't small talk — it's your opening argument. Present who you are, prove it with one specific result, and connect it to why you're in the room. Do that in 90 seconds and you've set the tone for the whole interview.

Related: What is an AI interview copilot? · Is Slaydit safe?