The HR Round Is Not a Formality: How Freshers Lose Offers in the Last Twenty Minutes

A student called me in November, genuinely bewildered. He had cleared an online assessment, two technical rounds, and a system design discussion at a product company — four stages over three weeks — and had then been rejected after a twenty-five-minute conversation with someone from HR. "They only asked me about myself," he said. "There was nothing technical in it. How do you fail that?"

You fail it the same way you fail anything you did not prepare for. He had told the interviewer he was "looking for a place to learn and grow", had no idea what the company built, said his biggest weakness was that he "works too hard", and when asked why he had left an internship after six weeks, gave three different reasons in ninety seconds. None of that made him a bad engineer. All of it made him a risk, and the HR round exists precisely to price risk.

The pattern repeats every year, and it is one of the most avoidable losses in the entire placement process. Students spend six months on data structures and roughly zero hours on the round that decides whether the company wants to work with the person attached to those data structures.

What the HR round is actually assessing

It helps to know what the person across the table has been asked to find out. In most companies, the final conversation — whether it is run by a recruiter, an HR business partner, or the hiring manager — is checking four things, and technical ability is not one of them, because that has already been established.

The first is retention risk. Will this person still be here in eighteen months, or are they taking the offer as a placeholder while they wait for something else? Hiring and training a fresher is expensive, and a candidate who reads as a flight risk is a poor investment however good their code is.

The second is the ability to work with other people. Almost all engineering work is collaborative, and the round is looking for evidence that you can disagree without escalating, take feedback without collapsing, and describe a conflict without blaming everyone in it.

The third is honesty and consistency. Your resume, your answers in the technical rounds, and your answers here should describe the same person. Contradictions are noticed far more often than students think, and they are the fastest way to lose an offer you had already won.

The fourth is basic professional judgement: whether you turn up prepared, whether you know what the company does, whether you can hold a structured conversation with an adult you have never met. That is a low bar, and a surprising number of candidates walk under it.

The questions, and what they are really asking

Most HR rounds are assembled from the same fifteen questions. They look bland, which is why students under-prepare, but each one has a specific thing it is trying to establish.

The question	What it is actually testing	What a weak answer looks like
Tell me about yourself	Whether you can structure a two-minute narrative	Reciting your resume from Class 10 onwards
Why do you want to join us?	Whether you did ten minutes of research	"It's a reputed company with good growth"
Where do you see yourself in five years?	Retention risk, and whether the plan involves them	"Doing an MBA" or "starting my own company"
What is your biggest weakness?	Self-awareness and honesty	A strength in disguise — "I'm a perfectionist"
Tell me about a conflict in a team	Whether you handle friction like an adult	"I've never had any conflict with anyone"
Why this role and not the one you studied for?	Genuine interest versus desperation	Anything that sounds like you'd take any job
Do you have any questions for us?	Curiosity and preparation	"No ma'am, you've covered everything"

None of these require invention. They require having thought about your own history for two hours before the interview rather than for two seconds during it.

Do companies really reject candidates in the HR round?

Yes, and more often than campus folklore suggests. The rejection rate at this stage is lower than at the online assessment or the first technical round, but it is far from zero, and it is concentrated in a few recognisable failure modes.

The most common is a mismatch between what the candidate says they want and what the job is. A student who spends the conversation talking about how they intend to prepare for higher studies has told a service company that it will lose them after the training period. That is a rational reason to pass.

The second is inconsistency. If your resume says you led a project, the technical round revealed you wrote one module of it, and here you describe yourself as the person who "handled the whole architecture", the interviewer is not admiring your ambition. They are recalculating how much of everything else you said was true.

The third is compensation and location surprises. A candidate who discovers in the final round that the role is in a city they will not move to, or who reacts badly to the stipend during the training period, ends the conversation there. Read the offer terms before the round, not after it — our guide on what to check before signing a fresher offer covers the clauses worth knowing in advance.

The fourth, and the saddest, is simple lack of energy. Interviewers are human, and a candidate who sounds bored, exhausted, or resigned reads as someone who does not want the job. By the fifth round of a long placement season that is often just fatigue, but it costs offers all the same.

The STAR structure, without the jargon

Behavioural questions are the ones that begin "tell me about a time when". Students answer them badly not because their experience is thin but because they narrate in circles: background, more background, and then the interviewer's follow-up arrives before the outcome does.

The fix is a four-part shape that takes ninety seconds. Say what the situation was in one sentence. Say what you specifically had to do. Say what you actually did, in the most detail. Say how it ended, with a number or a concrete result if you have one. That is the whole method, and it is worth practising out loud on three or four stories from your own life until the shape is automatic.

Choose the stories in advance. You need roughly five: a project you finished under pressure, a disagreement you resolved, a mistake you made, something you learned quickly from scratch, and a time you helped someone else. Almost every behavioural question in an entry-level interview is a variant of one of these, and having them ready means you spend the round telling stories rather than searching for them.

The mistake story is the one students dread and the one that pays best. Interviewers are not testing whether you have ever failed — they know you have. They are testing whether you can describe a failure without either hiding it or drowning in it. "I under-estimated the integration work, we missed the deadline by a week, and now I plan backwards from the demo date" is a good answer. "I don't think I've made any major mistakes" is not.

What should I say when they ask about salary expectations?

For a fresher in a campus process, this question is usually informational rather than a negotiation, because the package is fixed and published. The correct answer there is straightforward: say you are aware of the advertised range, that it works for you, and that you are more focused on the role and the team at this stage. Trying to negotiate a standardised campus offer mostly signals that you have not understood the process.

Off campus there is more room, and the useful move is to ask before you answer. "Could you tell me the band you have budgeted for this role?" is a completely normal question and often gets a real answer. If you are pushed to name a number first, give a researched range rather than a single figure, and make it a range you would genuinely accept at the bottom of.

What loses offers is not asking about money; it is asking badly. Leading with compensation before the interviewer has raised it, refusing to give any indication at all, or reacting with visible disappointment all read poorly. Money is a legitimate part of the conversation — it simply has a place in the order of it, and this is also where the longer-term question of package versus career momentum is worth having thought about beforehand.

The questions you ask are part of the assessment

"Do you have any questions for us?" is not the polite end of the interview. It is the last scored item, and "no, everything is clear" is a wasted answer that a large fraction of candidates give.

Two or three genuine questions are enough. Ask what the first six months look like for someone in this role. Ask how new engineers are supported when they get stuck. Ask what distinguishes someone who does well here from someone who struggles. These are questions whose answers you actually want, which is what makes them sound real.

Avoid questions that a thirty-second look at the careers page would have answered, and avoid stacking questions about leave policy and appraisal cycles into the first conversation. There is a time for those, and it is after the offer letter, not before it.

Preparing for it in a week

This round does not need months. A week of light, deliberate work is enough, and most of it is writing rather than reading.

Write out your two-minute introduction and say it aloud until it stops sounding rehearsed — this is the single highest-return hour, because that answer opens every interview you will ever sit. Write your five stories in STAR shape, as bullet points rather than scripts. Spend twenty minutes on the company: what they build, who their customers are, one recent piece of news, and how the role you applied for fits into that. Prepare three questions. Then do one mock with a friend who is willing to interrupt you, because being interrupted is the part nobody practises.

If speaking under pressure is the specific thing that undoes you, that is a separate and fixable problem, and we have written about it at length in building spoken confidence for interviews. The HR round rewards clarity far more than vocabulary, and clarity is trainable in weeks.

The round in proportion

None of this makes the final conversation the most important part of your candidacy. You still have to clear the online assessment, you still have to write code in front of a stranger, and you still need a resume that gets read in the first place. The HR round cannot rescue a weak technical performance.

But it can end a strong one, and that asymmetry is the reason to take it seriously. You have already done the hard part by the time you reach it. Spending one week making sure you can explain who you are, why you are here, and what you did when something went wrong is the cheapest insurance available on six months of preparation.

Cleared the technical rounds and still not converting offers? Talk to a Career Call counsellor. We'll run a mock HR round, find the specific answers that are costing you, and rebuild them into something that sounds like you.