'Tell me about yourself' is asked in nearly every Indian job interview: and most candidates still answer it poorly. They either recite their resume word-for-word or ramble without direction. This guide gives you a precise formula, shows you sample answers for both freshers and experienced professionals, and explains exactly what interviewers are evaluating when they ask this question.
What the interviewer is really asking
When an interviewer in India asks 'Tell me about yourself,' they are not asking you to read out your resume. They are evaluating four things simultaneously:
- Can you communicate clearly and concisely?
- Do you understand what is relevant to this role?
- Are you self-aware about your own career narrative?
- Does your background genuinely fit what we need?
Your answer sets the tone for the rest of the interview. A confident, focused 90-second response puts the interviewer in an engaged and positive frame of mind. A rambling 4-minute answer creates work for them before the real questions have even started.
The 3-part formula that works in India
The most reliable structure for Indian interviews is:
- Part 1: Present: Who you are right now (your current role, company, and what you do in 1–2 sentences)
- Part 2: Past: Your key background that is relevant to this role (education, prior experience, notable accomplishments: focus only on what matters for this specific job)
- Part 3: Future: Why you are here and what you want next (connect your goal to this company)
This structure works because it is forward-looking. You end on what you are moving toward, not on a summary of what is already on your resume. This naturally leads into 'Why this company?' questions and gives the interviewer a thread to pull.
Total time: 75–90 seconds. Practice until you can hit this target consistently.
Sample answer: fresher (engineering campus placement)
"I am a Computer Science final-year student at NIT Surathkal, graduating this May. During my degree I have focused specifically on backend development: I completed two internships, one at a startup called LogiQ where I built a real-time inventory tracking API using Node.js and PostgreSQL, and one at a mid-sized IT firm where I worked on microservices migration. My final-year project is a distributed job scheduler built with Kafka and Redis, which has been my deepest technical work to date.
I am applying to [Company] because your engineering team is known for working on real-scale distributed systems problems, which is exactly where I want to grow. I am looking for a role where I can go deep technically from day one, and I believe this position gives me that."
What makes this work: It is specific (real project names, technologies, outcomes), not generic. It connects past experience to a stated future goal. It flatters the interviewer's company without being obsequious.
Practise 'Tell me about yourself' with HireStepX's AI interviewer. Get real-time feedback on clarity, pacing, and content: then drill the follow-up questions that come right after.
Practice freeSample answer: experienced professional (switching companies)
"I am currently a Senior Data Analyst at PhonePe, where I have spent the last three years building the analytics infrastructure for our merchant dashboard: we went from 50,000 to 1.8 million active merchants during my tenure and I built most of the funnel and cohort tracking systems that helped the business team understand what was driving that growth.
Before PhonePe I was at a Series A startup in the edtech space, which is where I developed my SQL and Python skills from scratch under tight deadlines.
I am looking to move because I want to work on problems where the data scale is fundamentally different: your platform has 10x our transaction volume. I have been studying [Company's] engineering blog and I am excited about the work your team is doing on real-time anomaly detection at scale."
What makes this work: Specific numbers (50,000 → 1.8M), concrete tools, a clear reason for moving that is about growth rather than escape, and genuine research into the target company.
Common mistakes Indian candidates make
These are the patterns that cost candidates marks in Indian interviews:
- Starting with 'Myself [Name]': this phrasing is uniquely Indian and signals communication habits that interviewers note negatively. Start with 'I am...' instead.
- Giving a full chronological resume narration: interviewers have your resume. They want synthesis, not repetition.
- Ending with 'That's it' or 'That's all about me': end with the forward-looking statement (why you are here), not a summary of what you just said.
- Mentioning hobbies and family details unprompted: this is appropriate in some Indian social contexts but not in professional interviews unless specifically asked.
- Exceeding 2 minutes: every 30 seconds over 90 seconds tests the interviewer's patience. Practise with a timer.
How to tailor your answer for different interview contexts
Campus placement (dream company round): Lead with your most impressive technical project. Interviewers at companies like Google, Microsoft, or Atlassian are specifically looking for evidence of technical depth. Your campus name matters but your work matters more.
Service IT (TCS/Infosys/Wipro/Cognizant): They are hiring at volume. Be clear, confident, and communication-focused. Mention your CGPA if above 8.0. Mention any certifications. They value reliability over brilliance.
Startup interview: Lead with what you have built or shipped, even if small. Startups want to hire people with a bias for action. Mention a side project if you have one.
Senior-level (6+ years): Your answer should be primarily about impact. Revenue saved, users acquired, systems scaled. Save the background for the end: what you have done is more important than where you studied.
Frequently asked questions
Practice these questions on HireStepX