Almost every interview starts with "Tell me about yourself". It sounds casual, but it sets the tone for everything that follows. A clear one-minute answer makes you look prepared and steers the conversation towards your strengths.
What the interviewer wants
- A quick summary of who you are professionally.
- Why you are interested in this role.
- Something specific they can ask follow-up questions about, ideally a project.
They do not want your life story, your hobbies list or your resume read aloud.
Present, past, future
Present (who you are now)
Your current situation and focus. "I'm a final-year B.Com student focusing on data analytics, mainly SQL, Excel and Power BI."
Past (what you have done)
One or two concrete things that prove your skills, ideally projects. Name the problem, what you did and what you found.
Future (why this role)
Connect to the job. "I'm looking for an analyst role where I can work on real business data, and your team's work on customer analytics is exactly that."
A fresher example
"I'm a final-year B.Com student, and over the last year I've focused on data analytics: SQL, Excel, Power BI and some Python. The project I'm proudest of looked at why repeat customers were dropping for a fictional quick-commerce company. I joined orders, customers and delivery data in SQL, built cohort retention in pandas and found that customers whose first order arrived late came back far less often. I recommended a first-order delivery guarantee. I enjoy that mix of digging into data and explaining the answer to the business, which is why this analyst role appeals to me."
That is about a minute. It has a clear background, real skills, one specific project and a reason for applying. It also invites the obvious follow-up: "Tell me more about that project".
Tips
- Prepare, do not memorise word for word. Know the three parts and your key project, then say it naturally.
- Lead with your strongest project. You want the interview to go there.
- Adapt to the company. Change the last line for each role.
- Keep it around a minute. Shorter can feel thin; much longer loses attention.
- Be ready for the follow-up. Know your project's data, steps, challenges and results in detail.
Mistakes to avoid
- Starting with your school, family or hometown.
- Listing every tool you have heard of.
- Saying you want to "learn" without saying what you can offer.
- Mentioning a project you cannot explain in depth.
Practise aloud
Say your answer aloud several times, record yourself once and listen back. Then rehearse with a mock interview. If you do not yet have a project you are proud of, start one of our live projects; it will give you something real to talk about.
Practise what you just read
Reading helps; writing the code yourself is what sticks. Start here: