Tell me about yourself.

Short answer: Use a Present-Past-Future structure in 60 to 90 seconds: who you are now, what shaped you, and why this role is the logical next step. Keep it role-specific and outcome-driven, not a full life story. End with one line that connects directly to the job description.

Why this matters in Interview Preparation

For this question, interviewers evaluate communication clarity, relevance, and confidence in the first impression.

Step-by-step approach

1. Start with your current role and core expertise in one concise sentence.
2. Add 1 to 2 major achievements from recent work with measurable impact.
3. Briefly mention background context that is relevant to this role only.
4. Explain why you are interviewing now and what scope you are targeting.
5. Close with a role-fit line tied to the company’s product or technical challenge.
6. Practice your version aloud until it sounds natural and under 90 seconds.

Real-world example

Priya, a backend engineer from TCS, kept giving long introductions in interviews and lost panel attention. Rahul from Razorpay helped her rewrite the answer into Present-Past-Future format with one metric-heavy project example. She used that script in a Flipkart interview and the panel moved quickly into deep technical questions. The improved opening changed her confidence and she cleared the round.

What to say / email template

Sample 1 (Fresher): "I am a final-year CS graduate focused on backend development using Java and Spring Boot. During my internship, I built an API monitoring tool that reduced debugging time for the team. I am now looking for an entry-level backend role where I can contribute to production systems and continue growing in distributed architecture."

Sample 2 (1-3 years): "I am currently an SDE at Infosys, working on payment APIs and reliability improvements. Over the last year, I helped reduce critical incident volume by 30% through better retry logic and observability. I am exploring this role because it offers deeper product ownership and larger scale challenges, which align with my next growth goal."

Sample 3 (Experienced): "I lead backend delivery for checkout services at a fintech team, with focus on scalability and release quality. Recently, I drove a migration that improved p95 latency by 22% and reduced rollback frequency. I am now looking for a role where I can combine architecture leadership with hands-on execution in a high-growth product environment."

Mistakes to avoid

• Starting from school history and spending 3+ minutes before role relevance.
• Using generic adjectives like "hardworking" without proof.
• Not tailoring the answer to the company or position.
• Memorizing a robotic script and sounding unnatural.

If your intro exceeds 90 seconds, trim it.