HR interview questions look simple on paper. "Tell me your weakness." "Where do you see yourself in five years?" "Why do you want this job?" Most freshers read a list of these, think they're prepared, and then freeze or ramble when asked live.

The problem isn't the questions. It's that the answers aren't practised out loud. Reading an answer and speaking it are completely different skills. This post gives you 15 of the most common HR interview questions for freshers, with a sample answer structure for each — and the honest truth about what the interviewer is actually listening for.

What HR is actually evaluating

HR interviewers are not trying to trick you. They're checking three things: whether you can communicate clearly, whether you'll fit the team, and whether you're self-aware. The "right" answers aren't memorised scripts — they're structured, honest, and specific to you. Every answer below is a starting structure, not a script to copy word for word.

The 15 questions

1. Tell me about yourself

What they want: A 90-second professional summary — not your life story.
Structure: Who you are → what you've studied/done → why you're here.
Example: "I'm a final-year Computer Science student at [college]. During my degree I focused on data structures and built two projects — one was a real-time chat app using Node.js. I'm here because I'm looking for a developer role where I can work on backend systems and grow in a structured environment."

2. What are your strengths?

What they want: One or two real strengths relevant to the role, backed by an example.
Don't say: "I'm a hard worker" or "I'm a fast learner" without proof.
Example: "I'm good at breaking complex problems into smaller steps. During my final year project, I had to refactor a system that wasn't scaling — I mapped every component, fixed the bottleneck, and got response time down by 40%."

3. What is your weakness?

What they want: Honesty and self-awareness. A real weakness, not a fake-positive like "I work too hard."
Structure: Real weakness + what you're actively doing about it.
Example: "I tend to spend too long trying to solve something independently before asking for help. I've been working on this by setting a personal time limit — if I'm stuck for more than 30 minutes, I ask."

4. Why do you want to work here?

What they want: Evidence that you researched the company. Not "it's a good company."
Structure: Something specific about the company + how it connects to what you want to do.
Example: "I read about how your team is building microservices for the logistics product. That's exactly the kind of distributed systems work I've been learning, and I want to apply it in a real production environment."

5. Where do you see yourself in 5 years?

What they want: Direction, not a rehearsed corporate answer.
Don't say: "In your position" (even as a joke).
Example: "I want to develop strong technical depth in the first two years, and eventually move into a role where I'm leading small feature teams. I don't have a rigid plan — I want to grow with the problems the organisation is trying to solve."

6. Why should we hire you?

What they want: Your specific value, not a generic "I'm hardworking."
Structure: What you bring + what you'll contribute + why you're ready now.
Example: "I've built two working applications end-to-end, I'm comfortable with your tech stack, and I'm at a stage where I learn fast. I won't need six months to become useful — I can contribute in the first few weeks."

7. Tell me about a challenge you faced and how you handled it

What they want: Problem-solving process and resilience. Use STAR (Situation, Task, Action, Result).
Example: "In my final year project, our dataset was incomplete two weeks before submission. I identified what was missing, found an alternative public dataset, cleaned it, and integrated it in 4 days. We submitted on time and scored well on the evaluation criteria."

8. Are you comfortable relocating?

Answer honestly. If you're comfortable: say so directly. If there's a specific constraint: state it matter-of-factly without over-explaining. Interviewers respect honesty far more than a "yes" that becomes a problem later.

9. What do you know about our company?

What they want: That you spent 15 minutes reading their website before you came.
Prepare: What they do, who their customers are, recent news, and one thing that's relevant to your role.

10. How do you handle pressure or tight deadlines?

What they want: A real example, not "I work well under pressure."
Example: "During exam season I was also completing a freelance project. I made a daily task list, cut anything non-essential, and communicated proactively with the client about timeline. Both got done."

11. Tell me about a time you worked in a team

What they want: Collaboration skills — how you communicated, handled disagreement, contributed.
Tip: Pick an example where something actually went wrong or got resolved — smooth stories are forgettable.

12. Do you prefer working independently or in a team?

Don't pick a side rigidly. The honest answer for most roles: "I'm comfortable with both. I like working independently when the task is well-defined, and I find collaboration useful when the problem involves unknowns or design decisions."

13. What motivates you?

What they want: Something genuine, not "money" or "growth" without context.
Example: "I'm motivated by seeing something I built being used. When I released my first app and people actually used it, that feeling pushed me to build better."

14. Do you have any questions for us?

Always say yes. Saying "no" signals you're not curious about the role. Ask one or two genuine questions — about the team, the first 90 days, or how success is measured in the role. Never ask about salary in an HR round unless they bring it up.

15. What are your salary expectations?

What they want: A realistic number, stated calmly.
Research first: Look up the typical range for the role on Glassdoor or AmbitionBox.
Example: "Based on the role and my research, I'm expecting something in the range of ₹4–5 LPA. I'm open to discussing this based on the full compensation structure."

The only way to actually prepare

Reading these answers will help you think. Speaking them out loud is what will prepare you. Record yourself answering each question. Play it back. Notice where you ramble, where you lose structure, where you say "basically" or "so, like" too often. That feedback loop — speaking, hearing yourself, adjusting — is what actually builds interview readiness.

Sanviora's AI mock interviews give you exactly this loop, with structured feedback after each answer. Your first session is free. Try it before your next interview.