HR Interview Questions and Best Answers for Indian Companies 2026

'Tell me about yourself.' This is not a request for your biography: it is an invitation to make a compelling first impression. Structure: 1) Who you are professionally (2 lines: background + current status). 2) What you have built or achieved (2–3 specific highlights from your resume). 3) Why this opportunity (1 line connecting your trajectory to this role).

Fresher example: 'I am a final-year computer science student from VIT Chennai, graduating this June. During my studies, I built a food ordering app that processes 500+ orders daily in my college canteen: this gave me hands-on experience with React and Node.js in a real production environment. I also completed a summer internship at Freshworks where I worked on their CRM notification system. I am applying to Swiggy because I want to build products at the scale of millions of users, and Swiggy's engineering challenges in food logistics genuinely excite me.'

'What are your strengths?' Mistake: generic answers ('hardworking, team player, dedicated'). Strong answer: one specific strength + a concrete example that proves it. 'My strongest skill is breaking down ambiguous problems into structured solutions. In my final year project, we had a vague brief from our guide: I spent the first week structuring requirements, defining the tech stack, and splitting work across the team. We delivered the highest-graded project in our batch.'

'What is your weakness?' Mistake: false weaknesses ('I work too hard'). Strong answer: a real but manageable weakness + what you are doing about it. 'I sometimes struggle to delegate: I prefer to do things myself to ensure quality. I have been actively working on this: in my last project, I assigned specific modules to teammates and resisted the urge to rewrite their code, focusing instead on code reviews and guidance.'

'Why do you want to join this company?' Never: 'Good brand, good salary, job security.' Always: specific knowledge of the company's products, engineering challenges, or culture. 'I specifically want to join Razorpay because I have read about your payment API and how you solved the challenge of achieving 99.99% uptime during festive sale spikes. I want to work on systems where reliability is genuinely the product, not just a feature.'

'Where do you see yourself in 5 years?' Mistake: vague ambition ('leadership position'). Strong answer: specific skill growth + contribution trajectory. 'In 5 years, I want to be a senior engineer who can independently lead a feature from architecture to deployment. Specifically, I want to build deep expertise in distributed systems: the kind of problems Swiggy's logistics platform deals with every day. I see this role as the right foundation to build toward that.'

'What are your salary expectations?' Research first. Know the market rate for your role and experience level. Quote a number slightly above your minimum: this leaves negotiation room. 'Based on my research and similar roles in the market, I am expecting a total compensation of ₹8–10 LPA. I am open to discussing the structure of the package.' Never say 'Whatever you offer is fine': this signals that you have not done your research and weakens your negotiation position.

'Do you have any other offers?' Answer honestly but vaguely. 'I am in advanced stages with one other company but have not received a final offer yet.' If you have an offer, use it as leverage: 'I have an offer from [Company] at ₹X LPA, and I am genuinely more excited about this role. If we can get close to that range, I would love to join here.'

'Are you willing to relocate?' For companies with known relocation requirements (Paytm to Noida, Zerodha to Bengaluru): research before the interview. If genuinely open to relocation: 'Yes, I am open to relocating for the right opportunity.' If not: be honest: accepting a role you will leave in 3 months because you dislike the city hurts both you and the company.

'When can you join?' Give a realistic answer. Freshers: 'I can join after my graduation in June, so from 1st July.' Experienced: 'My current notice period is 60 days, so I can join by [date].' Mention buyout options if you are open to joining earlier.

The STAR method (Situation, Task, Action, Result) structures answers to behavioural questions. Every 'Tell me about a time when...' question should use this framework.

'Tell me about a time you worked in a difficult team.' Situation: 'During my third-year project, our team of 4 had a member who consistently missed deadlines and did not communicate blockers.' Task: 'As the project lead, I needed to get the project back on track without damaging team cohesion.' Action: 'I had a one-on-one conversation to understand what was blocking him: it turned out he was struggling with the technology stack. I paired him with another team member for two sessions, simplified his task scope, and set daily 10-minute check-ins.' Result: 'He completed his module on time in the final week, and we delivered the project successfully. I learned that blockers are usually solvable if you identify them early rather than waiting.'

'Tell me about a time you failed.' This question is designed to see self-awareness and learning orientation. Use a real failure, not a disguised success. Be specific about what went wrong. Focus on the lesson. 'In my second year, I submitted an assignment plagiarised from an online source: I was pressured for time and made a poor decision. The professor caught it, and I received a zero. The experience made me genuinely uncomfortable about integrity shortcuts: I have not repeated it.'

'Tell me about a time you handled conflict.' Use a professional context, not a personal one. Show that you resolved it maturely without making the other person look bad.