'Tell me about yourself' is the opening question in nearly every Indian interview, yet most candidates answer it poorly: they either read their resume chronologically or give a vague self-description with no memorable content. This question is your only chance to set the agenda for the entire interview. A structured, specific, well-rehearsed answer signals confidence and self-awareness before the technical content begins. This guide covers the exact structure that works, sample answers for freshers and experienced candidates, and the six mistakes that consistently hurt candidates.
The Structure That Works in 90 Seconds
The 5-part structure, timed:
(1) Academic background or role identity (15 seconds): For freshers: 'I am a final-year Computer Science student at [College], graduating in [Year] with a CGPA of [X].' For experienced: 'I have [X] years of experience as a software engineer, currently at [Company] working on [product/team].'
(2) Most relevant project or achievement (20-25 seconds): The ONE thing most relevant to this specific role. Be specific: 'I built a recommendation engine using collaborative filtering that improved click-through rates by 28% in our A/B test.' Not: 'I worked on a machine learning project.' The specificity signals that you are the kind of person who thinks in measurable outcomes.
(3) Key skills with context (15 seconds): 2-3 skills with one line of context each. 'I have strong experience with Java and Spring Boot, which I have used to build REST APIs serving 500,000 daily requests in production.'
(4) Career motivation (15 seconds): one sentence that is specific, not generic. Not 'I want to learn and grow.' Instead: 'I am specifically interested in product companies at Swiggy's scale because I want to work on systems where the traffic and reliability challenges are genuinely complex.'
(5) Bridge to this company (10 seconds): one researched, specific reason. Not 'you are a great company.' Instead: 'I have been following Razorpay's API-first approach to embedding payments and I want to work on the infrastructure that makes that possible.'
Total: 90 seconds. If the interviewer wants more detail on any point, they will ask. Your job is to give them 5 well-chosen anchor points, not to tell your entire story.
Sample Answer for a Fresher with No Work Experience
Sample: 'I am a final-year Computer Science student at BITS Pilani, graduating in May 2027 with a CGPA of 8.4. The project I'm most proud of is a real-time collaborative code editor I built using React, Node.js, and WebSockets. I handled the operational transformation algorithm for conflict resolution when multiple users edit the same line simultaneously; it was a genuinely hard problem and I spent 3 weeks getting it right. I have strong skills in JavaScript, Node.js, and PostgreSQL and have started working on system design concepts over the last 6 months. I am specifically interested in Razorpay because I have used the payment APIs as a developer and I find the problem of making payments reliable at scale deeply interesting.'
What makes this answer strong: it opens with the specific project (not 'I am a hardworking student'), the technical challenge is concrete (operational transformation, not 'complex algorithms'), the interest in the company is specific and genuine (used the APIs as a developer), and the whole thing takes under 90 seconds.
What to avoid: 'I am a hardworking and dedicated individual who is passionate about technology and always eager to learn.' This wastes 15 seconds of your opening and tells the evaluator nothing specific about you.
Sample Answer for an Experienced Software Engineer
Sample: 'I have 4 years of experience as a backend software engineer, currently at Urban Company working on the platform team. The work I am most proud of is the migration of our home-service booking system from a monolith to a set of loosely coupled services, which reduced our average API response time from 800ms to 120ms and allowed us to deploy the booking and payment flows independently. My primary stack is Java and Spring Boot, with PostgreSQL and Redis, and over the last year I have been working on distributed systems concepts because I want to move into technical leadership of larger systems. I am specifically interested in Flipkart because the scale of your inventory and order management systems is an order of magnitude larger than anything I have worked on, and I believe the engineering challenges there will accelerate my growth significantly.'
Key elements: specific achievement (monolith to services migration with concrete metrics), primary stack with production context (serving real traffic), honest motivation (scale that exceeds current experience), specific connection to the target company (inventory scale, not just 'great company').
Practise your 'tell me about yourself' answer with HireStepX's AI voice interviewer. Get real-time scored feedback on structure, specificity, and delivery. First 2 sessions free.
Practice freeSix Common Mistakes to Avoid
Mistake 1: Starting with 'I am a hardworking and dedicated individual who is passionate about technology.' This is the default answer and signals no self-awareness about what makes you distinctive. Evaluators have heard this hundreds of times.
Mistake 2: Reciting your resume from Class 10 onward. The evaluator has your resume. Use this question to surface the 2-3 most relevant highlights, not to summarise your entire education and employment history.
Mistake 3: Speaking for more than 2 minutes. Most evaluators lose attention after 90 seconds. If you are still talking at the 3-minute mark, you have already failed to prioritise.
Mistake 4: Vague project descriptions. 'I worked on a machine learning project in my final year' is not memorable. 'I built a churn prediction model using LightGBM that reduced customer churn by 18% in our A/B test on a dataset of 2.3 million users' is memorable.
Mistake 5: Generic company connection. 'I want to work here because you are a great company with a great culture' tells the evaluator you did not research the company. Replace it with one specific, researched reason.
Mistake 6: Delivering it robotically as a memorised script. Practise until it sounds natural and conversational. Record yourself and watch the playback. The content should feel spontaneous even though you have rehearsed it.
Frequently asked questions
Explore more