Most people fail interviews before they walk in. Not because they lack skills, but because they treat the meeting as a test of memory instead of a conversation with evidence. Good job interview preparation is not about cramming clever answers the night before. It is about building a small set of true stories you can pull out on demand, and knowing your own resume cold.

Here is the uncomfortable truth about Indian hiring rounds: the interviewer has often read your CV for the first time as you sit down. The first question exists to buy them a minute to skim. That question is almost always the same, and almost everyone gets it wrong.

Job interview preparation starts with “Tell me about yourself”

This is not an invitation to recite your biography from birth. It is a 60 to 90 second pitch. Structure it as present, past, future: what you do now, one or two things that led you here, and why this role is the logical next step. Skip your school, your hometown, and your family unless it is directly relevant.

A weak answer: “I am from Pune, I did my B.Com from Fergusson, I like cricket, I am a hardworking person.” A strong one: “I am a data analyst with two years at a logistics firm, where I built the weekly delivery-performance dashboards the ops team runs on. Before that I taught myself SQL and Power BI on the job. I am here because this role moves that same skill into a product team, which is where I want to grow.” Every sentence there is checkable, and every one invites a follow-up you actually want.

The questions you will almost certainly face

Prepare honest, specific answers for these. They come up in some form in most interviews across IT, banking, sales, and support roles in India.

  • Why do you want to work here? Do the homework. Name something real about the company, a product, a market they operate in, a recent expansion. “It is a reputed company” tells them you did zero research.
  • Why are you leaving your current job? Never trash your employer or manager. Frame it forward: you want a larger scope, a different domain, better technical depth. Bitterness here is a red flag that follows you.
  • What are your strengths? Pick two, and attach a story to each. “Strong communication” means nothing on its own; “I ran the daily standup and translated client requirements for the dev team” proves it.
  • What is your biggest weakness? Do not run the tired “I am a perfectionist” line, interviewers hear it ten times a week. Name a genuine, non-fatal gap and show what you are doing about it: “My documentation used to lag, so I now block 30 minutes every Friday to update it.”
  • Where do you see yourself in five years? Show ambition tied to the role, not a plan to leave. Growing into a senior or lead position in the same track is a safe, true answer for most.

Use STAR for behavioural questions

When you hear “Tell me about a time when…”, reach for STAR: Situation, Task, Action, Result. It stops you from rambling and forces a clean arc.

Say the prompt is “Tell me about a time you handled a conflict in a team.” Situation: two developers disagreed on an approach and the sprint stalled. Task: you had to unblock it without a manager. Action: you set up a 20-minute call, laid out both options against the deadline, and pushed for the one that shipped faster. Result: the feature went out on time and the two kept working together fine. Thirty seconds, concrete, and it shows judgement instead of claiming it.

Build three or four of these stories before any interview: a conflict, a failure or mistake, a time you led something, a time you solved a hard problem. The same four stories, reshaped, answer a dozen different behavioural questions.

Technical and role-specific rounds

For a software role, expect DSA or a live coding round; practise on paper and out loud, because explaining your thinking counts as much as the answer. For a data role, expect SQL joins and a case question. For sales, expect a mock pitch or a “sell me this pen” variant. For any role, expect them to drill into a line on your resume, so re-read your own CV the night before and be ready to defend every single claim on it.

If you do not know something, say so cleanly and reason out loud toward it. “I have not used that specific tool, but it is similar to X, and I would approach it like this.” Faking knowledge is worse than admitting a gap; the moment they catch a bluff, they doubt everything else you said.

Do the research most candidates skip

An hour of homework separates you from the pack. Read the company’s website, its products, and its recent news. Look up the people interviewing you if their names are on the invite. Re-read the job description and map your experience to each requirement it lists, so that when they probe a skill, you already have the example ready. For a listed company, a glance at what it actually sells beats a vague “I admire your growth.”

Prepare the boring logistics too, because they sink more interviews than people admit. For an in-person round, know the exact location and travel time, and reach 15 minutes early. For a video call, test your camera, mic, and internet beforehand, sit somewhere quiet with a plain background, and keep a printed copy of your resume within reach. A frozen screen and a barking dog in the background undo a lot of good preparation. Carry hard copies of your resume and, where relevant, your certificates and ID, since Indian interviews often ask for them at the desk.

The end of the interview, and after

When they ask “Do you have any questions for us?”, always have two or three ready. Silence here reads as disinterest. Ask about the team structure, what success looks like in the first six months, or how the role has changed recently. Do not open with salary and leave in the first round; that conversation belongs once there is genuine interest on both sides.

Handle salary honestly when it comes. Know your market rate, give a researched range rather than a single rigid number, and be straight about your current pay if asked, because a fabricated figure can unravel during background verification. Dress one notch above the role’s daily norm, join a video call five minutes early on a stable connection, and keep your phone on silent.

Afterwards, a short, polite thank-you email is fine and quietly separates you from most candidates. If you are still building the experience these questions probe, the fix is the work itself, and knowing which skills Indian employers actually want tells you where to point that effort.