What Motivates You? How to Answer the Interview Question

To answer “what motivates you,” name one or two genuine drivers tied to the work itself — like solving hard problems, seeing measurable impact, or helping customers — then back each one with a short, specific example from your experience. The mistake to avoid is naming money, promotions, or perks, because the interviewer is testing whether you’ll be engaged by the actual job, not just the paycheck.

Keep the answer to 60–90 seconds. This is not a trick question, but a vague or self-serving answer quietly costs you.

Why Interviewers Ask This

The question has one purpose: to predict whether you’ll be energized or drained by this specific role. Every job has a core of daily work — writing code, closing deals, analyzing data, managing people — and the interviewer wants to know that the core of the job lines up with what actually gets you out of bed.

A good answer does two things at once. It sounds authentic (not rehearsed corporate-speak), and it maps your motivation onto what this role actually involves. If the job is heavy on independent problem-solving and you say you’re motivated by structure and clear direction, you’ve just told them you might struggle — even though nothing you said was “wrong.”

Good Motivators vs. Ones That Backfire

Strong motivators	Weak or risky ones
Solving complex problems	Money and compensation
Seeing measurable impact of your work	Job titles and promotions
Learning and mastering new skills	Perks and benefits
Helping customers or teammates succeed	”I just like being busy”
Building or shipping something real	Avoiding boredom
Hitting ambitious, concrete goals	Pleasing my boss
Collaborating with sharp people	Anything you can’t back with an example

The left column works because each item is intrinsic to good work. The right column isn’t immoral — of course you want to be paid well — but naming it here signals that the content of the job doesn’t matter to you, which is exactly the wrong signal.

The Structure

You don’t need STAR for this one. Use a simpler three-part shape:

1. Name the motivator (one sentence). Be specific. “Solving problems that don’t have an obvious answer” beats “I’m a hard worker.”

2. Prove it with an example (two or three sentences). A brief, real moment where that motivation showed up and drove a result. This is what separates a believable answer from a platitude.

3. Connect it to the role (one sentence). Show that the thing that motivates you is abundant in the job you’re interviewing for.

That’s it. One or two motivators, each proven and connected. More than two starts to sound like you’re listing every virtue you can think of.

Match Your Motivator to the Role

Before the interview, look at the job description and pick a genuine motivator that the role clearly rewards. You’re not inventing a fake motivation — you’re choosing which of your real ones to lead with.

• Engineering / technical roles: solving hard problems, building things that last, learning new systems.
• Sales / business development: hitting goals, the direct feedback loop of closing, helping customers solve a real pain.
• Product / project management: shipping something people use, aligning a team around a goal, measurable impact.
• Support / customer success: helping people succeed, turning a frustrated customer into a happy one.
• Analytical / research roles: finding the answer inside messy data, being right for reasons you can defend.
• Creative roles: making something from nothing, the craft of getting it right.

Sample Answers

Software engineer

“What motivates me most is untangling a problem that doesn’t have an obvious solution. Last year we had a data pipeline that was silently dropping records once a week and nobody could reproduce it. I spent three days instrumenting it, found a race condition that only triggered under a specific load pattern, and fixed it. That kind of work — where the answer is genuinely hidden and you have to earn it — is what I find most satisfying. This role looks like it’s full of exactly that kind of problem, which is a big part of why I applied.”

Salesperson

“I’m motivated by the clarity of the feedback loop in sales — you either helped the customer see the value or you didn’t, and the number tells you. In my last role I inherited a stalled territory, and the thing that kept me energized wasn’t the quota itself, it was working out what each prospect actually needed and watching a genuinely stuck deal come back to life. I closed the biggest account in that territory by focusing on their real problem instead of my pitch. I’m drawn to this role because it’s a market where solving the customer’s problem well is what wins.”

Project manager

“What drives me is shipping something real and then seeing people use it. I can grind through the unglamorous parts — the dependency tracking, the risk logs, the awkward conversations — because I know they add up to a launch. On my last project we shipped a redesigned onboarding flow, and watching activation climb after months of coordination work was the payoff that made all of it worth it. This role is that same shape: a lot of coordination in service of a launch that actually changes a metric, and that’s the kind of work I do my best in.”

Common Mistakes

Leading with money or titles. Even if it’s honest, it tells the interviewer the job itself doesn’t move you. Save compensation for the offer conversation.

Staying abstract. “I’m motivated by success” or “I like challenges” says nothing. Without a specific example, it’s a slogan, and interviewers have heard it a hundred times.

Naming a motivator the role doesn’t offer. Saying you’re driven by mentoring a big team when the role is an individual contributor position signals a mismatch. Pick a driver the job actually feeds.

Listing five motivators. It reads as an attempt to cover every base rather than an honest answer. One or two, done well, is stronger.

Confusing it with “why do you want this job.” They overlap, but motivation is about what energizes you in general; “why this job” is about this specific company and role. Keep the motivation answer focused on the nature of the work.

Sounding rehearsed. A word-for-word memorized answer sounds flat. Memorize the motivator and the example, not the exact sentences — and practice it out loud so it lands like a real thought, not a recitation. Running it in a mock interview with Alex, an AI interview coach is a quick way to hear whether your answer sounds genuine or scripted.

FAQ

Can I ever mention money as a motivator?

Not as your primary answer. It’s fine that compensation matters to you, but naming it here signals that the work itself doesn’t. If you want to acknowledge it, fold it in briefly — “fair pay matters, of course, but what actually gets me engaged day to day is…” — and spend your real answer on an intrinsic driver.

What if I’m honestly motivated by different things than the role rewards?

Then you’re probably eyeing a role that isn’t a great fit, and it’s worth being honest with yourself about that. But most people have several genuine motivators — pick the one that overlaps most with the job. You’re selecting which true motivation to lead with, not fabricating one.

How is “what motivates you” different from “why do you want this job”?

“What motivates you” is about the kind of work and outcomes that energize you in general. “Why do you want this job” is about this specific company, team, and role. A strong strategy is to make your motivation answer flow naturally toward why this role feeds it — but keep the two answers distinct so you’re not repeating yourself.

Should I use a personal example or a work example?

Default to a work example — it’s the most relevant evidence. A personal example (a side project, a volunteer role, a hobby you pursue seriously) can work if it genuinely illustrates your driver and you don’t have a strong work case, but keep the connection to how you’d bring that same energy to the job explicit.