Suggest an editImprove this articleRefine the answer for “Changing jobs”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**The main goal of the answer is to show that you are not "running away" from something, but moving toward something.** **Key point:** talk about growth, challenges and goals, not about problems and people.Shown above the full answer for quick recall.Answer (EN)ImageThe main goal of your answer is to **show that you are not "running away" from something, but moving toward something** --- ## General principle > Do not talk about problems and people. > Talk about growth, challenges and goals. --- ## Universal answer structure (works for any field) 1. **Gratitude** - show that you respect your previous place. 2. **Reason** - focus on growth, not on dissatisfaction. 3. **Goal** - connect your move to a new stage of your career. **Formula:** > "I'm grateful to my current place, it gave me <something>, but right now I'm looking for opportunities to <develop in something> and I see this direction as the logical next step." --- ## Examples for IT (Frontend / Backend / Fullstack / DevOps) ### Option 1 - growth and scale of tasks > I like what I've been doing at my current place, I gained good experience, but the tasks there started to repeat themselves. > Right now I'm interested in developing further - working with more complex architecture, distributed systems and a modern stack. > I want to feel that I'm growing technically and creating a tangible product effect. --- ### Option 2 - technology stack > At my current place I worked in a stable environment, but the technology stack there is a bit outdated. > It matters to me to develop with modern tools - for example, Next.js, NestJS, TypeScript, Docker, CI/CD, microservice architecture. > So I'm looking for a project where the technology matches my growth direction. --- ### Option 3 - impact and product > At my previous place I worked on narrow tasks and didn't always see the impact of my work on the product. > Right now I want to take part in the full cycle: from architecture and DevOps to UX and metrics. > I'm interested in building systems, not just writing code. --- ### Option 4 - growing responsibility > At my current place I grew into a confident middle level and feel I've hit a ceiling. > I want more responsibility, influence over architecture, and the chance to take part in decision-making. > It matters to me to be not just an executor, but an engineer who understands *why* they make certain decisions. --- ### Option 5 - culture and process > The company is great, but the processes are quite bureaucratic, and new ideas get adopted slowly. > I'm more comfortable working in an environment that values initiative, fast feedback and engineering freedom. > I want to be part of a team where I can genuinely influence the product and its quality. --- ## What **not** to say | Mistake | Why it's bad | |---|---| | "I don't like my manager / team" | Comes across as a conflict-prone person | | "I'm underpaid" | Acceptable only as a secondary reason | | "Everything there is falling apart" | Sounds like a complaint, HR will flag it as toxic | | "I'm just tired" | Unconvincing and doesn't add confidence | | "I want something new" | Too vague, doesn't show self-awareness | --- ## How to strengthen the answer You can add a small touch about **shared values**: > I noticed that you emphasize quality, architecture and engineering culture - and that's exactly the environment where I want to grow.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.