By the time you reach the HR round, your technical or aptitude score already got you here. This round isn’t testing whether you’re competent — it’s testing whether you’re someone the company actually wants to hire, work with, and keep. That’s a different skill than the one that got you through the earlier rounds, and most freshers walk in unprepared for it because they assume it’s “just a formality.”
It isn’t. HR rounds reject candidates constantly, usually not because of a bad answer to a hard question, but because of a forgettable answer to an easy one. Here’s how to fix that.
”Tell me about yourself” — the question everyone gets wrong
This is not a request for your resume read aloud. The interviewer already has your resume. What they actually want is a 60-90 second narrative that connects your background to why you’re a fit for this specific role.
A weak answer: “I’m from Bangalore, I did my B.Tech in Computer Science from XYZ college, I have a CGPA of 8.2, I know Python and Java, and I did a project on…”
A stronger structure — past, present, why-this-role:
“I got into programming in my second year through a college hackathon, which led me to build a couple of personal projects around web development. Right now I’m finishing my final year, and I’ve been specifically drawn to backend systems — I interned for two months at [company] working on API development. I’m looking for a role like this one because it’s backend-focused at a product company, which is exactly the kind of work I want to go deeper on.”
Notice this version tells a story with a direction, ends by connecting directly to the role, and takes under 90 seconds. Practice this out loud — not memorized word-for-word, but comfortable enough that you’re not searching for words mid-answer.
”What are your strengths and weaknesses?”
Strengths: Pick one, back it with a specific example, don’t just list adjectives. “I’m good at problem-solving” means nothing on its own. “I tend to break down ambiguous problems into smaller pieces before jumping into code — that’s what let me finish my final-year project two weeks ahead of the deadline while two other teams were still debugging integration issues” is a claim with evidence.
Weaknesses: This is where most freshers panic and either lie (“I work too hard” — interviewers have heard this a thousand times and it signals you’re not being honest) or genuinely self-sabotage by naming something disqualifying for the role. The right answer is a real weakness that isn’t central to the job, paired with what you’re actively doing about it.
“I used to avoid public speaking whenever I could — I’d let teammates present group project work instead of doing it myself. I forced myself to present at two internal review sessions during my internship instead of opting out, and it’s gotten noticeably easier each time.”
This works because it’s specific, believable, not disqualifying, and shows active effort to improve — which is what’s actually being evaluated, not the weakness itself.
“Why should we hire you?”
Freshers often answer this with generic enthusiasm (“I’m a hard worker and a fast learner”). Every candidate says this. Instead, connect one specific thing about you to one specific thing the role needs.
“From the job description, this role needs someone comfortable working with ambiguous requirements from multiple stakeholders. During my internship, that’s exactly what I dealt with — the product spec changed twice in six weeks, and I was the one who kept the team’s task list updated as priorities shifted. I’d bring that same adaptability here.”
If you don’t know enough about the role to make this connection, that’s a sign to research the company and job description more before the interview — not a sign to fall back on generic phrasing.
”Where do you see yourself in 5 years?”
This isn’t really asking about your five-year plan. It’s checking two things: are you likely to stick around for at least a couple of years, and do you have any direction at all versus total aimlessness. You don’t need a rigid plan — you need to show you’ve thought about growth in a way that’s compatible with staying at the company.
“I want to go deep on backend engineering over the next few years — understanding system design well enough to make architecture decisions, not just implement features. I’d love for that growth to happen here if the role and the company are the right fit, which is part of why I’m interested in this specific position.”
Avoid two failure modes: sounding like you’ll leave in a year (“I want to start my own company”), and sounding like you have zero ambition (“I haven’t really thought about it”).
”Do you have any questions for us?”
Never say no. This is one of the most under-rated parts of the HR round — asking a genuinely good question signals engagement more than almost anything else you’ll say in the interview. Have two or three ready:
- “What does a typical first three months look like for someone in this role?”
- “What’s the biggest challenge the team you’d be joining is currently working through?”
- “How is performance evaluated for freshers in the first year?”
Avoid questions you could’ve answered yourself with two minutes on the company website (like “what does the company do?”) — it signals you didn’t prepare.
Salary expectation questions
If asked directly, don’t dodge with “I’m flexible” — give a researched range based on what similar roles pay (see our salary negotiation guide for how to find that number), and frame it as open to discussion: “Based on my research for similar fresher roles at companies this size, I was expecting somewhere around ₹X-Y LPA, but I’m open to discussing based on the full compensation structure.”
The mistake that costs freshers the most
It’s not a bad answer to a hard question. It’s low energy and disengagement — flat tone, one-word answers, no questions asked back, checking the time. HR interviewers are explicitly evaluating whether they’d want to work with you day-to-day, and flat, disengaged answers read as disinterest even when that’s not what you’re feeling. Show up like you actually want the job, because at this stage, that’s most of what’s being measured.
Once you’ve cleared the HR round, the offer conversation comes next — and that’s where knowing what’s actually negotiable matters. If you’re still building your shortlist, browse current openings on EasyPlace.
