HR round interview questions — what's actually being decided in the round everyone underrates
The HR round isn't a formality after the "real" technical interview. It's where salary expectations, notice period, and offer decisions actually get made — here's what each common question is really checking.
The technical rounds get all the prep time, and the HR round gets treated as a formality you'll figure out on the spot. That's backwards. By the time you reach the HR round, the company has already decided you can do the job — this round decides whether they extend the offer, on what terms, and how fast.
"Tell me about yourself"
Almost always the opener, and most people answer it as a recited resume summary. What it's actually checking is whether you can frame your own background in a way that's relevant to this role — not a chronological list, but a short story that ends at "and that's why this role makes sense as the next step." A generic answer here sets a generic tone for the rest of the round.
"What are your salary expectations?"
The question everyone dreads and almost nobody prepares a real number for. Walking in without a researched range — based on your experience level, the role, and the company's typical band for it — puts you at the mercy of whatever number they suggest first. The honest prep here isn't a script, it's homework: know the market range for this specific role and city before you're asked, so the number you give is a real answer, not a guess made under pressure.
"Why do you want to leave your current company?"
This is checking for one thing specifically: whether you'll say something that reflects badly on you without meaning to. "My manager was terrible" is true for a lot of people and still a bad answer — it signals a pattern the interviewer can't verify and doesn't want to inherit. A better answer names what you're moving toward — growth, scope, a specific kind of work — rather than only what you're moving away from.
"What's your notice period, and can it be reduced?"
A logistics question with real weight behind it. Companies with urgent hiring needs sometimes deprioritize a strong candidate over a long notice period alone. Knowing your actual contractual notice period, and whether there's realistic room to negotiate it (buyout, partial serving), before this question comes up avoids an awkward pause that reads as unprepared.
"Do you have any other offers?"
Not a trick question, though it's often treated like one. Being vague or evasive here doesn't protect your leverage — it just makes the interviewer trust the rest of your answers a little less. A direct, brief answer ("yes, at an early stage" or "no, this is my priority process right now") reads as more confident than a dodge.
"Where do you see yourself in five years?"
The question isn't really asking for a five-year plan — almost nobody has an accurate one. It's checking whether your stated direction is even roughly compatible with what this role and company can offer. Answering with something wildly outside what the job could ever lead to (naming a completely different function or a founder title at a company that doesn't do internal transfers that way) signals a mismatch worth flagging before an offer, not after.
What's actually different about this round
The technical round is scored against a rubric — right, partially right, wrong. The HR round is scored on judgment: does this person represent themselves accurately, do their expectations match reality, will the terms actually work for both sides. That's a real evaluation, not small talk, and it deserves the same five minutes of prep you'd give any technical answer.
A quick honest note: Prepair practices the technical round — role-and-level questions with scored answers — not the HR round covered above, the group discussion, or the aptitude test some Indian hiring processes include before the technical stage. If your next hurdle is the technical interview itself, try a free session — 3 a month, no signup required to start.