'Walk me through your resume' sounds simple: yet it is the question where most Indian candidates lose the interview before it really begins. This guide shows you the exact structure, what to emphasise, and what to skip, so your answer sounds confident and strategic rather than a nervous bullet-point recitation.
Interviewers are not asking you to read your resume aloud. They want to see three things: how you tell your own story, whether you can prioritise what matters, and if your trajectory makes logical sense for this role.
- It is a calibration question: interviewers use it to anchor the rest of the conversation
- They are listening for self-awareness: do you know what makes you a strong candidate?
- Your energy and confidence in this answer sets the tone for everything that follows
- A muddled answer signals that you may also muddled in your actual work
- A sharp answer makes every follow-up question feel like an invitation, not a test
The most effective structure is PPF: start with where you are now, briefly explain how you got here, then connect to why this role is the logical next step.
- Present (30%): your current role, team size, what you build or own right now
- Past (40%): 2–3 milestones that show a clear progression: not every job
- Future (30%): what you want to build next and why this company is the right place
- Aim for 90–120 seconds: long enough to be substantive, short enough to invite questions
- End with a sentence that connects your trajectory to the specific role
Here is a real answer using the PPF framework for an SDE-2 applying at a product company:
- Present: 'I am currently a backend engineer at a fintech startup where I own the payments reconciliation pipeline: it processes about ₹200 crore daily.'
- Past: 'I joined as a fresher from IIT Roorkee, spent the first year on core APIs, then moved to payments after our system had a major downtime: I led the redesign that brought p99 latency from 800ms to 120ms.'
- Future: 'I want to work on larger-scale distributed systems. I have been building on microservices, but I have never operated at 10X the load your platform sees: that is what draws me here.'
- Notice: three roles collapsed to two turning points, no dates recited, ends with genuine motivation
If you have no full-time work experience, your resume walk covers academics, projects, and internships: but the logic is the same.
- Open with your degree and specialisation, not your college name
- Highlight the project that is most relevant to the role: one sentence on the problem, one on your contribution, one on the outcome
- If you have an internship, treat it as your 'present' even if it ended months ago
- End with what you want to learn/build in your first year: shows intent
- Avoid: listing every subject you studied, mentioning your percentage unprompted
These are the most common errors, seen repeatedly across thousands of Indian interview responses.
- Reading dates and company names in sequence: sounds like a newsreader, not a professional
- Starting with your school name: no one cares about Class 10 board results
- Using passive voice ('I was part of a team that'): own your contributions
- Going over 3 minutes: you have lost them
- Ending without a bridge to the role: 'So that is my background' is a dead stop