20 HR Interview Questions for Freshers (with Sample Answers)

The HR round is less about what you know than about how you communicate, how you make decisions and whether you actually want this job. It is not a test of perfect English or a flawless script.

Below are 20 questions freshers commonly hear, grouped by theme, each with what the interviewer is checking, a structure for your answer and a short sample written for a student. The samples show the shape of a good answer; replace every detail with your own.

What the HR round assesses

Most HR interviews come back to the same few things:

• Communication. Do you answer the question that was asked, clearly and briefly?
• Self-awareness. Can you name your strengths and gaps, and back both with examples?
• Motivation. Do you want this role at this company, or any job anywhere?
• Behaviour. How have you handled teamwork, disagreement, failure and pressure?
• Practical fit. Location, shifts, service agreements and salary. A mismatch here can end an application on its own.
• Consistency. Do your answers match your resume and each other?

For questions about you, use claim, evidence, link: say something about yourself, prove it with a specific example, and connect it to the job. For "tell me about a time" questions, use STAR:

1. Situation
2. Task
3. Action
4. Result

Questions about you

Keep each answer to about a minute, and only use examples you can discuss in detail.

1. Tell me about yourself

Checking: whether you can pick out what's relevant instead of reciting your resume.

Structure: present, past, future: who you are now, two or three relevant things you've done, and why this role is your next step.

Sample answer:

I'm a final-year Computer Science student, and most of my time outside class goes into web development. In our final-year project, an attendance system for the department, I own the backend and database. Last summer I interned at a small software company, fixing bugs in their billing module. I like building things people rely on, so a developer role on a product team is my next step.

2. What are your strengths?

Checking: whether you can prove a claim rather than list adjectives.

Structure: one or two strengths the role needs, each with a specific example and why it matters here. "Hard-working" says nothing on its own; the example does the work.

Sample answer:

I learn unfamiliar things quickly by breaking them into small steps. Our project needed email verification, which none of us had built. I split it into parts, read the documentation for each and had it working within a week. A first job means learning a new codebase, and that's the habit I'll rely on.

3. What is your biggest weakness?

Checking: honesty, and whether you're working on it. Disguised strengths such as "I'm a perfectionist" are recognised immediately.

Structure: a real weakness that isn't central to the role, one example of it, and what you're doing about it.

Sample answer:

I used to hesitate to speak up in groups. In a second-year project I didn't raise a doubt about our database design, and we had to redo part of it later. Since then I've volunteered to present our project reviews, and I write my points down before important discussions.

4. What is your greatest achievement so far?

Checking: what you value, and how you describe effort and results.

Structure: the goal, what you did and the result. Small is fine; for a team achievement, be precise about your part.

Sample answer:

Getting our college fest's registration site into real use. The organisers used paper forms, so three of us built a web form with a dashboard for the organising team. I built the backend and the spreadsheet export. It handled that year's registrations, and the committee asked us to run it again.

5. Why did you choose your branch, and this field?

Checking: whether your direction is a decision, and whether you'll stay in the field. Expect it when your degree and the role don't match.

Structure: how you started (honestly), when your interest became deliberate, and what you've done since.

Sample answer:

I chose Electronics because I enjoyed physics at school. A microcontrollers course had me writing C for the first time, and I enjoyed the programming more than the circuits. Since then I've completed a data structures course, practised problems regularly and built two web projects. Software is where I've spent my own time for the last two years.

Check that these five answers agree with each other and with your resume. The interviewer may ask about anything you mention.

Questions about the company and the role

These test whether you prepared. The company's website, careers page, job description and recent news cover most of what you need.

6. What do you know about our company?

Checking: whether you prepared, and whether you applied on purpose.

Structure: what the company does and for whom, one or two specific recent facts, and why they interest you. Don't guess at figures you can't source.

Sample answer:

You build software for hospitals and clinics, mainly for appointments and patient records. Your careers page says freshers train first and then join product teams, and you recently launched an app for patients. Healthcare interests me because mistakes have real consequences, and I'd like to learn how teams release software with that responsibility.

7. Why do you want to work here?

Checking: motivation beyond "you're hiring", and whether you'd accept an offer and stay.

Structure: link something specific about the company to something specific about you. If your answer would fit any company ("good work culture"), it's too general.

Sample answer:

Two reasons. Your freshers work on the product after training, and I want to build software that customers use. And my attendance project made me curious about keeping records accurate and secure, which is what your products do at a much larger scale.

8. Why should we hire you?

Checking: whether you can match yourself to the role with evidence, without overclaiming.

Structure: two or three requirements from the job description, each matched with evidence. Don't compare yourself with candidates you haven't met.

Sample answer:

The role asks for strong fundamentals, quick learning and teamwork. I've practised data structures in Java for two years. In my internship I learned an unfamiliar framework and shipped two bug fixes in my first month. Our final-year project runs on code reviews within the team. I don't have industry experience yet, but I learn quickly.

9. Where do you see yourself in five years?

Checking: whether your plans fit what the company offers, and whether you'll stay.

Structure: growth in skill and responsibility rather than a job title, linked to the path this company offers. A clear direction is enough.

Sample answer:

I'd like to be trusted with complete features, from design to release, and to have gone deep in one area, probably backend systems. I'd also like to help new joiners the way seniors helped me. From what I've read about your teams, that path exists here.

10. Do you plan to pursue higher studies?

Checking: whether you'll leave for an MBA or a master's degree soon after training.

Structure: answer honestly. If you do plan to study later, explain why work experience comes first.

Sample answer:

Not in the next few years. Real projects will teach me more about what to specialise in than another degree would right now. If I study later, it would be something that builds on my work.

Teamwork, pressure and setbacks

These behavioural questions treat how you acted before as a guide to how you'll act again, so answer with a real situation using STAR. Prepare four or five stories from projects, internships, clubs or part-time work; one story can often answer several questions.

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

Checking: how you work with others, and whether you can describe your own contribution rather than saying "we" throughout.

Structure: the team and its goal in one sentence, then one thing you did that helped the team, and the result.

Sample answer:

Four of us built a library management app for a course, and I handled the backend. Our frontend teammate kept falling behind because the API kept changing. I suggested we document the endpoints and agree on any change before making it. Integration went much more smoothly after that, and we submitted a week early.

12. Tell me about a conflict with a teammate

Checking: whether you can disagree respectfully, reach a decision and avoid blaming others.

Structure: a disagreement about work, not a personal feud: both sides fairly, how you resolved it and the outcome, even if you were wrong.

Sample answer:

A teammate wanted a NoSQL database for our project and I wanted a relational one. After two meetings going back and forth, I suggested we each list our data and queries and show them to our project guide. Our data was highly relational, so we went with that, and my teammate led the reporting work. I learned to argue from requirements, not opinions.

13. Tell me about a time you failed

Checking: whether you own mistakes without excuses, and what you changed afterwards.

Structure: a real failure (small is fine), plain responsibility, what you changed and evidence that it worked. Avoid disasters and successes in disguise.

Sample answer:

In my first college coding contest I solved nothing in the first hour. I'd only practised easy problems without a timer, which was my mistake. Afterwards I did timed practice every weekend and studied the problems I couldn't finish. In the next contest I solved three of the five.

14. How do you handle pressure and deadlines?

Checking: whether you plan, prioritise and communicate, or only "work harder".

Structure: your method and one example. It's fine to admit pressure affects you if you show how you manage it.

Sample answer:

I plan backwards from the deadline and flag risks early. Last semester our project demo fell in exam week. I listed everything that was due, agreed a split with my team so nobody was overloaded, and finished my part a week early. Most of my stress comes from starting late, so I start early.

15. Tell me about a time you showed leadership

Checking: initiative and influence, not a title. Interviewers know most freshers haven't managed anyone.

Structure: a time you took responsibility for an outcome and got others involved, and the result.

Sample answer:

Juniors in our coding club kept asking the same setup questions, so I wrote a short setup guide, ran two evening sessions and asked two classmates to take a topic each. More juniors started coming to the weekly problem-solving sessions, and the guide is still pinned in the club's group.

Practical and closing questions

These have fewer right answers and more honest ones. A mismatch on location, shifts or terms is better discovered now than after you accept an offer.

16. Are you willing to relocate?

Checking: whether you'll join where the company needs you. For large fresher intakes, the company often decides the location.

Structure: if yes, say so plainly. If you have a real constraint, state it honestly with how flexible you can be; saying yes now and declining later helps nobody.

Sample answer:

Yes. I've lived in a hostel for four years, so moving cities isn't a concern, and I'm comfortable going wherever the role is.

17. Are you comfortable with shift work or a service agreement?

Checking: whether you accept the conditions of the role, so neither side is surprised later.

Structure: find out the terms before the interview. Accept them if you can, and ask if something is unclear, such as how long an agreement runs.

Sample answer:

Yes. The job description mentions rotational shifts, which is fine, and I'm comfortable with the service agreement. Could you tell me whether it runs from the joining date or from the end of training?

18. Can you explain this gap or low score?

Checking: whether you're honest, and whether the issue is behind you.

Structure: a brief explanation without drama or blame, what you did about it, and evidence that it's resolved.

Sample answer:

I was unwell for several weeks in my fourth semester and had a backlog in one subject. I cleared it in the next attempt, and my results since then have been back to my usual level. It taught me to ask for help early.

19. What are your salary expectations?

Checking: whether your expectations fit the budget, and whether you've done any research.

Structure: campus packages are usually announced in advance, so say whether you're comfortable with it. Off campus, research similar roles through job postings and seniors, then give a range or ask for theirs. Replace X and Y below with your own figures.

Sample answer (off-campus):

From postings for similar fresher roles in this city and conversations with seniors, I understand the range is roughly X to Y a year, and I'd be comfortable within it. Could you share the range budgeted for this role?

20. Do you have any questions for us?

Checking: interest and preparation. "No, nothing" can come across as indifference.

Structure: one or two genuine questions that the website doesn't already answer, such as:

• What do the first six months look like in this role?
• How is a new joiner's team decided?
• What do people who do well in their first year have in common?

Sample answer:

Yes, two. What do the first six months look like in this role? And is there anything you'd recommend I learn before joining?

If a question catches you off guard, pause or say "Let me think about that for a moment." A pause reads better than a rushed answer you have to take back.

Before the interview

Work through this list the day before:

• Reread your resume and be ready to discuss anything on it
• Note the requirements in the job description that you match best
• Research the company: what it does, who its customers are, one recent development
• Prepare four or five STAR stories covering teamwork, conflict, failure, pressure and leadership
• Say "Tell me about yourself" aloud until it takes about a minute without notes
• Decide your honest answers on relocation, shifts, service agreements and higher studies
• Check the announced package, or research the salary range for an off-campus role
• Write down two questions to ask the interviewer
• Confirm the time and the venue or video link, and keep your ID and printed resumes ready
• For an online interview, test your camera, microphone and connection

Most of these questions start from your resume, so make sure it is current and accurate.