A candidate in Hyderabad cleared the technical round for a data analyst role last month. SQL questions, case study, Excel exercise. Nailed all of it. The hiring manager wrote “strong hire” in the feedback. Then came the HR round. The recruiter asked “why are you leaving your current company?” and the candidate spent 2 and a half minutes talking about how his manager didn’t appreciate his work and the appraisal was unfair and the company culture was “political.” He got rejected. Not because of the SQL. Because of the 2 and a half minutes.
That’s the thing nobody tells you early enough. The technical round and the HR round aren’t the “hard round” and the “easy round.” They’re not the “important one” and the “formality.” They test completely different things and both of them can kill your offer independently. A company needs to answer two questions before they hire anyone: can this person do the work? And can this person exist on a team without making everyone else’s life harder? The technical round answers the first. The HR round answers the second. Fail either one and it’s a no.
Most candidates spend 3 weeks preparing for one and 30 minutes on the other. That imbalance is where offers go to die.
Why Companies Split the Interview
Every hiring manager has a story about the candidate who was technically brilliant and then made the team miserable within 6 weeks.
The developer who aced the coding test and then refused to join standups because he thought they were beneath him. The analyst who solved the case study perfectly and then sent passive-aggressive emails to 3 departments in her first month. The sales guy who crushed the roleplay and then lied to a client in week 3 because hitting his target mattered more than the company’s reputation.
Technical ability without professional behaviour creates chaos. Professional behaviour without technical ability creates dead weight. Companies learned this by hiring the wrong people enough times. So they split the evaluation. One round for what you can do. Another for who you are while doing it.
Both rounds carry veto power. “Strong technical, weak HR” doesn’t get you hired. It gets you a note in the system that says “good skills, culture concern” and a polite rejection email.
The Technical Round (What They’re Really Watching)
The specifics change by role. Developers get coding problems. Analysts get case studies or data exercises. Marketing people get asked to walk through a campaign and explain the numbers. Finance candidates build models or interpret balance sheets. The format is different. The underlying question is always the same: if we hand you the actual work, can you do it?
Here’s what catches most candidates off guard though. The interviewer isn’t just checking your answer. They’re watching how you get to it.
There’s a reason for this. On the job, you won’t solve problems in silence at your desk and then email the answer to your manager. You’ll explain your thinking to a team lead who disagrees with you. You’ll walk a product manager through your analysis when they don’t understand what a cohort is. You’ll present a recommendation to a client who wants to know why you chose this approach and not that one. The interview is simulating those moments.
A developer who writes working code without saying a word gets a different evaluation than one who talks through the problem as they go. “I’m starting with the edge case because that’s usually where this type of function breaks.” That narration gives the interviewer a window into your reasoning. The final code might be identical. The evaluation won’t be.
A data analyst who gives the right answer but can’t explain the method gets a weaker score than someone who says “I used a cohort analysis instead of a simple average because customer behaviour shifts dramatically between month 1 and month 6 and the average hides that.” The reasoning is the interview. The answer is just proof that the reasoning works.
So many freshers treat technical rounds like college exams. Right answer equals full marks. But this isn’t an exam. It’s a simulation of working with you on a Tuesday afternoon when a problem lands on the team’s desk. The interviewer is asking themselves: would I want this person next to me when something breaks? If you think out loud, stay composed when you’re stuck, and treat the problem like a conversation instead of a test, the answer to that question becomes yes. Even if your final output isn’t perfect.
The HR Round (It’s Not What You Think It Is)
Here’s what most candidates believe: the technical round is where the real evaluation happens and the HR round is where they ask you about your hobbies and your 5-year plan and your strengths and weaknesses and it’s basically a vibes check that everyone passes.
That belief is why so many technically strong candidates get rejected after the HR round and never understand what went wrong.
The HR interviewer is evaluating something that’s harder to measure and harder to fake than technical skill. Self-awareness. Emotional maturity. How you talk about other people. How you handle questions that don’t have right answers. Whether you can organise your thoughts under pressure or whether you ramble for 4 minutes and then say “does that answer your question?” with a nervous laugh.
Take the “why are you leaving?” question. The honest answer for a lot of people is some version of “the pay is bad, the manager is worse, and the company doesn’t value me.” All of which might be completely true. But saying any of it tells the HR interviewer one thing: this person talks negatively about employers. Which means in 2 years, when they’re sitting in another interview, they’ll say the same things about us. That’s a risk no recruiter wants to take. So the candidate who says “I’ve outgrown my current role and I’m looking for broader responsibilities” gets the nod. Same underlying truth, minus the damage.
Or take the weakness question. “I work too hard” stopped being a clever answer about 15 years ago. Every HR interviewer on earth has heard it. At this point it just signals that you Googled “how to answer weakness question” and picked the first result. What actually works is naming a real thing. “I tend to get buried in details and lose track of the bigger deadline. I’ve started time-boxing my tasks to fix that.” That answer is honest, specific, and shows you’re working on it. Three things the interviewer is actually scoring. The “I work too hard” answer scores zero on all three.
But here’s what gets missed in all the question-by-question prep advice: the HR interviewer is also evaluating things you don’t know you’re being evaluated on. Whether you let them finish their question before you start answering. Whether you make eye contact or stare at the table. Whether your body language matches your words. Whether you seem rehearsed or reflective. These aren’t on a formal checklist. But every experienced HR professional has rejected a technically qualified candidate because something felt off. That “something” is usually one of these signals. You can’t prepare for them by memorising answers. You prepare by actually reflecting on your career, your choices, and your motivations until your answers come from a real place instead of a script.
One more thing about the HR round that candidates consistently underestimate. When the interviewer asks “do you have any questions?” and you say “no, I’m good,” you’ve just told them you don’t care about the team, the culture, or the work environment. You spent 40 minutes answering their questions about you and you have zero questions about them. That asymmetry registers. Ask something. “What does the team dynamic look like day to day?” “What does growth typically look like for someone in this role?” Even one genuine question changes the interviewer’s notes from “seemed disengaged” to “showed real interest.”
The Mistakes That Actually Cost Offers
The biggest one isn’t a mistake during the interview. It’s a mistake before it. Preparing for the technical round for 3 weeks and spending the night before Googling “HR interview questions” and memorising 5 answers. That imbalance is the source of almost every HR-round rejection for technically strong candidates.
The thing about memorised HR answers is that they sound memorised. HR interviewers are professionally trained to detect this. It is literally what they do for a living. A candidate who recites a rehearsed 3-minute “tell me about yourself” without pausing, without adjusting to the interviewer’s body language, without breathing, gives themselves away immediately. Not because the content is wrong. Because the delivery screams performance. And performance is the opposite of authenticity. And authenticity is the thing the HR round is measuring.
Speaking badly about a previous employer deserves its own paragraph because it kills more offers than any other single mistake. More than wrong answers. More than weak technical performance. More than showing up late. When you complain about your last company in an interview, the recruiter does one mental calculation: “this person will say the same things about us when they leave.” That calculation ends your candidacy. It doesn’t matter that your previous manager really was terrible. It doesn’t matter that the culture genuinely was toxic. The interview room is not the place to process that. Talk about what you learned. Talk about what you’re looking for. Leave the complaints for your group chat with friends.
The other thing that silently kills candidacies: treating the HR round as less important. Showing up sharp and focused for the technical round and then showing up relaxed and casual for HR because “the hard part is over.” The HR interviewer notices the shift. They notice when a candidate is performing at full energy versus coasting. And their feedback carries exactly as much weight as the technical interviewer’s. Sometimes more, because the hiring manager reads the HR feedback last and it becomes the final impression before they make the decision.
FAQ’S about HR Interview vs Technical Interview
Do all companies run separate technical and HR rounds? Most structured ones do. Some startups combine them into a single conversation where the founder asks both types of questions in 45 minutes. But at any company with an HR team and a defined process, expect at least two rounds. Sometimes three if there’s a managerial interview in between.
Can you get hired if you only clear the technical round? Almost never. Both rounds carry independent veto power. “Technically excellent but poor culture fit” is one of the most common rejection reasons in corporate hiring in India. The reverse is equally fatal. Being wonderful to talk to doesn’t help if you can’t do the job.
Is the HR round actually easier? It feels easier because nobody hands you a coding problem or a case study. But it tests something harder to fake: how well you understand yourself, your career, and your relationships with other people. A wrong answer on a technical question loses you marks. A wrong signal in an HR round loses you the offer. Both hurt. They just hurt differently.
How should preparation be different for each? Technical: practise role-relevant problems. Revisit past projects. Prepare to explain reasoning, not just deliver answers. Talk through your approach out loud during practice so it becomes natural during the interview. HR: reflect on your career story honestly. Prepare real answers for the 5 most common questions. Say them out loud to a mirror or a friend until they sound natural and not robotic. Research the company enough to ask one real question about the team or the culture.
When does salary come up? Almost always in the HR round. Sometimes early as a screening question. Sometimes at the end once the technical evaluation is done. Either way, it’s an HR conversation. Come prepared with market data and a researched range. Don’t wing it.
All the Best!
