Interview Preparation Tips India 2026: Complete Guide for Tech Freshers to Experienced

For freshers (campus placement, targeting product companies):

• 6 months before: start DSA: arrays, strings, trees, graphs, DP. Target: 100 LeetCode Easy-Medium problems by the end of this phase
• 4 months before: add system design fundamentals (for senior roles) and CS fundamentals review (OS, DBMS, networking, OOPS). Start behavioural story bank
• 3 months before: mock interviews (1–2 per week). Apply to companies with October–November OAs
• 2 months before: company-specific preparation: Amazon LPs, Infosys patterns, Flipkart system design flavour
• 1 month before: mock interviews 3–4 times/week, reduce new problem solving, focus on speed and communication

For experienced engineers (1–5 years, job switch):

• 12 weeks out: DSA refresh (3–4 weeks on LeetCode Medium, your weakest topics), then system design (4–5 weeks)
• 6 weeks out: behavioural answers: STAR stories from your actual work experience
• 4 weeks out: company-specific prep + weekly mocks
• 2 weeks out: reduce study intensity, mock interviews, rest

Warning signs you're underprepared:

• You can solve LeetCode Medium but can't explain your approach clearly out loud
• You haven't prepared any STAR stories from your actual work
• You haven't done a single mock interview under time pressure
• You haven't researched the company you're interviewing with

Indian candidates typically over-prepare on DSA and under-prepare on the other three dimensions:

Dimension 1: Technical (DSA / Coding)

• Most candidates prepare this; the guide elsewhere in this blog covers it in depth
• Key gap: candidates solve problems silently and never practice speaking while coding
• Fix: at least 30% of your practice sessions must involve narrating your thought process out loud

Dimension 2: System Design (tested from SDE-2 / 2+ years experience)

• Most candidates underestimate how much depth is expected
• Fix: read 'Designing Data-Intensive Applications' (DDIA), then practice 10–15 system design questions
• Resources: Grokking System Design, System Design Primer on GitHub

Dimension 3: Behavioural / HR

• The most neglected dimension: Indian candidates often give generic answers ('I work hard', 'I am a team player')
• Fix: prepare 8–10 STAR stories from your real experience. Each story covers: Situation, Task, Action, Result (with numbers where possible)
• Stories you need: project failure, conflict with teammate, tight deadline, feedback received and acted on, cross-functional collaboration

Dimension 4: Company Knowledge and Cultural Fit

• Not preparing company-specific questions ('Why this company?', 'What do you know about our product?') is a red flag
• Fix: spend 2–3 hours researching the company's products, engineering blog, recent news, tech stack, and team structure before every interview

Behavioural interviews are where Indian candidates most consistently underperform relative to their technical ability.

Why Indian candidates struggle with behavioural questions:

1. Engineering education in India focuses almost entirely on technical skills: soft skills interviews are new
2. Cultural tendency toward humility makes it uncomfortable to talk about personal achievements
3. Lack of practice speaking in English under pressure
4. Generic answers: 'I worked hard and completed the project on time': no specifics

The STAR method (must use for every behavioural answer):

• Situation: brief context (1–2 sentences)
• Task: what was your specific responsibility or challenge
• Action: what YOU did (not 'we': use 'I')
• Result: quantifiable outcome where possible

8 stories every Indian candidate should prepare:

1. A project or task that failed: what went wrong and what you learned
2. A time you had a conflict or disagreement with a teammate or manager: how you resolved it
3. A time you worked under a very tight deadline: what you did differently
4. A time you received critical feedback: how you responded and what changed
5. A time you learned a new technology quickly: the situation and your approach
6. A time you made a difficult decision with incomplete information
7. A time you went above your job scope to help the team or project
8. Your proudest achievement: what made it challenging and what the impact was

Amazon Leadership Principle tips (if targeting Amazon): Amazon maps every behavioural question to one of 16 Leadership Principles. Research each LP and prepare a specific story for the 8 most commonly assessed: Customer Obsession, Bias for Action, Deliver Results, Ownership, Think Big, Invent and Simplify, Have Backbone, Earn Trust.

Solving LeetCode problems alone does not prepare you for the interview experience. Mock interviews are the single highest-ROI preparation activity for most candidates, yet most Indian candidates do fewer than 5 before their actual interviews.

Why mock interviews matter:

• The interview is not the same as LeetCode: you must speak, think, and code simultaneously
• Time pressure feels completely different in a live 45-minute round than in your bedroom
• Behavioural answers that sound fine in your head sound stilted, vague, or too long when spoken
• Receiving feedback from someone else reveals blind spots you can't see yourself

How to get mock interview practice in India:

• HireStepX voice mock interviews: AI interviewer that conducts realistic voice mock interviews with STAR evaluation, DSA questions, and coached model answers
• Pramp: free peer-to-peer mock interviews (both participants interview each other)
• Interviewing.io: anonymous mock interviews with engineers from top companies (paid for premium)
• College seniors or alumni: reach out to seniors who are already placed at product companies: most are willing to do a 45-min mock
• LinkedIn connections: engineers you know at target companies may be willing to conduct a mock in exchange for helping them on something

Mock interview schedule recommendation:

• 8–12 weeks before interviews: 1 mock/week
• 4–8 weeks before: 2 mocks/week
• Final 4 weeks: 3–4 mocks/week (including day-before-interview mocks for nerves reduction)

What to do after each mock:

• Write down every question asked and your answer
• Identify 2–3 specific things to improve (not 'be better': 'explain complexity before coding', 'don't use 'we' in STAR stories')
• Fix those specific things before the next mock

Salary negotiation is culturally unfamiliar for most Indian candidates but can add ₹2–10 LPA with a single 15-minute conversation.

The negotiation mindset shift: Most Indian engineers accept the first offer without negotiating: seeing the offer as final. Companies in India expect some negotiation at the senior level and are generally fine with it at all levels. Asking doesn't risk your offer being withdrawn.

What to say when you get an offer: 'Thank you for the offer: I'm really excited about the role and the team. I've been doing some research on the market rate for this level, and I was hoping we could discuss the compensation. Based on my experience and the research I've done, I was expecting something in the range of ₹X–Y LPA. Is there flexibility to move closer to that range?'

What to have ready:

• A competing offer (real or stated): the single most powerful negotiation tool
• Market rate data: levels.fyi has India compensation data; glassdoor.co.in; LinkedIn Salary; this blog's salary sections
• Your specific value-add: a specific skill or experience the team particularly needs

What CAN be negotiated:

• Base salary (most important; affects all future raises)
• Signing/joining bonus (one-time, doesn't affect annual raises)
• Stock (RSUs): more negotiable at product companies, especially if you have competing offers
• Work location flexibility (WFH days)

What usually CANNOT be negotiated:

• Job level/band (set by the offer, you'd need to request a re-evaluation which is rare)
• Benefits package
• Start date (usually some flexibility)