How to Answer "What Motivates You?" in an Interview

"What motivates you?" sounds like small talk, and many candidates answer it that way. This section explains what the interviewer is actually trying to learn and why a vague answer costs more than it seems. In short, they are predicting whether the daily reality of this job will keep you engaged.

Every role has a texture: long debugging sessions, a steady stream of customer calls, slow stakeholder alignment, a sales target that resets each quarter. The interviewer wants to hear that what energizes you overlaps with that texture. A candidate motivated by variety applying to a deeply repetitive role is a retention risk, however talented.

They are also checking self-awareness. Someone who can name a specific motivator and point to evidence of it has thought about their own work, which is a signal in its own right.

A three-part structure keeps the answer short and specific:

• The motivator. One concrete thing, stated plainly: solving problems nobody has pinned down yet, seeing a customer's situation actually change, getting a messy process to run cleanly, helping a team get better.
• The proof. A brief example from real work where that motivator showed up. Two or three sentences, not a full STAR story.
• The link. Why this role, at this company, gives you more of it.

Keep the whole thing to under a minute. If the interviewer wants the full story behind your example, they will ask, and you will be ready. Rehearsing it aloud a few times is the fastest way to find the right length; the mock interview tool can ask the question and let you hear your answer back.

Software engineer: "I'm most motivated when I'm tracking down a problem that nobody has explained yet. On my last team, checkout requests were failing intermittently, and I spent two days narrowing it to a race in our retry logic. Fixing it felt better than any feature launch. Your platform team owns exactly that kind of reliability work, which is a big part of why I applied."

Customer success manager: "What keeps me going is seeing a customer go from frustrated to confident. One account was close to cancelling, and after we rebuilt their onboarding together they became one of our references. This role is built around that recovery work."

Career changer: "I'm motivated by learning something difficult and then using it for real. I taught myself SQL to automate reporting in my operations job, and it freed up hours for my team every week. I want a role where that's the whole job."

Notice that none of these claims to be motivated by everything. One specific driver, backed by one specific moment, is more believable than a list.

• Only money or perks. Compensation matters to everyone, and saying it is your sole motivator suggests you will leave for the next offer.
• Buzzwords with no evidence. "I'm passionate and driven" tells the interviewer nothing they can check.
• A motivator the role cannot satisfy. Saying you love building from scratch when the job is maintaining a mature system invites a follow-up you cannot win.
• Fear-based answers. "Not letting people down" can be honest, but lead with what draws you in, not what you are avoiding.

This question often arrives alongside tell me about yourself and why do you want to work here; the three answers should tell one consistent story. More guides for common questions are in the mock interview and practice guides. In a live video interview, SubcueAI can transcribe the question and draft a structured outline from the desktop app or browser extension, with no bot in the call, but the example itself has to be yours, and anything on a shared screen is visible to the interviewer.