HR interview questions for experienced candidates, with sample answers

"I have [four] years of experience as a [Java backend developer]. I started at [company A], where I worked on [a banking client's loan processing system] and learned Spring Boot and SQL in depth. For the last [two] years I've been at [company B], building [payment APIs] for an e-commerce platform; I now own [two microservices] and review my teammates' code. I'm looking for a role with more ownership of design decisions, which is why this position interested me."

Keep it to about a minute: where you started, what you do now, and what you want next.

"I've learned a lot at [company], but my work for the last year has been mostly maintenance on the same module. I want to work on [new product development / larger-scale systems], and this role offers that. It's a move for the kind of work, not away from my team."

Never criticise your current employer or manager, even if the criticism is fair. Talk about what you want, not what you dislike.

"That's fair to ask. I joined [company] for [a cloud migration project], but it was put on hold three months after I joined, and I've been assigned to [manual support work] since. I gave it time, and I spoke to my manager about moving to another project, but there isn't an opening. I'm looking for a place where I can stay for several years and grow, and a product team like yours is that kind of place."

Give the real reason in one or two sentences, show that you tried to fix it, and say why this move is a long-term one.

"My current CTC is [9.5] lakh per annum. Of that, [8.4] lakh is fixed and the rest is a performance bonus paid [yearly]. I'm happy to share my latest payslips when you need them."

Split fixed and variable pay, because companies compare fixed pay. Never inflate the number: the payslip check will catch it, and a caught lie usually ends the process.

"Based on the role's responsibilities and what I've seen for similar roles with [four] years of experience in [backend development], I'm looking for [12.5 to 13.5] lakh per annum. I'm flexible within that range depending on the overall package, such as the variable pay and benefits."

Give a range, not one number, and give a reason. Research the role on salary sites and with people you know in the industry before the interview, so your range has a basis.

"My current CTC is below the market for my experience, partly because my last appraisal cycle was frozen. In this role I'll be handling [system design and code reviews], which is a step up from what I do now. That said, I'm open to discussing the structure: if the fixed pay comes closer to my expectation, I'm flexible on the variable part."

Show that the number comes from the role, not from a wish, and show where you can bend.

"My notice period is [90] days. I've completed my main deliverables, and I expect my manager to release me after a handover of about [45] days. If you need me earlier, I can also look at buying out the remaining notice period, depending on the offer."

Say only what you can deliver. If your company never releases people early, say so; a missed joining date damages trust more than a long notice period.

"Yes, I have one offer from [a product company] at [12] lakh, and I'm in the final round with one more. This role is my first preference because of [the team and the domain], so I'd like to close this process if we can agree on the details."

Be honest and specific, and never invent an offer to push the number up. Companies sometimes ask for the offer letter.

"No. My reason for moving is the work I want to do, and a higher salary in my current role doesn't change that. I've already discussed with my family, and once I accept an offer, I'll join."

Mean it. Backing out after accepting an offer burns a bridge with that company, and HR teams talk to each other.

"I left [company] in [month] to care for a family member after a surgery. That's now behind us. During the last three months I've been back to full-time preparation: I completed [a Kubernetes certification] and rebuilt [a side project] to practise the newer Spring Boot version. I'm ready to start immediately."

State the reason in one line, show what you did to stay current, and end with your availability.

"[Company] closed its [India development centre] in [month], and our whole team of [40] was let go. It wasn't performance-related, and my manager has agreed to be a reference. Since then I've been interviewing selectively, because I want my next move to be a long one."

Layoffs are common and HR knows it. Say it plainly, without bitterness, and offer a reference if you can.

"Last year our [order service] slowed down badly during sales, with page loads above [six] seconds. I found that [two queries] were running without indexes and that we were calling the inventory API in a loop. After I fixed both and added caching, response times dropped to under [one] second, and we handled the next sale without an incident. My manager put me forward for the [quarterly award] for it."

Use the STAR shape: the situation, your task, what you did, and a result you can name. The STAR method guide has more examples.

"You need someone who can take ownership of [backend services] from day one. I've spent [two] years owning [payment APIs] end to end, from design to on-call support, and I've worked with the same stack you use: [Java, Spring Boot, PostgreSQL and AWS]. I also review code and help new joiners, so I can add to the team, not just to the backlog."

"We work well together. We don't always agree — last quarter I thought we should fix our test coverage before adding new features, and my manager wanted to keep the release date. We agreed to ship on time and spend the next sprint on tests, which worked out. I value that we can disagree and still decide quickly."

Show a real disagreement handled well. "We've never disagreed" sounds rehearsed.

"Yes, I'm open to relocating to [Pune or Bengaluru]. For shifts, I can work [UK or US-overlap hours] for client calls; I've done that for the last year with my current client. If a role needs a permanent night shift, I'd like to understand the rotation before committing."

Agree to what you can sustain, and ask about anything you can't. A yes you later take back is worse than an honest question now.

Ask two or three of these:

• "What would you expect me to deliver in the first six months?"
• "How is the team structured, and who would I report to?"
• "How does the appraisal cycle work, and when would my first review be?"
• "What is the policy on working from the office or from home?"
• "What does the joining process look like, and which documents will you need?"

Keep salary negotiation for when there is an offer to discuss; in this round, show interest in the work.