How to Answer 'Why Are You Leaving Your Current Job?' in Indian Tech Interviews 2026

Two things this question evaluates: (1) Retention risk assessment: companies typically invest 6-12 months before an engineer becomes fully productive. Interviewers want to know whether you will stay long enough for that investment to return value. If your answer reveals a reason to leave that also applies to this new role (you are leaving because of 'too much work', and this role is also demanding), the interviewer calculates a high churn risk. Your answer should reveal a gap at your current company that this new company specifically fills. (2) Professional self-awareness and maturity: how you talk about your current employer reveals how you will talk about this employer someday. Candidates who speak disparagingly about their manager or company signal that they may have contributed to the problems they describe, and will likely have similar complaints in the future. The interview format is professional; your answer should be professional: honest and direct, but not a venting session. The interviewer does not need to know everything; they need to know enough to feel confident in your motivations.

Three-part answer structure: (1) Brief genuine positive (5-10 seconds): name one specific thing you genuinely learned or valued at your current role. This signals that you are a fair evaluator and can see value even in situations you are moving away from. Not a platitude ('it has been a great learning experience') but a specific thing ('the mentorship I received on system design in my first 18 months was genuinely valuable'). (2) The specific gap (15-20 seconds): name the concrete thing your current role lacks, with enough specificity that the interviewer understands it as a real constraint, not just a preference. Avoid emotionally loaded terms ('toxic', 'terrible'). 'The product has been in maintenance mode for 24 months and I have not shipped a new user-facing feature in a year' is specific. 'There is no growth' is vague. 'My manager is difficult' is unprofessional. (3) Why this role specifically fills that gap (15-20 seconds): connect to a specific aspect of the role or company that addresses your stated gap. 'This role at Swiggy specifically addresses this because I would be working on demand forecasting and supply optimisation at 300x the traffic of my current system, which is the scale exposure I am looking for.' This signals that you researched the role, not just the company brand.

Situation 1 (Stagnation): 'I have learned a lot about API design at [company]. In the last 18 months, though, the product scope has narrowed significantly and I have been maintaining existing features rather than building new ones. I am specifically looking for a role where I build systems at higher scale and face genuinely new technical problems. This role at Razorpay, working on payment infrastructure that serves 5 million daily transactions, is specifically that.' Situation 2 (Compensation): 'The technical experience has been strong and my team lead has been an excellent mentor. After 3 years, though, my compensation has not kept pace with the market for a mid-level backend engineer with my experience. I am looking for compensation that reflects current market rates while staying on the kind of challenging technical problems I have at my current company. This role does both.' Situation 3 (Layoff or shutdown): 'The product I was working on was sunset as part of a business reprioritisation. It was not a performance issue; the team was strong and the product was well-built, but the business priority shifted. I took the opportunity to reflect carefully on what I want to build next, and this role aligns well with both the domain and the technical challenges I am most motivated by.' Situation 4 (Limited scale): 'I have enjoyed building the [product type] at [company]. The company serves [X] users, which means the largest technical challenge I can face is limited by that scale. I want to build systems that serve 10-100x more traffic, which requires a different class of distributed systems problems. This role is specifically that opportunity.' Situation 5 (Culture mismatch): 'I have come to realise that the engineering culture, specifically the limited investment in code review and technical specs, is not the environment where I develop best. I am looking for a team where engineering quality practices are genuinely valued. I have read your engineering blog and the talks from your engineers at [conference], and this is the culture I am looking for.' Situation 6 (Career direction change): 'I have built strong [backend/frontend/data] foundations at [company], and I am looking to transition into [ML engineering/platform engineering/security]. I have been building the relevant skills via [specific certification or project], and I am looking for a role that gives me the environment to develop this new domain professionally. This MLE role at [company] is specifically where I want to make that transition.'

The five most damaging answers: (1) 'My manager is terrible / impossible to work with.' Even if true, this frames you as someone who attributes problems to others. Reframe: 'I am looking for a management style with more technical depth and mentorship than my current situation offers.' (2) 'The culture is toxic.' Too vague and emotionally loaded. Reframe to a specific practice: 'The team has a culture where engineers are rarely involved in design decisions before they are committed to. I work best when I can contribute to technical decisions early.' (3) Compensation as the only reason: 'I just want more money.' This signals you will leave for any higher offer. Pair compensation with a genuine growth reason. (4) Naming your new company or comparing it to your current company unfavourably in ways that could embarrass you. (5) Mentioning confidential information: unannounced products, unreleased financial results, internal conflict details, or competitor intelligence. None of this belongs in an interview.