HR Interview Questions and Sample Answers for Freshers and Experienced

What the HR round is really about

The HR interview checks three things: Are you honest and clear? Will you fit the team and the job conditions? Are your expectations realistic? It is not a trap. Prepare short, specific, truthful answers, and speak naturally rather than reciting.

A simple answer formula: direct answer first, then one example or reason, in about 30–60 seconds.

1. Tell me about yourself

They want a focused summary, not your life story. Use present, past, future:

"I'm Priya, a final-year computer science student at XYZ College. I enjoy building web applications; my main project is a job tracker in React and Node.js that classmates now use for placements. I also did a three-month internship where I fixed bugs in a Java backend. I'm looking for a developer role where I can keep learning from experienced engineers, and your focus on cloud products matches what I want to work on."

Experienced version: current role and impact, one or two achievements with numbers, and why you are moving.

2. Why do you want to join this company?

Show you did basic research: what they build, their clients or products, the technologies, or the training. "I read that your team works on payment systems at large scale, which is an area I've explored in a small project. I also like that fresh engineers get structured training and real project exposure." Avoid answers about salary or brand name only.

3. What are your strengths?

Pick two real strengths, each with proof. "I learn quickly. In my internship I picked up Spring Boot in two weeks and shipped a small feature. I'm also consistent: I solved coding problems daily for three months before placements."

4. What is your weakness?

Choose a genuine, non-critical weakness and show what you are doing about it. "I used to spend too long perfecting small details. I now set time limits for each task and ask for feedback earlier." Avoid "I'm a perfectionist" without substance, and avoid weaknesses that disqualify you.

5. Where do you see yourself in five years?

They want ambition that fits the role. "I want to become a strong engineer who owns features end to end, and later mentor newer team members. I'd like to deepen my skills in backend systems."

6. Why should we hire you?

Link their needs to your evidence. "You need someone who can learn fast and contribute on a backend team. I have hands-on experience with Java and SQL from my project and internship, and I've shown I can deliver and learn on my own."

7. Are you willing to relocate or work in shifts?

Be honest. If flexible, say so. If not, explain calmly and offer what you can do. Do not promise something you cannot keep, since this often appears in written terms later.

8. Do you have any other offers?

Be honest without pressure. "I'm interviewing with a couple of companies, and this role is one of my top choices because of the work and learning opportunities."

9. What are your salary expectations?

For freshers, many companies have fixed bands, so say: "I'd like to understand the role and the company's standard range for this position. I'm more focused on learning and growth at this stage." For experienced candidates, research the market first and give a range (salary negotiation guide).

10. Why are you leaving your current job? (experienced)

Stay positive and forward-looking: growth, new technology, scope. Never criticise your employer. "I've learned a lot in my current team. I'm now looking for bigger scale and ownership, which this role offers."

11. Tell me about a challenge you faced

Use the STAR method (Situation, Task, Action, Result) with a real example and what you learnt.

12. How do you handle pressure or deadlines?

Give a method and an example: break work into parts, prioritise, communicate early about risks.

13. Tell me about a time you worked in a team or had a conflict

Focus on listening, finding common ground and the outcome, not on blaming anyone.

14. Do you have any gap in your education or career?

Be factual and brief, and show what you did in that time (preparing, learning, family responsibility, health). Do not apologise excessively or invent explanations.

15. What do you know about our products or services?

Spend ten minutes before the interview on the company website and one recent news item.

16. How do you keep learning?

Mention specific habits: courses, documentation, projects, newsletters or communities.

17. Are you comfortable working with a team of different backgrounds?

Answer with an example of working with people from different colleges, cities or experience levels.

18. What motivates you?

Choose something real: solving problems, building things people use, learning, helping the team.

19. Do you have any questions for us?

Always ask something. Good questions: "What does onboarding look like for new engineers?", "What kind of projects would I start on?", "How does the team measure success in the first six months?"

20. When can you join?

Freshers: give the real date after exams or notice. Experienced: state your notice period and whether it is negotiable.

Mistakes to avoid

• Memorised, word-for-word scripts
• Criticising a previous employer, college or team
• Over-claiming skills you cannot demonstrate
• Giving one-word answers
• Asking nothing at the end

Practise

Record yourself answering five questions, listen back, and cut anything vague. Then do a mock interview with a friend. For the full process see the interview process guide, and for company-specific preparation see how Cognizant and Wipro run their HR rounds.