How to Answer "Tell Me About Yourself" (Formula + Examples)

It's the first real question in almost every interview, and it sets the tone for everything after. Yet most people fumble it — either a nervous life story or a flat resume recital. Here's the structure that works.

The present–past–future formula

Keep it to 60–90 seconds, in three beats:

1. Present — who you are professionally right now. "I'm a backend engineer at X, focused on payments infrastructure."
2. Past — one or two proof points that led here. "Before that I scaled a checkout service from 50 to 5,000 requests per second."
3. Future — why you're in this room. "Now I'm looking to work on developer-facing products at a company like yours, which is exactly what this role is."

The future beat is the secret weapon: it tells the interviewer you're intentional, not just shopping.

Three example answers

New grad:

"I just finished my CS degree at X, where I specialized in distributed systems. During my final year I built a real-time chat app that handled 10k concurrent users for a class project, which got me hooked on backend performance. I interned at a fintech startup last summer and shipped a feature that's now in production. I'm looking for a new-grad backend role where I can keep going deep on systems — and your infrastructure team is doing exactly the kind of work I want to grow into."

Career switcher:

"I spent five years in data analysis in healthcare, and over time I found I was the person automating everyone's reports. That pulled me into engineering — I did a bootcamp, then freelanced building internal tools. The healthcare background means I think about edge cases and compliance by default. I'm now looking for a full-time software role where domain rigor matters, which is why this position stood out."

Senior:

"I'm an engineering lead with about ten years in fintech, currently running a team of six on a billing platform that processes nine figures a year. I came up as an IC on payments, moved into leadership four years ago, and I'm happiest when I'm both shaping architecture and growing engineers. I'm looking for a staff or lead role with more product ownership — your team's scope is a strong fit."

What to leave out

• Your hometown, hobbies, or marital status (unless genuinely relevant).
• A chronological walk through every job since college.
• Anything negative about a current or past employer.
• Salary, notice period, logistics — that's for later.

Tighten it with reps

The difference between a 60-second answer and a 2-minute meander is practice. Record yourself, cut the filler, and run it until it's automatic but not robotic. If you rehearse with live structure feedback, you'll catch yourself drifting into the "past" beat for too long — the most common failure mode.

---

Next: the 20 most common interview questions and the behavioral STAR method.