Guide

How to answer "Tell me about yourself"

It's often the first question, and it sets the tone for the rest of the interview. Here's a simple structure, two sample answers, and how to practise until it sounds natural rather than memorised.

What the interviewer actually wants

"Tell me about yourself" isn't a request for your life story. The interviewer wants three things: a quick picture of who you are professionally, a sense of why you're in this room for this role, and a feel for how clearly you speak. It also gives them a few threads to pull on for follow-up questions, so what you mention matters.

A good answer runs for about a minute to ninety seconds. Shorter, and you've given them little to work with. Much longer, and they start waiting for you to finish.

A structure that works: present, past, future

Present. What you do now, in one or two sentences. Your current role, or your degree and what you're focusing on.
Past. Two or three things that led here and are relevant to this job: a project, a responsibility, a result. Pick examples you'd be happy to be asked more about.
Future. Why this role, and why now. Connect what you've done to what they need.

You can swap the order to past, present, future if your story reads better chronologically. What matters is that it ends on why you're a fit, not on a stray detail.

Sample answer: a fresher

I'm in the final year of a B.Tech in electronics and communication at a college in Pune. Over the last two years I've moved more towards software. I built a small attendance app for our department with two classmates, which taught me how to work with real users who report problems at the worst possible time. I also did an eight-week internship at a logistics start-up, where I wrote scripts to clean up their delivery data and cut a weekly manual report from a day to about an hour.

What I enjoyed most in both was taking something messy and making it simpler for the people using it. That's why this graduate engineer role appeals to me: your team builds internal tools for operations staff, and that's exactly the kind of problem I want to get better at.

Notice what it leaves out: school marks, hobbies, family background. Those can come up later if they ask.

Sample answer: an experienced engineer

I'm a backend engineer with about six years of experience, currently at a payments company where I lead a team of four working on our settlement systems. Before that I spent three years at a mid-sized e-commerce firm, mostly on order processing and search.

The work I'm proudest of recently is a rebuild of our reconciliation pipeline. It used to need manual fixes most mornings; after the rebuild, those mostly disappeared, and I learnt a lot about designing for failure rather than hoping it won't happen.

I'm now looking for a role where reliability is central to the product, and where I can keep mentoring while staying hands-on. Your platform team seems to be exactly that, which is why I applied.

It's specific, it names a result without inflating it, and it ends by linking back to the job.

Common mistakes

Reciting your CV. They've read it. Pick the parts that matter for this role and say why they matter.
Starting too far back. "I was born in..." or "In school I..." uses up your best minute on the least relevant part.
No ending. Many answers trail off with "...so, yeah". Plan your last sentence and stop there.
Memorising word for word. A script sounds like a script, and if you lose your place you freeze. Memorise the three or four points and the closing line, not every word.
Being vague about results. "I worked on a lot of projects" says nothing. One concrete example is worth five general claims.
Undercutting yourself. Phrases like "I just helped a bit" or "it was only a small project" make the interviewer discount what follows. Say what you did plainly.

How it should sound

Delivery matters as much as content here because it's the first impression. Aim for a steady pace, a pause between your present, past and future sections, and eyes on the interviewer (or the camera, for a video call). If you tend to rush when nervous, the first answer is where it shows most. Our guide on reducing filler words has a few techniques that help here too.

Practise it in Kayavak

Open Interview mode with the Common interview questions set (or Campus placements and freshers if you're a student) and answer "Tell me about yourself" out loud. Check the answer length, pace and filler words in your report, then use Retake and compare the two attempts side by side. Do it three or four times over a couple of days rather than ten times in one sitting. More on how sessions work is on the interview practice page.