Common HR Interview Questions and How to Answer Them (With Examples)

You have cleared the technical rounds. Now the HR round arrives, and the questions seem simple: "Tell me about yourself." "Why do you want to leave your job?" Yet this is where many strong candidates stumble. They sound rehearsed, negative or vague.

HR and managerial rounds check three things: Will you fit here? Will you stay and perform? Can you communicate and be honest? If you know what each question is really asking, answering becomes easier.

Use this for most questions:

1. Answer directly in one sentence.
2. Support it with an example: what happened, what you did.
3. End with the result or what you learnt.

For stories, use STAR: Situation, Task, Action, Result. Keep answers to about one to two minutes.

What they want: a short professional summary and a sense of how you communicate.

Structure: present, past, future. Don't recite your resume.

Example (experienced):

"I'm a backend developer with four years of experience, currently at a fintech company where I work on payment APIs in Java. Before that, I built internal tools at a logistics firm. Recently I led the move of two services to the cloud, which reduced response time by 40%. I'm now looking for a role with larger-scale systems and more design responsibility, which is why this position interests me."

Example (fresher):

"I recently completed my B.Tech in electronics. I enjoyed programming, so I built a few projects, including an inventory app for a local shop that they still use. I did a three-month internship where I learnt to work in a team and use Git. I'm looking for my first full-time role where I can keep learning and contribute to real products."

Keep it under 90 seconds. See LinkedIn profile for recruiters for writing your professional summary.

What they want: proof that you researched them and have a real motive.

How to answer: mention something specific: a product, a value, the team's work or growth. Connect it to your skills and goals.

"I've used your app for two years and noticed how fast you've improved the checkout experience. I'm interested in working on that kind of customer-facing problem, and my experience with payment systems fits it."

Avoid: "Because it's a big brand" or "Because I need a job."

What they want: to know whether you'll stay and whether you speak badly about employers.

How to answer: focus on growth, never blame. Be honest.

"I've learnt a lot in my current role, and I'm proud of what we delivered. I'm now looking for bigger technical challenges and a path to lead projects, which isn't available in my team at the moment."

Avoid complaining about your manager, pay or colleagues. If you were laid off, say so plainly and briefly, and move on to what you want next. For deciding your own move, see when to switch jobs.

What they want: relevant strengths with evidence.

Pick two or three that match the job, and prove each with an example.

"I'm good at breaking down complex problems. Last quarter our reporting job was failing intermittently. I traced the cause to a timing issue, fixed it and added a test, so it hasn't failed since."

Avoid empty adjectives like "hard-working" with no example.

What they want: self-awareness and a willingness to improve.

How to answer: choose a real but non-critical weakness, and show what you are doing about it.

"I used to take on too much myself instead of delegating. I realised it slowed the team, so now I assign tasks with clear expectations and check in. It's still something I watch."

Avoid fake weaknesses ("I'm a perfectionist") and anything that disqualifies you for the role.

What they want: ambition that fits the role, and signs you'll stay.

"I'd like to grow into a senior role where I take responsibility for design decisions and mentor others. I'd like to build that expertise here, and I'm interested in how your team grows engineers."

Avoid "I want your job" and "I don't know".

What they want: a clear, confident summary of fit.

Connect their need, your skill and a proof point.

"You need someone who can improve payment reliability. I've done that on a similar system, cutting failures by 30%, and I can start contributing quickly while learning your stack."

What they want: problem-solving and resilience. Use STAR.

"Situation: our app crashed during a sale. Task: I had to find the cause quickly. Action: I checked logs, found a database query that slowed under load, added an index and caching. Result: the page recovered in two hours, and we added load tests so it didn't recur."

For the debugging mindset, see how to debug any bug.

What they want: emotional maturity.

Choose a real, moderate disagreement. Show that you listened, found common ground and kept the relationship.

"A teammate and I disagreed on the approach. I asked for his reasoning, we compared trade-offs and ran a small test. His approach was better for one part, mine for another, and we combined them."

Avoid making the other person the villain.

What they want: honesty and learning.

Choose a real mistake and show the lesson.

"I once deployed a change without testing it on production-like data, and it broke a report. I rolled back within the hour, told the team and added a checklist step. Since then I always test with realistic data."

What they want: to check fit with budget.

Do research first: market data, job listings and peers. Give a range, based on your value, and show flexibility.

"Based on my experience and the role's scope, I'm looking at ₹X to ₹Y. I'm open to discussing the whole package."

If asked early, you can say you'd like to understand the role fully first. For details, see salary negotiation in India and CTC vs in-hand salary.

Be honest and clear. Say whether it can be shortened or bought out. See notice period guide.

Always ask something. Good questions:

• "What does success look like in the first six months?"
• "How is the team structured?"
• "What are the biggest challenges the team faces?"
• "How do you support learning and growth?"

Avoid asking only about salary and leave.

Be honest and positive. Say what you did (study, health, family, travel, upskilling) and what you learnt, then redirect to your readiness now.

Write 5 to 6 stories covering:

• A technical or work problem you solved
• A time you worked in a team
• A conflict and how you handled it
• A mistake and what you learnt
• A time you led or took initiative
• A time you learnt something quickly

Each story can answer several questions with small changes.

• Be on time, and test your tech for online interviews.
• Dress slightly smarter than the workplace norm.
• Greet warmly, make eye contact (or look at the camera) and smile naturally.
• Listen fully before you answer. Pausing for two seconds is fine.
• Be honest. If you don't know, say so and explain how you'd find out.
• Don't criticise past employers.
• Say thank you, and follow up with a short email.

Nerves are normal. See overcoming stage fright for techniques.

• Memorising and reciting
• Rambling for five minutes
• Being negative about your last company
• Giving no examples
• Not researching the company
• Lying about experience or salary
• Having no questions

Memorise the structure and key points, not exact words. It will sound more natural.

One to two minutes for most. Longer for stories, but stay focused.

Yes. "Let me think about that for a moment" is fine.

Use projects, internships, college activities, sports and volunteering as examples.

Such questions may be inappropriate in a hiring process. You can answer briefly if you wish, or politely redirect to your qualifications and availability.

Practice with a friend or record yourself. Every company's process differs, so use these as a starting point.