
"What motivates you?" sounds simple. It isn't. Interviewers aren't looking for enthusiasm — they're trying to predict whether you'll stay engaged six months in when the novelty wears off.
The best answers name a specific motivator, back it with a real story, and connect it to what the role actually requires. This guide walks you through why the question gets asked, what to say, and what to avoid.
Why Interviewers Ask This Question
The question isn't small talk. It serves three real purposes.
Self-awareness check. A candidate who can't explain what drives them is often someone who hasn't reflected on their own work patterns. Interviewers want to hear that you know yourself.
Alignment signal. If you say you're motivated by autonomy and the role is highly structured, that's a red flag — for both of you. Honest answers help everyone avoid a bad fit. Research on motivation consistently shows that intrinsic drivers (purpose, mastery, autonomy) predict sustained performance better than external ones.
Engagement risk assessment. Disengaged employees cost organizations real money. A Gallup study on employee engagement found that highly engaged teams show 17% higher productivity. Interviewers use this question to spot candidates who are likely to stay switched on.
A 3-Part Formula That Works
Answering "What motivates you?" well isn't about being positive. It's about being specific and credible.
1. Name the motivator — Be direct. State what drives you in one clear phrase. "Solving problems that don't have obvious answers" is more useful than "I'm passionate about making a difference."
2. Prove it with a story — Give a brief example from your work or studies. What happened, what you did, and what the outcome was. This turns a claim into evidence.
3. Connect it to the role — Tie your motivator to something specific about the position you're interviewing for. This shows you did your homework and that the fit is real, not manufactured.
This structure works because it mirrors how self-determination theory frames intrinsic motivation: genuine motivation comes from within and is tied to competence, autonomy, and relatedness — things you can actually point to.
Motivators That Land Well
Some answers resonate because they're believable and role-relevant. Here are motivators that tend to work:
Impact and outcomes. You care about seeing results, not just completing tasks. "I'm most engaged when I can trace what I shipped back to a business outcome."
Learning and growth. You're energized by problems that push you past what you already know. Strong in engineering, research, early-stage roles, and any environment that's still figuring itself out.
Craft and problem-solving. The quality of the work itself drives you — getting the architecture right, writing clean copy, finding an elegant solution. Works well for technical and creative roles.
Collaboration and shared wins. You do your best thinking alongside other people and find group momentum motivating. Relevant for team-oriented roles, product, and cross-functional work.
Mission alignment. You care about what the organization is trying to accomplish in the world. This one only lands if it's specific — "I care about education" is weaker than "I've been following your work on adult literacy for two years."
Motivators to Avoid
Some honest answers will sink your candidacy. Here's what to keep out of your response:
- Money and compensation. True for almost everyone, but it signals you're here for the paycheck, not the work. Save it for the offer negotiation.
- Job security. Comes across as risk-averse, which makes interviewers wonder if you'll take initiative or just do what you're told.
- Remote work or flexibility perks. Legitimate preferences, but not motivators. This makes you sound like you're optimizing for comfort, not output.
- Avoiding boredom. "I need to be busy" isn't a motivator, it's a complaint waiting to happen.
Sample Answers by Role
These are examples you can adapt. The key is making them yours — specific company, specific project, specific outcome.
Software engineer: > "I'm motivated by shipping things that actually get used. At my last internship, I built a feature for our notifications system that I expected maybe 20% of users to try. When we saw 70% adoption in the first week, that feedback loop made everything click. I want to keep working at that intersection of technical craft and real user impact — which is why the scale of problems you're solving here stood out to me."
Nurse: > "Seeing a patient go from scared and confused to confident about their care plan is what I come back for every shift. It's a small window, but I know what clear communication does for recovery outcomes. I looked at how your unit approaches patient education before this interview, and it matches exactly what I'm trying to get better at."
Sales rep: > "I'm motivated by the moment a prospect realizes they've been solving the wrong problem. I love the discovery process — asking questions, listening, and figuring out where the real gap is. I've closed deals by slowing down when everyone else speeds up. Your team's consultative approach is why I applied here specifically."
Teacher: > "When a student gets something they've been stuck on for weeks — that's it for me. I teach AP Chemistry, and last year I had a student who failed two exams and came back to ace the final. It took a lot of one-on-one work and a different approach to the material, but watching that shift is what I think about when the job gets hard."
Recent grad: > "I did a lot of different things in school to figure out what I actually liked doing. The work that felt effortless was the research project I did on urban transit data — I spent two extra weekends on it because I couldn't stop thinking about what the patterns meant. I think I'm motivated by complexity that has a real-world stake, which is why roles in policy analysis or research feel right to me."
Follow-Up Questions to Expect
Interviewers often drill down after you answer. Be ready for:
- "Tell me about a time you were unmotivated at work. What did you do?"
- "How do you stay motivated when a project isn't going well?"
- "What does [motivator you named] look like on a bad week?"
The best prep for these is to think through one or two genuine low points from your work history and what you actually did about them. Maslow's hierarchy of needs is a useful frame here: once basic needs are met, people are driven by belonging, esteem, and self-actualization — knowing which layer you operate at helps you talk honestly about what knocks you off course.
Before the Interview
Knowing how to answer "What motivates you?" is one piece of interview prep. The part most candidates skip is knowing who they're talking to. Understanding the interviewer's background and priorities before you walk in changes the conversation — answers that would normally be generic become specific, and specific answers get remembered.
If you're preparing for a role and want to go deeper on the person interviewing you, Articuler builds a Playbook on the interviewer — their background, what they've worked on, what they likely care about. That kind of prep doesn't replace a good answer to "What motivates you?" It makes it land better.
For a broader look at how to handle similar behavioral questions, see our guides on why do you want this job and why are you interested in this position — both follow the same principle: specific beats generic, every time. Our guide on what is your greatest strength covers a closely related question you'll likely face in the same interview.
FAQ
What is the best answer to "What motivates you?"
The best answer names a specific motivator, backs it with a brief story from your work or studies, and ties it to something concrete about the role. Avoid generic phrases like "I'm a hard worker" — give the interviewer something they can remember.
What motivates you — example answers?
Good motivators include: seeing the impact of your work on real users or outcomes, solving problems that require learning something new, the quality and craft of the work itself, collaborating with a team that challenges you, and mission alignment with what the organization is building.
What should you not say when asked what motivates you?
Avoid mentioning money, job security, remote work perks, or avoiding boredom. These are honest answers for many people, but they don't tell interviewers anything useful about how you'll perform and can signal poor fit.
How long should my answer be?
Keep it to 60–90 seconds — roughly three to four sentences. Name the motivator, give one brief example, connect it to the role. If an interviewer wants more, they'll ask.
How do I answer if I don't know what motivates me?
Think back to projects or tasks where time passed faster than expected, or where you kept working past the point anyone asked you to. That's where your motivation lives. Pick one example and build the answer from there.