'Why are you leaving your current job?' is one of the most frequently asked and poorly answered questions in Indian tech interviews. Candidates either over-share (venting about their manager, complaining about salary, or revealing interpersonal conflicts), under-share (giving a vague non-answer that raises suspicion), or give an answer that contradicts the role they are interviewing for. This guide gives you the exact frameworks, example answers for different situations, and five red-flag answers that will cost you the offer.
Why Indian Interviewers Ask 'Why Are You Leaving?' — The Real Purpose
This question serves four distinct purposes for interviewers at Indian tech companies, and understanding each helps you answer it better. First: flight risk assessment. If you left your last three companies in under 18 months each, the interviewer wants to know whether you will leave this company just as quickly. They are looking for stability signals. Second: motivation alignment. If you say 'I want to work on AI/ML' but are interviewing for a DevOps role, there is a mismatch that suggests you will be unhappy and leave quickly. Third: culture signal. How you talk about your current employer reveals how you will talk about this employer. Candidates who immediately criticise their manager or team are a yellow flag for culture problems. Fourth: confirmation of narrative consistency. Interviewers at the same company compare notes: if you give different reasons to the technical interviewer and the HR interviewer, both will notice and flag it. Know your answer and deliver it consistently across every round.
Four Answer Frameworks That Work for Indian Tech Engineers
Framework 1 — Growth opportunity: 'I have built strong expertise in [backend Java services] at my current company, and I am now looking for a role where I can tackle [distributed systems at scale / mobile engineering / ML engineering], which this position offers directly.' Specific, positive, forward-looking — explains what you are moving toward, not what you are running from. Framework 2 — Technical challenge: 'I have worked on the same tech stack and problem domain for [N] years and want to expand into [Kubernetes, React Native, LLMs], which is central to this role.' Signals learning motivation rather than company dissatisfaction. Framework 3 — Domain or stage shift: 'I am currently at a service IT company and want to move to a product company where I can own features end-to-end and see the direct user impact of my work.' Or: 'I have been at a startup for 4 years and am now looking for the structure, mentorship, and scale of a mid-to-large product company.' Stage and domain transitions are universally respected reasons. Framework 4 — Total compensation realignment: 'I want total compensation aligned with the current market rate for my skills and experience, and I believe this role reflects that.' This is professional and common; avoid making it the only reason, but it is perfectly acceptable to name as one of several reasons.
Five Answers That Will Cost You the Offer
Five answer patterns that raise immediate red flags in Indian tech interviews: (1) Criticising your manager personally. 'My manager is incompetent', 'My manager plays favourites', 'My manager never listens to me.' Even if every word is true, this signals to the interviewer that you will say the same about your next manager. Replace: 'I am looking for a management style with more technical mentorship and visibility into engineering decisions.' (2) Salary as the sole reason. 'They underpaid me' or 'I am not earning what I am worth.' This makes you sound transactional. Replace: 'I want total compensation aligned with the current market, and this role offers that alongside [technical challenge / domain / company stage] that I am genuinely excited about.' (3) Interpersonal conflict. 'I do not get along with my team' or 'There is too much office politics.' Replace: 'I am looking for a team culture that prioritises [direct communication / engineering ownership / individual autonomy].' (4) Vague non-answer. 'Just looking for a change' or 'Time for something new.' These signal that you are hiding a real reason. Interviewers will probe harder when they get non-answers. (5) Short tenure without explanation. Being at a job for less than 12 months is common post-2022 layoffs, but leaving it unexplained raises eyebrows. Pre-empt it: 'I joined for [X] but the role changed significantly after a restructuring' or 'I was part of a layoff.'
Struggling with HR interview questions? HireStepX's AI voice coach gives you instant feedback on how you answer 'Why are you leaving?', 'Tell me about yourself', and other critical HR questions that determine whether you get the offer after clearing the technical rounds.
Practice freeHandling Special Situations: Layoff, PIP, and Short Tenure
Laid off: be direct and brief. 'My role was eliminated as part of a company restructuring. This is a pattern I have seen across the industry post-2022 and it gave me time to [upskill, work on open source projects, do a course]. I am excited to bring what I have learned to this role.' Interviewers understand layoffs in the 2022-2024 period: they do not require extended explanation. Performance Improvement Plan (PIP): this is the hardest to navigate. If you left because you were on a PIP, be prepared for a background check that might reveal it. The recommended approach: be honest that the role was not the right fit and the company offered a separation, focus on what you have learned and improved since, and let your technical performance in the interview demonstrate your current capability. Avoid lying (background checks increasingly verify termination reasons in India's larger companies). Short tenure (under 1 year): 'The role I joined for was significantly different from what was described during the interview process — after [N] months it became clear the team's direction had changed after a leadership transition. I made the difficult decision to look for a role that matched my actual skills and career goals.' This is honest, neutral, and explains the short tenure without blaming individuals.
Frequently asked questions
Explore more