A job interview is a skill, not a talent.
The candidates who consistently perform well in interviews are not necessarily the most qualified people in the room -- they are the ones who have prepared most thoroughly.
Understanding what interviewers are actually evaluating, having structured, evidence-backed answers ready, and knowing how to navigate salary conversations are learnable skills that make a measurable difference in offer rates.
This guide gives you a comprehensive interview preparation framework covering every stage: before, during, and after.
Whether you are preparing for your first job or a senior leadership role, these principles apply.
๐ Table of Contents
Understanding interview types
Different interview formats require different preparation strategies.
The most common types in India: HR screening (initial call to verify basics, culture fit, salary expectations), technical interview (coding, system design, or domain knowledge assessment depending on the role), behavioural interview (structured questions probing how you have handled past situations), case interview (used in consulting, analytics, and strategy roles -- requires structured problem-solving), and panel interview (facing multiple interviewers simultaneously, common at larger companies).
Many processes include multiple rounds combining several of these formats.
The sequence at a typical Indian tech product company: online assessment or assignment, technical interview (1-2 rounds), system design (for senior roles), and HR/behavioural round.
Knowing what type of interview is coming lets you direct your preparation appropriately rather than preparing generically.
Research and pre-interview preparation
Thorough company research is the single most differentiating preparation activity most candidates skip.
Interviewers consistently rate candidates who demonstrate genuine knowledge of the company, its products, and its challenges as more impressive than those who clearly researched only the night before.
Spend at least 2 to 3 hours on company research for any serious interview.
What to research: the company business model, revenue model, and main products; recent news (funding rounds, product launches, executive changes, press coverage); the specific team you would be joining and its work; the company culture from Glassdoor and LinkedIn posts; and the interviewer LinkedIn profile if known.
Prepare 3 to 4 specific observations about the company that you can weave naturally into conversations -- a product improvement suggestion, a question about a specific strategic decision, or a connection between your background and a current company challenge.
Answering behavioural questions: STAR method
Behavioural questions ask you to provide specific examples from your past experience: "Tell me about a time you managed a difficult stakeholder" or "Describe a situation where you had to meet a tight deadline under pressure." The STAR method (Situation, Task, Action, Result) gives you a structure that produces concise, compelling answers.
Situation: Set the brief context.
What was the scenario? Keep this short -- one to two sentences.
Task: What specifically was your responsibility in this situation? Action: What specific steps did you take? This is the most important part -- be specific about what YOU did, not what the team did.
Result: What was the measurable outcome? Quantify wherever possible.
Prepare 8 to 10 strong STAR stories from your experience covering: leadership, conflict resolution, working under pressure, failure and recovery, initiative, cross-functional collaboration, data-driven decision making, and a key achievement.
Common interview questions with frameworks
"Tell me about yourself" is not an invitation for your life story.
A strong answer follows the formula: current role and key responsibilities (2-3 sentences), your most relevant achievement or expertise, and a brief statement of what you are looking for.
Keep it under 2 minutes.
"Why do you want to work here?" requires specific research.
The answer should reference something specific about the company -- a product you use and value, a mission you connect with, a technology challenge that aligns with your skills -- not generic statements about culture or growth.
"What is your greatest weakness?" is best answered with a genuine area of development (not a disguised strength) paired with specific steps you are taking to address it.
"Why are you leaving your current job?" should always be framed positively -- pull factors toward the new opportunity rather than push factors away from the current one.
Never criticise your current employer in an interview.
Technical interview preparation
For software engineering roles, technical interviews typically cover data structures and algorithms (DSA), system design (for senior roles), and sometimes a take-home assignment.
DSA preparation: solve 50 to 80 LeetCode Easy problems and 30 to 50 Medium problems.
Focus on the most commonly appearing patterns: arrays and hashing, two pointers, sliding window, binary search, trees and graphs, dynamic programming basics.
The NeetCode 150 list is an excellent curated preparation resource.
For system design: study common architectures (load balancers, caches, CDNs, databases -- SQL vs NoSQL, message queues, microservices).
Practice designing systems like URL shorteners, social media feeds, and ride-hailing apps.
For data roles, expect SQL queries, Python/Pandas data manipulation exercises, and statistical reasoning questions.
For non-tech roles (marketing, finance, operations), prepare specific examples of how you have used data and tools in your past work, and be ready to do a short analytical exercise in the interview.
Communication and body language
In face-to-face or video interviews, how you say things matters as much as what you say.
Confident eye contact, an upright posture, and a measured speaking pace all communicate competence and credibility.
The most common communication mistakes in Indian interviews: speaking too quickly when nervous (consciously slow down), excessive use of filler words like "basically" and "you know" (practice eliminating them), and giving very long, meandering answers rather than structured, concise ones.
For video interviews: ensure your background is clean and professional, your face is well-lit from the front rather than backlit, your audio is clear, and you are looking at the camera rather than the screen image of the interviewer (looking at the camera simulates eye contact).
Log in 5 to 10 minutes early to test audio and video.
Silence your phone and close irrelevant tabs and notifications.
Dress professionally -- video interviews are formal meetings, not casual calls.
Questions to ask the interviewer
The questions you ask at the end of an interview signal your genuine interest, your preparation, and your professional maturity.
"Do you have any questions for us?" is not a formality -- it is an opportunity.
Good questions: "What does success look like in this role after 6 months?", "What is the biggest challenge the team is currently working through?", "How would you describe the culture on the team?", and "What do you personally find most exciting about working here?"
Avoid questions that are easily answered by a basic Google search (it signals poor preparation), questions focused purely on your benefits and perks (save salary, leave, and WFH policy questions for after an offer), and aggressive questions that put the interviewer on the defensive.
Aim for 2 to 3 thoughtful questions.
Asking nothing signals disinterest.
Asking too many long questions signals poor time awareness.
Salary negotiation in the interview process
Salary negotiation is most effective after you have an offer, but the groundwork is laid during the interview.
When HR asks for your "current CTC" or "expected CTC" early in the process, you are being asked to set an anchor.
Know your market rate before any conversation (LinkedIn Salary, Glassdoor, AmbitionBox) and give an informed range based on the role and company rather than just stating your current salary plus a percentage.
When an offer comes, express genuine enthusiasm for the opportunity before negotiating -- negotiating from a position of clear interest is more effective than a purely transactional approach.
Come with a specific counter-offer backed by evidence: your market research, your relevant skills, and any competing offers if you have them.
Most Indian companies expect negotiation and make initial offers below their maximum budget.
Even a 10 to 15% improvement on an initial offer compounds significantly over a career.
The worst-case outcome of a reasonable, professional counter-offer is that the employer holds their position -- they do not withdraw offers.
Frequently Asked Questions
For a significant role, plan 5 to 10 hours of preparation: 2 to 3 hours on company research, 2 to 3 hours rehearsing STAR answers, and 2 to 4 hours on role-specific technical preparation. For senior roles or at competitive companies, 2 to 4 weeks of structured preparation is appropriate.
Say so honestly rather than bluffing. "That is a great question -- I do not have the specific answer at hand, but my approach to it would be X" is far better than a confident but wrong answer. Interviewers value intellectual honesty and problem-solving process over perfect recall.
You are not legally obligated to reveal your current salary in most Indian states, though some companies still ask. Giving a range based on market rate rather than your current salary protects you from being anchored below market. If pressed, you can say "I am targeting Rs X based on my market research for this role and my experience level."
Case interviews are common at consulting, analytics, and strategy firms. Practice case frameworks (profitability, market entry, pricing) using Case in Point or CaseCoach resources. Practise structuring your thinking out loud -- interviewers evaluate the quality of your reasoning process as much as the final answer. Aim for 20 to 30 mock cases before a serious case interview.
Send a brief thank-you email within 24 hours to your primary interviewer, referencing something specific from the conversation. If you do not hear within the stated timeline, follow up once politely by email. Regardless of outcome, note what questions you struggled with and prepare better answers for next time. Every interview is preparation for the next one.
