HR Round Questions in India 2026: What They Actually Want to Hear (Real Scripts That Work)

You cleared 4 technical rounds. DSA, system design, machine coding — all done. Then HR asks 'Tell me about yourself' and suddenly you're sweating more than you did during the system design round. Here's the thing nobody tells you: the HR round in India isn't a formality. It's where offers get rescinded, salaries get negotiated down, and 'cultural fit' decisions get made in 20 minutes.

Let me start with a story from a friend who works as a Senior HR at a mid-tier product company in Bangalore.

She told me: "I rejected a candidate last week who cleared all 5 technical rounds. His coding was better than our current SDE-2s. But when I asked why he's leaving his current company, he spent 8 minutes trashing his manager. That told me everything."

The HR round is not a formality. It's a filter. And in 2026, with hiring budgets tighter and companies becoming more selective, HR rounds have more weight than they did two years ago.

I've interviewed over 200 engineers in the last three years — some for hiring, some as peer interviewers, some helping friends prep. Here's what the HR round actually looks like in India in 2026, question by question, with scripts that have worked for real people.

Why the HR Round Matters More in 2026 Than Ever

Three things changed between 2023 and 2026:

1. Companies got burned by bad hires. Attrition in Indian IT hit 23% in 2023. HRs are now trained to spot flight risks, salary-only candidates, and people who'll leave in 8 months.

2. Reference checks and BGV are stricter. Everything you say in HR gets cross-verified. Lying about reason for leaving? HR calls your manager. Inflating current CTC? They check your payslip and ITR. More on this below.

3. Budget approvals need HR sign-off. Even if the tech panel wants to hire you at ₹32 LPA, HR can block it or push it down to ₹26 LPA based on your HR round performance. I've seen this happen at Razorpay, Swiggy, and even TCS Digital.

So no, "I'll wing the HR round" is not a strategy anymore.

The 15 HR Questions You WILL Be Asked (And What They Actually Mean)

Here's the brutal truth: HRs across India use the same 15-20 questions. The variation is tiny. Let me break down the real ones and what they're probing for.

Question 1: "Tell me about yourself"

What they're actually asking: Can you communicate clearly? Are you self-aware? Can you tell a coherent story about your career?

What NOT to say: Your date of birth, your father's occupation, your 10th and 12th percentages (unless you're a fresher), your hobbies.

The script that works (3-year experienced SDE):

"I'm a software engineer with 3 years of experience, currently at [Company] working on their payments platform. I started my career at Infosys after graduating from [College] in 2022, where I spent 1.5 years working on Java microservices for a US banking client. In early 2024, I switched to [Current Company] to work on more product-focused engineering — specifically, I've been owning the refund processing module that handles about ₹40 crores in transactions per month. What I enjoy most is working on systems that have real business impact, which is exactly why I was interested in this role when the recruiter reached out."

Notice the structure: present → past → why I'm here. 60-90 seconds. Specific numbers. No fluff.

Question 2: "Why are you looking to switch?"

What they're actually asking: Are you a flight risk? Will you leave us for ₹2 LPA more in 10 months? Are you running away from something?

NEVER say:

• "My manager is horrible"
• "My current company is going bankrupt" (even if true)
• "For better salary" (as the primary reason — more on this below)
• "No growth" (too vague)

The script that works:

"I've been at my current company for 2.5 years and have grown a lot — I was promoted to SDE-2 last cycle. But the roadmap for the next 18 months is mostly maintenance work on legacy systems. I'm looking for a role where I can work on greenfield projects at scale, which is why your platform engineering team caught my attention. Compensation is a factor, but the primary reason is the technical scope."

This answer does three things: shows loyalty (2.5 years), shows growth (promotion), gives a legitimate push reason, and hints at a pull reason (their specific team).

Question 3: "Why do you want to join our company?"

What they're actually asking: Did you even research us? Or are you just spraying resumes everywhere?

The 30-second homework: Before every HR round, know these 5 things:

• The company's main product
• Their recent news (funding, launch, acquisition — Google it)
• Their tech stack (from their engineering blog)
• The specific team you're interviewing for
• One competitor they'd compare themselves to

Script:

"Three reasons. One, I've been following your engineering blog, and the post about scaling your notification system to handle 10 million events a day was fascinating — that's the exact kind of distributed systems problem I want to work on. Two, you recently expanded into [X market], which means the engineering team will have interesting new challenges. Three, from my conversations with [recruiter name] and reading Glassdoor, the engineering culture seems to value ownership, which matches how I like to work."

HR Questions About Your Current Job and Why You're Leaving

This is where most candidates mess up. Let me go deeper.

Question 4: "What do you dislike about your current company?"

This is a trap question. HRs want to see if you'll badmouth. Don't take the bait.

Bad answer: "The management is political and promotions are based on favoritism."

Good answer: "Honestly, it's a solid company and I've learned a lot. The one thing I'd say is that as a service-based model, the project allocation sometimes doesn't align with individual learning goals. That's why I'm looking for a product company where I can go deep on one domain."

Diplomatic. Factual. Doesn't name individuals.

Question 5: "What is your current CTC and expected CTC?"

This question deserves its own article (and we have one — benchmark your salary on CareerLens before any HR round). But quickly:

Rules:

1. Never lie about current CTC. BGV will catch it.
2. State fixed + variable + ESOPs separately, not just total.
3. For expected, give a range, not a single number.
4. Justify your expectation with market data, not personal needs.

Script:

"My current fixed is ₹18 LPA, with ₹2 LPA variable, so total CTC is ₹20 LPA. Based on the role scope and current market rates for SDE-2s with my experience at product companies, I'm looking at ₹32-36 LPA fixed. Happy to discuss the structure based on what works for you."

Question 6: "If we match your current CTC, will you join?"

Trap. They're testing if you're salary-driven or genuinely interested.

Script:

"I'm looking for a meaningful jump because I'm trading job security for a switch. If the compensation doesn't move significantly, it's hard to justify the move. But I'm open to a reasonable discussion if the role and growth path are strong."

Behavioral and Situational HR Questions

These are increasingly common at product companies and startups like Zepto, Razorpay, PhonePe, and Flipkart. If you've done practice with AI mock interviews, you've probably seen these.

Question 7: "Tell me about a time you had a conflict with a teammate"

Use the STAR method: Situation, Task, Action, Result.

Script:

"During a sprint last quarter, our tech lead wanted to use a NoSQL database for a new feature, but I felt a relational approach was better because the data had clear relationships and we needed transactional consistency. (Situation + Task) I didn't push back in the meeting — instead, I built a quick 2-day prototype comparing both approaches, including query performance and migration complexity. I shared the findings in a document and we had a technical discussion with the team. (Action) We ended up going with PostgreSQL, and the feature shipped on time with better performance than the NoSQL prototype. More importantly, my relationship with the tech lead got stronger because he saw I disagreed with data, not emotion." (Result)

Question 8: "Tell me about your biggest failure"

Never say "I'm a perfectionist" or any version of it. HRs will visibly cringe.

Script:

"In my first year at Infosys, I pushed a change to production on a Friday evening without proper testing because I was eager to close the ticket. It broke a reporting job that the client discovered on Monday morning. I had to come in on Sunday night to roll back and fix it. The learning was two-fold: never deploy on Fridays unless it's an emergency, and always test on staging even for 'small' changes. I built a personal pre-deployment checklist after that and shared it with my team."

Specific. Owned the mistake. Showed learning. Showed impact on others.

Question 9: "Where do you see yourself in 5 years?"

Nobody actually knows. But don't say "I don't know."

Script:

"In 5 years, I see myself as a senior engineer or tech lead, owning a critical system end-to-end. I'd like to have deep expertise in distributed systems and have mentored at least a few junior engineers. I'm not someone who's chasing management for the sake of it — I want to go deep technically first and then decide whether IC or management is the right path."

The Awkward HR Questions Nobody Prepares For

Question 10: "Are you interviewing anywhere else?"

Be honest, but strategic.

Script:

"Yes, I'm in final stages with 2 other companies — one is a fintech product company and the other is a MAANG. I wanted to be transparent so you know I may need to make a decision in the next 2-3 weeks."

This creates urgency without being arrogant.

Question 11: "Why should we hire you over other candidates?"

Script:

"I can't speak to other candidates, but what I bring is a mix of 3 years of hands-on backend work at scale, strong fundamentals in Java and distributed systems, and proven ownership — I've led two zero-to-one projects at my current company. I ramp up fast on new stacks because of my CS fundamentals, and I'm genuinely interested in your product domain."

Question 12: "Are you willing to relocate / work from office?"

In 2026, with most companies pushing 4-5 day RTO policies, this matters. Be honest. If you can't relocate, say so upfront — don't waste both parties' time.

Question 13: "What are your weaknesses?"

Don't say: "I work too hard" / "I'm a perfectionist" / "I take on too much."

Script:

"I used to struggle with saying no to work. Early in my career, I'd take on 4-5 parallel tasks and end up delivering all of them 70% well instead of 2 of them 100% well. I've worked on this by having explicit priority conversations with my manager at the start of every sprint, but I still have to actively watch for it."

Question 14: "Do you have any questions for us?"

Always have 3-4 questions ready. Not having questions = not interested.

Good questions:

• "What does success look like for this role in the first 6 months?"
• "How is the team structured and who would I be reporting to?"
• "What are the biggest technical challenges the team is facing right now?"
• "How does performance review and promotion work here?"

Don't ask: Leave policy, work hours, WFH policy as your first question. Save those for after the offer.

Question 15: "When can you join?"

Know your notice period. If it's 90 days, say so. Mention buyout possibilities only if you're willing to do it.

Company-Specific HR Round Differences

Not all HR rounds are the same. Here's a quick comparison:

| Company Type | HR Round Duration | Focus Areas | Difficulty | |---|---|---|---| | TCS / Infosys / Wipro | 20-30 min | Communication, flexibility, bond acceptance | Low | | Capgemini / Accenture / Cognizant | 25-35 min | Project fit, relocation, CTC fit | Low-Medium | | Product MNCs (Amazon, Microsoft) | 45-60 min | Leadership principles, behavioral depth | High | | Indian Product (Flipkart, Razorpay) | 30-45 min | Culture fit, ownership stories, CTC | Medium-High | | Startups (Zepto, Blinkit, early-stage) | 30-60 min | Hustle, ownership, equity understanding | Medium-High |

HR Round at MAANG / Product Companies

Amazon's HR round is essentially the Bar Raiser interview — it's basically a full behavioral round, not casual chit-chat. Expect 5-7 STAR-method questions tied to Amazon's 16 Leadership Principles. Prep 10-12 stories from your experience that can be reused.

HR Round at Service Companies

TCS, Infosys, Wipro HR rounds are mostly filters for:

• Communication skills (will you work with US/UK clients?)
• Flexibility (will you accept any location?)
• Bond acceptance (will you sign the 2-year service agreement?)
• Salary fit (will you accept the standard package?)

Honestly, if you can speak coherent English and don't argue about location or bond, you're through.

Red Flags HRs Look For (That You Might Be Showing Without Knowing)

Based on conversations with HRs across Flipkart, Infosys, PhonePe, and Zoho:

1. Multiple short stints (less than 1 year each at 2-3 companies in a row) — be ready to explain each
2. Vague answers about why you're leaving — looks like you're hiding something
3. Trashing current employer — automatic yellow flag
4. Asking only about salary, WFH, leave policy — looks mercenary
5. Not knowing anything about the company — looks lazy
6. Overly rehearsed, robotic answers — looks fake
7. Inability to give specific examples — looks like you've exaggerated your resume
8. Lying about current CTC — guaranteed offer rescinded during BGV

If you're worried about any of these in your profile, check your ATS score on CareerLens first — many red flags start showing up in the resume itself before HR even talks to you.

How to Prepare for an HR Round in 48 Hours

Here's the exact prep plan I recommend:

Day 1 (2-3 hours):

• Research the company (product, recent news, tech blog, Glassdoor reviews)
• Write out your "Tell me about yourself" script and practice it out loud 5 times
• Write out your "Why are you leaving" script
• Prepare your CTC expectation with justification

Day 2 (2-3 hours):

• Write 6-8 STAR stories from your past projects covering: conflict, failure, success, leadership, ownership, learning
• Practice saying them out loud (not just reading)
• Prepare 4 thoughtful questions to ask
• Do one mock interview — ideally with a friend or practice with AI mock interviews to get real-time feedback

Day of interview:

• 30 minutes before: re-read your scripts
• Have a glass of water nearby
• Smile when you join the call (yes, they can tell)
• Check your lighting and audio

What to Do If the HR Round Goes Badly

If you fumbled a question, don't panic. Options:

1. Mid-interview recovery: "Sorry, let me rephrase that answer — what I actually meant was..." HRs appreciate self-correction.

2. Post-interview email: Within 24 hours, send a thank-you email that briefly addresses the question you fumbled: "I wanted to add one more point about the conflict resolution question you asked..."

3. Don't ghost: Even if you think you tanked it, respond to the recruiter's follow-up. The HR might still be in your favor.

FAQ

Q1: Is the HR round in India just a formality or can I actually get rejected?

You can absolutely get rejected, and in 2026, HR rejections have gone up significantly. I personally know engineers who cleared all technical rounds at companies like Flipkart, Walmart, and Razorpay but got rejected in HR for reasons like badmouthing current employer, being inflexible on CTC, showing lack of research about the company, or coming across as a flight risk. HRs now have genuine veto power, and in budget-tight 2026, they're using it more. Companies are also doing extensive reference checks and BGV, so lies in the HR round can lead to offers being rescinded even after you've resigned from your current job.

Q2: Should I negotiate salary in the first HR round or wait?

Share your current CTC and expected range in the first HR round when asked — that's expected. But the actual negotiation happens after you get the offer letter. In round 1, state your expectation with a reasonable range (e.g., ₹28-32 LPA fixed), and justify it with market data. Once the offer comes, you can push back on components like joining bonus, ESOPs, variable split, and base. Don't try to hard-negotiate in round 1 because you don't have leverage yet — you don't even have an offer. Focus on creating a good impression first; negotiate hard after they've decided they want you.

Q3: What if I'm asked a question I genuinely don't have a good answer to?

Three options. First, buy time: "That's a great question, let me think for a moment." Taking a 5-second pause is far better than rambling. Second, be honest about limited experience: "I haven't faced that exact situation, but a similar scenario was..." and pivot to a related story. Third, acknowledge the gap: "I don't have direct experience with that, but here's how I'd approach it if I did..." HRs respect honesty far more than fabricated answers. The one thing you should never do is make up a story, because follow-up questions will expose you quickly, and once trust is broken, the round is effectively over.

Q4: How do I handle the "Why TCS/Infosys/Wipro?" question when I'm obviously joining for the job itself?

Even for mass-recruiter companies, show you've done basic research. For TCS, mention their TCS Digital division, their work on BaNCS (banking platform), or their global presence. For Infosys, mention their work with Finacle or their Mysore training. For Wipro, mention their domain focus or specific client work. Pair this with legitimate personal reasons: "I value the structured learning path for freshers, the exposure to international clients, and the ability to work across multiple domains early in my career." You don't need to pretend it's your dream company — just show you have reasons beyond "I need a job."

Q5: Can I ask about WFH, salary structure, and perks in the HR round?

Yes, but sequence matters. In the first HR round, your questions should focus on role, team, growth, and culture — not perks. Save WFH policy, leave structure, insurance details, and salary breakdown for the HR discussion that happens after you get the verbal offer. Asking about work-from-home as your first question signals that your top priority is lifestyle, not the job itself. Once you have an offer in hand, you have full right to ask detailed questions about every component. Many companies now have a separate "offer discussion" call precisely for this.

Bottom Line

• The HR round is a real filter in 2026, not a formality — I've seen candidates lose ₹5-10 LPA or get rejected entirely after clearing all technical rounds
• Prepare 6-8 STAR stories covering conflict, failure, success, ownership, and leadership — you'll reuse them across every HR round for the next 5 years
• Never badmouth your current employer, never lie about CTC, and never ask about WFH/leave as your first question
• Research the company for 30 minutes minimum — know the product, recent news, tech stack, and one specific thing about the team
• Salary negotiation happens after the offer, not in the first HR round — state your expected range with justification and move on
• Practice out loud, not just in your head — the gap between what you think you'll say and what actually comes out is massive, which is why mock interviews on CareerLens matter

The HR round is the one interview where you have 90% control over the outcome if you prepare. Don't waste that advantage.