HR Interview Questions for Freshers: 12 Questions and How to Answer Them
You cleared the aptitude test and the technical round, and now there's "just the HR round". It isn't a formality. Candidates do get rejected here, usually not for lack of skill but for an answer that raised a doubt. The questions are predictable, so the doubts are avoidable.
What the HR round is really for
The technical round asks "can you do the work?". The HR round asks everything else:
- Will you communicate well with teammates, managers and clients?
- Will you stay? Hiring and training a fresher costs a company months. HR is looking for signs you'll leave in six.
- Do you fit the practical terms: location, shifts, joining date, salary band, any service agreement?
- Is your story consistent? Your answers should match your resume and what you said in earlier rounds.
Keep those four in mind and most answers write themselves. Here are the questions you're most likely to get.
1. "Tell me about yourself."
Almost every HR round opens with this. Give a one-minute answer in three parts: who you are now, one or two things that shaped you, and why this role is the next step. Leave out your date of birth, your family's occupations and your hometown's history; they're on the form if HR needs them.
"I'm a final-year computer science student at [college]. Over the last two years I've mostly worked on backend development: my final-year project is a complaint-tracking app for our hostel, which about 300 students use, and I did a two-month internship where I built internal reporting APIs. What I enjoyed most was making something people actually rely on, which is why this role, working on production systems from day one, is the kind of start I'm looking for."
Notice there's nothing generic in it. Every sentence gives the interviewer something to ask about next, which is exactly what you want.
2. "What are your strengths?"
Pick two, not five, and back each with a quick example. "I'm hardworking and a quick learner" is what everyone says. "I learn new tools quickly: I picked up React in two weeks for my internship project and shipped the dashboard on time" is evidence.
3. "What is your greatest weakness?"
"I'm a perfectionist" and "I work too hard" are recognized instantly and cost you credibility. Name a real, non-critical weakness and what you're doing about it:
"I used to find it hard to speak up in group discussions, so in my project team I'd agree to things I had doubts about. This year I started writing my points down before meetings and making sure I say at least one. It's helped, and I now volunteer to present our project updates."
Avoid anything that's core to the job you're applying for. A developer shouldn't say "I'm not very comfortable with coding".
4. "Why should we hire you?"
Match yourself to the role in two or three points: a relevant skill, proof you can learn, and genuine interest in the work. Don't compare yourself with other candidates; you don't know them, and it sounds arrogant.
5. "Why do you want to join our company?"
This is where preparation shows. Spend twenty minutes on the company's website and recent news before the interview. Then name something specific: a product, the kind of clients they serve, the technology they use, or the training program for freshers. "It's a big, reputed company" is true of dozens of companies and tells them nothing about you.
6. "Where do you see yourself in five years?"
They're checking ambition and, again, whether you'll stay. A good answer is about growing skills and responsibility, ideally within the company: "I'd like to be someone the team relies on for [area], and to have started mentoring newer engineers." Avoid "in your chair", "running my own startup" or "doing an MBA abroad", even if they're true; each suggests you're passing through.
7. "Are you willing to relocate?" / "Can you work in shifts?"
Answer honestly. If you say yes and then refuse the posting, it causes far bigger problems later than a clear answer now. If you have a genuine constraint, say so calmly and say what you can do: "I'd prefer Bengaluru or Pune because of family commitments, but I'm open to other locations for the initial training period."
8. "What are your salary expectations?"
At many companies, fresher packages are fixed for the role, so there's little to negotiate. A safe answer is: "I understand the package for this role is standard for freshers, and I'm comfortable with it." If you don't know the package, it's fine to ask: "Could you tell me the range for this role?" Don't name a number far above the market; it can end the conversation.
9. "Are you okay with signing a service agreement?"
Some companies, often large ones that invest in months of training, ask freshers to sign a service agreement (commonly called a bond) to stay for a set period. Before you answer, ask what it covers: how long it lasts and what happens if you leave early. Then answer honestly. Agreeing now and trying to back out after joining is worse for everyone, including your reputation.
10. "Why do you have a backlog?" / "Why is there a gap in your education?"
Don't hide it or blame anyone. Give the reason in one sentence, then move to what you did about it: "I had a backlog in second year in Engineering Mathematics because I underestimated it. I cleared it the next semester and my scores improved after that." For a gap year: say what you did with it (preparing for an exam, a family responsibility, a course) and what you took from it. A short, calm explanation almost always ends the topic.
11. "Do you have other offers?" / "Are you interviewing elsewhere?"
It's fine to be honest: "Yes, I'm in the process with a couple of companies, but this role is my first preference because…". Don't invent offers to create pressure; it's easy to check and freshers rarely have room to negotiate anyway.
12. "Do you have any questions for us?"
"No, nothing" signals low interest. Have two or three ready:
- "What does the training period look like for freshers?"
- "What would a typical first project be for someone in this role?"
- "How is performance reviewed in the first year?"
Save questions about leave and holidays for after you have the offer.
Five things that quietly cost freshers the offer
- Inconsistency with your resume. If your resume says you led the project, don't describe yourself as "helping out". Read your own resume the night before.
- Criticizing your college, teachers or a previous employer. It makes HR wonder what you'll say about them.
- Memorized answers. They sound flat and collapse at the first follow-up. Know your points, not your sentences.
- Very long answers. One to two minutes is plenty. Stop, and let them ask more.
- Poor setup for a video interview. Test your camera, microphone and internet beforehand, sit facing a light, and keep your phone on silent.
How to practice
HR answers are short, so it's tempting to prepare them in your head. Don't. The difference between a hesitant answer and a confident one only shows up when you say it out loud:
- Say each answer aloud and time it. Aim for one to two minutes.
- Prepare stories, not lines. Many HR questions ("a time you handled pressure", "a conflict in your team") are behavioral. Our guide to behavioral interview questions and the STAR method shows how to build a small set of stories that covers them.
- Practice with follow-up questions. A friend, a mentor, or an AI interviewer that asks "why?" and "what happened next?" is far better than rehearsing alone.
On SkillLynk you can do the last part any time: an AI voice mock interview has you answer out loud, asks follow-up questions and gives feedback as soon as you finish. And since HR will read your resume closely, the free Resume Review checks it for formatting and content problems first.
Practice answering out loud, with follow-up questions, before your HR round.
Try an AI mock interview