"I'm motivated by challenges."
Every interviewer on the planet has heard that sentence. Multiple times today. It doesn't tell them anything about you — it tells them you've prepared a non-answer.
"What motivates you?" is one of the most poorly answered questions in job interviews, not because candidates don't think about it, but because they answer it with personality traits instead of evidence. The question sounds introspective. The right answer is actually quite specific.
What the interviewer is actually asking
This isn't a personality question dressed up as small talk. The interviewer wants to know whether your motivations fit what this role actually delivers day-to-day.
A candidate who says they're motivated by public recognition is a risk in a role with no external facing work. A candidate who says they're motivated by deep technical problem-solving is a risk in a fast-paced generalist role where decisions have to be made quickly and you move on. A candidate whose motivations genuinely match what the job rewards is someone who'll stay, perform, and not burn out.
That's what the question is checking. It's a culture fit and retention screen in the form of an open-ended question.
Why generic answers fail
There are three answers interviewers hear constantly. All three fail for different reasons.
"I'm motivated by challenges." This is the most common answer and the least useful. Every candidate says it. The problem isn't that it's untrue — it might be perfectly true — it's that it's meaningless without definition. What kind of challenges? Intellectual? Operational? Interpersonal? And more importantly: what does the interviewer do with that information? Nothing. It's an answer that sounds good and lands nowhere.
"I'm motivated by making an impact." Close second. "Impact" is the kind of word that means everything and therefore means nothing. If you're going to use it, you have to define it — impact on what, measured how, over what timeframe? Without that, the interviewer mentally moves on before you've finished the sentence.
"I'm a people person — I love working with great teams." This isn't an answer to the question. Enjoying your colleagues is not a motivator — it's a preference about working conditions. If your answer is roughly equivalent to "I like it when work is pleasant", you haven't answered.
The common thread: all three answers could describe literally any candidate applying to any role at any company. That's the test. If your answer could slot into any job on LinkedIn without changing a word, it's not a good answer.
The framework: specific driver + evidence + role connection
A strong answer has three components, and the third one is what most candidates skip.
The whole answer should run about 60–90 seconds when spoken aloud. If you're clearing two minutes, you're over-explaining. If you're under 30 seconds, you're not giving the interviewer enough to work with.
This structure pairs naturally with the STAR method — the evidence component of your motivation answer is essentially a compressed STAR story. You don't need all four elements, but Situation and Result are the two that make it credible.
Worked examples by role type
Here's the framework applied to three different roles. Notice that none of them use the word "challenge" or "impact."
Operations / process improvement role
"I do my best work when I can fix something that's been quietly costing a business money for longer than anyone realises. In my last role, I mapped our supplier onboarding process and found we were doing six manual steps that could be cut to two — that alone freed up about 12 hours a week across the team. That kind of problem-solving, where the result is measurable and immediate, is what keeps me going. I noticed from the job description that a big part of this role is process standardisation across new regions — which is exactly the environment where I tend to perform at my best."
Sales / commercial role
"What drives me is closing something where I genuinely had to earn it — not a warm lead handed off from marketing, but a prospect who didn't think they needed the product until I understood their actual problem well enough to reframe it. In my last role I built a territory from scratch over 18 months and hit 140% of target by the end of year one. It came down to listening first and pitching second. I can see this role has a similar challenge — a competitive market, outbound-heavy, where the relationship work matters as much as the product. That's the kind of environment I look for."
Technical / engineering role
"I'm most motivated when a problem has no obvious answer and I have to dig into first principles to find one. Not bugs — I mean architectural decisions where the wrong call compounds over time. At my last company, I led a migration from a monolith to microservices over eight months. It wasn't glamorous, but the performance results were significant — latency dropped by 60% — and the team's velocity improved because we weren't fighting the same scaling constraints every sprint. This role involves greenfield infrastructure work, which is exactly the kind of problem I find genuinely interesting."
Each answer names a specific type of situation (not a trait), backs it with a concrete outcome, and then connects it to something visible in this job description. That's the whole structure.
The counterintuitive version: what if money motivates you?
Here's the honest answer: money motivates almost everyone. That's not a character flaw. But naming money in a job interview doesn't tell the interviewer anything useful about whether you'll do the work well or stay long enough to matter.
The real question isn't whether money is a motivator — it's whether it's your primary motivator when you're actually in the work. Most people who say they're motivated by money still find certain tasks energising and others draining. That gap — what you're actually doing when you lose track of time, what types of wins feel disproportionately satisfying — is what the interviewer wants to understand.
So if your honest answer involves compensation, you don't have to lie. You could say: "Earning based on results matters to me — I work harder when the link between performance and reward is direct. That's part of why a commission-based commercial role appeals to me, and it's also why I tend to be self-managing rather than needing structure to stay productive." That's truthful, and it translates financial motivation into something the interviewer can actually evaluate.
What you shouldn't do is lead with "I'm motivated by earning good money" and stop there. It's not wrong, but it's not an answer.
What NOT to say
Too vague to mean anything. Every candidate says this. If you can't name what type of challenge and why it fires you up, the interviewer has nothing to work with. Define it or drop it.
This sounds good and communicates nothing. Learning what? Applied how? Unless you can connect it to a specific skill gap this role will fill or a technical area you're actively developing, it reads as filler.
This answers a different question — what kind of environment you prefer, not what motivates you to do your best work. It also raises a quiet concern: is this person going to struggle in periods of solo, heads-down work?
Even a specific, well-evidenced motivation answer fails if it describes something the job can't deliver. If you say you're motivated by creative freedom and you're interviewing for a compliance role, you've handed the interviewer a red flag. Research the role before you answer.
Why this question trips people up more than it should
Across easedit.co's AI interview coaching sessions, "What motivates you?" consistently generates more generic first attempts than almost any other question — including the classic weakness question. Candidates who give sharp, specific answers to "tell me about a time you failed" revert to vague personality language the moment they're asked what drives them.
The pattern suggests the question feels like it's asking for self-knowledge, so candidates reach for self-description. But the interviewer isn't asking who you are. They're asking what conditions produce your best work, and whether this role creates those conditions. Framing your preparation around that question — not "what are my personality traits?" but "what was I doing the last three times I felt genuinely energised at work?" — tends to produce much more usable answers.
This connects to where do you see yourself in 5 years — both questions are really asking the same underlying thing: will you stay, and will you care when you're here? Your motivation answer and your five-year answer should tell a consistent story.
The difference between a forgettable answer and a memorable one isn't having a more impressive career. It's being specific about the right things and connecting them to this role in a way the interviewer couldn't have predicted.
At easedit.co, you can practise this question live — with a voice AI that pushes back if your answer's too vague and adapts based on your actual target role. The specificity you find in practice is the specificity that lands in the real thing. Practise your answer — from $39, no data stored.