HR Interview Questions for Freshers, With Sample Answers

Last updated (2026-11-02)

These HR interview questions for freshers cover what the HR or behavioral round actually asks, with a short sample answer for each. The samples use a fictional fresher, so treat them as a shape to follow, not a script to memorise.

The guide covers Indian campus and off-campus hiring as well as new-grad interviews in the US, the UK and similar markets, and calls out where the norms differ (salary talk, bonds, personal questions, work authorization).

What the HR round checks

By the HR round, your technical fit is usually already assessed. HR is checking whether you will communicate well, work with a team, stay long enough to be worth training, and accept the practical terms of the job.

  • Communication: can you answer clearly in a minute or two without rambling?
  • Honesty and self-awareness: do your answers match your resume, and can you talk about mistakes calmly?
  • Fit and motivation: do you know what the company and role are, and why you want them?
  • Practical fit: location, joining date, shifts, service agreements and, outside India, work authorization.
Know your own resume line by line. Many HR questions are follow-ups on something you wrote, so build it carefully with the resume builder and read it again the night before.

The STAR method for behavioral interview questions

Behavioral questions start with "Tell me about a time when...". Answer them with STAR: a real story told in four short parts.

  1. Situation: one or two sentences of context (project, team, deadline).
  2. Task: what you specifically were responsible for.
  3. Action: what you did, step by step. This should be the longest part, and use "I", not only "we".
  4. Result: what happened, and what you learned. A modest, honest result is fine.

Freshers can draw stories from college projects, internships, hackathons, clubs, part-time jobs or volunteering. Prepare four or five stories in advance; one good story can often answer several questions. For 35 more questions by theme and a story bank method, see the behavioral interview questions guide.

HR interview questions for freshers with answers: about you

The opening questions. They set the tone for the rest of the round, so practise them out loud.

1.Tell me about yourself.

What they check: whether you can give a clear, relevant summary in about a minute. It is not a request for your life story. The full structure is in our self introduction guide.

Sample answerFictional fresher, about 60 seconds when spoken.

I'm Aditi, a final-year computer science student. Over the last two years I've mostly worked on backend development, and my main project is a library management API in Java with Spring Boot and PostgreSQL that our college library now uses for issue and return records.

Last summer I interned at a small fintech startup, where I wrote unit tests and fixed bugs in a payments reconciliation service. That taught me how much I enjoy working in a real codebase with code reviews.

I'm now looking for a software engineering role where I can keep building backend systems and learn from an experienced team, which is why this position interested me.

Avoid: reciting your resume line by line, starting with your family background, or listing marks from every year.

2.Walk me through your resume.

What they check: that you can connect the items on your resume into a story and that everything on it is genuinely yours.

Sample answer

I'll go in order. I studied computer science, and in second year I joined the coding club, which is where I started building projects. My first real project was a timetable generator; the bigger one is the library API, which I can go deeper into if useful.

Then came my internship, where I worked on testing and bug fixes. The skills section lists what I used in those projects, and I'm comfortable answering questions on any of them.

Avoid: listing a skill you cannot discuss for two minutes. If it is on the resume, it is fair game.

3.What are your strengths?

What they check: self-awareness, and whether you can back a claim with evidence.

Sample answer

I think my main strength is that I'm persistent with problems. In my library project, issue records were randomly duplicating, and it took me two days of reading logs to find a missing transaction boundary. I enjoyed that process rather than giving up.

I'm also fairly organised: I keep a simple task board for my projects, which helped me balance the internship with coursework.

Avoid: a list of adjectives ("hardworking, dedicated, passionate") with no example behind any of them.

4.What is your greatest weakness?

What they check: honesty and whether you are actively working on yourself.

Sample answer

I used to hesitate to ask questions, because I wanted to figure everything out myself. During my internship I spent most of a day stuck on a configuration issue that my mentor solved in ten minutes.

Since then I give myself a time limit: if I'm stuck for about an hour after trying the obvious things, I write down what I've tried and ask. It has made me faster and my questions better.

Avoid: fake weaknesses like "I'm a perfectionist" or "I work too hard". Interviewers hear them constantly and read them as evasive.

5.How would your friends or classmates describe you?

What they check: how you work with peers, seen from the outside.

Sample answer

Probably as the person who's reliable before a deadline. In group projects I'm usually the one who sets up the shared repository and keeps a checklist of who is doing what. A couple of friends would also say I explain things patiently, since I often helped juniors in the coding club debug their code.

6.Can you explain the gap in your education or your lower marks in one year?

What they check: that you are honest and that the issue is resolved. Common in Indian campus and off-campus hiring, where marks and backlogs are often screened.

Sample answer

In my second year I had a backlog in Engineering Mathematics, partly because I was dealing with a family health situation that semester. I cleared it in the next attempt, and my grades from third year onwards have been consistent. It taught me to plan my time earlier instead of leaving everything to the exam week.

Avoid: hiding a gap or blaming professors. A short, factual explanation plus what changed is enough.

7.What do you do outside of academics?

What they check: that you are a rounded person, and sometimes signs of discipline or teamwork outside the classroom.

Sample answer

I play badminton most evenings, and I was part of our college team's organising committee for the inter-college tournament. I also read a lot of tech blogs, especially engineering write-ups about how companies debugged production issues.

Avoid: claiming a hobby you cannot talk about. If you say you read, expect "What did you read last?"

Behavioral interview questions (answer with STAR)

Each sample below follows Situation, Task, Action, Result. Swap in your own real story.

8.Tell me about a time you worked in a team.

What they check: what you personally contributed, and how you coordinate with others.

Sample answer (STAR)

Situation: In a 36-hour hackathon, our team of four was building a food donation app.

Task: I owned the backend API and the database.

Action: I proposed we agree on the API contract in the first hour, wrote it as a shared document, and mocked the endpoints so the frontend teammates weren't blocked while I built the real ones.

Result: We had a working demo with a few hours to spare. We didn't win, but the judges liked the demo, and I've used the "agree on the contract first" habit in every group project since.

9.Describe a conflict you had with a teammate and how you handled it.

What they check: maturity. They want calm, respectful resolution, not a story where you were right and everyone else was wrong.

Sample answer (STAR)

Situation: In our final-year project, a teammate and I disagreed on whether to use a relational database or a document store.

Task: We needed to decide within a week to stay on schedule.

Action: Instead of arguing in the group chat, I suggested we each list our requirements and test the two main queries on both options. I also asked our guide for input.

Result: The relational option fit our data better, and my teammate agreed once we saw the comparison. We got along better after that because the decision felt fair to both of us.

Avoid: saying "I've never had a conflict" or criticising the other person.

10.Tell me about a time you failed.

What they check: ownership and learning. A real failure handled well is better than a disguised success.

Sample answer (STAR)

Situation: In third year I signed up for a competitive programming contest and a club event in the same week.

Task: I was responsible for the event's registration website.

Action: I underestimated the work, and the site went live a day late, so the club had to extend registrations. I apologised, fixed it, and wrote down what went wrong.

Result: The event still ran, but with fewer registrations than planned. Since then I break work into tasks with estimates before committing, and I say no earlier when I'm overloaded.

11.Tell me about a time you worked under a tight deadline.

What they check: prioritisation and staying calm under pressure.

Sample answer (STAR)

Situation: During my internship, a bug in the reconciliation report was found two days before a monthly release.

Task: I was asked to write tests that reproduced it and help verify the fix.

Action: I first wrote a failing test that reproduced the bug, shared it with my mentor so the fix could start immediately, then added tests for the related edge cases while the fix was in review.

Result: The fix shipped with the release, and the tests stayed in the suite. I learned that reproducing a bug first saves everyone time.

12.Give an example of when you took initiative.

What they check: whether you notice problems and act without being told, which matters a lot for new hires.

Sample answer (STAR)

Situation: Our college library tracked book issues in a spreadsheet, and records were often wrong.

Task: Nobody asked me to fix it, but I was learning backend development and saw a real use case.

Action: I spoke to the librarian about what went wrong most often, built a small API with a simple web form, and ran it alongside the spreadsheet for a month to compare.

Result: The library switched to it for issue and return records. It also became the main project on my resume.

13.Tell me about a time you had to learn something new quickly.

What they check: learning speed. Freshers are hired partly on how fast they can pick up the company's stack.

Sample answer (STAR)

Situation: On my first week as an intern, the team used Docker, which I had never used.

Task: I needed to run the service locally to start on my tickets.

Action: I followed the official getting-started tutorial in the evening, then read our project's Dockerfile line by line and noted anything I didn't understand to ask my mentor the next morning.

Result: I had the service running by day three and later updated the README with the setup steps I had struggled with, which the next intern used.

14.Describe a time you received critical feedback.

What they check: coachability. New engineers get a lot of code review feedback.

Sample answer (STAR)

Situation: My first pull request at my internship got many review comments.

Task: I needed to address them and get the change merged.

Action: The main point was that my functions were too long and untested. Instead of only fixing the lines mentioned, I asked my reviewer to explain the reasoning, then split the code and added tests.

Result: The next pull requests needed far fewer rounds. I now read the team's review comments on other people's code too, to learn the standards faster.

Motivation and company fit questions

15.Why do you want to work here?

What they check: that you researched the company and are not applying everywhere with the same answer.

Sample answer

From your engineering blog and the product itself, I can see a lot of your work is backend systems handling high volumes of transactions, which is exactly the area I want to grow in. I also liked that your graduate program has new engineers working on real product teams with a mentor, because that's how I learned the most during my internship.

Avoid: "It's a big brand" or "It's a good package". Both say nothing about the company.

16.Why should we hire you?

What they check: whether you can connect your skills to the role's needs in a confident, not arrogant, way.

Sample answer

The role needs someone who can work in Java backend services and write tests, and I've done both: my library API is in Spring Boot, and most of my internship was writing and fixing tests in a production codebase.

I'm not claiming I know everything, but I've shown I can learn a new tool quickly and take review feedback well, which I think matters most in the first year.

17.What do you know about our company?

What they check: basic preparation. Know what the company sells, who its customers are, and something recent about it.

Sample answer

You build payroll and HR software for small and mid-sized businesses, mainly sold as a subscription. I read about your recent launch of a mobile app for employees to view payslips, and I noticed several of your open roles mention moving services to the cloud, so I assume that's a big engineering focus right now.

Avoid: reading out the company's Wikipedia summary, or guessing facts you are not sure of.

18.Why this role and not another one?

What they check: that you understand what the role involves day to day.

Sample answer

I enjoy the backend side more than UI work: designing data models, writing APIs and debugging issues with data. This role is focused on backend services, so it matches what I've enjoyed most in my projects and internship.

19.Are you interviewing with other companies?

What they check: your timeline and how serious you are about them. Being honest is fine; you do not have to name the companies.

Sample answer

Yes, I'm in the process with a couple of other companies, which is normal at this stage of placements. This role is one of my top choices because of the backend focus, and I'd be happy to keep you updated if my timeline changes.

20.How do you handle pressure or stress?

What they check: a concrete method, not "I don't get stressed".

Sample answer

I break the work into small tasks and finish the most important one first, so I always have something done. If I can see I'll miss a deadline, I tell the person depending on me early rather than at the last minute. Outside work, playing badminton helps me reset.

Career goals and salary expectation questions

These test whether your plans fit the role. The salary question is handled differently in India and in the US or UK, so both are covered.

21.Where do you see yourself in five years?

What they check: that your goals are realistic and that this job is a step toward them, not a stopgap.

Sample answer

In five years I'd like to be a solid backend engineer who can own a service end to end: design, build, monitor and fix it in production. I'd also like to be mentoring newer engineers, the way my internship mentor helped me. I see this role as a strong foundation for that.

Avoid: "In your seat", or plans that clearly lead away from the company soon (for example, "I'll be doing an MBA abroad next year") unless that is genuinely true and you want to say so.

22.What are your salary expectations?

What they check: whether you are realistic and whether your expectation fits their budget. For campus roles in India the package is usually fixed and announced in advance, so the answer is simple. For off-campus roles, and in the US, UK and similar markets, research the typical range for the role and city first and answer with a range.

Sample answer (campus, package already announced)

I've seen the package shared with the placement cell, and I'm comfortable with it. For me the role and the learning matter most at this stage.

Sample answer (off-campus, US or UK new grad)

Based on what I've researched for entry-level backend roles in this city, I'm looking for something in the typical market range for new graduates. I'm flexible depending on the full package, including benefits and learning opportunities. Could you share the range budgeted for this role?

Avoid: naming a number with no research behind it, or quoting your friend's offer from a different company. In some US states and other places, employers must disclose a pay range in the job posting, so check the listing first.

23.Are you planning to do higher studies, like an MS or MBA?

What they check: whether you will leave soon after training. Common in Indian fresher hiring.

Sample answer

Not in the near future. I want to get real industry experience first, and I think working on production systems will teach me more right now than another degree. If I study further later, it would be to deepen what I'm already doing at work.

Avoid: lying. If you have already applied for a master's starting soon, it is better to say so than to leave a few months after joining.

24.Would you be open to a different role or team than the one you applied for?

What they check: flexibility. Large fresher batches are often allocated to teams after training.

Sample answer

Yes. My strongest interest is backend development, but as a fresher I'd be happy to start where the team needs me, especially if it's related to development or testing. I'd just like the chance to build backend skills over time.

25.What would success look like for you in your first year?

What they check: whether your expectations of a first job are grounded.

Sample answer

By the end of the first year I'd want to understand our codebase well enough to pick up tasks without much hand-holding, have shipped a few features to production, and be someone the team trusts to handle bug fixes in my area on my own.

26.How long do you plan to stay with us?

What they check: commitment, since training freshers is an investment.

Sample answer

I'm looking for a place where I can grow for the long term, not just a first job to put on my resume. As long as I'm learning and contributing, I don't see a reason to move.

Practical questions: relocation, bonds, shifts and your questions

These look simple, but a vague or dishonest answer here can cost you an offer later. Know your real constraints before the interview.

27.Are you willing to relocate?

What they check: whether you will accept the location they assign, which matters for large fresher batches and multi-city teams.

Sample answer

Yes, I'm open to relocating. I've lived away from home for college, so moving to a new city isn't a concern for me. If there's a choice, I'd slightly prefer Bengaluru or Pune, but it isn't a condition.

Avoid: saying yes if you genuinely cannot move. A preference is fine; just be clear about any real constraint.

28.Are you comfortable signing a service agreement or bond?

What they check: that you accept the offer terms. Some Indian employers ask freshers to sign a service agreement tied to their training. This is rare for new-grad roles in the US and UK.

Sample answer

I understand the company invests in training freshers, and I'm planning to stay for the long term anyway. I'd like to read the agreement terms carefully before signing, but in principle I'm comfortable with it.

Avoid: agreeing without reading the actual terms. Ask for them in writing before you sign.

29.When can you join? Do you have a notice period?

What they check: your availability. For final-year students it depends on exams and the degree completion date; for off-campus candidates already working, it is the notice period in your current contract.

Sample answer

My final exams end in May, so I can join any time after that. I'll have my provisional degree certificate shortly after the results, and I can share it as soon as it's issued.

30.Are you okay with night shifts or rotational shifts?

What they check: fit for support, operations or teams that serve clients in other time zones.

Sample answer

Yes, I understand some teams support clients in other time zones. I'm comfortable with rotational shifts. Could you tell me how often the rotation changes, so I can plan for it?

Avoid: agreeing to shifts you know you cannot do for health or family reasons. Say it politely now rather than after joining.

31.Are you authorized to work here, and will you need visa sponsorship?

What they check: a legal requirement in the US, UK, Canada, Europe and Australia. Answer factually; it is a normal screening question there, not a trick.

Sample answer (international graduate)

I'm currently authorized to work on my post-study work permit, and I'll need sponsorship later to continue beyond it. I'm happy to share the exact dates so your team can plan.

Avoid: guessing about your own status. Check your visa or permit dates before the interview.

32.How should I handle questions about my age, marital status or family plans?

What they check: ideally nothing, because these should not affect hiring. In the US and UK, interviewers generally avoid them because of anti-discrimination laws, and you should not volunteer this information. In India such questions still come up sometimes.

Sample answer (polite redirect)

I'd prefer to keep the focus on the role, but I can say I'm fully able to commit to the joining date, location and responsibilities we've discussed.

Avoid: getting defensive. A calm redirect to what the employer actually needs to know (availability, commitment) usually ends the topic.

33.Do you have any questions for us?

What they check: genuine interest. "No questions" can read as disinterest. Ask one or two about the work, the team or growth, not things clearly answered on the website.

Sample questions to ask

What does the first few months look like for a new graduate on this team? Is there a structured training program?

How do new engineers usually get feedback on their work?

What do people who do well in this role in their first year have in common?

Avoid: leading with leave, work-from-home days or salary revision in the first conversation. Those are fair questions, but better asked once you have an offer.

Put this guide to work

Build a one-page resume, check it against a real job description, then practice your answers out loud.

Frequently asked questions

How long should my answer to tell me about yourself be?

Aim for about 60 to 90 seconds when spoken. Cover who you are, one or two relevant projects or internships, and why you want this role, then stop and let the interviewer ask follow-ups.

How do I prepare for behavioral interview questions as a fresher?

Prepare four or five real stories from projects, internships, clubs or part-time work and practise telling each one with the STAR method. One good story can often answer several different questions.

Should I memorise HR interview questions for freshers with answers?

Memorise the structure and your key facts, not the exact words. Interviewers notice scripted answers, and a natural answer built on your own experience is more convincing.

Can a fresher be rejected in the HR round?

Yes. The HR round can reject candidates for unclear communication, answers that contradict the resume, or practical mismatches such as location, joining date or shift requirements.

How should a fresher answer the salary expectation question?

For campus roles with an announced package, say you are comfortable with it. For off-campus roles, research the typical range for the role and city beforehand, answer with a range, and ask what range is budgeted.