How to Answer "Tell Me About Yourself" in a Job Interview

The best answer follows a Present → Past → Future structure: where you are now, the one or two things in your background that got you here, and what you're looking for next. Kept to 60–90 seconds, it gives the interviewer exactly what they're actually asking for — a quick, relevant summary — instead of your full life story.

Why Interviewers Ask This

It's almost never asked out of genuine curiosity about your life. It's an opening question that does two jobs: it warms up the conversation, and it tests whether you can communicate clearly and concisely under mild pressure. A rambling, unstructured answer here sets a weak tone for the rest of the interview, even if your technical skills are strong.

The Present → Past → Future Structure

Present

One sentence on where you are right now — your current role, degree, or what you're focused on. "I'm a final-year Computer Science student specializing in backend development."

Past

The one or two experiences most relevant to this specific role — a project, internship, or achievement — with a concrete detail, not just a label. "During my internship, I built a REST API that handled the college's event registration system for about 2,000 students."

Future

Why you're here, tied to the role you're interviewing for. "I'm looking for a role where I can keep building backend systems at a larger scale, which is what drew me to this position."

Example Answer

"I'm a final-year Computer Science student with a focus on backend development. Over the past year, I built and shipped a full-stack event registration system as part of my internship, which taught me a lot about designing APIs that actually hold up under real usage. I'm now looking for a role where I can keep working on backend systems at scale, which is why this position caught my attention."

That's under 60 seconds spoken aloud, and it naturally invites a follow-up question about the project — which is exactly where you want the conversation to go next.

Mistakes That Make Candidates Ramble

Starting from childhood. Nobody needs your school history. Start from whatever is actually relevant to the role.

Listing skills instead of telling a story. "I know Python, Java, React, SQL..." is a resume, not an answer. Pick one concrete example instead.

No ending. If you don't land on a clear "future" statement, the interviewer is left to guess what you actually want — ending your answer on a stat clarifies it for them.

Practice It Out Loud

This answer only works if it sounds natural, not memorized word-for-word — which means the only way to get it right is to practice saying it out loud, more than once. Run it through a live-scored AI Mock Interview to see how it actually lands under time pressure, or use Flash Practice to drill this and similar behavioral questions in 60-second reps.

Frequently Asked Questions

What structure should I use to answer "tell me about yourself"? Present → Past → Future: where you are now, the one or two experiences most relevant to the role, and what you're looking for next — kept to 60–90 seconds.

Why do interviewers ask this question? It's rarely genuine curiosity — it's an opening question that warms up the conversation and tests whether you can communicate clearly and concisely under mild pressure.

How long should my answer be? Under 90 seconds spoken aloud. Longer answers tend to ramble and bury the point the interviewer is actually listening for.

What's the biggest mistake candidates make with this answer? Starting from childhood or school history instead of what's relevant to the role, listing skills instead of telling a story, or ending without a clear "future" statement that tells the interviewer what you actually want.