For a fresher, "tell me about yourself" is about potential. With two or more years of experience, it is a 90-second pitch that tells the interviewer what kind of engineer you are, what you have shipped and why this role is the next step. It also sets the agenda: interviewers often pick their next question from something you just said.
Below is a simple formula, six sample answers for common Indian career paths, and the mistakes that make experienced candidates sound junior. Replace every detail with your own. An answer only works if you can defend each line under follow-up questions.
The 90-second formula: present, proof, direction
Present: your current role, years of experience and the kind of systems you work on, in one or two sentences. Proof: one or two specific achievements with scope, your part and a result, such as latency cut, releases shipped or incidents reduced. Direction: why you are looking and why this role fits. End on the role, not on your past.
Keep it to 60 to 90 seconds, roughly 150 to 220 words spoken. Skip school, hobbies and a list of every technology. Mention the stack that matches the job description and leave the rest for the technical round.
Sample 1: backend developer, 3 years
"I'm a backend developer with three years of experience, currently at a fintech services company in Pune, where I build Java and Spring Boot services for loan processing. The work I'm proudest of is our repayment service. I redesigned how it handles retries with idempotency keys, which stopped duplicate debits that used to cause support escalations every week. I also own the service's alerting, so I've learned to design for failure, not only for the happy path. I'm now looking for a product team where I can work closer to scale and system design decisions, which is why this backend role on your payments platform stood out to me."
Sample 2: frontend engineer, 5 years
"I've been a frontend engineer for five years, mostly React and TypeScript. For the last two I've led the frontend for a B2B dashboard used by around two hundred client companies. My biggest contribution was a performance project: we moved heavy tables to virtualised rendering and split the bundle by route, which made the main dashboard noticeably faster on the low-end laptops many clients use. I also set up our component library so three teams could ship consistent UI. I'm looking for a role with more ownership of frontend architecture, and your design-system work is exactly that."
Sample 3: QA engineer moving to SDET
"I'm a QA engineer with four years of experience in e-commerce testing. I started with manual regression and moved into automation: I built our Selenium and TestNG suite for checkout and later added API tests with Rest Assured in the CI pipeline, which cut our release regression from two days to a few hours. I now spend most of my time writing test code and reviewing developers' pull requests for testability. I'm looking for an SDET role where automation and quality engineering are the core job, which is what this position describes."
Sample 4: service company to product company
"I have four years at a large IT services company, working on a retail client's order management system in Java and Angular. Over time I moved from bug fixes to owning features end to end: I led the migration of the client's returns flow to a new microservice, including the data migration plan and the rollback strategy. Working directly with the client's architects taught me to justify design decisions, not just implement them. I want to move to a product company so I can own a product long-term and see the impact of what I build, and this team's focus on the core platform is why I applied."
Sample 5: tech lead, 8+ years
"I'm a tech lead with nine years of experience, the last three leading a team of six engineers on a logistics platform. My focus is reliability and delivery. We split a monolith's shipment-tracking module into event-driven services, which let us release that area weekly instead of monthly, and I introduced on-call runbooks that reduced repeat incidents. I still write code, mainly on critical paths and in reviews, but most of my impact now comes from design reviews and growing engineers. I'm looking for a staff or lead role where I can shape architecture across teams, which matches this opening."
Sample 6: returning after a career gap
"I'm a full-stack developer with three years of experience in Node.js and React. I took a year's break for a family responsibility, and I used the last few months of it to refresh my skills. I built and deployed a small booking app with authentication, payments in test mode and CI, and completed a cloud certification. Before the break, I built internal tools at a healthcare startup, including a reporting module the operations team used daily. I'm ready to return full-time, and this role's mix of Node.js and React is a strong match for what I've done."
Tip: state a gap once, briefly and without apology, then move straight to what you did to stay current. Interviewers mostly want to know you are ready now.
Mistakes that make experienced candidates sound junior
Reciting the resume line by line. Listing technologies instead of outcomes. Saying "we" for everything, so the interviewer cannot tell what you did. Complaining about your current employer as the reason for leaving. Ending with "that's it" instead of a reason for this role. Going past two minutes.
Also prepare the follow-ups your pitch invites. If you mention idempotency keys, expect "how did you store them and for how long?" If you mention leading a migration, expect "what went wrong?" The pitch is a menu, so only list dishes you can serve.
Practise it properly
Write your version, then say it aloud and record it. Trim anything you stumble on. In CrackInterviewAI, load your resume and type "tell me about yourself" to get a structured outline based on your own experience. Then compare it with your version and keep the strongest lines in your own words. Rehearse until you can deliver it naturally without reading. For the fresher version, see self introduction for freshers.
Build your pitch from your own resume
Load your resume in CrackInterviewAI, generate a structured outline, then rehearse it aloud until it sounds like you.
Frequently asked questions
How long should "tell me about yourself" be for an experienced candidate?
About 60 to 90 seconds, roughly 150 to 220 spoken words. Longer answers lose attention and crowd out the questions that follow.
Should I mention my current salary or notice period in my introduction?
No. Keep the introduction about your work and the role. Salary and notice period come up separately, usually with HR.
How do I introduce myself when switching from a service company to a product company?
Lead with ownership: features you drove end to end, design decisions you made and their impact. Then explain why you want long-term product ownership.
Should I talk about my personal life?
Only briefly, if at all. With experience, interviewers want your professional story. A one-line personal detail at the end is fine if it is relevant.
Is it okay to use a prepared answer?
Yes, as long as it is your real experience in your own words, and you can defend every line when the interviewer asks follow-up questions.
Keep exploring
Return to the CrackInterviewAI homepage to download the Windows app, or browse all guides on the interview prep blog.