# HR interview questions for freshers, with sample answers

By RoundAlpha team · Published 2026-09-30 · https://www.roundalpha.com/blog/hr-interview-questions-for-freshers

The HR round for freshers in India keeps coming back to the same fifteen or so questions: tell me about yourself, why should we hire you, strengths and weaknesses, relocation, night shifts, bonds, expected CTC, gaps and backlogs. Each has a short, honest answer that works, and the trick is to prepare the shape of each one and rehearse it out loud, not to memorise a script.

## Key takeaways

- The HR round checks fit, honesty and flexibility, not technical depth.
- Most HR questions for freshers repeat, so you can prepare every one in advance.
- Answer awkward questions (gaps, backlogs, a non-CS branch) briefly and truthfully, then move to what you did about it.
- For relocation, shifts and bonds, say yes only to what you can actually live with.
- Keep each answer under a minute or two, and rehearse them out loud rather than on paper.

## What does the HR round check for freshers?

The HR round checks whether you'll fit in, stay, and be straightforward to work with. By the time you reach it, the technical interviewer has usually decided you can do the work; HR wants to know whether you communicate clearly, tell the truth, and accept the practical terms of the job.

For freshers in India, especially in campus drives and mass hiring at service companies, the HR round is often short, sometimes fifteen or twenty minutes. That makes it feel like a formality, and that's exactly why people get caught out. A careless line about not wanting to relocate, a vague story about a gap year, or a salary demand far from the offered package can undo a strong technical round.

The good news is that the questions barely change from company to company. Below are the ones freshers hear most, each with a short model answer. Treat the samples as shapes to adapt, not lines to recite. Many people search for these as HR questions for a first resume-based interview; the answers below assume you have a CV with projects, an internship or two, and your degree.

## How do you answer “tell me about yourself” as a fresher?

Give a ninety-second story in three beats: what you're doing now, one or two things you've built or learned that matter for this job, and why this role is the natural next step. Don't recite your CV or start with your hometown and family.

Sample answer for a fresher: “I'm finishing my B.Tech in electronics and communication from a college in Pune. Over the last two years I've moved steadily towards software. I built a small attendance app for our department in Java with a MySQL database, and did a two-month internship where I wrote test scripts for a web portal. I enjoy the moment something I've written actually works for real users, and a graduate engineer role here is where I can build on that properly.”

If you're a career switcher, for example someone who worked in sales for a year before a coding course, keep the same three beats and make the switch the heart of the middle one. For the full method, see [our guide to answering “tell me about yourself”](https://www.roundalpha.com/blog/answer-tell-me-about-yourself).

## What is a good answer to “why should we hire you”?

Name two or three specific things you bring that match the role, back each with a quick example, and finish with your willingness to learn. Avoid claiming you're the best candidate; you haven't met the others.

Sample answer: “You're hiring freshers who can pick up a new stack quickly and work in a team. In my final-year project, four of us built a library management system and I learned the backend framework from scratch in about three weeks. I also handled our demo to the panel, so I'm comfortable explaining technical work to people. I'm not claiming I know everything, but I learn fast and I finish what I start.”

See [our guide to answering “why should we hire you?”](https://www.roundalpha.com/blog/why-should-we-hire-you-answer) for versions aimed at experienced candidates and career switchers.

## How do freshers answer strengths and weaknesses?

Pick one strength with a real example behind it, and one genuine weakness you're actively working on. The weakness should be real but not central to the job, and the second half of the answer should be what you're doing about it.

Sample strength: “I'm persistent with problems. When our college project's database kept losing records, I spent two evenings tracing it to a transaction we never committed, and after that I started writing small tests for every feature.”

Sample weakness: “I used to say yes to every task and then rush all of them. In my last semester I started writing a short weekly list and telling people honestly when I couldn't take something on. It's better, though I still have to remind myself.” Avoid the tired “I'm a perfectionist” line; HR panels hear it every day. See [our guide to strengths and weaknesses answers](https://www.roundalpha.com/blog/strengths-and-weaknesses-interview-answers) for more examples.

## Where do you see yourself in five years?

Say you want to be very good at a real skill, trusted with more responsibility, and still growing inside the company. HR is checking that you plan to stay a while and that your ambitions fit what this role can offer.

Sample answer: “In five years I'd like to be a strong developer who others come to for help, ideally leading a small module or mentoring new joiners. I'd also like to have gone deep in one area, perhaps cloud or testing automation, depending on where the projects take me.”

Don't say you plan to do an MBA next year or move abroad, even if you might. It isn't dishonest to keep your longer plans to yourself; it's simply not relevant yet. See [our guide to the five-year question](https://www.roundalpha.com/blog/where-do-you-see-yourself-in-5-years) for more.

## How do you answer “why do you want to join our company”?

Give one or two reasons that are specific to this company, such as its training programme, the kind of clients or projects it works on, or something you learned from someone who works there. Generic praise like “it's a reputed company” tells HR you haven't looked.

Sample answer: “Two things. Your training programme for new joiners is structured and long, which matters to me because I'm coming from a non-CS branch. And I read that your teams work across banking and retail clients, so I'd get to see very different systems early in my career.”

Spend twenty minutes on the company's careers page and recent news before the interview. See [our guide to answering “why do you want to work here?”](https://www.roundalpha.com/blog/why-do-you-want-to-work-here) for a fuller method.

## Are you willing to relocate?

If you genuinely can, say yes plainly and add a line showing you've thought about it. If you can't, say so honestly and early; a false yes leads to a reneged offer or an unhappy first year.

Sample answer: “Yes. I'm open to any location, and I've already talked it through with my family. If I had a preference it would be Bengaluru or Hyderabad, but it isn't a condition.”

Mass recruiters in particular usually assign locations after joining, so a rigid “only my home city” answer can end the conversation. If you have a real constraint, such as caring for a parent, mention it briefly and ask how location is decided rather than making demands.

## What should you say about night shifts and bond agreements?

Be honest and calm: say yes if you can accept them, and ask a clear question if you need to understand the terms first. HR asks these questions because some freshers accept and then drop out, and they'd rather know now.

On shifts, a good answer is: “Yes, I understand support and client-facing projects can need rotational or night shifts, and I'm fine with that. Could you tell me whether it's a fixed night shift or rotational?”

Some Indian IT and services companies ask freshers to sign a service agreement, often called a bond, promising to stay a set period or repay training costs. Read the actual document before you sign. In the interview, a good answer is: “I plan to stay and grow here, so a service agreement isn't a problem in principle. I'd just like to read the terms, like the duration and any amount, before I sign.” Never agree to terms you haven't seen.

## What should a fresher say when asked for expected CTC?

For most fresher roles the package is fixed, so say you're comfortable with the company's standard offer for freshers. If the role genuinely allows negotiation, give a researched range rather than a single number.

Sample answer for a campus or mass-hiring role: “I understand there's a standard package for this role, and I'm comfortable with it. At this stage the learning and the work matter more to me.”

For an off-campus role at a startup or product company where the salary isn't published: “Based on what I've seen for similar fresher roles in this city, I'd expect something in that range, but I'm open to discussing the full package, including learning and growth.” Look up real ranges for the role and city before the interview so you aren't guessing. See [our guide to salary expectations](https://www.roundalpha.com/blog/salary-expectations-interview-answer) for negotiating once you have experience.

## Why IT after a non-CS branch like mechanical or civil?

Tell a short, true story about when you started enjoying software, then prove it with what you've done since: courses, projects, certifications or coding practice. HR isn't against non-CS candidates; it just wants to see that the move is deliberate and not a fallback.

Sample answer for a mechanical engineer: “In my third year I used Python to automate the calculations for a thermodynamics lab, and I enjoyed that far more than the lab itself. Since then I've done a data structures course, solved problems regularly on coding practice sites and built a small inventory app. Core mechanical jobs are fewer in my area, but that isn't the main reason. I simply enjoy building software more.”

Never run down your own branch or say you chose it only because of your parents. Speak about your degree with respect; it taught you problem-solving that still counts.

## How do you explain a gap year?

Say briefly and truthfully what happened, then spend most of the answer on what you did during or after the gap that makes you ready now. A gap is only a problem if you seem evasive about it.

Sample answer for a gap spent preparing for exams: “After graduating I spent a year preparing for the GATE exam. I didn't get the rank I wanted, but the preparation made my fundamentals much stronger, especially in operating systems and databases. In the last few months I've built two projects and I'm now clear that I want to work in software development.”

For a health or family reason, one sentence is enough: “I took a year off to support my family through a health issue. That's resolved now, and I used the last part of the year to complete an online course in web development.” You don't owe HR private details.

## How should you answer questions about backlogs?

Admit the backlog plainly, say it's cleared (or when it will be), and mention what changed. Never hide it: companies usually check marksheets, and a hidden backlog discovered later looks far worse than one you mentioned.

Sample answer: “Yes, I had one backlog in engineering mathematics in my second semester. I didn't take the subject seriously at the start and underestimated it. I cleared it in the next attempt, and since then I've had no backlogs. It taught me to plan revision early instead of the week before.”

Check each company's eligibility rules before you apply. Many set a limit on active backlogs at the time of joining, and the exact rule varies by company and year, so read the current notice rather than relying on what seniors remember.

## What is a good answer to “tell me about a time you failed”?

Pick a real, modest failure, take clear ownership, and spend most of the answer on what you learned and did differently afterwards. HR wants to see self-awareness, not a disaster or a disguised success.

Sample answer: “In a hackathon in my third year, I insisted we build three features instead of one. We ran out of time and demoed something half-working, and we didn't place. I realised I'd pushed the team because I wanted to impress the judges. In my final-year project I suggested we finish one core feature properly before adding more, and we delivered on time.”

## How do you answer teamwork questions as a fresher?

Describe one specific team situation from a project, internship, college fest or sports team, what your role was, and how you helped the group get to a result. Use the situation, task, action, result shape, but keep it brief.

Sample answer: “For our final-year project, one teammate kept missing deadlines. Instead of complaining to our guide, I asked him what was going on. He was struggling with the frontend framework, so we paired for two evenings and I split his work into smaller pieces. He caught up, and we submitted on time.”

Avoid stories where you did everything and the team was useless. HR hears that as a warning sign about how you'll treat future colleagues.

## How do you handle pressure? A sample answer

Say you handle pressure by breaking work into small steps and prioritising, then give one real example of a tight deadline you met. A bare “I work well under pressure” proves nothing.

Sample answer: “During my internship, the week before a client demo, three bugs were assigned to me on the same day. I listed them, asked my mentor which one blocked the demo, fixed that first and kept him updated each evening. All three were closed before the demo. I've learned that pressure is easier when you're clear on the order of things and you tell people early if something is slipping.”

## What should you ask when HR says “any questions for us”?

Always ask one or two genuine questions about the role, training or team. Saying “no questions” can read as low interest, and a good question is your last chance to leave a strong impression.

- “What does the training for new joiners look like, and how long does it last?”
- “How are freshers assigned to projects and locations after training?”
- “What would a good first year look like for someone in this role?”
- “What's the next step in the process, and when should I expect to hear back?”

## What mistakes should freshers avoid in the HR round?

The biggest mistakes are inconsistency, over-rehearsed answers, and saying yes to terms you'll later refuse. HR often compares what you say with your CV and with what you told the technical panel, so keep your story consistent.

- Reciting memorised answers word for word, which falls apart at the first follow-up.
- Lying about marks, backlogs, gaps or skills. Background checks and marksheets catch it.
- Speaking badly about your college, professors or a past internship.
- Giving one-line answers with no example, or five-minute answers with no point.
- Agreeing to relocation, shifts or a bond you have no intention of honouring.
- Asking about salary and leave before the interviewer brings them up.
- Forgetting the basics: arriving late, a noisy background on a video call, or not having your CV open in front of you.

## How should you prepare and rehearse for the HR round?

Write a few bullet points for each question above, then say every answer out loud several times until the structure comes naturally. HR answers go wrong in speech, not on paper: you ramble, lose the thread, or freeze on an awkward question like a backlog.

1. List the awkward facts in your own profile, such as a gap, a backlog, a branch change or a low score, and prepare a two-sentence honest answer for each.
2. Write three to five bullet points, not full sentences, for every common question.
3. Record yourself answering on your phone and listen back for filler words and long pauses.
4. Ask a friend to play HR and throw follow-ups at you, especially “why?” after each answer.
5. The day before, read the company's careers page again and confirm your two reasons for joining.

## Can you practise the HR round with an AI mock interview?

Yes, and it helps because the questions arrive cold and the follow-ups depend on what you actually said. Reading answers silently doesn't prepare you for that.

On RoundAlpha, an AI interviewer asks questions built from your CV, pushes when an answer is thin, and gives you a report afterwards. It's a low-stakes way to hear how your answers to the gap-year or backlog question really sound before a real HR panel hears them. Whatever you use, end your preparation with an out-loud run-through; see [our guide to questions to ask the interviewer](https://www.roundalpha.com/blog/questions-to-ask-the-interviewer) for the last few minutes.

## Frequently asked questions

### How long is the HR round for freshers?

It varies by company, but in campus drives and mass hiring it's often short, commonly around fifteen to thirty minutes. Product companies and startups sometimes fold HR questions into a longer conversation with a manager.

### Can you be rejected in the HR round?

Yes. It isn't just a formality. Candidates are turned down for inconsistent or dishonest answers, refusing relocation or shifts the role requires, or seeming uninterested in the company.

### Should I answer HR questions in English or Hindi?

Answer in the language the interviewer uses, which for most IT and corporate roles is English. Simple, clear English is far better than complicated sentences. If you're nervous about spoken English, practise out loud daily for a couple of weeks beforehand.

### Is it okay to say I don't know in an HR interview?

Yes, if it's true. For a factual question, say you're not sure and how you'd find out. For a personal question, take a few seconds to think instead of saying “I don't know”; a short pause is fine.

### What should I wear to an HR interview as a fresher?

Formal or smart-formal clothes that are clean and comfortable: a plain shirt and trousers, or equivalent formal wear. For video interviews, dress the same from the waist up and sit somewhere quiet with good light.

### How do I answer if I have offers from other companies?

Be honest but polite. Say you have another offer or are in process elsewhere, and that this company is a strong preference for a specific reason. Don't use it as a threat, especially for fresher roles with fixed packages.

### What if HR asks about my family background?

Keep it to one or two neutral sentences, such as your parents' occupations and siblings, then steer back to yourself. HR often asks this as small talk; it shouldn't take more than a few seconds.