You cleared the aptitude test. You survived the technical round, even the linked-list question you half-guessed. Now the coordinator says "HR round, room 4, ten minutes", and you relax, because everyone in the hostel said HR is just a formality. Then the HR manager looks at your resume, asks why you have a backlog in the third semester, and follows up with "So would you be fine with a two-year service agreement and a posting in any city?" Suddenly it does not feel like a formality.
The short answer
The HR round in an IT company checks five things: whether you will fit the team, whether you can communicate clearly, whether what you say matches your resume, whether there are red flags, and whether you will actually join and stay. Most HR interview questions for freshers are versions of those five checks. You do not need memorised scripts. You need short, honest answers that you have said out loud before, so you sound like yourself instead of a template. Below are 15 questions freshers commonly report being asked in an HR round interview, what each one is really asking, a sample answer to adapt, and what to avoid.
What the HR round is actually checking
Technical interviewers decide whether you can do the work. HR decides whether hiring you is a safe bet.
- Fit. Will you work well with a team, take feedback, and not be a headache to manage?
- Communication. Can you explain yourself in clear, simple sentences?
- Consistency. Does what you say match your resume, your application form and what you told the technical panel? HR often has the panel's notes in front of them.
- Red flags. Unexplained gaps, backlogs you are evasive about, an attitude problem, or answers that sound copied from the internet.
- Joining intent. In campus and mass off-campus hiring, companies make many offers and worry about how many people will actually join. Questions about relocation, shifts, bonds and other offers are often about this.
15 HR interview questions for freshers
1. Tell me about yourself
What they are really asking: Can you give a structured 60-to-90-second summary without reading your resume back to them?
I'm Priya, I just finished my B.Tech in Electronics from a college in Pune. In my final year I moved towards software, built a small attendance app in React with a Node backend, and did a two-month internship fixing bugs in a billing module. I enjoy the debugging side most. I'm looking for a developer role where I can work on real production code and learn from a team.
Avoid: Starting with your date of birth and your parents' occupations, or reciting your tenth and twelfth percentages. We have a full breakdown in how to answer "tell me about yourself" in an IT interview, and a separate one on the more formal self-introduction for IT interviews that many campus panels ask for.
2. Why should we hire you?
What they are really asking: Do you know what the role needs, and can you connect yourself to it without arrogance?
This role needs someone who can learn your stack quickly and work in a team. In my internship I picked up a codebase I'd never seen and shipped fixes within the first two weeks, and in my final-year project I was the one who kept the four of us on schedule. I won't know everything on day one, but I learn fast and I don't disappear when I'm stuck.
Avoid: "Because I am hardworking, dedicated and a quick learner." Every candidate says those three words. Give one piece of evidence for each claim you make.
3. Why do you want to join this company?
What they are really asking: Did you do five minutes of research, or are you applying everywhere with the same answer?
I looked at your work in the banking domain, and I'm interested in how large financial systems are built and tested. Your training programme for freshers is also a big reason. I'd rather start somewhere that teaches properly than somewhere that expects me to know everything already.
Avoid: Praising the company's size and brand only, or reading lines from their website.
4. What are your strengths?
What they are really asking: Do you know yourself, and can you back it up?
I'm patient with problems that take time. In my project we had a bug where data saved twice on slow networks, and I spent two evenings tracing it to a double form submit. I like that kind of work more than most people in my batch did.
Avoid: Listing five strengths with no examples. One strength with a real story beats five adjectives.
5. What is your biggest weakness?
What they are really asking: Are you honest and self-aware, and are you doing anything about it?
I used to stay quiet in group discussions even when I had something useful to say. I noticed it during project reviews, so I started making myself speak first at least once in each meeting. It's better now, though I still have to push myself in larger groups.
Avoid: "I am a perfectionist" or "I work too hard." HR hears these daily and they sound like dodges. Also avoid a weakness that is central to the job, such as "I can't concentrate for long".
6. Where do you see yourself in five years?
What they are really asking: Will you stay long enough to be worth training, and do you have any direction at all?
I'd like to be a strong developer who others trust with a whole module, and maybe starting to guide newer people. I'm not fixed on a specific title yet. I want to find out over the first couple of years whether I lean towards backend or towards something like cloud.
Avoid: "In your chair", "running my own startup", or "preparing for an MBA abroad".
7. Are you willing to relocate?
What they are really asking: Will you accept the offer and actually turn up if they post you to a city you did not pick?
Yes. I'd prefer Bangalore or Pune if there's a choice, but I'm open to any location for the first role.
Avoid: Saying "yes, anywhere" if it is not true and then declining after the offer. If you have a genuine constraint, such as a parent's health, say it plainly and early.
8. Are you okay with night shifts or rotational shifts?
What they are really asking: Many service and support projects run on client time zones. Will you accept the reality of the role?
Yes, I understand some projects follow client hours. I'd like to know whether it's a permanent night shift or rotational, so I can plan, but I'm fine with either for a project that needs it.
Avoid: Agreeing to everything without asking anything. Asking what the shift pattern actually is shows maturity, not reluctance.
9. Are you okay signing a service agreement or bond?
What they are really asking: Will you commit for the training period without trouble later?
I'm okay with a service agreement in principle. Could you tell me the duration and what it covers, for example whether it relates to the training cost? I'd like to read it properly before signing. Could you also tell me whether original certificates are kept?
Avoid: Arguing about bonds in the interview, or agreeing without knowing the terms. You are allowed to ask what you are signing.
10. You are from a non-CS branch. Why IT?
What they are really asking: Is this a real interest, or just where the jobs are? And can you show the effort you have put in?
I'm from Mechanical, and honestly, I started coding in second year because a friend was building a website and I got curious. Since then I've done a data structures course, built two projects in Python and JavaScript, and solved problems regularly. I enjoy it more than anything in my core branch.
Avoid: "There are no jobs in my branch." It may be true, but it makes you sound like you are settling. Lead with what you have done, not what you are escaping.
11. Can you explain this gap year or this backlog?
What they are really asking: Is there a hidden problem, and will you be honest about it?
I had a backlog in Engineering Maths in third semester. I'd underestimated it and was spending too much time on a college fest. I cleared it in the next attempt and haven't had one since. It taught me to plan subjects I find hard much earlier.
For a gap year:
I took a year after twelfth to prepare for an entrance exam. It didn't go the way I wanted, so I joined B.Tech the next year. I don't regret the attempt, and it's part of why I take preparation seriously now.
Avoid: Hiding it, blaming a professor, or giving a vague answer that makes HR dig. A short, honest explanation plus what changed afterwards is almost always enough.
12. What are your salary expectations?
What they are really asking: In campus hiring the package is usually fixed and known, so this checks whether you have realistic expectations. Off-campus, it may be a genuine question.
As a fresher, I'm going with the standard package for this role. My priority right now is learning and good work. If there's a range for the role, I'm happy to hear it.
Avoid: Quoting a number far above the announced package, or saying "anything is fine" in an off-campus interview where you have no idea of the range. Find out the typical fresher range for the role and city beforehand so you are not guessing.
13. Tell me about a time you failed or handled a conflict
What they are really asking: How do you behave when things go wrong, and do you take responsibility?
In our final-year project, two teammates disagreed on whether to use Firebase or our own backend, and work stopped for a week. I suggested we each list what the project actually needed, and we found Firebase covered it. We lost a week, and I learned to raise disagreements early instead of waiting for them to fix themselves.
Avoid: A story where you were perfect and everyone else was wrong. Use the situation, task, action, result structure explained in the STAR method for behavioural interviews, and keep it under two minutes.
14. Do you have any other offers?
What they are really asking: How likely are you to join, and how competitive are you?
I have an offer from one company, but this role is my first preference because of the work in the cloud domain.
Don't promise to accept an offer you have not seen. If your college has a one-offer placement policy, say so; HR already knows the rule.
Or, if you have none:
Not yet. I'm interviewing at a couple of places, but this is one I'm keen on.
Avoid: Inventing offers to sound in demand. A lie here undermines everything else you said.
15. Do you have any questions for us?
What they are really asking: Are you interested enough to have thought about the job?
What does the training programme for freshers look like, and how are people assigned to projects after it? And what does a good first year look like for someone in this role?
Avoid: "No, everything is clear." Also avoid opening with leave policy or when you can switch companies. Ask about the work, training and team first.
How to prepare without sounding scripted
Reading sample answers is easy. Saying them in the room, with someone watching, is not. A few things help:
- Write bullet points, not paragraphs. For each question above, note two or three facts from your own life. Memorised sentences sound memorised, and one follow-up knocks you off the script.
- Check every answer against your resume. If your resume says you led a project, your conflict story should not describe someone else leading it.
- Prepare your awkward answers first. Backlogs, gaps, a branch change, a low percentage. Say them out loud until they feel boring.
- Say everything out loud. Time yourself. Most HR answers should be well under two minutes.
- Practise follow-ups. HR will push on whatever sounds vague. "You said you're a quick learner. Give me an example."
- Stay calm when you don't know. A short pause and an honest answer is fine, as covered in how to handle a question you don't know.
The HR round usually comes after the technical rounds, so do not let HR preparation crowd out the rest. If you are still building your overall plan, the interview preparation for freshers hub puts the technical, coding and HR pieces in one place, and what happens in a technical interview covers the round that usually comes before this one.
Practise the answers out loud
The fastest way to test your answers is to say them to someone who will push back. A friend or senior helps. Sia, the AI interviewer on 99interview, runs technical rounds rather than HR ones, but it asks one question at a time and follows up on what you said, which is good practice for keeping answers short and clear under follow-up questions; communication is one of the five criteria every round is scored on.
If you would rather hear it from a person, a live 40-minute Zoom interview with a working engineer gives you real follow-ups on your projects, the round that usually comes before HR, and written feedback. Either way, walk into the HR round having already said your honest answers out loud, so on the day they sound like you.