HR Round Questions at Indian Product Companies (Freshers)

A student of mine cleared three technical rounds, then said "I am not sure" about relocation, and the offer went to someone else. The HR round at an Indian product company is not a formality. It is a behavioral interview that decides whether you actually get the offer, and freshers who prepped for TCS-style HR questions keep losing it.

Prepare for the HR round at an Indian product company as a behavioral interview, not a formality. Expect "tell me about a time" questions with follow-up pressure, research the company's real details, and keep salary expectations flexible — product companies leave more room to move than services giants.

• First, treat the HR round as a behavioral interview, not a formality.
• Then, expect "tell me about a time" questions with follow-up pressure.
• Finally, research the company's real details and keep salary expectations flexible — product companies leave more room to move than services giants.

Why is HR at a product company a different interview?

The product-company HR round checks whether you will join, stay, and not become an onboarding problem, not your technical skill, so it carries real decision weight. The interviewer is not asking if you can code. They already know you can. They are checking if you are someone they can work with for the next few years.

At a services company like TCS or Infosys, the HR round is largely a formalities check: your location preference, your bond, whether you are willing to do shift work. At a product company, the questions are behavioral. They ask "tell me about a time you disagreed with a teammate" and then push with follow-ups like "what did you personally do?" and "what happened next?"

Product-company prep differs from services prep because services guides tell you what documents to carry, whereas product-company prep means practising your stories until the follow-up questions cannot shake them.

What is the four-stage flow and where does HR sit?

The standard IT fresher flow is initial HR screening, technical assessment, technical interview, and final HR round, so the final HR is your last gate before the offer.

• First, the initial screening is a quick phone call.
• Then, the technical assessment filters who moves forward.
• Next, the technical interview proves your skills.
• Finally, the final HR round decides if you actually get the offer.

The four stages of a typical IT fresher interview: initial screening, technical assessment, technical interview, final HR round.

1. Initial HR screening

   A 15-minute call checking your basics: availability, location preference, salary expectation range. This is a filter, not a decision.

2. Technical assessment

   A coding test or take-home assignment. This is where most candidates get filtered out.

3. Technical interview

   Live problem-solving, data structures, algorithms. This proves you can do the job.

4. Final HR round

   A behavioral interview that decides the offer. This is the gate you are preparing for right now.

Some companies merge stages. Some product companies merge technical and HR into a final chat with a hiring manager. For example, at a startup, the last round might be a 30-minute call where the manager asks both a coding question and a behavioral one. The trend is clear: product companies and modern IT firms are giving HR questions more weight, not less.

You can also fail at this final stage even after your technical rounds went well. The HR round is a real filter, not a rubber stamp.

How do you prepare 'Tell Me About Yourself' and 'Why This Company'?

Keep "tell me about yourself" under 90 seconds and end on why this specific role interests you, and name a real detail about the company — not generic praise — for "why join us". Your self-intro is the first impression. If you ramble for three minutes, the interviewer starts mentally switching off.

The formula is simple:

• Who you are now: your degree, your skills, what you are currently learning.
• One proof point: a project, an internship, a paper, a hackathon.
• Why you are here: why this role at this company interests you specifically.

For the "why this company" question, generic answers like "great culture" or "good growth" do nothing. Research one real detail: a product they launched, a tech blog they publish, a recent funding round, an open-source contribution. Name that detail. It shows you did your homework (source).

The weakness question is where most freshers trip. The answer should be a real minor gap paired with a fix already in progress. Say "I struggle with public speaking, so I am presenting at my college tech club every month" — not "I am a perfectionist." Say the real gap and the fix. The scripted line is easy to spot.

How do you answer behavioral questions with STAR follow-ups in mind?

For "tell me about a time" questions, build a STAR answer, Situation in two sentences, every Action in "I", Result with a number, and expect follow-ups like "what did you personally do?" and "what happened next?" STAR stands for Situation, Task, Action, Result. It is the structure that keeps your answer tight and complete.

The common failure mode is the reverse: Situation takes half the answer, Action is full of "we", and Result has no number. Here is a weak answer to hear the difference. "Our group project was in trouble because one member left. We managed to finish the module. It went well." Now the same story rewritten strong with I-actions and a number.

"Our four-member college project lost one member in week three. I took over the database module and wrote the schema myself. We delivered the final demo on time and I fixed 12 bugs during testing." The first version is forgettable. The second one shows you and a number. Here is the shape a strong answer takes:

The follow-up pressure is the real test. Here is how a good exchange sounds. Interviewer: What did you personally do? You: I wrote the sorting logic myself and debugged the edge cases. Interviewer: What happened next? You: We shipped on time and the code review passed without changes. That is the depth the interviewer wants.

Stopping at the first action is weak because the interviewer wants to see you think through the consequences. Now hear the weak version. Interviewer: Your teammate missed a deadline. You: I would inform my manager. Interviewer: And then what? You: I don't know. The first version survives follow-ups. The second collapses. Interviewers also ask "what would you have done differently?" to check for reflection (source). Your story needs to survive all three.

In Indian managerial rounds, answering a scenario question with "I would inform my manager" and stopping is weak. Show the full expansion in dialogue. Interviewer: Your teammate has broken the build 20 minutes before release. You: I would inform my manager. Interviewer: And then what?

You: I gather the facts: which commit broke it and who owns that code. Then I propose a rollback or a quick fix. Finally I follow up after the release to see if the issue stayed resolved. The interviewer wants to see that you can think beyond the first action (source).

Why can you fail after clearing the technical round?

You can fail the HR round even after clearing technical — seeming unwilling to relocate or being evasive about other offers are common traps. Every round before HR is about your ability. The HR round is about your availability and your judgment. Both can sink an otherwise perfect application.

Say the interviewer asks if you can relocate to Bengaluru and you answer "I am not sure, let me think about it." That is a real situation. The interviewer hears "this person may decline the offer later." That hesitation is enough to move to the next candidate.

The other common trap is being evasive about other offers. If you have an offer from another company, say so clearly. Being vague sounds like you are hiding something. The interviewer is not trying to trap you; they want to know your timeline and your seriousness about this role (source).

The fix is simple: decide your boundaries before the interview. Which cities can you work in? What is the minimum salary you will accept? What is your joining timeline? If you know the answers in advance, you never sound evasive, only prepared.

How do you discuss salary with room to move?

Product companies and startups leave more salary room than services giants, whose bands are fixed by track, so research the band, give a range, and delay a hard number. TCS publicly separates Ninja, Digital and Prime packages, so saying "I have no number" reads as evasive; HR panels check whether you did homework, not for an exact match (source).

When the interviewer asks for your expectation, give a range, not a single number. A range signals flexibility. Then anchor that range in research: "Based on what I have seen on AmbitionBox and Glassdoor, I am looking at 4.5 to 6 lakhs per annum." The range is honest. The research shows you are serious. Understand the structure behind your number. At an Indian product company, the CTC is split into base salary and variable pay.

At product companies variable is typically 10-20% of CTC. At some services firms it can be 30-40%. CTC is not take-home. Your take-home is base minus taxes and provident fund. A realistic fresher band at a mid-tier product company is roughly 4-8 LPA, based on AmbitionBox/Glassdoor postings I checked on [date]. At Zoho it tends to be 3-4.5 LPA, at Razorpay 10-14 LPA, also per those listings. The room to move is mainly in base salary, not variable pay.

Do not say "I have no number, whatever you think is fair." That answer works in a services interview where the band is fixed. At a product company, it reads as laziness. The interviewer is not expecting you to name the exact number they are offering. They want proof you thought about it (source).

Start with a negotiating bottom line before the interview. Keep the conversation collaborative, not adversarial. The HR person wants you to accept the offer. Help them get there.

What six mistakes sink freshers and how do you avoid them?

Biggest mistakes include reusing one story for every question, letting the Situation drag on, using "we" instead of "I", and inventing perfect stories that collapse under follow-up pressure. Each one is avoidable with preparation.

Each mistake has the same root: not preparing real stories. If your answer is honest, the follow-up questions only add detail. If it is invented, the first "what went wrong?" exposes it.

Spend time before the interview writing down 4-5 real situations from your college projects, internships, or part-time work. Practice each one aloud for 60-90 seconds. Time yourself. Record yourself. The repetition makes the answer automatic, and the follow-ups become easy because you are telling the truth.

For more context on where HR fits in the overall job search, see our guide on the cracking the coding interview in India.

What is your next step?

Take one STAR story you already have, rewrite it with every Action in "I" and a numbered Result, then practice aloud for 60-90 seconds, and use mock-mate.com/mock-interview/behavioral for a follow-up simulation. Do this today, not the night before. The HR round rewards preparation, and the person who prepared their stories will always sound more honest than the person who invented them on the spot.

If you are still in the earlier stages, our guide on cracking the coding interview in India covers the technical side. When you reach the HR round, you will be ready for what comes next.