Interview guide HR interview questions
25 HR interview questions and how to answer them
By Manideep · Updated 21 October 2026 · 10 min read
HR interview questions test three things: whether you can communicate clearly, whether you will fit and stay, and whether your expectations match the job. Below are the 25 questions asked most often in HR rounds in India, from campus placements to experienced hiring, each with what the interviewer is really checking and a model answer you can adapt.
Do not memorise the answers word for word. Use them to see the shape of a good answer, then put your own facts into it.
How to answer any HR question
Almost every good HR answer has the same three moves: answer the question directly in the first sentence, back it with one specific example, and connect it to this job. If you do those three things in under a minute, you will rarely go wrong.
For questions that start with "tell me about a time", use the STAR method: the situation, your task, the action you took, and the result.
Questions about you
1. Tell me about yourself.
It tests whether you can give a clear, relevant summary. Cover who you are now, one or two achievements that matter for this job, and why you want it, in about a minute.
Model answer: "I'm a final-year B.Tech student in electronics, and I've spent the last year building embedded projects, including a soil-moisture sensor system for my uncle's farm that cut his watering by about a third. I'm applying for this role because I want to work on hardware that ships to real customers, and your IoT division does exactly that." Our full guide to tell me about yourself has more samples.
2. What are your strengths?
It tests self-awareness and whether your strengths fit the job. Name one or two, each with proof.
Model answer: "I'm good at breaking a big task into steps and seeing it through. In my final-year project our team had six weeks to build a working prototype, and I set up a weekly plan that got us to a demo a week early."
3. What is your greatest weakness?
It tests honesty and whether you work on yourself. Give a real weakness that is not central to the job, and what you are doing about it.
Model answer: "I used to take on too much myself instead of asking for help, which slowed me down near deadlines. I now flag early when something is at risk, and on my last project I asked a teammate to take the testing, which got us done on time."
4. How would your friends or colleagues describe you?
It tests how you see yourself through others. Pick two traits and support one with something someone actually said.
Model answer: "Reliable and calm. My last manager once said that when something broke, I was the person she wanted on the call, because I'd find the cause before guessing at a fix."
5. What motivates you?
It tests whether the job will keep you engaged. Link your motivation to the work itself.
Model answer: "Seeing something I built get used. During my internship, a small report I automated saved the finance team a day each month, and that mattered more to me than the grade."
6. What are your hobbies?
It tests whether you are a rounded person, and sometimes it is just a breather. Mention one real hobby and what it says about you, and be ready for a follow-up on it.
Model answer: "I play cricket for a local club on weekends. I'm the one who keeps the score and the stats, which is probably why I ended up enjoying data work."
Questions about the job and the company
7. Why do you want to work here?
It tests whether you researched the company and want this job rather than any job. Mention something specific.
Model answer: "Your company builds payment software for small shops, and I grew up helping in my father's shop, so I've seen the problem first hand. I'd like to work on something I understand from the user's side."
8. What do you know about our company?
It tests preparation. Cover what they do, who for, and something recent, then say why it interests you. Ten minutes on their website and recent news is enough.
Model answer: "You provide IT services to banks and insurers, you have a large delivery centre in Pune, and you recently announced a cloud partnership. That cloud work is what drew me to this role."
9. Why should we hire you?
It tests whether you understand what the job needs. Match two or three of its requirements with your evidence.
Model answer: "You need someone who can write clean SQL, explain findings to non-technical people and learn your tools quickly. I've done the first two in my internship, where I built the weekly sales report for the regional managers, and I picked up Power BI in two weeks for that project."
10. Why did you choose this career?
It tests whether your choice is deliberate. Give a genuine reason and a moment that confirmed it.
Model answer: "I chose computer science because I liked solving puzzles, but I knew it was right when I built a small app for my college fest and watched a thousand people use it over two days."
11. What do you expect from this job?
It tests whether your expectations are realistic. Talk about learning and contribution, not perks.
Model answer: "I expect to learn how large projects are run, to get regular feedback, and within the first year to own a piece of work end to end."
Questions about your future and commitment
12. Where do you see yourself in 5 years?
It tests ambition and whether you will stay. Show growth inside this kind of role, not a plan to leave.
Model answer: "Having become strong at backend development here, and leading a small module or mentoring new joiners." See our guide to where do you see yourself in 5 years for answers by career stage.
13. Are you willing to relocate?
It tests flexibility, and for service companies it is often a real requirement. If yes, say so clearly. If you have a genuine constraint, say it honestly and early.
Model answer: "Yes. I've lived away from home through college, and I'm happy to work from any of your locations."
14. Are you comfortable with night shifts or a service agreement?
It tests whether you have understood the terms. Only say yes if you mean it; backing out after joining costs you more than a no now.
Model answer: "Yes. I've read the terms, and I'm comfortable with them."
15. Do you plan to study further, such as an MBA or MS?
It tests whether you will leave in a year. Be honest without signalling an exit.
Model answer: "Not in the next few years. I want to build work experience first. If I study later, it would be to go deeper in this field, ideally alongside work."
16. Do you have any other offers?
It tests your market value and how likely you are to accept. Be honest, and show this one is your preference if it is.
Model answer: "I have one offer from a mid-sized firm, but this role is my first choice because of the cloud work, and I'd like to make a decision with you first."
Questions about past experience
17. Why did you leave your last job?
It tests whether you leave for good reasons. Stay positive about your old employer and focus on what you are moving towards.
Model answer: "I learned a lot there in two years, but the product had stabilised and there was little new work. I want to work on systems at a larger scale, which this role offers."
18. Tell me about a challenge you faced and how you handled it.
It tests problem-solving. Use STAR, and spend most of the answer on what you did.
Model answer: "Two weeks before our project demo, our dataset turned out to be mislabelled. I split the team so two of us relabelled the data while the others kept building, and we checked a sample every day. We demoed on time with a model about 12% more accurate than before."
19. Tell me about a time you worked in a team.
It tests collaboration. Show your specific part, not only the team's.
Model answer: "In a hackathon team of four, I took the backend so the others could focus on the app. When we fell behind, I wrote mock data so the front end could keep moving, and we submitted a working build."
20. Tell me about a conflict with a colleague.
It tests maturity. Pick a real disagreement, keep it professional, and end on how it was resolved.
Model answer: "A teammate and I disagreed on which database to use. Instead of arguing, we each wrote down our reasons and tested both with our real data for a day. His choice was faster for our case, so we went with it."
21. Tell me about a mistake you made.
It tests accountability. Own it, show how you fixed it, and what you changed afterwards.
Model answer: "I once sent a report with last month's numbers to a client. I called them within the hour with the right figures, told my manager, and since then I check the date range before anything goes out."
22. Explain the gap in your resume.
It tests honesty. State the reason in one line and move to what you did and are ready for now.
Model answer: "I spent a year preparing for the civil services exam. It didn't work out, but I came out of it with strong discipline and general knowledge, and I've since completed a data analytics course to move into this field."
Questions about pay and the close
23. What are your salary expectations?
It tests whether your expectations fit their budget. Research the typical range first, give a range rather than one number, and keep it tied to the role.
Model answer for a fresher: "I understand the package for this role is fixed for freshers, and I'm comfortable with it." For an experienced hire: "Based on my experience and the market for this role, I'm looking for something in this range, and I'm open to discussing the full package."
24. When can you join?
It tests availability. Know your notice period, and whether it can be shortened.
Model answer: "My notice period is sixty days. I've checked with my manager, and I may be able to leave in forty-five if the handover is complete."
25. Do you have any questions for us?
It tests interest. Always ask one or two, about the work rather than leave policy.
Good questions: "What would a successful first three months look like in this role?" "What does the team I'd join work on right now?" "How do new joiners get feedback?"
Mistakes to avoid in the HR round
- Treating it as a formality. Many candidates are rejected in HR rounds for weak communication or unclear commitment.
- Criticising a former employer or college, even when asked about problems.
- Saying yes to relocation, shifts or a service agreement you do not intend to honour.
- Giving a salary figure before you know the role's range.
- Answering "no questions" at the end. One good question shows interest.
- Reciting memorised answers. HR interviewers hear the same lines all day; a real example stands out.
The best preparation is saying your answers out loud to someone who will ask a follow-up. An AI mock interview does that on your own schedule: it asks one question at a time, waits for your spoken answer, and pushes on anything vague.
A few more answers
Frequently asked questions
What questions are asked in an HR interview?
Most HR rounds cover a self-introduction, your strengths and weaknesses, why you want the job and the company, where you see yourself in five years, relocation and commitment, past challenges and conflicts, salary expectations and joining date, and a chance for you to ask questions.
How long does an HR interview last?
Usually ten to thirty minutes. In campus placements it is often short and comes after the technical round; in experienced hiring it can be longer and include salary discussion.
Can you fail an HR interview?
Yes. Candidates are rejected in HR rounds for unclear communication, unrealistic expectations, a poor attitude towards past employers, or signs they will not stay. It is a real round, not a formality.
How should I answer HR questions as a fresher?
Use examples from projects, internships, college events and part-time work. Interviewers do not expect job experience from freshers, but they do expect specific examples and a clear reason for wanting the role.
What should I not say in an HR interview?
Avoid criticising past employers, saying you have no weaknesses, asking only about leave and perks, giving a salary number too early, and committing to terms such as relocation or shifts that you do not mean to keep.