Guides › Interviews
20 HR Interview Questions for Freshers and How to Answer Them
"Tell me about yourself", strengths and weaknesses, relocation, bond, salary — what the interviewer is really checking and sample answers you can adapt.
The HR round is rarely where freshers get rejected for lack of knowledge — it is where they get rejected for sounding unprepared, negative or inconsistent. Every question below has a purpose. Understand the purpose, and the right answer becomes obvious.
General rules: keep answers to 1–2 minutes, be honest, give a specific example whenever you can, and never criticise your college, teachers or a previous employer.
1. Tell me about yourself.
What they check: communication, and whether you can summarise yourself clearly.
Use present → past → future in about a minute:
"I'm a final-year B.Tech Computer Science student at XYZ College. Over the last two years I've focused on Java and web development — I've solved around 250 DSA problems and built a library management system with Spring Boot and MySQL that our department now uses. I also enjoy competitive programming and took part in a few weekly contests. I'm looking to start my career as a software engineer where I can keep building real products, which is why I'm excited about this role."
Don't recite your resume line by line, and don't start with your family background.
2. Why should we hire you?
What they check: whether you understand the role and can link your skills to it.
Mention two or three strengths with proof, and connect them to the job: "You need someone who can learn quickly and work on backend systems — I built and deployed two backend projects on my own and picked up Spring Boot in a month for my internship."
3. What are your strengths?
Pick one or two that matter for the job and back each with a short example. "I'm persistent — when my project's login kept failing in production, I spent two days reading logs until I found a timezone bug in token expiry."
4. What is your biggest weakness?
What they check: self-awareness and whether you work on yourself.
Choose a real but non-critical weakness and show what you are doing about it: "I used to find public speaking hard, so I volunteered to present our project at the department fest and now take part in mock interviews every week." Avoid fake answers like "I'm a perfectionist" and anything core to the role.
5. Where do you see yourself in five years?
Show ambition that fits the company: "I'd like to have grown into a strong engineer who owns features end to end and mentors new joiners — ideally growing here."
6. Why do you want to join our company?
Research the company beforehand: what it builds, its clients, a recent project, its training programme. Mention one specific thing; generic praise ("it's a big company") is a red flag.
7. Are you willing to relocate?
If yes, say so clearly. If you have a genuine constraint, be honest and polite — but know that for most service-company roles, the expected answer is yes.
8. Are you comfortable with night shifts or rotational shifts?
Answer honestly. If you are flexible, say so. Inconsistent answers here cause problems after joining.
9. The role has a service agreement (bond). Is that okay?
Read the terms before the interview so you can answer confidently. If you have questions, ask them politely rather than sounding reluctant.
10. What are your salary expectations?
For campus roles the package is usually fixed: "I'm aware of the package for this role and I'm comfortable with it." For off-campus roles, research the typical range and give a range, not a single number.
11. Tell me about a challenge you faced and how you handled it.
Use the STAR method:
- Situation — the context in one line
- Task — what you had to do
- Action — what you did (most of your answer)
- Result — what happened, ideally with a number
12. Describe a time you worked in a team. Was there a conflict?
Show that you listen and focus on the outcome: a disagreement about the tech stack, how you compared the options with data, and how the team decided.
13. Tell me about a failure.
Pick a real failure, take responsibility, and spend most of the answer on what you learned and changed. Failing a first coding test and then building a daily practice routine is a perfectly good answer.
14. Why is there a gap in your education? / Why is your CGPA low?
Be brief and honest, don't make excuses, and move quickly to what you have done since: projects, skills, certifications.
15. How do you handle pressure and deadlines?
Give an example: exam week clashing with a project deadline, how you broke the work down and prioritised.
16. Do you prefer working alone or in a team?
The best answer is "both, depending on the task", with a one-line example of each.
17. What do you know about our company?
Founding, what it does, its main services or products, a recent achievement and its values. Two minutes of research per fact is enough.
18. Do you have other offers?
Be honest. If you have one, say so politely and explain why this company is still your preference.
19. What motivates you?
Something genuine and related to work: solving problems, building things people use, learning new technology.
20. Do you have any questions for us?
Always say yes. Good questions:
- "What does the training period look like for freshers?"
- "What technologies would someone in this role work with in the first year?"
- "What do the most successful people in this team have in common?"
Avoid asking about leave or salary hikes in a first interview.
Practise out loud
Reading these answers is not the same as saying them. Record yourself answering five questions on your phone, then watch it back — you will immediately notice filler words and rambling. Or use the AI mock interview in HR mode with voice: it asks the questions aloud, listens to your answers, and scores your content plus your speaking pace, filler words and pauses. Practise the technical side with interview questions and flashcards, and see the 6-month placement plan for the full preparation timeline and how the campus placement process works for what happens before and after the HR round.
More guides
- How to Use Codify: A 7-Day Start Plan — New here? Pick a roadmap, make a study plan, start the DSA sheet, revise with notes, practise for placements and test yourself — one step a day, then a daily routine.
- Infosys Preparation Guide: Online Test, Pseudocode and Interview — Roles (SE, DSE, SP), what each section of the Infosys online test checks, how to crack pseudocode and reasoning, a 4-week plan and the interview.
- Wipro Elite NLTH Preparation: Aptitude, Essay and Coding — The Wipro fresher test round by round — quant, logical and verbal, the written essay, two coding problems — plus a 3-week plan and interview tips.
- Accenture Preparation Guide: Cognitive, Technical, Coding and Communication — Every Accenture round explained — cognitive, MS Office/networking/cloud technical MCQs, pseudocode, coding and the spoken-English test — with a 4-week plan.