The HR round decides more offers than people think. A strong technical candidate who rambles through “Tell me about yourself” or criticises their last manager can still lose the job. These are the HR and behavioural questions asked most in IT interviews in India, with answers that work.
One rule for all of them: answer first, then give one real example, then stop. For behavioural questions use STAR: the situation, your task, the action you took and the result, with a number if you have one.
HR interview questions
Why are you looking to switch from your current role?
Keep it positive and forward-looking: what you've learned where you are, and what you want next that this role offers. For example: 'I've learned a lot building internal tools at Acme. I want to work on customer-facing products at scale, which is what this role is about.' Never criticise your current company or manager.
What the interviewer listens for: Growth, not complaints, Links to this role.
What's your notice period, and is it negotiable?
Give the exact notice period, then show flexibility honestly: 'My notice period is 60 days. My company allows an early release once handover is done, and I can also discuss a buyout if needed.' Don't promise what you can't deliver.
What the interviewer listens for: A clear number, Flexibility.
What are your current and expected CTC?
State your current CTC accurately (fixed and variable), then give an expected range with a reason: 'My current CTC is 8 LPA. Based on the role's responsibilities and market rates for my skills, I'm looking for 11 to 12 LPA, and I'm open to discussing the overall package.' Research the range before the interview.
What the interviewer listens for: Current figure, Expected, with a reason.
Are you open to relocating, or to working from the office five days a week?
Answer clearly and honestly: 'Yes, I'm open to relocating to Pune', or 'I'm comfortable working from the office five days a week.' If there's a constraint, say it plainly with any flexibility you have.
What the interviewer listens for: A straight answer.
What is your greatest strength, with an example?
One strength that matters for this job, with a short real example and its result: 'I'm good at debugging production issues: last quarter I traced a memory leak that crashed our service weekly, and it hasn't happened since.'
What the interviewer listens for: One clear strength, A real example.
What's a weakness you're working on?
A real weakness that isn't central to the job, and what you're doing about it: 'I used to take on too much myself. I now break work into tasks and ask for help early, and our sprint planning has improved.' Avoid fake weaknesses like 'I'm a perfectionist'.
What the interviewer listens for: A real weakness, What you do about it.
Where do you see yourself in five years?
Show a direction that fits the company: 'I want to become a senior engineer who owns a product area end to end and mentors juniors, and I'd like to grow that here.' Avoid saying you plan to leave, start a business or switch fields.
What the interviewer listens for: Direction, Fits this company.
Why do you want to join us?
Mention something specific about the company (its product, customers, technology or culture) and connect it to your skills: 'Your team builds payment systems at huge scale, and I've spent three years on payment APIs, so I can contribute from the start.' Research the company first.
What the interviewer listens for: Something specific about us, What you bring.
I see a gap in your career. What did you do during that time?
Be honest and brief about the reason, then show you stayed sharp: 'I took eight months off for a family health situation. During that time I completed a Spring Boot course and built a small project on GitHub, and I'm ready to commit fully now.'
What the interviewer listens for: Honest reason, Kept skills current.
Why do you want to move from a service company to a product company?
Positive about both: 'At a service company I learned to deliver for many clients and to work with different technologies. Now I want to own one product for the long term, see the impact of my work on users, and go deeper.'
What the interviewer listens for: Ownership, Respect for past work.
Do you have any other offers right now?
Be honest and calm: 'Yes, I have one offer and I'm in process with two companies. This role is my first preference because of the product, so I'd like to see it through.' Don't invent offers to bargain.
What the interviewer listens for: Honest, calm answer.
Why should we hire you?
Match your skills to what the job needs, add evidence, and show attitude: 'I already know Java and Spring Boot from my internship, where I built two APIs that went live. I learn quickly and I'm keen to grow with a strong team.'
What the interviewer listens for: Skills that fit, Attitude.
Do you have any questions for us?
Always ask one or two real questions: 'What would success look like in the first three months?' or 'What are the biggest challenges the team is working on now?' Avoid asking about salary or leave first.
What the interviewer listens for: A real question.
We have a service agreement for two years. Are you comfortable with that?
A clear, honest answer: 'Yes, I understand the two-year service agreement and I'm comfortable with it.' If you have doubts, ask about the terms politely rather than refusing outright.
What the interviewer listens for: A clear answer.
Behavioural interview questions
Tell me about a time you missed a deadline. What happened?
Use STAR: the situation (a release with a hard date), what went wrong (an underestimated integration), what you did (told your lead early, re-planned, delivered the core part first), and what you learned (now you flag risks at the first sign and add buffer). Own the mistake. Don't blame others.
What the interviewer listens for: The situation, What you did, What you learned.
How did you handle a disagreement with a teammate on a technical choice?
Show you listened and used data: 'A teammate wanted MongoDB. I thought Postgres fit better. I asked for his reasons, then we built a small proof of concept with our real queries. The relational joins were clearly simpler, he agreed, and we documented the decision.' End with the outcome and that the relationship stayed good.
What the interviewer listens for: Listened first, Used data, Outcome.
Tell me about a mistake you made at work and how you fixed it.
Own it: what you did wrong, how you fixed it quickly, and how you prevent it now: 'I deployed a config change without testing it in staging and broke logins for 20 minutes. I rolled back, informed the team, and since then I've added a staging check to our pipeline.'
What the interviewer listens for: Owned it, Fix, Prevention.
Describe a time you worked under a lot of pressure.
Pick a real high-pressure moment and show how you prioritised and stayed calm: what was at stake, what you did first and why, how you communicated, and the result. 'I listed what had to ship, cut the nice-to-haves with my manager, and we released on time.'
What the interviewer listens for: Prioritised, Result.
Tell me about a time you pushed back on a requirement.
Show you pushed back with reasons and an alternative, not just a no: what the requirement was, why it was risky (cost, users, security), what you proposed instead, and the result.
What the interviewer listens for: Why it was wrong, Offered an alternative, Outcome.
Tell me about a time you had to learn a new technology quickly.
Name the technology, how you learned it fast (official docs, a small prototype, help from a senior), and what you delivered with it and when.
What the interviewer listens for: How you learned, Delivered with it.
Tell me about a time you helped a teammate who was stuck.
Describe how you helped (paired, explained, debugged together), what it unblocked, and what they learned, so it isn't only you fixing it for them.
What the interviewer listens for: What you did, Result.
Tell me about some tough feedback you received and what you did with it.
Quote the feedback briefly, how you felt but acted on it, and the specific change you made with its result. Shows you can take criticism.
What the interviewer listens for: The feedback, The change.
Describe a time you led something without being the manager.
Show initiative and influence without authority: the problem you noticed, how you got others to agree, what you led, and a measurable result.
What the interviewer listens for: Took initiative, Brought people along, Impact.
Tell me about a time you dealt with an unhappy client or user.
Show empathy and action: you listened, found the root cause, fixed or worked around it, kept the client updated, and followed up afterwards.
What the interviewer listens for: Understood the problem, Fixed and followed up.
Two urgent tasks land at the same time. How do you decide which comes first?
Explain your method: weigh business impact and urgency (customers affected, deadlines), check with your manager or stakeholders when it's unclear, communicate what will wait, and then do the most important one first.
What the interviewer listens for: Impact and urgency, Talk to stakeholders.
What's the biggest impact you've had on a project? Use numbers if you can.
One result with numbers and your exact part: 'I designed the retry logic for our payment service, which cut failed payments from 3% to 0.5% and saved about 2 lakh rupees a month.'
What the interviewer listens for: A number, Your part.
Practise the HR round
Choose “HR” as the round type in our AI mock interview. We measure filler words, long pauses and whether you covered what matters, then tell you what to fix.
Next: how to answer in 30 seconds.