Interview Tips: Top 20 HR Questions and Best Answers

Everyone says "be yourself" in interviews. Don't.

That's not cynicism. It's just honest advice that most interview guides won't give you because it sounds bad on paper. The version of yourself that shows up to work in a comfortable environment, after six months of settling in, after you know your colleagues and understand the unspoken rhythms of the office — that person is great. That person is probably worth hiring. But an HR interview is not the place to introduce that person. It's a performance. A specific, controlled, strategic performance. And the sooner you accept that, the better you'll get at it.

I've watched a lot of people walk into interviews being genuinely themselves — nervous, unprepared, honest about their weaknesses in ways that sound like confessions rather than self-awareness — and lose offers that should have been theirs. I've also seen people who are, frankly, less talented walk in with a clear structure in their head and walk out with the job. That gap is learnable. That's what this is about.

The 20 questions listed below are not surprising. HR interviewers across India — whether you're sitting in front of a TCS recruiter at a campus placement or across from a startup HR manager in Bengaluru — are pulling from a fairly consistent playbook. What makes the difference is not whether you've heard the question before. It's whether you've actually thought through your answer, and whether you understand what the interviewer is really trying to figure out when they ask it.

The Questions They Always Ask (And What They're Actually Asking)

Let's start with the one everyone butchers.

"Tell me about yourself."

This question is not an invitation to summarise your resume. They have your resume. They've read it. What they're asking is: can you communicate clearly, do you know what's relevant about yourself for this role, and do you have enough self-awareness to present a coherent narrative?

The formula that works — and has worked consistently, from what I've seen — is Present-Past-Future. Start with where you are now: your current role, your current skills, the work you're doing. Then briefly touch on how you got here: the education, the key experiences, the thread that connects your path. Then pivot to why you want this role, this company, this next step. Done in 90 seconds to two minutes, it's a strong, purposeful answer that doesn't feel like a monologue.

Here's roughly what that sounds like: "I'm currently a final-year engineering student at [college], where I've been focusing on software development — I've done two internships, one at a fintech startup and one at a mid-size IT firm, both doing backend work in Python. Before this, I got into coding through some personal projects during my first year, which led me to the internship path. I'm looking for a full-time role now where I can build on that backend experience, ideally in a team that values structured development practices — which is why TCS Solutions stood out to me."

Specific. Directional. Ends on why them, not just why you want a job.

"What are your strengths?" and "What are your weaknesses?"

These two travel together. One is easy to mess up by being vague. The other is easy to mess up by being either falsely modest or genuinely alarming.

For strengths: don't say "hardworking" or "good team player." Every single candidate says this. It means nothing. Pick one or two strengths that are specific, relevant to the role, and that you can back up with an example. "I'm good at breaking down complex problems" becomes credible when you add "— in my internship, I was given a performance bottleneck that had been open for three weeks. I mapped the data flow, found a redundant API call nobody had noticed, and cut load time by about 40%."

For weaknesses: this is genuinely tricky. The classic "my weakness is I work too hard" answer is now so played out that interviewers will actually mark you down for saying it — it signals you're either not self-aware or you think they're naive. Pick a real weakness, something that was genuinely a problem, but pair it with what you've done about it. "I used to struggle with public speaking — I'd lose the thread of what I was saying under pressure. So last year I joined a college debate club specifically to get reps in high-pressure speaking situations. It's not fully fixed, but I'm a lot better."

A real weakness handled with a real solution. That's what they want.

"Why do you want to work here?"

Here's the thing about this question: they can usually tell within about eight seconds if you've done research or not. "Your company has a great reputation" is not an answer. "I've read that you're expanding your cloud infrastructure practice and I've been specifically building skills in that area" is an answer.

Before any interview, spend 20 minutes on the company's LinkedIn page, their recent news, their job listings (which tell you what they're building towards), and if possible, talk to someone who works or has worked there. Even one Quora thread or a LinkedIn message to a junior employee asking about the culture can give you something genuine to say. That effort shows.

Situational Questions — Where Most People Freeze

A big chunk of HR interviews now use behavioural or situational questions. These are the ones that start with "Tell me about a time when..." or "Describe a situation where..." or "Give me an example of..." They're not asking about hypotheticals. They want a real story.

The tool here is the STAR method. Situation — what was happening? Task — what was your specific role or responsibility in that situation? Action — what did you actually do? Result — what happened because of what you did? It's a simple structure, but it stops you from rambling. It keeps your answer focused on you, specifically, rather than "we did this" or "the team handled it."

A few questions in this category that come up constantly:

"Tell me about a time you handled a conflict with a colleague."

HR is checking whether you can work with other humans without creating drama. The worst answers are either "I don't really have conflicts, I get along with everyone" (unbelievable) or a story where you were clearly right and the other person was clearly wrong and you're a little bit smug about it. What they want is: a real conflict, where you took initiative to address it directly, where you listened, and where the resolution was professional even if it wasn't perfect.

Something like: "During a group project in my third year, a teammate and I disagreed on the approach — I wanted to build a feature that would take longer but would scale better; he felt we were short on time and should cut scope. I set up a 30-minute call, we both laid out our reasoning, and we eventually agreed on a middle-ground approach — a simpler version of my idea that met the deadline. The project came out well and we submitted on time." Not dramatic. Professional. Shows communication, flexibility, initiative.

"Tell me about a time you failed."

Don't avoid this one. Don't pick a fake failure. Pick something that actually went wrong, own it cleanly, and then tell them what you took from it. The failure demonstrates honesty. The takeaway demonstrates growth. Both matter.

"Describe a time you worked under pressure."

Good STAR story territory. Pick something with a real deadline, a real problem, and describe your specific actions — not what happened around you, but what you did. Ended it with the result: "We delivered the presentation on time, the client was happy, and that experience taught me to build buffer time into any project I own now." Tidy. Done.

The Career Questions — Where You Need to Sound Like You've Thought Things Through

"Where do you see yourself in five years?"

This question has two failure modes. One is being too vague: "I see myself growing with the company and taking on more responsibilities." That says nothing. The other is being too specific in ways that signal you'll leave: "I want to start my own company in three years." Genuinely true for a lot of people, but probably not something to say in an HR interview for a job you're trying to get.

The answer they're looking for is: you have direction, you've thought about your growth, and that growth is plausibly aligned with what the company can offer you. "In five years, I'd like to be working at a senior level in backend architecture, ideally leading a small team. I think a company at your scale — with the kind of complex systems you're running — is exactly the kind of environment where I could develop towards that." You're showing ambition that fits the role. That's what they want.

"Why are you leaving your current job?" (or "Why did you leave your last job?")

Be careful here. Don't lie. They might check. Don't trash your previous employer even if they deserve it. HR people talk, industries are smaller than they look, and "my manager was impossible to work with" makes you sound difficult regardless of whether it's true.

Honest and forward-looking is the right register: "The role was good, but I've reached the ceiling of what I can learn there. I want to be somewhere with more complex challenges" or "The company went through a restructure and my team was affected" or "I'm looking for a role more focused on X, which wasn't possible in my previous position." All of these are true things people can say without burning bridges.

"What motivates you?"

Probably the most open-ended question in the standard list. And the most honest to answer, paradoxically. Think about what actually drives you at work — not what sounds good, but what actually makes you want to show up. For some people it's solving hard problems. For others it's shipping things people use. For others it's being part of a team that's building something ambitious.

Say that thing. Specifically. "I'm motivated by being given a hard problem without a clear answer and having to figure it out. I know that sounds a bit strange, but the phase where I'm completely stuck on something and then start to see the shape of a solution — that's genuinely what I find most satisfying about technical work." That's a real answer. It's memorable. It sounds like a person, not a template.

The Salary Question — The One Everyone Avoids Thinking About

"What are your salary expectations?"

This question is awkward and almost everyone handles it worse than they need to. Two common mistakes: giving a number too low because you don't want to seem greedy, or refusing to give any number at all and saying "I'm flexible" which just makes you seem like you haven't thought about it.

Research before the interview. Check Glassdoor, AmbitionBox, LinkedIn Salary — find what the market rate is for this role, at this company's size, in this city. Then give a range where your floor is actually your floor: "Based on my research and my experience level, I'm looking in the range of X to Y. That said, I'm open to discussing the full compensation package." That's it. Confident, researched, not a negotiation in the first interview.

One more thing on this: don't low-ball yourself hoping it makes you more hireable. It mostly doesn't. It makes hiring managers wonder why you don't value your own work. Know what you're worth and say it clearly.

The Questions You Ask Them

Most interviewers end with "Do you have any questions for us?" and most candidates either say no (bad) or ask something generic about growth or work culture (forgettable).

This is actually a chance to look sharp. Ask something specific. "What does success in this role look like at 90 days?" "What's the biggest challenge the team is working through right now?" "How does feedback typically work here — is it formal review cycles, or more ongoing?" These are the questions someone asks when they've already thought about actually doing the job, not just getting it.

Don't ask about salary or leave policy in the first interview unless they bring it up. Don't ask anything you could have found on their website in five minutes. And ideally, have two or three questions ready so that if one gets answered during the interview, you have backup.

The Complete List of 20 Questions to Prepare For

For quick reference, here are the 20 HR questions most likely to come up. We've gone deep on many of them above, but this is the full preparation list:

1. Tell me about yourself.
2. What are your strengths?
3. What are your weaknesses?
4. Why do you want to work here?
5. Where do you see yourself in five years?
6. Why are you leaving your current job?
7. Tell me about a time you handled conflict with a colleague.
8. Describe a time you worked under pressure or a tight deadline.
9. Tell me about a time you failed and what you learned from it.
10. What motivates you at work?
11. How do you handle criticism or negative feedback?
12. Describe your ideal work environment.
13. Are you a team player or do you prefer working independently?
14. How do you prioritise tasks when you have multiple deadlines?
15. What are your salary expectations?
16. Do you have any questions for us?
17. How would your previous manager or teammates describe you?
18. What's your greatest professional achievement so far?
19. Are you open to relocation or travel if the role requires it?
20. Why should we hire you?

Questions 11 through 20 follow the same underlying logic as the ones we've gone through in detail. They're checking your self-awareness (11, 13, 17), your organisational habits (14), your flexibility and fit (12, 19), your ability to articulate your own value (18, 20), and your genuine interest in the company (4, 16). Prepare for each with at least a rough structure in mind, even if you don't write out full scripts.

General Principles That Actually Help

A few things that cut across all of these questions:

Use specific numbers and details wherever you can. "I improved performance by 40%" is more credible than "I improved performance significantly." "I managed a team of five during this project" is better than "I had some leadership experience." Specificity signals that you actually did the thing, not just that you're claiming to have done it.

Don't over-rehearse to the point of sounding robotic. There's a version of interview preparation where you script every answer so precisely that you sound like you're reciting something in front of a live audience. Interviewers notice. Prepare the structure, not the exact words. Know the STAR beats, know your examples, but let the language come naturally in the room.

Silence is not failure. If you need five seconds to think before answering, take them. Say "That's a good question, let me think for a second" if you want to fill the silence. An interviewer watching someone genuinely think is not a bad sign to them. An interviewer watching someone panic and fill space with words that go nowhere is.

Body language matters, even on video calls. Eye contact. Not fidgeting. Sitting up rather than slouching. These things register below the conscious level of the interviewer but they do register. For video calls specifically: camera at eye level, not pointed up at your ceiling, decent lighting on your face, and check that your background isn't visually chaotic.

Research the company genuinely. This comes up in multiple questions — why do you want to work here, what do you know about us, how does this role fit your goals — but the underlying thing is the same. Do the 20 minutes of homework. Look at their LinkedIn, their recent news, their product or service, their stated values. It's not much effort and it makes a disproportionate difference to how you come across.

For campus placements specifically — companies like TCS, Infosys, Wipro, and Cognizant running large-volume drives at engineering colleges — the HR rounds tend to follow a very consistent format. "Tell me about yourself," strengths and weaknesses, situational questions, and a few questions about your long-term goals and your specific interest in that company. The volume of candidates they're screening means your answers need to be clean and tight. Meandering answers are easy to screen out. Direct, structured answers with real examples are what get you through.

What You're Actually Selling

Here's a useful frame to hold in your head while preparing. An HR interview is not really about the questions. The questions are just the delivery mechanism. What you're actually trying to communicate across the full conversation is three things.

First: that you can do this job. Your skills, your experience, your concrete examples — all of that builds the case that you're technically capable.

Second: that you'll fit here. Your communication style, your answers about conflict and pressure and feedback, your questions at the end — together they're making the case that working with you won't be difficult.

Third: that you want this specifically. Not just any job. This one. Companies — even large IT companies running campus placements with hundreds of candidates — do actually care about this. Someone who wants the job tends to work harder and stay longer than someone who took it because it was available. Your research, your genuine questions, your stated reasons for being interested in this company rather than just in employment — that's the evidence for the third thing.

Every question maps back to one of those three. When you're preparing your answers, it helps to ask yourself: what is this question trying to assess? Which of the three is it probing? Once you understand that, the right shape of an answer becomes fairly clear.

A Note on Authenticity

Back to where we started. "Be yourself" is bad advice — but be honest is good advice. Those aren't the same thing.

A strategic, structured, well-prepared interview performance isn't dishonest. It's showing up with the best version of your professional self. Actors prepare for performances. Athletes warm up before games. Lawyers rehearse arguments. Nobody says those people are being inauthentic because they showed up ready.

What would be dishonest is fabricating examples, claiming skills you don't have, or saying whatever you think they want to hear without regard for whether it's true. Don't do those things, not just for ethical reasons, but because they tend to unravel. Interviewers are usually more experienced than candidates at detecting inconsistency. And getting hired for a version of yourself that doesn't exist is a problem you haven't solved, just delayed.

But being prepared? Knowing how to structure your answers? Having thought through your examples in advance? Presenting yourself deliberately and strategically? None of that is inauthentic. That's just being ready.

So — be yourself in interviews. Just the version of yourself that's done the work to show up prepared. That's the one worth hiring.