- Keep answers to one or two minutes. If the interviewer wants more, they will ask.
- Use one concrete example per answer. "I handled a production outage at 2 a.m." is more convincing than "I work well under pressure".
- Stay consistent with your resume and application form. HR compares them, and background checks confirm dates and job titles later.
- Be honest about constraints such as notice period, location or a planned exam. Surprises after an offer cost more goodwill than honest answers before it.
- Never criticise a current or former employer, even if the criticism is fair. It makes interviewers wonder what you will say about them.
HR interview questions and how to answer them
The HR round decides more offers than candidates expect. It checks whether you will fit the team, stay long enough to be worth training, and accept terms the company can offer. Prepare these questions as seriously as the technical ones.
Questions every candidate is asked
These come up in almost every HR round, whatever the role or level.
-
01 Tell me about yourself.
How to answer: Keep it under two minutes: who you are, what you have built or studied that fits this role, and why you applied here. Skip personal details unless asked. -
02 Why do you want to join our company?
How to answer: Mention something specific: a product they ship, the tech they use, or the kind of customers they serve. Generic praise ("good brand, good growth") sounds rehearsed. -
03 What are your strengths and weaknesses?
How to answer: Back each strength with a short example. For the weakness, pick a real one that does not block the role and say what you are doing about it. -
04 Are you comfortable with the location, shift timings and work mode?
How to answer: Answer honestly. If you have a constraint, say it now rather than after the offer, and mention any flexibility you do have. -
05 Do you have any questions for us?
How to answer: Always ask one or two: what the first 90 days look like, how the team is structured, or how performance is reviewed. Avoid asking only about leave and salary.
Questions for freshers
Without work history, HR focuses on your projects, your attitude and practical details such as bonds and relocation.
-
01 Walk me through your final year project.
How to answer: Explain the problem, your exact contribution, the tech you chose and why, and one thing that went wrong and how you fixed it. Interviewers dig into this, so know every line you claim. -
02 You have no work experience. Why should we hire you?
How to answer: Point to proof of effort: projects, internships, certifications, open source or competitive coding. Show that you learn fast and can take feedback. -
03 Are you willing to sign a service agreement or relocate?
How to answer: Many campus and fresher roles include a bond or training period. Read the terms before the interview so you can answer clearly. -
04 Where do you see yourself in three to five years?
How to answer: Show ambition within the field: owning features, mentoring juniors, going deeper in a technology. Avoid saying you plan to leave for higher studies soon.
Questions for experienced candidates
When you are switching jobs, expect questions about why you are leaving, your achievements, your notice period and your salary.
-
01 Why are you looking for a change?
How to answer: Focus on what you are moving towards (scope, technology, ownership), not complaints about your current employer. -
02 Describe the most complex problem you solved in your current role.
How to answer: Use the STAR format: situation, task, action, result. Quantify the result where you can, such as time saved, errors reduced or users served. -
03 What are your current and expected CTC, and what is your notice period?
How to answer: Know your exact fixed and variable split. Research the market range for the role and give a reasoned figure. If you can buy out or shorten notice, say so. -
04 Tell me about a disagreement with a teammate or manager.
How to answer: Pick a professional disagreement, show you listened to the other side, and explain how it was resolved. The interviewer is checking maturity, not who was right.