You do your best on the job when the work feeds a real need like visible progress, a problem that matters, or room to decide how you operate. That's the honest answer for most people.
Interviewers ask because they want to know if this opening supplies that fuel. Pay still counts. It rarely carries a whole career by itself.
U.S. hiring teams treat the question as a fit screen, not small talk, because they need to guess whether you'll still care after the offer. Managers should listen for that too.
If the job cannot feed that driver, even a strong hire will fade.
Pick one true motivator. Prove it with a short story. Tie it to a duty in the posting.
Why this question keeps coming up
Behavioral interviews treat past action as a preview of future action, which is why career offices drill you on stories instead of slogans. Yale's Office of Career Strategy wants examples, not adjectives.
MIT CAPD puts most of the airtime on what you personally did. Turns out the question is a values check as well.
They need to hear whether your best days look like the days this job will actually contain. A person who needs public praise may struggle in a quiet, independent seat. Someone who needs long craft time may hate a calendar stuffed with status meetings.
Neither person is broken. The pairing is.
Drivers that tend to last
Self-determination theory keeps landing on three needs: autonomy, competence, and relatedness. You push harder when you have some say in the method, when you can get better at a real skill, and when you feel tied to the people or the point of the work.
A review of SDT in workplaces links those needs to satisfaction and effort. The work itself usually outlasts a bonus. Fair pay still matters as a floor. Unfair conditions will sour even a mission you believed in on day one, and then you'll start counting hours instead of problems.
Use this map when you choose what to say.
| Driver | What it looks like on a good day | Where it clashes | | Autonomy | You pick the approach and own the tradeoffs. | Heavy scripts and six-level approvals. | | Competence | Hard problems and skill growth keep you honest. | Repetition with no feedback. | | Relatedness | You extra-effort for a team or customer you can name. | Isolated work or a cold culture. | | Impact | You care that the output changes something outside the file. | Work with no visible beneficiary. | | Clear goals | Visible targets tell you if you're winning. | Fuzzy success metrics. |
Don't recite the table in the room. Name the one that's actually you.
Build the answer in three beats
Keep it under two minutes.
- State the driver in plain words. Try: "I do my best when I can see a broken process, fix it, and check the result." Skip "passionate self-starter."
- Prove it with STAR. Keep situation and task tight. Spend the bulk on your actions. Close with a result you can defend. MIT's breakdown puts most of the story on action, not setup.
- Aim it at this job. Mention a duty, a customer, or a team habit from the posting that would feed the same need.
Draft 3 to 5 stories before you walk in. One win. One messy save. One moment you helped other people, if that's real. Jot bullets, not a speech.
Say it out loud once. Cut anything that sounds like a banner headline.
What a believable answer sounds like
Mastery as the fuel might sound like this. You inherited a messy intake queue. Errors were landing on the next team. You mapped the failure points, wrote a short checklist with the people who actually did the work, and ran it for a month. The afternoon cleanup shrank to a brief review. Then you point at the bottleneck this role owns.
Relatedness might sound different. The quarter got ugly. You still pushed because the teammates and the customer had names, not because a poster said excellence. You describe one concrete assist. Then you connect it to how this group actually collaborates.
Keep numbers only if they're yours. Made-up lifts are easy to catch. To be honest, a smaller result you can walk through beats a dramatic one you can't explain, which is why a line like we cut the weekly error pile from a full afternoon to a short checklist lands harder than a round percentage with no method behind it.
Lines that fall flat
These answers waste the question:
- "I'm motivated by money and a good salary."
- "I just always give 110% and work hard."
- "I want to grow and take the next step in my career." (no skill, no story)
- "I need a boss who stays out of my way." (sounds like a warning)
Growth is fine when you name the skill and why this desk would stretch it. Don't dump on a former manager. Don't claim a purpose your last two jobs never touched.
Read the posting twice. An execution role doesn't want a strategy-only story. A people-lead job doesn't want a headphones-all-day story.
If you are the hiring manager
You don't need poetry. You need a person whose best conditions exist in the job you actually run.
Thing is, a polished speech is cheap. Ask when that driver was missing and what they did next. People who know themselves can answer. Script readers stall.
Then protect what you heard. If they need autonomy, don't drop them into six approvers and act surprised when the energy dies.
Use the same driver in the rest of the search
Your resume should not fight your interview. If you say you care about fixing broken processes, one bullet should show a process you actually fixed.
Applicant tracking software won't score "motivation." A human screener will notice the match.
If your resume is a pile of duties with no fingerprints, this interview question will feel impossible because you will be searching for a story that you never wrote down in the first place, and then you will invent one under pressure, and it will sound like it.
Same for the job-board application. Mirror language from the posting only where it's true. Don't paste "purpose-driven" into every field.
Save the STAR notes next to the posting. You'll reuse them for "tell me about yourself" and "why this role."
Do this before the next screen
Open the job description. Circle two tasks that would feed your real driver. Write one STAR story that proves you've already worked that way. Record it once on your phone. Cut the slogans.
That's the next step. Not a new personality. A clearer story about the one you already have.