15 HR Interview Questions for Freshers, With Sample Answers

The HR round is short, but it can still end your application. Interviewers are checking three things: whether you can communicate clearly, whether you will fit in and stay, and whether what you say matches your resume. Below are 15 questions freshers are asked again and again. For each one you get what the interviewer is really checking, how to build your answer, a sample answer, and what to avoid.

The sample answers are there to show structure, not to be memorised. The words in square brackets are yours to fill in with true facts. An interviewer can tell a memorised answer within a sentence, and a follow-up question will expose an invented one.

Before you start: the STAR method

For any question that begins "Tell me about a time…", answer in four parts:

• Situation: where and when, in one or two sentences.
• Task: what you had to do.
• Action: what you did. This is the longest part, so say "I", not "we".
• Result: what happened, with a number if you have a real one, and what you learned.

A good STAR answer takes about a minute to say. The most common mistake is spending most of it on the Situation and rushing the Action.

Questions about you

1. Tell me about yourself.

What they are checking: whether you can give a clear, relevant summary, not your life story.

How to answer: present, past, future, in about a minute. Say who you are now, two or three things you have done that are relevant to this job, and why this role is your next step.

Sample answer:

"I'm a final-year [B.Tech in Computer Science] student at [college]. Over the last two years I've focused on backend development. My main project is [a library management system in Java and MySQL that our department now uses for issue and return records], and I did a [two-month internship at a startup] where I wrote [REST APIs in Node.js]. I enjoy work where I can see real users depend on what I build, which is why I'm interested in this [software engineer] role."

Avoid: reciting your resume line by line, family details, or hobbies that do not connect to anything.

2. What are your strengths?

What they are checking: self-awareness, and whether you can back up a claim.

How to answer: pick two strengths that matter for the role, and give one concrete example for each.

Sample answer:

"I'm persistent with problems. In my [final-year project], our [image upload kept failing on large files]; I spent two evenings reading the [library's] documentation, found it was a [timeout setting], and fixed it. I'm also comfortable explaining technical things simply. I [ran the coding club's beginner sessions] for a semester."

Avoid: a list of adjectives ("hardworking, honest, team player") with no evidence.

3. What is your biggest weakness?

What they are checking: honesty, and whether you are working on it.

How to answer: name a real weakness that is not central to the job, then say what you are doing about it and what has changed.

Sample answer:

"I used to take on too much myself instead of asking for help. In my [second-year group project] that meant I [finished my part late]. Since then I've started breaking tasks down at the beginning and telling the team early when something is taking longer. In my [internship] I raised a blocker on the second day instead of the fifth, and we fixed it together."

Avoid: fake weaknesses such as "I'm a perfectionist" or "I work too hard". Interviewers have heard them hundreds of times.

4. Where do you see yourself in five years?

What they are checking: whether you will stay, and whether your plans fit this job.

How to answer: talk about the skills and responsibility you want to grow into, in a direction this company can offer.

Sample answer:

"I want to become a strong engineer in [backend systems] first: someone the team trusts with an important module end to end. In five years I'd like to be [leading a small piece of a product and mentoring newer engineers]. From what I've read about [your company's] projects in [domain], that's a path I can follow here."

Avoid: "doing an MBA", "starting my own company", or "in your chair". They may all be true, but they tell the interviewer you will leave.

Questions about the job and the company

5. Why should we hire you?

What they are checking: whether you understand the role and can match yourself to it.

How to answer: connect two or three of the job's requirements to things you have actually done, then add one quality that makes you easy to work with.

Sample answer:

"The role needs [Java, SQL and working with a team on a live product]. I've used Java and SQL in [my main project and the internship], and I've worked in a team of [four] with code reviews and deadlines. I also pick things up quickly: I [learned React in three weeks for my internship] because the project needed it."

Avoid: "because I need a job", or claiming skills you could not demonstrate if asked.

6. Why do you want to join our company?

What they are checking: whether you did any research, and whether you are genuinely interested.

How to answer: mention something specific: their products, the kind of projects they do, their training programme, or the domain. Then say why it matters to you.

Sample answer:

"I read that [your company] works on [banking software for clients across 40 countries], and that freshers go through [a structured training programme] before joining projects. I want to start my career somewhere I'll learn proper engineering practice on systems that large, and I liked that your [developer blog post on how you test releases] was about process, not just technology."

Avoid: "It's a big company with a good brand", or getting basic facts about the company wrong.

7. What do you know about our company?

What they are checking: preparation.

How to answer: before the interview, spend 20 minutes on the company's website and recent news. Know what they sell or build, who their customers are, roughly how big they are, and one recent development. Say three or four facts and finish with what interests you.

Avoid: guessing, or reading out numbers you are not sure of. "I'm not sure of the exact figure" is better than a wrong one.

8. What are your salary expectations?

What they are checking: whether your expectations are realistic for a fresher role.

How to answer: for campus or fresher hiring the package is usually fixed and already announced. Say that you are comfortable with it, and that learning matters more to you at this stage.

Sample answer:

"I understand the package for this role is [the one announced for campus hiring], and I'm comfortable with that. At this stage, the learning and the projects matter more to me."

Avoid: a number far above the announced package, or "anything is fine", which sounds like you have not thought about it.

9. Are you willing to relocate or work in shifts?

What they are checking: whether you will accept the posting you are offered.

How to answer: answer honestly. If you are flexible, say so plainly. If you have a real constraint, say it now: it is far worse to accept the offer and then refuse the posting.

Sample answer:

"Yes, I'm open to relocating anywhere in India, and I understand some projects need shift work. I'd adjust."

Avoid: saying yes when you mean no.

10. Are you comfortable signing a service agreement (bond)?

What they are checking: whether you plan to stay for the agreed period.

How to answer: many large service companies ask freshers to sign a service agreement for a period after training. Read the actual terms before you answer: how long it lasts and what you would owe if you left early. If you accept them, say so clearly. If something is unclear, it is fine to ask.

Sample answer:

"Yes. I understand it covers [the training period and the following year], and I'm planning to stay and grow here, so it isn't a concern for me. Could you tell me whether it starts from the joining date or after training?"

Avoid: agreeing to terms you have not read.

Questions about your experience

11. Tell me about a challenge you faced and how you handled it.

What they are checking: problem-solving under pressure. Use STAR.

Sample answer:

"Situation: In my final-year project, two days before our review, the [app crashed whenever two users saved at the same time]. Task: I was responsible for the [database part], so it was mine to fix. Action: I reproduced it with two browser windows, found that [both requests were updating the same row without a transaction], wrapped the update in a transaction, and wrote a small script that sent 50 saves at once to test it. Result: It stopped crashing, we presented on time, and since then I test anything involving shared data with more than one user."

Avoid: a challenge with no clear action by you, or one where the result was luck.

12. Tell me about a time you worked in a team, or disagreed with a teammate.

What they are checking: whether you can work with people, including when you disagree.

Sample answer:

"Situation: In a [hackathon] team of four, a teammate and I disagreed about [whether to build a mobile app or a website] in 24 hours. Task: We needed a decision within the first hour. Action: Instead of arguing, I suggested we list what each option needed and how long it would take. The list made it clear the [website] was the only one we could finish, and he agreed. I then took the part he was least comfortable with so he could work on [the design] he cared about. Result: We finished a working demo and [placed in the top five], and we still work together."

Avoid: blaming the other person, or a story where you were simply right and nothing else happened.

13. Tell me about a failure.

What they are checking: whether you own mistakes and learn from them.

How to answer: pick a real but recoverable failure, take responsibility for it, and spend most of the answer on what you changed afterwards.

Sample answer:

"In my [third year] I [failed to clear the coding round of an internship test] because I had only practised easy problems. I took it as a signal, made a plan of [two medium problems a day for three months], and tracked my mistakes in a sheet. In the next [internship test] I cleared the coding round and got the offer."

Avoid: failures that were someone else's fault, or "I've never really failed".

14. Why is there a gap in your education, or why are your marks low in one semester?

What they are checking: whether there is a problem you are hiding.

How to answer: give the true reason in one sentence, without excessive detail, then show what you did afterwards.

Sample answer:

"My marks dropped in [fifth semester] because [I was unwell for part of it]. I cleared the backlog the next semester, and my [last two semesters' grades] are back to my usual level."

Avoid: long explanations, blaming teachers, or inventing a reason. Inconsistencies are easy to check.

The question at the end

15. Do you have any questions for us?

What they are checking: interest and preparation. "No" sounds like neither.

How to answer: ask one or two genuine questions about the work or how you will learn, not about leave or salary.

Good questions to ask:

• "What does the training look like for freshers, and how are people assigned to projects after it?"
• "What would you expect a new joiner in this role to have learned by the end of the first six months?"
• "What technologies does the team I might join use day to day?"

How to practise

1. Write a short, honest answer to each of the 15 questions using your own facts, with the STAR structure for questions 11–13.
2. Say each answer out loud and record it on your phone. Most people are surprised by how long and how vague their first attempt sounds.
3. Cut every answer down to about a minute, then practise until it sounds like you talking, not like you reciting.

A mock HR interview asks these questions and gives feedback on your answers, so you can do step 2 with an interviewer instead of a phone. For the technical round, see 20 OS and networks questions with answers.

FAQ