The HR round is where freshers lose offers they technically earned. You cleared the aptitude test. You got through the technical round. Then a recruiter at TCS or Infosys asks "where do you see yourself in five years?" and you say something that makes them quietly mark you as a no-hire. The HR round interview mistakes that freshers make are rarely about knowledge. They're about saying the wrong thing with full confidence, in a round they assumed was a formality.
Here are the 10 specific things freshers say that tank their candidacy, and what to say instead.
"I'm a quick learner and a team player"
Every single candidate says this. Every one. The recruiter has heard it 40 times today. When you say it, you've just told them nothing about yourself while using up 15 seconds of their attention.
The problem isn't that it's false. It's that it's unverifiable. Anyone can claim it. Recruiters at large service companies process hundreds of candidates per drive. A generic claim gets a generic response: disinterest.
What to say instead: give a one-sentence story. "During my final year project, our backend broke two days before submission. I picked up Docker in a weekend to fix the deployment issue and we shipped on time." That's a quick learner. Show it, don't label it. The story takes the same 15 seconds and leaves a completely different impression.
"My biggest weakness is that I work too hard"
Recruiters are trained to spot this. It's not a clever dodge. It signals you're either dishonest or you haven't thought seriously about the question. Either way, it's a red flag that follows you into the debrief.
Name a real weakness. Then show what you're doing about it. "I get anxious when I have to present to large groups. I've been doing weekly stand-up presentations in my college tech club to get more comfortable with it." That answer is honest, self-aware, and shows initiative. It's the opposite of what most freshers give. Bonus: it's also easy to remember under pressure because it's true.
Saying you have no questions at the end
"Do you have any questions for us?" and you say "No, I think you've covered everything." This is a quiet disaster. It signals you're not genuinely interested in the role. It also wastes the one moment in the interview where you control the conversation.
Prepare two questions before every interview. Not "what's the salary?" Not "how many leaves do I get?" Ask something like: "What does the first three months look like for a fresher joining this team?" or "What's the most common reason freshers struggle in the first year here?" These show you're thinking beyond just getting the offer. They also give the recruiter something real to say about you in the debrief.
Giving a vague answer about your five-year plan
"I want to grow with the company" means nothing. Recruiters at Wipro or Cognizant hear this constantly. They're trying to assess whether you'll stay long enough to be worth training, and whether you have any self-direction at all.
You don't need a perfect plan. You need a directional one. "I want to spend the first two years building strong fundamentals in backend development, then move toward technical leadership on a product team." That's specific enough to be credible and flexible enough to be honest. If you're joining a service company, you can acknowledge the client project model: "I want to work across two or three client engagements to build breadth, then specialize." That kind of answer shows you understand the business you're joining.
Badmouthing your college, professors, or previous internship
This happens more than you'd think. A recruiter asks "tell me about your internship" and the candidate says "honestly it was unorganized, my manager didn't know what he was doing." Even if that's true, you've just shown the recruiter how you'll talk about them someday.
Keep criticism structural, not personal. "The team was small and we didn't have a formal review process, so I had to be proactive about getting feedback." Same situation. Completely different impression. The recruiter hears initiative instead of resentment. This applies to college too. "My curriculum was fairly traditional, so I supplemented it with personal projects" lands far better than "my college was useless."
Freezing on "tell me about yourself"
This is the first question in almost every HR round, and it's the one most freshers prepare least for. They either recite their resume line by line (boring) or ramble for three minutes without a clear point (exhausting to listen to).
Structure it in 60 seconds: who you are, what you've built or done, and why you're here. "I'm a CS graduate from VIT Vellore. I spent my final year building a ride-pooling app for our campus that got 400 active users. I'm here because I want to work on products that solve real logistics problems at scale." Done. Confident. Memorable. Practice it out loud at least five times before the interview. The version in your head always sounds better than the one you actually say the first time.
Negotiating salary without any data
Some freshers refuse to negotiate at all. Others name a number pulled from thin air. Both are mistakes that cost real money.
Know the band before you walk in. Check Glassdoor, AmbitionBox, or ask seniors from your college who joined the same company last year. If TCS's standard fresher package is ₹3.36 LPA but you've seen offers at ₹4.5 LPA for NQT high-scorers, you have ground to stand on. "Based on my research and my NQT score, I was expecting something closer to ₹4.5 LPA. Is there flexibility there?" is a real negotiation. It's specific, it's calm, and it gives the recruiter something to take back to their manager. "I want more money" is not a negotiation. It's a wish.
Claiming skills you can't back up for 60 seconds
You wrote "proficient in React" on your resume. The HR interviewer isn't technical, but they will sometimes ask "can you explain what React is in simple terms, for context?" Freshers who stumble here have just created a trust problem that follows them into the technical round. The technical interviewer will have read the same resume.
Only list skills you can explain to a non-technical person and demonstrate to a technical one. If you've used React for one project and you know what it does and why, that's enough. "Familiar with React, used it to build the frontend for my capstone project" is honest and defensible. "Proficient" when you've touched it twice is a liability that will surface at the worst possible moment.
Giving a rehearsed answer that doesn't match the question asked
Recruiters notice when you're delivering a prepared speech instead of responding to what they actually asked. They'll say "tell me about a time you handled conflict in a team" and you'll launch into a story about a successful project you're proud of. The stories don't match. Now they think you're not listening, or you're hiding something.
Practice answering the question that was asked, not the question you wanted. Record yourself doing mock HR rounds and read back the transcript. You'll catch this pattern immediately. It's one of the most common issues we see in session replays, and it's almost always fixable once you see it. Our guide on AI mock interview mistakes covers exactly how to use recorded sessions to catch this kind of drift before the real interview.
Treating the HR round as a formality
This is the root cause of most of the mistakes above. Freshers spend weeks on DSA and system design, then walk into the HR round assuming it's a rubber stamp. At service companies like TCS and Infosys, the HR round eliminates a real percentage of candidates who cleared the technical filter. At startups like Zepto or CRED, the HR round often carries more weight because culture fit is an actual hiring criterion with teeth, not a buzzword on a careers page.
The HR round is a structured evaluation with specific failure modes. Prepare your "tell me about yourself," your weakness answer, your five-year plan, and your two closing questions before every interview. Run a timed mock round. Say your answers out loud, not just in your head. The difference between a polished answer and a rambling one is almost always rehearsal, not intelligence. Candidates who treat this round seriously are a small minority. That's exactly why it's an opportunity.
Most freshers fail the HR round for the same reason they fail the first mock interview: they've thought about their answers but never said them out loud under real pressure. The candidate who gets the offer isn't always the most qualified. It's usually the one who sounds like they've been here before.
Prepare like that's achievable. Because it is.
Want to practice your HR round with an AI that asks the follow-ups a real recruiter would? Start with 3 free interviews — no credit card needed.