A sweeping statement about passion sounds like the safe answer to “What motivates you?” It gives an interviewer little evidence of how you work. A specific problem you chose to pursue and the reason you stayed with it say more about what genuinely keeps you engaged. That distinction matters when the “What motivates you?” interview question comes up in a behavioral or craft interview.
A designer might say they enjoy solving complex problems. A stronger answer identifies the kind of complexity: finding where people abandon a setup flow, weighing simpler layouts against accessibility needs, and testing whether a revision helps. The details let the interviewer ask useful follow-ups and let you answer from work you actually did.
The myth that a bigger passion sounds more convincing
The myth is that your motivation must sound ambitious and all-encompassing to be credible. It is easy to see why: the question can feel personal, and a broad declaration seems safer than naming a narrow preference. But “I am passionate about making an impact” gives no clue about which tasks draw your attention or how you respond when the work gets difficult.
You can be motivated by a specific kind of challenge without claiming it drives every career decision. Perhaps you like finding the point where a clear interface still fails in testing, then working through the tradeoffs until the flow improves. Your answer becomes more credible when you can connect that preference to a decision you made and a result you observed. You do not need to manufacture enthusiasm for every part of the role.
Pick a moment that shows the preference in action
Choose one example you can discuss in detail. For a case or portfolio interview, that could be a redesign where initial research challenged your preferred solution. For a cross-functional interview, it could be a moment when you had to reconcile conflicting input from research, engineering, and support. The best choice is work that genuinely held your attention and resembles the challenges in the role you are discussing.
Build the answer around three questions.
- What kind of problem pulls you in? Be specific enough that someone can recognize it in actual work.
- What did you do when you encountered one? Name your decision, including a tradeoff or obstacle.
- What kept you engaged through the less exciting parts? Show persistence without pretending the entire project was enjoyable.
A sample answer might begin, “I am motivated by finding the friction that people have learned to work around. On a setup-flow project, I kept hearing that the instructions were clear, but test participants still paused at the same step.” From there, explain the change you proposed, how you evaluated it, and what you learned. Only claim an improvement if you have evidence for it.
Keep the answer honest and adaptable
Do not memorize a speech that fits only one interview. Keep a short record of several projects, with the problem, your decision, the outcome, and the part of the work that energized you. Then choose the example that fits the conversation. A craft interviewer may want to hear your design reasoning; a cross-functional interviewer may care more about how you handled disagreement. The underlying motivation should stay the same.
To organize examples you can adapt to different questions, use this guide to building a reusable interview story bank.
Your answer also has to fit the job. If the role is centered on maintaining an established system, an answer devoted entirely to starting things from scratch may raise a fair question about fit. You can explain what interests you about improving existing work, if that is true. Avoid reshaping your preferences to match a posting you have not thought through.
Prepare evidence before the question arrives
After your next meaningful project, write down the problem that held your attention and one decision that shows why. Those details give you more to work with than an abstract statement about passion. When you want to keep those examples available for future interviews, save your work stories in ImpactLogr.