Ask most candidates what the HR round is for and they will say it is a formality, or that it is about culture fit, or that HR is checking whether you are a nice person. None of that is quite right, and the misunderstanding is expensive: people who have already cleared the hard technical rounds lose offers here regularly, usually without ever being told why.
An HR round is four assessments wearing the costume of a conversation:
- Will you accept and join? Companies count offer-to-join ratios. A candidate who accepts and ghosts costs the recruiter a filled requisition and two months.
- Will you stay? Attrition inside twelve months is expensive and visible.
- Is anything going to blow up in background verification? Dates, titles, the relieving letter, the gap.
- Can you communicate with people who are not in your function? For most roles this is a genuine job requirement, not a niceness test.
Every question below is one of those four in disguise. Once you can see which, the answers stop being guesswork.
"Tell me about yourself"
The most-asked and most-wasted question in Indian interviewing. The failure mode is autobiography: born in Mysuru, schooling at St. Joseph's, then B.E. from VTU with 8.1 CGPA, then joined Infosys as a systems engineer, then...
The interviewer stopped listening at "schooling". This question is a request for a ninety-second professional summary aimed at this role. Structure that works:
I'm a backend developer, three years in, currently at a logistics startup in Bengaluru where I own the shipment-tracking services — Java and Spring Boot, about 40k requests a day. Before that I was at Wipro for a year on a banking client, which is where I learnt to work in a regulated codebase. I'm looking to move because the platform work I enjoy is now maintenance rather than building, and this role is squarely a build role.
Present, past, then why you are here. It answers the question and hands the interviewer their next three questions, all on your terms.
"Why do you want to leave your current company?"
This is assessment 2 — will you stay — and it is the question people most often answer honestly and badly.
The rule is not "never say anything negative". The rule is that whatever you name as the reason must be something this new role visibly fixes. If you say your manager is difficult, the interviewer's next thought is that managers are difficult everywhere, so you will leave again. If you say the work has stopped growing and the role in front of you is a step up, you have made leaving a consequence of the job rather than of you.
Works:
I've been on the same product for two and a half years and the scope has narrowed — most of what I do now is keeping it running. I want to be building again, and ideally closer to the business side, which is what this role looks like.
Does not work, in ascending order of damage: "the pay is low" (fine as a reason, weak as an answer — it says you will leave for the next raise), "my manager doesn't support me" (unverifiable, and reads as a pattern), "there's too much politics" (says nothing about the company, quite a lot about you).
If you are leaving something genuinely bad — a company that stopped paying salaries on time, a role that turned out to be nothing like the posting — say it plainly and without adjectives. Facts land as facts. It is the editorialising that reads as a warning.
"Where do you see yourself in five years?"
Nobody expects a plan. What is being checked is whether your stated direction is compatible with the job they are filling. If you say you want to start your own company in two years, the honest interviewer stops considering you for a role that needs three years of continuity — and they are right to.
Answer with a direction, not a title:
In five years I'd like to be the person who owns a system end to end — architecture, not just implementation — and to have mentored a couple of juniors. Whether that comes with a title I'm not too fussed about.
Avoid naming a title above the one you are interviewing for on a timeline shorter than the company can plausibly deliver. "Engineering Manager in two years" told to a company where that takes six is not ambition, it is a scheduled resignation.
"What is your expected CTC?"
The one that costs the most money, and it usually arrives in the first ten minutes of the first call, before you know the band, the components or the role's real scope.
The full treatment is in negotiating salary in India. The short version for this round:
First, try to get their number. Politely, once:
I'd rather understand the role fully before putting a number on it. Do you have a budgeted range for this position?
Often you get it — most Indian recruiters have a band and will share it, because a mismatch wastes their time too.
If pressed, give a range and anchor it to the market, not to your current salary:
Based on what I've seen for this scope in Bengaluru, I'd be looking at 18–22 lakhs fixed. If the role turns out to be broader than the posting, I'd revisit that.
Do not lie about your current CTC. Background verification and, increasingly, your Form 16 or payslips will surface it. A candidate caught inflating their current salary loses the offer, and reasonably so.
Do not say "as per company standards". It reads as agreeable and gets you the bottom of the band. You are not being generous; you are being budgeted.
"What are your strengths and weaknesses?"
The strengths half is easy and low-value — name two that the job needs and attach one example each.
The weakness half is a trap with three standard failures: the humblebrag ("I'm a perfectionist", "I work too hard"), which insults the interviewer; the disqualifier ("I'm bad at deadlines"), which is honest and fatal; and the deflection ("I can't think of any"), which reads as no self-awareness at all.
What works is a real, non-central weakness plus the specific thing you do about it:
I'm slow at saying no. Early on I'd take on three parallel things and deliver all of them late. What I do now is keep a visible list with my manager and make the trade-off explicit — if something new comes in, we agree together what moves. It's still effort rather than instinct.
That is a genuine weakness, it does not undermine the core of the job, and the second half shows you have a system rather than an apology.
"Why should we hire you?"
Rarely asked in that blunt form these days, but the underlying question runs through everything. The answer is not enthusiasm. It is the two or three things about your background that map to the hardest part of the role.
You're building the payments integration from scratch and you've said reconciliation is the painful part. That's the exact thing I spent last year on — I've dealt with the settlement mismatches and the reversal edge cases already, so I'd be useful from week one rather than month three.
To say something like that you have to know what the hardest part of the role is, which means asking. Which is the next section.
"Do you have any questions for us?"
Saying no is a genuine mistake — it reads as no interest, and it wastes the one part of the interview you control. It also happens to be the point where you learn whether you want this job.
There is a full guide to this at questions to ask the interviewer. If you remember one thing: ask about the work, not about the perks.
The parts of this round that are administrative
Somewhere near the end an HR round becomes logistics, and these answers matter more than they sound:
Notice period. Give the contractual number and whether a buyout is possible, accurately. Overpromising a joining date you cannot hit is the single most common way a candidate turns a good offer into a bad start. Notice periods and relieving letters covers what is actually enforceable.
Other offers in hand. Being in another process is normal and saying so is fine — it is mild leverage and it moves timelines. Inventing an offer you do not have is a bluff that gets called roughly as often as you would expect.
Gaps and short stints. Answer in one flat sentence and stop. "I took eight months off for my father's treatment and started applying in March." The length of the explanation is what makes a gap look like a problem, not the gap.
Documents. Payslips, Form 16, relieving letters, education certificates. Know which of these you can actually produce. Discovering during BGV that your previous employer will not issue a relieving letter is a problem you want to find now, not in week three of onboarding.
Three answers that end a process quietly
You will not be told these are why. They are:
- Criticising a former employer with heat. One sentence of fact is fine. A paragraph of grievance transfers the risk to them.
- Being vague about dates or titles. It reads as something to hide, and BGV is where it gets confirmed.
- Treating the round as beneath you. The recruiter running it usually has a veto, frequently briefs the hiring manager afterwards, and remembers.
Preparation, honestly bounded
You cannot script this round, and the people who try sound scripted, which is its own failure. What is worth doing the night before is small:
- Write your ninety-second summary and say it aloud twice. Not memorised — just enough that you do not start with your birthplace.
- Have one sentence ready for leaving, and check it names something this role fixes.
- Know your number, your notice period and your dates cold.
- Have three questions written down. Bring them on paper; nobody minds.
That is about forty minutes of work and it is the difference between an HR round that confirms the offer and one that quietly loses it. If your technical rounds are still ahead of you, interview preparation that actually moves the needle covers those.