What you will learn
- Build a 60-90 second "Tell me about yourself" answer using the Present-Past-Future structure
- Adapt the same structure for different company types (startup vs. big tech vs. service company)
- Avoid the 5 most common mistakes Indian CS students make in this answer
Why this matters
"Tell me about yourself" is the first question in 90%+ of interviews. A rambling, unfocused answer in the first 90 seconds sets a negative tone for the entire interview. A structured answer does three things: it shows communication skills, it guides the interviewer toward your strengths, and it sets up follow-up questions you are prepared for.
The Present-Past-Future structure
This is not a memorized speech. It is a 3-part framework you fill in differently for each interview.
Part 1: Present (15-20 seconds)
What you are doing right now. Lead with your most relevant current identity.
"I'm a final-year CS student at NIT Trichy, currently building a RAG-based document search tool as my capstone project and interning part-time at a fintech startup where I work on their payments API."
Part 2: Past (20-30 seconds)
One or two experiences that are relevant to this specific role. Do not recite your entire resume.
"Last summer I interned at Razorpay on the merchant onboarding team, where I built an internal tool that reduced KYC verification time by 35%. Before that, I got into backend development through a full-stack project — a multi-tenant task management app — which taught me how to think about database design and API contracts."
Part 3: Future (15-20 seconds)
Why you are here, specifically. Connect your past to this company and role.
"I'm drawn to [Company] because your search infrastructure team works on the kind of retrieval problems I've been exploring in my capstone. I want to go deeper on distributed systems and work at a scale where design decisions actually matter."
Adapting for different company types
For startups (Razorpay, CRED, Zerodha)
Emphasize: breadth, ownership, shipping speed, willingness to wear multiple hats.
"...I like small teams where I can own a feature end-to-end. At my internship, I went from Figma to production in two weeks."
For big tech (Google, Microsoft, Amazon India)
Emphasize: scale, systems thinking, specific technical depth.
"...I'm interested in building systems that handle millions of requests. My capstone project pushed me to think about caching and indexing strategies at scale."
For service/consulting (TCS Digital, Infosys Power Programmer)
Emphasize: adaptability, learning speed, breadth of tech exposure.
"...I've worked across the stack — React frontends, Python backends, and basic DevOps. I pick up new technologies fast, which I showed when I learned Go in two weeks for a side project."
The 5 mistakes to avoid
1. Starting with "I'm a passionate developer..."
Everyone says this. It communicates nothing. Start with a concrete fact about what you are doing right now.
2. Reciting your resume line by line
The interviewer has your resume. They want a narrative, not a reading. Pick 1-2 highlights that connect to the role.
3. Going over 90 seconds
Practice with a timer. If you hit 2 minutes, you are rambling. The interviewer's eyes have glazed over.
4. Not connecting to the specific company
"I want to work at a good company" is generic. Name something specific about the company: a product, a team, a tech stack choice, a blog post.
5. Ending without energy
Do not trail off with "...so yeah, that's about it." End with a clear, forward-looking statement: "I'm excited about the systems engineering challenges on your team and I'd love to dig into the details."
Practice template
Fill in these blanks and practice aloud 3 times:
[PRESENT] I'm a [year] CS student at [college]. Right now I'm
[most relevant current activity — project, internship, or research].
[PAST] Previously, I [one relevant experience + specific result].
That's where I got deep into [skill/area relevant to this role].
[FUTURE] I'm interviewing at [Company] because [specific reason
tied to the role]. I want to [growth goal that aligns with the
team's work].
Time yourself. Aim for 60-90 seconds.
Quick quiz
Q: You are interviewing for a backend role at a fintech startup. Which "Past" section is stronger?
How to explain it in an interview
"When asked 'tell me about yourself,' I use a Present-Past-Future structure: what I'm working on now, one or two relevant past experiences with specific outcomes, and why this specific role excites me. I keep it under 90 seconds and tailor it to the company — I'd never give the same answer to a startup and a big tech company."