"What motivates you?" sounds like a simple question. Most candidates either answer too vaguely ("I'm motivated by challenges and growth") or too personally ("I need to support my family"). Neither lands. The question is really asking: will this person be engaged and effective in this specific role, or will they lose interest quickly?
What the interviewer is actually asking
Interviewers ask this to assess fit, not to hear a personal manifesto. They want to know whether what drives you aligns with what this job actually involves. If you say you're motivated by creative freedom and the job is highly structured process work, that's a red flag for both sides. If you're genuinely motivated by what the role offers, this question is an opportunity to show why you're a strong fit.
How to structure your answer
A strong answer has three parts: the motivator itself (be specific, not generic), a real example of that motivation in action, and a link to why this role and company connect to that motivator. The last part is what most candidates miss, and it's what makes the answer feel genuine rather than rehearsed.
- The motivator: what specifically drives you (problem-solving, impact, craft, team growth)
- Evidence: a real example of that motivator in your work history
- Connection: why this specific role and company match that motivator
Keep it to 60-90 seconds. This is not a values essay. It's a concise, honest window into what makes you effective.
Sample answers for different roles
For a data or analytical role
"What drives me is finding patterns in messy data that change how the business makes a decision. I find that genuinely satisfying, especially when the insight is counterintuitive. At my last company, I spent three weeks digging into why one customer segment was churning faster than any other and found it was a specific onboarding step that confused them. Fixing it reduced churn in that segment by 30%. That kind of direct impact from analysis is what I want more of, and from what I've seen about the data challenges here, this role has that."
For a customer-facing role
"I'm motivated by helping people solve problems they'd been stuck on. The moment when something clicks for a customer, or when I can cut through a complex issue and give someone a clear path forward, that's where I do my best work. I had a customer last year who was on the verge of cancelling because of a technical problem they couldn't resolve. We worked through it together over two sessions and they ended up expanding their contract. The relationship part of this role is what draws me to it."
What not to say
Don't say money. Even if it's true, it signals that you'll leave for a higher offer, which is the exact concern the interviewer is trying to assess.
Don't say "I'm motivated by learning." Every candidate says this. It's too vague to mean anything. If learning matters to you, say specifically what you want to learn and why, and link it to the role.
Don't say "making a difference." Same problem: too broad, too clichéd. Be specific about what kind of difference, in what context, with what kind of impact.
Don't answer in a way that conflicts with the job. If the role is repetitive and process-heavy, don't say you're motivated by variety and creativity. If you genuinely don't know what the day-to-day looks like, ask before answering.