40 HR Interview Questions for Freshers (With How to Answer)
The 40 HR interview questions freshers face most, what each one tests and how to answer, plus a one-week practice plan for placement season.
HR interviews for freshers mostly test five things: whether you can explain yourself clearly, why you want this job, how you handle problems and people, whether your expectations fit the role (location, shifts, salary, further studies), and whether your resume is true. Prepare a 60-second introduction, three short stories from projects or college life, and honest answers about relocation and your plans. The 40 questions below cover the ones that come up most.
Each question has a short note on what the interviewer is checking and how to answer. For the full timeline of a placement season, from aptitude tests to the HR round, see our campus placement preparation plan.
How to answer HR questions as a fresher
Harvard's career office gives two rules that cover most HR answers: "Show, don't tell", meaning use a specific example and only relevant details, and, for behavioral questions, follow the order of situation, action and result. Freshers often answer with adjectives ("I am hardworking and a team player"). A one-line story from a project, internship, sports team, fest or part-time job is far more convincing.
It also helps to know what the questions are probing for. The US National Association of Colleges and Employers (NACE) lists eight career-readiness competencies employers look for in graduates, including communication, teamwork, critical thinking and professionalism. Most HR questions are a way of checking one of these, so each story you prepare should show at least one.
| Question type | What they check | Answer shape | Length |
|---|---|---|---|
| About you | Clarity, confidence, honesty | Present, proof, strengths, goal | 45–60 sec |
| Motivation and company | Research and genuine interest | Specific reason + link to your skills | 30–45 sec |
| Strengths and weaknesses | Self-awareness | Claim + example, or weakness + what you're doing about it | 30–45 sec |
| Behavioral ("Tell me about a time…") | How you actually behave | Situation, action, result | 60–90 sec |
| Situational ("What would you do if…") | Judgement | Steps you'd take, in order | 30–60 sec |
| Practical (relocation, shifts, salary) | Fit with the role's conditions | Direct, honest answer | 10–20 sec |
About you (questions 1–8)
1. Tell me about yourself.
The opener in almost every interview. Give your degree and college, one project or internship with a result, two strengths relevant to the job, and why you want this role. Keep family details out. Our guide to the self introduction for freshers has ten samples by degree.
2. Walk me through your resume.
Go top to bottom but pick highlights; don't read every line. Spend most time on your best project. The walk me through your resume guide shows the structure.
3. Why did you choose this branch or degree?
Give the honest reason, then show how your interest grew. "I chose ECE because I liked physics, and in second year I found I enjoyed the programming side of embedded systems more than circuits, which is why I'm applying for software roles."
4. What did you learn from your final-year project?
Name one technical lesson and one team lesson, with an example of each. Be ready to explain any technology you mention.
5. How would your friends describe you?
Pick two qualities and back each with a short example: "Dependable. I was the one who kept our project's GitHub organised and made sure we submitted on time."
6. What are your hobbies?
Mention one or two you actually do, and expect a follow-up. A hobby that shows discipline or learning (running, chess, coding contests, music practice) gives you more to talk about than "watching movies".
7. Did you have any backlogs? Why?
Answer truthfully; it's on your marksheet. Say what happened, that you cleared it, and what you changed. "One backlog in second-year maths. I underestimated it, cleared it the next semester, and started solving past papers weekly after that."
8. Is there a gap in your education? What did you do?
State the reason briefly (illness, family, exam preparation) and focus on what you did or learned during the gap. Our guide on explaining a gap in an interview has wording for different situations.
Motivation and company (questions 9–15)
9. Why do you want to join our company?
Give two specific reasons: the training program, a product or client area, the technology stack, or growth paths you read about. Generic praise ("it's a reputed company") sounds unprepared. See how to answer "why do you want to work here".
10. What do you know about our company?
Cover what they do, their main business areas, recent news you read, and where this role fits. Harvard's guide advises researching the company, field and position through its website, social media and industry news. Ten minutes on the company's careers page and latest annual report or press releases is enough.
11. Why should we hire you?
Match two or three things the role needs with proof that you have them, then add one quality that helps you learn fast. Our "why should we hire you" answer guide has samples.
12. Why do you want to work in IT when your degree is in mechanical or civil?
Show a real interest with evidence: courses, projects, a coding contest record. "I enjoyed the programming in my CAD and simulation work, took the NPTEL Python course and built two small tools for our lab."
13. Where do you see yourself in five years?
Describe growth within the field: becoming strong in a technology, taking ownership of modules, guiding juniors. Avoid "in your chair" or plans to leave soon. More in where do you see yourself in five years.
14. Are you planning higher studies (MBA, MS)?
Be honest but show commitment to the job. If you have no immediate plans, say you want to build experience first. If you might study later, say so calmly and focus on what you'll contribute now.
15. What kind of work do you want to do?
Name a direction that fits the role (development, testing, support, data) and say why, but show you're open to the company's training and allocation.
Strengths and weaknesses (questions 16–20)
16. What are your strengths?
Pick two that matter for the job, with an example of each. Harvard's guide lists "What strengths would you bring to this position?" among the common questions; answer the "to this position" part.
17. What is your greatest weakness?
Choose a real, fixable weakness that isn't central to the job, and explain what you're doing about it. Harvard's advice: be honest, take responsibility and focus on improvement. Our strengths and weaknesses guide has examples.
18. What is your biggest achievement?
Choose one where you did something specific, not just a group result. Say what made it hard and what changed because of your work.
19. Tell me about a failure.
Pick a real failure with a clear lesson, such as a missed deadline or a project demo that broke. Spend most of the answer on what you learned and did differently later.
20. What makes you different from other candidates?
Point to a combination: "Most candidates know Java; I've also deployed two projects on AWS and handled real users' bug reports."
Behavioral questions (questions 21–28)
Behavioral questions begin with "Tell me about a time…". Answer with a short situation, what you did (most of the answer), and the result. Freshers can draw on projects, internships, fests, sports, NSS/NCC, hostel committees or part-time work. Our guide to STAR method answers has full examples.
21. Tell me about a time you worked in a team.
Describe your role clearly; interviewers want to know what you did, not what "we" did.
22. Tell me about a conflict with a teammate.
Show that you listened, found the real disagreement and agreed on a way forward. Don't blame the other person.
23. Tell me about a time you led something.
Leadership doesn't need a title. Organising a fest event, coordinating a project or teaching juniors all count.
24. Tell me about a time you worked under pressure.
Exam weeks plus a project deadline is a fine example. Show how you prioritised.
25. Tell me about a time you made a mistake.
Own it, fix it, and show the lesson. Harvard lists this one ("a time when you made a mistake or failed") as a common question.
26. Tell me about a time you learned something quickly.
A new framework for a hackathon or a tool for an internship works well. Mention how long it took and what you built.
27. Tell me about a time you helped someone.
Keep the focus on what you did and the result for them.
28. Tell me about a time you disagreed with a teacher or senior.
Show respect and evidence: you raised the point politely, with data or reasoning, and accepted the final decision.
Situational and work-style questions (questions 29–34)
29. What would you do if you couldn't finish a task by the deadline?
Tell your lead early, explain where it stands, propose a new date or what can be delivered first, and ask for help if needed.
30. What would you do if your manager gave you a task you don't know how to do?
Clarify the goal, look for documentation and examples, try for a set time, then ask specific questions.
31. How do you handle criticism?
Give an example where feedback on your code, report or presentation made it better.
32. Do you prefer working alone or in a team?
Most jobs need both. Say which you enjoy and show you can do the other.
33. How do you keep learning?
Name concrete habits: a course you're doing, a newsletter, coding practice, a side project.
34. How do you manage your time?
Describe a simple system you actually use, such as a daily to-do list, calendar blocks or weekly goals.
Practical questions every fresher gets in India (questions 35–40)
| # | Question | How to answer |
|---|---|---|
| 35 | Are you willing to relocate? | Answer honestly. If yes, say so clearly. If you have limits, mention them now rather than after the offer. |
| 36 | Are you okay with night shifts or rotational shifts? | Say what you can manage. Many service and support roles need it; a clear "yes" or an honest "only day shifts" both beat a vague answer. |
| 37 | What are your salary expectations? | In campus hiring the package is usually fixed; say you're comfortable with the company's standard offer for the role. Off campus, give a researched range. See salary expectations answers for India. |
| 38 | Are you comfortable with a service agreement or bond? | Read the terms in the offer before you answer. If you accept them, say so; if you have questions, ask what the agreement covers. |
| 39 | Do you have other offers? | Be truthful. If you do, mention it neutrally and say why this role interests you. |
| 40 | Do you have any questions for us? | Always ask one or two. Harvard suggests "What do you see as the challenges for the person taking this job?" or "What do you enjoy most about working here?" |
A one-week practice plan
| Day | Practise |
|---|---|
| 1 | Write your 60-second introduction and say it aloud five times |
| 2 | Research the company: careers page, business areas, recent news |
| 3 | Write three stories (team, challenge, mistake) in situation-action-result form |
| 4 | Prepare strengths, weakness, five-year and "why us" answers |
| 5 | Decide your honest answers on relocation, shifts, bond and higher studies |
| 6 | Mock interview with a friend; record it and watch it once |
| 7 | Fix the two weakest answers; prepare two questions to ask |
Harvard's guide also says to know your resume: every line on it is fair game. Read yours the night before and be ready to explain each project, skill and certificate.
For mock interviews, InterviewGPT can transcribe your practice session and suggest answers in a STAR shape based on your own resume, so you can compare your answer with a structured one. Download it for Windows and use the free 10-minute sessions to practise questions from this list.
