What interviewers are really worried about
When an interviewer asks a career changer why they are switching, the underlying worry is one of three things: you are running away from a problem in your current field (burnout, failure, conflict), you are chasing something unrealistic and will be disappointed when the new field does not match your expectations, or you will be a poor fit because your experience does not transfer well enough to justify the investment in training you. A strong answer addresses all three concerns without being defensive about them.
The best career change answers are pull, not push: they explain what you are moving toward and why, rather than what you are escaping. If you have a legitimate push reason (your industry is contracting, you have reached a ceiling, the work is not meaningful), you can include it, but it should not be the primary driver in your answer.
How to structure your answer
Step 1: Acknowledge the transition directly. Do not minimise or apologise for the change. Own it as a considered decision. "I am making a deliberate move from X to Y, and I want to explain why." Step 2: Explain the pull. What specifically draws you to the new field? Go beyond "it seems more interesting." Reference specific aspects of the work, the problem space, or the impact that you find genuinely compelling. Step 3: Show the bridge. What skills and experiences from your previous career are directly applicable to the new one? The best career changers do not ask employers to ignore their past: they show how it creates a specific advantage in the new field. Step 4: Show evidence of preparation. What have you already done to prepare for the transition? Courses, projects, community involvement, self-study? This addresses the training cost concern directly.
Sample answers
Operations to data analytics: "I have spent five years in supply chain operations and what I have noticed is that the decisions that matter most, routing, inventory levels, supplier selection, are constrained by the quality of the analysis available at decision time. I want to be on the analysis side of that equation rather than the operational execution side. I started teaching myself Python and SQL eight months ago, completed a data analytics certificate, and built a project using publicly available logistics data to model reorder point optimisation. The combination of operational domain knowledge and data skills is one I think creates something genuinely different from a pure data analyst background, and this role is where I want to build it properly."
Journalism to UX research: "Journalism and UX research turn out to share a core skill: extracting genuine insight from people through structured questioning and synthesis. I have spent seven years interviewing people, finding the story in what they say, and translating it for an audience that needs to act on it. What I want now is a domain where I can build deeper relationships with the people I am studying and see my research directly shape decisions rather than just inform opinion. UX research gives me that, and I have spent the past six months doing unpaid research projects with two early-stage startups to demonstrate I can apply the skill in a product context."