HR Interview Questions for Freshers: 40 Questions with Sample Answers

Freshers spend weeks on aptitude and DSA and fifteen minutes on HR. Then they lose an offer because they hesitated on "Are you willing to relocate?" or answered "What is your weakness?" with "I am a perfectionist." The HR round is short, but it is a real filter, especially at mass recruiters where the technical bar is clearly defined and HR decides between many technically qualified candidates.

This guide covers the forty questions you are most likely to hear in Indian campus and off-campus HR rounds. For each, you get what the interviewer is really checking and a sample answer. Do not memorize the samples word for word; replace every detail with your own. A recruiter who has heard the same internet answer fifty times that week will notice.

What the HR Round Is Really Testing

The format differs by company type. At large service companies (TCS, Infosys, Wipro, Accenture, Cognizant, Capgemini), the HR round is often combined with or right after the technical interview and focuses on relocation, documents and attitude. At product companies and startups, it is usually a "culture fit" or behavioural round with deeper follow-ups on your stories. Company processes change every hiring season, so confirm the current format with your placement cell or recruiter; our company guides such as TCS interview preparation describe the commonly reported rounds.

A Framework That Works for Any HR Question

1. Answer the actual question first. One direct sentence. "Yes, I am open to relocating to any location."
2. Give one piece of evidence. A specific example from college, a project, an internship or home. Specific beats impressive.
3. Connect it to the job. One sentence on why it matters for this role or company.
4. Stop. Most fresher answers go wrong in the second minute. Aim for 45 to 90 seconds.

For behavioural questions ("tell me about a time..."), use STAR: Situation, Task, Action, Result. Our STAR method guide has more examples. Spend most of your words on the Action, and always use "I" for what you personally did.

Questions About You: Q1-8

Q1. Tell me about yourself.

Testing: communication, structure, and what you choose to highlight. It sets the tone for the whole interview.

Use present, past, future: who you are now, two or three things you have done that matter for this job, and why you are here. Skip your family history and hometown details unless asked. Keep it under 90 seconds.

I am a final-year B.Tech Computer Science student at [college], graduating in 2026 with a CGPA of 7.8. Over the last two years I have focused on backend development. My main project is a hostel complaint tracker built with Spring Boot and MySQL that around 300 students in my hostel used last semester, and I did a two-month internship at a small Pune startup where I wrote REST APIs for their inventory module. I also solve DSA problems regularly and have done about 350 problems on LeetCode. I am looking to start my career in a company where I can work on real client systems and learn engineering practices at scale, which is why I applied here.

We have a full guide with variations for different backgrounds: how to answer "Tell me about yourself".

Q2. Describe yourself in three words.

Testing: self-awareness. The words matter less than the proof behind each.

Curious, dependable and calm. Curious because I picked up Docker on my own when our project deployment kept breaking. Dependable because in three group projects I was the one who integrated everyone's code before deadlines. Calm because during our hackathon demo, when the database crashed, I switched us to a local backup and we still presented.

Q3. Walk me through your resume.

Testing: whether your resume is truthful and whether you can explain it. Go in reverse chronological order, spend most time on projects and internships, and be ready to go deep on anything written there. If you listed a technology, expect a question on it. If you cannot explain it, remove it before the interview. Our fresher resume guide covers what to keep.

Q4. What are your hobbies?

Testing: whether you are a real person with sustained interests. Pick one or two you actually do and can talk about for a minute. "Reading" and "listening to music" invite the follow-up "what was the last book?" so have an answer. Hobbies that show discipline (running, chess, a sport, playing an instrument) or teaching (tutoring juniors) are useful but only if true.

Q5. Why did you choose engineering / computer science?

I enjoyed maths in school, but what made me choose computer science was building a small quiz app in Class 11 using a tutorial. The idea that I could make something other people use, from just a laptop, stayed with me. In college I found I enjoy the problem-solving side as much as building, which is why I spend time on both projects and DSA.

A specific trigger is better than "IT has good scope." Honest pragmatic reasons are fine if paired with what you have since come to enjoy.

Q6. You are from a non-CS branch. Why software?

Testing: commitment. Will you leave for a core job in six months?

I am from Electronics, and I found that the part of my course I enjoyed most was programming microcontrollers. In my third year I took the NPTEL course on Data Structures, built two web projects, and have been practising coding problems for over a year. I want a long-term career in software, and my electronics background helps me understand how systems work at a lower level.

See our guide for non-CS branch students moving into software.

Q7. Your CGPA is low. Why?

Do not make excuses or blame professors. Acknowledge it, give the real reason briefly if it is reasonable, and show the trend or the compensating evidence.

My CGPA is 6.9, mainly because of my first two semesters, when I struggled to adjust to college and did not manage my time well. From the third semester I have been above 7.5 each semester, and I put a lot of my time into practical skills: I built three projects and completed an internship. I know marks matter, and I have learned to plan my time much better.

Q8. Do you have any backlogs or a gap year? Explain.

Be accurate; this is verified during background checks (see our BGV guide). Give the reason in one line, show what you did during the gap, and confirm the current status.

I had one backlog in Engineering Mathematics in my second year, which I cleared in the next attempt. I currently have no active backlogs. / I took a year after Class 12 to prepare for JEE. I did not get the rank I wanted, but that year built my problem-solving foundation, which helped me in college.

Questions About the Company and Role: Q9-15

Q9. Why do you want to join our company?

Testing: whether you did any research and whether you will accept the offer. Mention two specific things: something about the work (domains, clients, products, training programme) and something about growth. Connect each to yourself. Ten minutes on the company's careers page, recent news and annual report highlights is enough. Our guide on researching a company lists where to look.

Two reasons. First, your company works with banking and retail clients across many countries, so as a fresher I would get exposure to large production systems that I cannot get elsewhere. Second, the structured training programme for freshers covers technologies like cloud and Java, which matches the backend direction I want to grow in. I also spoke to two seniors from my college who joined last year, and both mentioned the learning opportunities in their first project.

Q10. What do you know about our company?

Cover what they do, scale in broad terms, main business lines, and one recent development. Avoid quoting exact revenue or employee figures unless you are sure; "one of the largest IT services employers in India" is safer than a wrong number. Then close with why that interests you.

Q11. Why should we hire you?

You need freshers who can learn fast and be productive on a project quickly. I have shown I can learn independently: I learned Spring Boot on my own for my internship and delivered three APIs that went to production. I am comfortable working in teams, as I led integration in three group projects. And I am fully flexible on location and shifts, so you can place me wherever the need is.

Three reasons, each with proof, ending with something that removes a hiring risk.

Q12. Where do you see yourself in five years?

Testing: retention and ambition. Show growth within the company and the field. Avoid "in your chair" jokes and avoid naming a different career.

In five years I see myself as a strong engineer who owns modules end to end and mentors new joiners. I would like to have deep expertise in one area, probably backend or cloud, and earn certifications along the way. I want to grow with a company where that path exists, and from what I have learned about the career structure here, it does.

Q13. Are you comfortable working on any technology, including testing or support?

Testing: flexibility. Service companies assign projects by business need. Saying "only Java development" can cost you the offer.

Yes. I have a preference for backend development because of my projects, but I understand project allocation depends on business needs. Any role will teach me how real systems run, and testing or support work in particular would teach me how systems fail, which makes anyone a better developer. I would give it my best and grow from there.

Q14. What is your ideal job or work environment?

Describe things the company plausibly offers: clear goals, a team you can learn from, feedback, and real responsibility. Do not describe a startup culture when interviewing at a large services company, or vice versa.

Q15. Do you have other offers? Which company would you choose?

Be honest and do not play companies against each other as a fresher. If you have an offer, say so and explain why this one interests you. Many colleges have one-offer policies; know your placement cell's rules.

I have an offer from [company] through campus placement. I am interviewing here because the role is closer to backend development, which is what I want to do, so if selected, this would be my preference.

Strengths, Weaknesses and Personality: Q16-22

Q16. What are your strengths?

Pick two strengths relevant to software jobs (learning quickly, persistence in debugging, explaining things clearly, ownership) and prove each with a short example. Avoid listing five adjectives.

My biggest strength is persistence when debugging. In my internship, a report API returned wrong totals only for some users. It took me two days, but I traced it to a time zone conversion issue in our date filters and fixed it. My second strength is explaining things simply; I ran DSA doubt sessions for about thirty juniors in my department.

Q17. What is your biggest weakness?

Testing: honesty and self-improvement. Choose a real but non-fatal weakness, and spend most of the answer on what you are doing about it. Avoid disguised strengths ("I work too hard") and avoid weaknesses central to the job ("I don't like coding").

I used to find it hard to speak up in group discussions, even when I had ideas. I noticed it during project meetings, where I would share points privately with a friend later. To work on it, I started presenting our weekly project updates and joined the college's tech talks as a speaker. I am much more comfortable now, though I still prepare notes before important meetings.

Other honest options: overcommitting and then working late (fix: estimating tasks), spending too long polishing before asking for help (fix: a time box), or limited experience with a technology the role uses (fix: a course you are taking).

Q18. How do you handle pressure or deadlines?

I break the work into small parts and do the riskiest part first. Before our final-year project review, our deployment failed two days before the deadline. I listed what was left, took the deployment issue myself since I knew the setup, and asked a teammate to finish documentation in parallel. We fixed it with a day to spare. Under pressure I try to communicate early rather than hope things work out.

Q19. Are you a team player or do you prefer working alone?

The right answer is "both, depending on the work", with an example of each. Software is a team sport, but a candidate who can never work independently is also a concern.

Q20. What motivates you?

Choose something genuine and linked to the work: seeing users use what you built, solving hard problems, learning, or being trusted with responsibility. "Money" alone sounds like you will leave for a small hike; it is fine to mention financial independence alongside learning.

Q21. How do you take criticism?

I try to separate feedback on my work from feedback on me. In my internship, my mentor's first code review had about fifteen comments, mostly about naming and error handling. I went through each, asked about two I did not understand, and made a checklist from them. By my last month my reviews had very few comments. I would rather get feedback early than repeat a mistake.

Q22. Rate yourself out of 10 in [Java / communication / coding].

Give a realistic number, usually 6 to 7 for a fresher, and justify it. Saying 9 invites a hard follow-up question you may fail; saying 3 undersells you. "I would rate myself 7 in Java: I am comfortable with OOP, collections and exceptions, and I have built a Spring Boot project, but I have not yet worked on multithreading in a real project."

Situational and Behavioural Questions: Q23-29

Q23. Tell me about a time you failed.

Situation: In my third year, our team entered a college hackathon to build a bus-tracking app. Task: I owned the backend. Action: I spent most of the first day building features nobody had asked for and left integration with the frontend for the last few hours. It broke, and we could not demo the live tracking. Result: We did not place. What I learned was to integrate early and build the simplest end-to-end version first. In the next hackathon we had a working version in the first six hours and finished second.

A real failure, your own responsibility, and a specific change in behaviour afterwards.

Q24. Describe a conflict with a teammate and how you resolved it.

Show that you addressed the issue directly and respectfully and focused on the work. Never portray the other person as the villain.

In our final-year project, a teammate and I disagreed on whether to use Firebase or our own backend. We had been arguing in the group chat for days. I suggested we each list pros and cons against our actual requirements: we needed custom reports, which Firebase made harder. Seeing it written down, we agreed on our own backend, and I offered to help him with the parts that were new to him. The project went smoothly after that.

Q25. Tell me about a time you showed leadership.

Leadership for freshers is often informal: organizing a team, mentoring juniors, running a club event, taking charge when something broke. Describe what you initiated, how you got others to act, and the outcome with a number if you have one.

Q26. What will you do if your manager gives you a task you do not know how to do?

First I would make sure I understand what is expected and by when. Then I would spend a fixed amount of time researching on my own, through documentation, the codebase and internal resources. If I am still stuck after that, I would go to my manager or a senior with specific questions and what I have tried, rather than staying silent or asking without trying. I would also keep my manager updated if the timeline is at risk.

Q27. What if you disagree with your manager's decision?

Disagree privately, with reasons and data, then commit to the decision once it is made unless it is unethical. Interviewers want neither a pushover nor someone who argues in front of clients.

Q28. What would you do if you saw a colleague doing something unethical?

Ethics questions have clear expected answers: you would not participate, you would raise it through the proper channel (your manager or the company's ethics or compliance process), and you would not try to handle serious matters through gossip. Mention data privacy and client confidentiality where relevant; IT services firms take these very seriously.

Q29. Tell me about something you learned on your own.

I learned Git properly last year. Our project team kept overwriting each other's work by sharing zip files. I went through the official Git tutorial and a few videos, set up a repository with branches for each feature, and taught the team the basic workflow of pull, branch, commit and pull request. It took a week to settle in, but after that we had no lost work, and I now use Git for every project.

Relocation, Shifts, Bonds, Salary and Higher Studies: Q30-37

These questions are where Indian freshers lose the most offers, because hesitation reads as "may not join". Decide your answers honestly before the interview, ideally after discussing with your family, so you do not have to think on the spot.

Q30. Are you willing to relocate?

For service companies, location is assigned based on project needs, and an unconditional yes is usually expected. If you have a genuine constraint, say so honestly; it is better than reneging later. If you have a preference but are flexible, state it that way.

Yes, I am open to relocating to any location. If there is an option to state a preference, I would prefer Pune or Hyderabad, but that would not affect my decision to join.

Q31. Are you comfortable working in night shifts or rotational shifts?

Many client-facing projects support clients in other time zones. Answer honestly; if yes, say so plainly. If you have a real constraint (a health condition, for example), mention it briefly and ask whether the role requires it. Women candidates may also ask about the company's transport and safety policies for late shifts; that is a reasonable question.

Yes, I understand some projects support clients in other time zones, and I am comfortable with shifts as the project requires.

Q32. Are you willing to sign a service agreement or bond?

Some companies ask freshers to sign a service agreement covering training costs, while many do not; policies vary by company and change over time, so rely on the documents you are actually given. Before answering, understand the duration, the amount, and what triggers it. In the interview, if you have read the terms and are fine with them, say yes. If the terms were not shared, it is fair to say you are open to it and would like to see the details.

Yes, I understand the company invests in training freshers and it is reasonable to expect a commitment in return. I plan to build my career here for the long term, so I am comfortable with it. I would just like to read the terms in the offer documents.

Q33. What are your salary expectations?

For campus roles with a fixed, announced package, this is a formality: accept it. For off-campus roles, research typical fresher packages for that company tier and give a range, while signalling flexibility. Fresher pay varies hugely between mass recruiters, higher-tier tracks within the same companies, and product companies, so anchor to the role you applied for.

I am aware the package for this role is fixed, and I am comfortable with it. At this stage, the learning and the projects matter most to me.

For off-campus and lateral situations, see our salary expectations answer guide.

Q34. Do you plan to pursue higher studies (MS, MBA, M.Tech)?

Testing: retention. If you have already applied abroad for next year, an honest interviewer will not hire you into a long training programme, and that is fair. If, like most people, you are undecided, say that you want to build industry experience first.

Not in the near future. I want to build solid industry experience first. If I consider higher studies later, it would be to deepen what I am doing at work, and many companies support part-time programmes or certifications for that.

Q35. When can you join?

Freshers usually join after final exams and results, on the date the company sets. Know your exam schedule and when your final marksheet and provisional degree certificate are expected. If you have a genuine constraint, mention it now, not after accepting.

Q36. Do you have all your documents (marksheets, ID proof, education gap affidavit)?

Know which documents the company requires and keep originals and copies ready: Class 10 and 12 marksheets, semester marksheets, ID and address proof, PAN, and an affidavit or declaration for any education gap if the company requires one. Missing or inconsistent documents (a different spelling of your name across certificates, for instance) cause onboarding delays; fix them early.

Q37. Your family is in [city]. Will they let you move? / Tell me about your family.

Interviewers sometimes ask this to judge whether you will actually relocate. Keep it brief and positive and confirm you have discussed it: "My parents and I have discussed it, and they support me moving for work." You do not have to share personal details you are uncomfortable with, and questions about marriage plans or religion are inappropriate; you can politely steer back to your readiness to join.

Closing Questions: Q38-40

Q38. Do you have any questions for us?

Always have two ready. Ask about the work and growth, not about leave or salary hikes at this stage.

• "What does the training programme for freshers cover, and how is project allocation decided after it?"
• "What do freshers who do well in their first year here typically have in common?"
• "Which technologies are most new joiners working on currently?"

More options, and which questions to avoid, in our questions to ask the interviewer guide.

Q39. What will you do if you are not selected today?

I would ask for feedback if possible, work on the areas I fell short in, and keep applying, including to your company in a future drive if that is allowed. Every interview so far has taught me something, and this one has too.

Q40. Is there anything else you would like to tell us?

Use this to add one strong point you have not covered, or to reaffirm interest in one or two sentences: "Only that I am very keen on this role. I am flexible on location and shifts and ready to start whenever you need." Then thank them. Do not use it to start a new five-minute story.

Red Flags, Video-Interview Tips and Final Prep

For video HR interviews

• Test your camera, microphone and connection 15 minutes before. Keep a phone hotspot ready as backup.
• Sit facing a window or light, with a plain background. Put the camera at eye level.
• Look at the camera when you answer, not at your own video.
• Keep your resume and a notepad nearby, but do not read answers from the screen; it is obvious.
• If the call drops, rejoin immediately and send a short message to the coordinator.

A three-day HR preparation plan

1. Day 1: Story bank and self-introduction. Write your five stories in STAR form and your 90-second introduction. Record yourself once and listen back.
2. Day 2: Company research and India-specific answers. Research each company you are interviewing with. Decide your answers on relocation, shifts, service agreements and higher studies with your family, so they come out naturally.
3. Day 3: Mock interview. Ask a friend or senior to ask you fifteen questions from this list in random order. Note where you rambled or paused, and tighten those answers.

The HR round rewards preparation more than talent. A fresher who has thought through these forty questions, with real stories and honest logistics answers, will sound more confident than most candidates in the room, and that confidence is exactly what HR is looking for. For the bigger picture of the hiring season, see our off-campus placement strategy.

Frequently Asked Questions

Pranjal Jain

Ex-Microsoft SDE · IIT Kanpur · Founder of Prepflix. Helps engineers crack startup and product company interviews across India.