'Why do you want to leave your current company?' is the question designed to trip candidates into negative territory. Most candidates fear it. It is actually one of the easiest questions to answer well once you understand the framework: interviewers are not asking you to condemn your current employer. They are asking you to articulate what you want in your next role and why this specific role at their company addresses it. This guide gives you the framework, scripts for common (and difficult) situations, and the red flags that cost candidates offers.
The Framework: Pull Toward, Not Push Away
The single most important principle for this question: focus on what you are moving toward, not what you are fleeing from. Two versions of the same honest reason: Push away (weak): 'My current team has no senior engineers to learn from and the tech stack is outdated. I am stagnating.' Pull toward (strong): 'I have built strong foundations in Java and distributed systems at my current company. I am now looking for a role with a larger-scale system design challenge and a strong senior engineering culture to continue growing. Razorpay's payment infrastructure and the team's reputation for engineering excellence is exactly the environment I am looking for.' Same underlying reason. Different framing. The Pull version tells the interviewer exactly what kind of role motivates you and positions you as someone who has done their research on the target company, not just someone who is unhappy where they are.
Scripts for the Most Common Reasons for Leaving in India
Reason 1: Growth ceiling. Script: 'I have been at my current company for 3 years and have delivered consistently strong results, including X (one specific achievement). The scope of work available to me has plateaued: the team structure means the next career step would take 2+ years, and I am ready to take on more now. I am looking for a role where I can lead projects end-to-end earlier in my tenure.' Reason 2: Compensation below market. Script: 'I have been performing above my role's requirements for 18 months and the compensation has not kept pace with the market for my skill set. I want to move to a role where the compensation reflects my contribution and the market rate for engineers with my background.' (Do not say you are underpaid: say the market has moved.) Reason 3: Tech stack too legacy. Script: 'My current role involves maintaining a Perl and PHP stack from 2004. I have been using my personal time to build in Go and React, and I am looking for a role where my primary work involves modern systems. I want to build in the stack that the industry is building in.' Reason 4: Company direction / stability. Script: 'I am looking for a role at a company with a clear growth trajectory in a sector I am excited about. I want to be part of building something that is scaling, not stabilising.' (Does not require mentioning your current company's problems directly.)
How to Answer If You Were Laid Off or Let Go
This is the situation candidates fear most. The right approach is calm, factual, and forward-focused. For a layoff: 'My role was eliminated as part of a company-wide restructuring. The company reduced headcount across all departments by 20% in response to a funding situation. I was among approximately 150 engineers who were let go. I have been focusing on upskilling during the transition and am excited to bring everything I built there to a new challenge.' What makes this work: it is factual (layoffs are public information, verifiable), it contextualises without self-pity (200 people, not just you), and it pivots immediately to forward momentum. For a performance-based exit: this requires more care. 'The role and my strengths were not a strong match: the company needed someone with deeper [specific skill] which was not my primary focus. In the time since, I have [specific action taken to address the gap]. I am confident that the role I am applying for now is a much better fit because [specific alignment].' What to avoid: do not lie about whether you were fired or laid off. HR does reference checks. A factual, non-defensive answer to a difficult exit is respected far more than a discovered lie about it.
Practise answering 'Why do you want to leave?' with HireStepX's AI interviewer. Get feedback on whether your answer frames the transition positively and connects to the specific role you are targeting.
Practice freeRed Flags That Cost Candidates Offers
Four answers that frequently eliminate otherwise strong candidates. Excessive negativity about the current manager: 'My manager is micromanaging and does not respect my expertise.' Even if completely true, this makes the interviewer wonder if YOU are the difficult person in the relationship. The interviewer only has your side and will assume the situation is more complex. Naming colleagues who caused problems: 'My senior, Rahul, was difficult to work with and took credit for my work.' This is professional immaturity in an interview context. Save specific complaints for a reference check conversation if ever asked. Framing entirely around salary: 'I need to earn more money.' Salary is a legitimate reason but should be framed as market alignment, not personal need. 'I need more' signals that you will leave again the moment someone pays you more, which is a retention risk for the hiring manager. No answer at all: 'I just feel like a change.' This signals you have not thought about your career intentionally and are making a reactive decision. Interviewers want to hire people who know what they want and have chosen this company specifically, not people who are change-seeking generally.
Frequently asked questions
Explore more