HR Interview Questions India 2026: Answers for Freshers & Experienced Candidates

This is almost always the first question. It is not an invitation to recite your resume: the interviewer has already read it. It is an opportunity to tell a coherent professional story.

The formula that works: Present → Past → Future

1. Present: Who you are right now, in one sentence (current role + years of experience + specialisation)
2. Past: The 1–2 experiences that made you good at what you do
3. Future: Why this role is the logical next step

Sample answer: Fresher (Computer Science graduate): 'I'm a 2026 Computer Science graduate from [College], where I specialised in full-stack development and data structures. During my degree, I completed two internships: one at a fintech startup where I built an API for payment reconciliation, and one at an e-commerce company where I optimised database queries that reduced load time by 40%. I'm now looking to join a product company where I can work on real-scale engineering challenges, which is why I'm particularly excited about this SDE-1 role.'

Sample answer: Experienced (3 years, switching companies): 'I'm a software engineer with 3 years of experience at [Current Company], primarily working on our payment processing microservices in Java and Spring Boot. In that time, I led the migration of our transaction settlement system from a monolith to microservices, which improved our throughput by 3x. I'm now looking for a role where I can own larger end-to-end systems and work on problems at higher scale: which is what drew me to this position.'

What not to say:

• Don't list every project on your resume
• Don't say 'I am a hardworking, dedicated professional': everyone says this
• Keep it under 2 minutes (90 seconds is ideal)
• Don't end abruptly: the 'future' part gives the interviewer a natural cue to respond

This question gives you explicit permission to sell yourself. Most candidates underuse it by giving generic answers.

What the interviewer is really asking: 'What specific value do you bring that other candidates may not?'

The framework:

1. Match your strongest skill to a stated need in the job description
2. Back it with a specific example (one sentence)
3. Express enthusiasm for the team/problem, not just the company brand

Sample answer: Fresher: 'The role mentions building scalable APIs: that's exactly what I focused on during my internship at [Company], where I designed REST APIs that handled 10K requests per minute at peak. I also picked up Go in the last 3 months specifically because I saw it in your stack, so I can contribute to your core services early without a ramp-up period. I'm applying to your team specifically because the engineering blog post about your event-driven architecture challenge is exactly the kind of problem I want to work on.'

Sample answer: Experienced: 'I bring three things your role specifically needs: production experience with the scale you're operating at: I've managed services handling 2M daily active users: deep knowledge of your tech stack (Java, Kafka, PostgreSQL), and a track record of on-time delivery. In my last two projects, I was the delivery lead and both shipped on schedule. I'm confident I can contribute meaningfully within the first 90 days.'

The mistake most people make: Answering with company praise ('because Razorpay is a great company and I've always admired the product'). That explains why you want to join, not why they should hire you.

Strengths: Pick 2 strengths that are directly relevant to the role. Back each with a one-sentence example. Don't say 'hardworking' or 'team player': every candidate says these.

Better strength answers:

• 'I'm strong at breaking down ambiguous problems. In my last role, we had a performance issue with no clear root cause, and I systematically isolated it to a database index missing on a high-traffic query.'
• 'I pick up new technologies fast. I learned React in 3 weeks to fill a gap on my team and shipped a working feature in my second week with it.'
• 'I communicate clearly across technical and non-technical stakeholders. At my current company, I translated our system design trade-offs into product timeline conversations with the PM team, which helped us negotiate a 2-week extension for the right architecture decision.'

Weaknesses: the correct approach: Mention a real weakness (not a fake one disguised as a strength) and describe what you're actively doing about it.

Fake weakness (bad): 'I work too hard.' 'I'm a perfectionist.' These are transparent and make you look dishonest.

Real weakness + fix (good):

• 'I've historically been slow to ask for help when I'm stuck: I tend to try to solve things independently. I've been working on this by setting a 30-minute timer: if I'm blocked for 30 minutes, I ask rather than continue alone. It's made me more effective.'
• 'I find it hard to say no to scope additions mid-project. I've been working on this by being more explicit about trade-offs in sprint planning: I've gotten better at articulating what gets de-prioritised when something new is added.'
• 'I'm still building confidence in formal presentations to senior leadership. I've started volunteering to present in team meetings to get more reps.'

This question assesses ambition, self-awareness, and whether your trajectory aligns with what the company can offer.

What not to say:

• 'In your position' (sycophantic and unrealistic)
• 'I haven't thought about it' (lack of self-awareness)
• 'Running my own startup' (signals the company is a temporary stop)

The framework: Show growth ambition + alignment with the role's growth path

Sample answer: Fresher: 'In 5 years, I want to be a senior engineer who can design and own systems end-to-end: from architecture decisions to production reliability. I want to have contributed to a product that millions of people use, and ideally to have mentored a few junior engineers along the way. The SDE career track at your company, with the kind of scale I'd be working at from day one, is exactly the kind of environment where that growth happens.'

Sample answer: Experienced (SDE-2 targeting SDE-3): 'I see myself as a senior engineer or tech lead in 5 years: someone who is the go-to person for a technical domain within the team, sets the architecture standard for new systems, and helps grow the engineers around me. I'm currently focused on deepening my distributed systems knowledge, and a role like this one gives me the problems and scale to do that meaningfully.'

Sample answer: PM: 'I want to be a Group PM managing a product area with real P&L ownership in 5 years. I'm focused on building depth in the fintech/consumer product space, and a role like this one: owning a core user journey: is exactly the kind of ownership I need to develop toward that.'

This is one of the most important HR questions, and one of the easiest to answer badly.

Rules:

1. Never badmouth your current employer, manager, or team: even if you have good reason
2. Always frame the answer as being drawn toward something, not pushed away from something
3. Be specific about what you're looking for: vague answers ('better growth') are weak

Answers that work:

'I've been at [Current Company] for 3 years and I'm grateful for what I've learned. The team is good, but the engineering challenges at my level have become predictable: I'm maintaining systems more than building new ones. I want to be in an environment where the problems are still unsolved, and the role here offers exactly that.'

'My current company is scaling down the product area I work in. While my role is secure, the scope of work is narrowing. I'd rather proactively find a role where my skills are fully applied.'

'I'm specifically targeting fintech roles now: the intersection of real-time systems and financial data is where I want to build expertise for the next 3–4 years. My current company is in a different domain, and a transition is better made now than later.'

If you were laid off: 'My role was eliminated in a restructuring: my entire team of 6 was let go when the company decided to exit the [product area]. I have strong references from my manager and am now focused on finding a role that's a strong long-term fit.' Layoffs are common and carry no stigma: don't over-explain.

Q: What do you know about our company? Research before the interview: revenue, product, recent news, tech stack, mission. Show you've done more than read the homepage. Sample: 'Groww has 12M+ active investors, launched Groww Mutual Fund after the AMC licence approval, and is building toward an IPO. The engineering team is known for the real-time stock price infrastructure work: I read the eng blog post about the Redis geospatial work. I'm interested in working on problems at that scale.'

Q: What is your expected salary? Never give a number first if you can avoid it. Try: 'I'd like to understand the full role and growth trajectory before discussing compensation. Could you share the band for this role?' If pressed, give a range based on your market research (use AmbitionBox/Glassdoor): 'Based on my research and experience, I'm targeting ₹X–Y LPA, but I'm open to discussion based on the full package.'

Q: Are you interviewing elsewhere? Always say yes (even if it's only one other company). It signals you're a desirable candidate. 'Yes, I have a few active processes: but this role is my top preference because [specific reason].'

Q: Do you have any questions for me? Always prepare 2–3 questions. Good ones: - 'What does success look like in this role in the first 6 months?' - 'What is the biggest technical challenge the team is currently working through?' - 'How does the team make architectural decisions?' Never ask about salary, leaves, or WFH policy in the first HR round.