Why did you choose data science (or this data role), and what keeps you motivated in it?
This question is about self-awareness and genuine fit — not a test of enthusiasm. The best answers trace a specific intellectual or professional turning point, connect it to what you find durable about the work, and tie it forward to why this role and company in particular appeal to you.
How to think about it
What the interviewer is actually testing
Motivation is a proxy for retention and performance. Interviewers want to know whether you chose this field deliberately — and whether you’ll still be engaged two years in — or whether data science simply seemed lucrative. They also use this answer to understand what kind of work excites you, which helps them assess fit with their team’s actual day-to-day.
How to structure a strong answer
Start with a specific origin story. A concrete turning point is far more believable than “I’ve always loved math.” Did a particular project in school reveal something? A dataset at a previous job that surprised you? A paper you read that reframed how you thought about a problem? Specificity signals authenticity.
Name what you find intrinsically interesting. Is it the problem formulation phase? The moment a model reveals something counterintuitive in the data? Productionizing something that runs reliably at scale? Knowing what you actually enjoy lets the interviewer assess whether the role gives you enough of that.
Connect to durable motivation. The field moves fast and the work gets hard. Why does the grind still make sense to you? Answers grounded in intellectual curiosity or real-world impact tend to be more credible than answers grounded in career prestige.
Bridge to this role specifically. End by connecting your motivation to something concrete about the company or team — their data scale, the domain problem they’re solving, a technical approach they’re known for. Generic enthusiasm reads as unprepared.
Skeleton example: “In my first job as a business analyst I noticed a pattern in return data that no one had looked at systematically. I built a rough model in Excel and it predicted a product defect before the quality team caught it. That moment hooked me — the idea that the data already contains the answer and your job is to surface it. That’s what pulled me into proper data science, and it’s what still gets me out of bed. I’m particularly drawn to this role because your team is operating at a scale where the signal-to-noise challenge is genuinely hard.”