When an interviewer asks “what motivates you?”, name one or two specific parts of engineering work that genuinely give you energy (tracking down the cause of a hard bug, watching users adopt something you shipped, making a slow system fast, helping a teammate get unstuck). Prove it with one recent moment where that motivator drove what you did, then connect it to what this role actually involves. Aim for 45 to 90 seconds. “I'm passionate about technology” tells the interviewer nothing; “I get the most energy from turning a slow, unreliable process into something fast and measurable, and here's the last time I did it” gives them something to picture and check.
Below: how to pick a motivator that fits the job, a three-part structure, three example answers, quick rewrites and the follow-ups. For the company-specific question, see our guide to “why do you want to work here?”; this page is about you, not the company.
What interviewers are checking when they ask “what motivates you”
The question sounds soft, but it's a fit check: will you stay engaged in this particular job, including the unglamorous parts, and do you know yourself well enough to say why? The interviewer listens for four things:
- Fit with the actual work. If you say you love greenfield building and the role is mostly maintaining a mature platform, the interviewer hears a future resignation.
- Self-awareness. Can you name what drives you in your own words, or do you reach for a cliché?
- Durability. Motivation rooted in the work itself outlasts novelty, praise or fast promotion.
- Evidence. A motivator you can't point to in your history sounds borrowed.
Each common wording leans a slightly different way:
| Wording you might hear | What it's really asking |
|---|---|
| “What motivates you?” | What kind of work keeps you engaged, and does this job have it? |
| “What gets you excited to start work in the morning?” | The same question, more casual. It still wants specifics. |
| “When were you most engaged in a job or project?” | A behavioral version: tell the story first, then name the driver. |
| “What do you want more of in your next role?” | Is what you're looking for actually available here? |
| “What demotivates you?” | Will the normal parts of this job drain you? |
| “How do you stay motivated on long or tedious work?” | Do you have habits, not just feelings? |
It often shows up next to “tell me about yourself” and “why this company” in hiring-manager conversations, which is how our Microsoft behavioral interview guide groups it.
Pick a motivator that's true and fits the role
Start with what's real, then filter by the job description. One useful lens comes from Daniel Pink's 2009 book Drive, whose publisher's description names three elements of motivation: autonomy (directing your own work), mastery (getting better at something that matters) and purpose (serving something larger than yourself). Most strong engineering answers fall into one of those buckets, made concrete:
| Motivator | How it sounds from an engineer | Fits roles that mention | Proof to bring |
|---|---|---|---|
| Hard problems | “I like problems where the cause isn't obvious.” | Debugging, performance, distributed systems, on-call | A bug or bottleneck you tracked down |
| User impact | “I want to see people use what I build.” | Product engineering, customer-facing teams | A feature and what changed for users |
| Craft and quality | “I like leaving code better than I found it.” | Platform, developer experience, reliability | A refactor, test suite or review habit you improved |
| Learning (mastery) | “I do my best work when I'm a little out of my depth.” | New stacks, fast-growing teams, new grad roles | Something you learned quickly and applied |
| Ownership (autonomy) | “I like owning a problem from start to finish.” | Startups, small teams, “own services end to end” | A project you drove from idea to production |
| Helping others grow | “I get a lot out of unblocking teammates.” | Senior, staff and lead roles, mentoring | Someone you mentored, or a doc others rely on |
| Measurable improvement | “I like turning a number that's going the wrong way around.” | Performance, cost, reliability, data | A before-and-after you can explain |
| Mission or domain (purpose) | “I want my work to matter to a specific group of people.” | Health, education, accessibility, climate | A real reason the domain matters to you |
Pick a motivator you can prove with something that actually happened, and check that the job really offers it. If you only light up on brand-new projects and the role is mostly maintenance, find the true overlap (“I like making a stable system faster and cheaper to run”) or ask whether the role is right.
What not to lead with
- Money, title or perks. Legitimate reasons to change jobs, but as the headline they suggest you'll leave for the next bigger offer. Pay belongs in the compensation conversation; our salary negotiation calculator helps with that one.
- Pressure and deadlines. “I thrive under pressure” can sound like you need emergencies to engage, or that you create them.
- Praise or beating others. Wanting clear feedback is healthy; needing applause or a rival reads as a team risk.
- Generic passion. “I love coding” is true of most candidates, so it doesn't separate you.
A three-part structure: name it, show it, aim it
- Name it (one sentence). The specific driver, in your own words: “What keeps me engaged is taking something slow or unreliable and making it measurably better.”
- Show it (30 to 45 seconds). One recent, concrete moment where that motivator drove what you did. Keep the setup short. It's a compressed STAR story (situation, task, action, result); our free STAR story builder helps you trim it to the essentials.
- Aim it (one or two sentences). Connect it to something specific in this role: a line from the job description, the team's product, the stage the company is at. “Your posting mentions owning the checkout service's latency, which is exactly that kind of work.”
You can add a second motivator in one sentence. Two is the limit; a list of five sounds like guessing.
Three example answers
These are example answers we wrote for this guide, not transcripts from real candidates. The details and numbers are illustrative; replace them with your own and use only results you can defend in a follow-up.
Example 1: new grad, motivated by learning fast
Name it: “I'm most motivated when I'm learning something new quickly and can use it right away on real work.”
Show it: “In my internship I joined a team that wrote its services in Go, which I'd never used. After two days reading the code, I asked for a small backlog bug instead of a practice project. The fix touched how the service handled timeouts, so I paired with an engineer for an hour, wrote the change with tests, and it shipped in my second week. By the end of the summer I owned a small endpoint on my own.”
Aim it: “What stood out about this role is that new grads join a product team and ship in the first month. That fast loop of learning and shipping is where I do my best work.”
Example 2: mid-level backend engineer, motivated by user impact
Name it: “What keeps me going is seeing a change I made show up in how customers actually use the product.”
Show it: “Our support team kept forwarding tickets about failed CSV imports. I pulled a month of logs and found most failures came from three formatting problems we could fix automatically. I built a validator that corrected those and gave clear error messages for everything else. Import tickets dropped sharply the next month, and support stopped routing that category to engineering.”
Aim it: “Your team owns the onboarding flow, where a small fix reaches every new customer. That's the kind of leverage I'm looking for next.”
Example 3: senior engineer, motivated by making the team faster
Name it: “At this point in my career, my biggest motivator is making the people around me more effective.”
Show it: “Our deploys took most of an afternoon and depended on one person. I wrote down every manual step, automated the three worst ones, and ran two short sessions so anyone could deploy. Within a quarter everyone on the team had shipped a deploy themselves, and the engineer who used to do them all got their afternoons back for project work.”
Aim it: “You mentioned the team is growing quickly this year. Getting new engineers productive fast is the work I'd want to own.”
Weak vs strong: quick rewrites
| Weak answer | Why it falls flat | Stronger version |
|---|---|---|
| “Money motivates me.” | True for most people; says nothing about the work | “Fair pay matters to me, but what keeps me engaged day to day is…” (then a real driver) |
| “I love solving problems.” | Nearly every candidate says it | “I like bugs that only show up under load. The last one took me three days to trace.” |
| “I'm passionate about tech.” | Vague and impossible to check | “I build small tools to automate my own repetitive work. The latest one…” |
| “I thrive under pressure.” | Suggests you need emergencies | “I like on-call when the runbooks are good, and I enjoy writing them.” |
| “I want to learn as much as possible.” | One-directional: what does the team get? | “I learn fastest by shipping, so I'd expect to own a feature within my first few weeks.” |
Follow-up questions to expect
Interviewers usually probe once or twice to check the motivator is real:
- “What demotivates you?” Pick something real that isn't central to this job, and say what you do about it: “Long stretches with no user feedback. When that happens, I ask to sit in on a few support calls.”
- “Tell me about a time you lost motivation.” Tell it as a short story: when you noticed, what you changed, how it ended. A recovery beats “it never happens.”
- “How do you stay motivated on maintenance or migrations?” Show a habit, not a feeling: break the work into measurable chunks, automate the repetitive part, and keep the outcome visible.
- “What would make you leave a job?” Keep it tied to your motivator and neutral about employers: “If I stopped learning for a long stretch and couldn't change that internally.” Our guide to “why are you leaving your current job?” covers the tone.
- “Where do you want that to take you?” This bridges to the career-goals question; see “where do you see yourself in 5 years?” for engineers.
How to prepare and practice your answer
- Find your pattern (15 minutes). Write down three or four times in the last two years when you lost track of time at work, then name what they share. Keep the one or two motivators that also fit the role.
- Build the proof story (10 minutes). Draft it in the STAR builder, then say it out loud and cut it to 30 to 45 seconds.
- Write one aim sentence per company. Link your motivator to something specific about the team, and check it against your strengths answer so the two don't reuse the same story.
- Rehearse out loud. Record yourself, or run a free AI mock interview. CoPilot Interview's Mock Interview builds behavioral questions from your résumé and the job description, reads them aloud, and scores each spoken answer out of 10 with what to fix and a model answer.
Make sure your motivator lines up with your “tell me about yourself” answer; interviewers notice when they point in different directions.
Practice your motivation answer out loud
Paste your résumé and the job description, choose a behavioral-heavy mix, and answer an AI interviewer out loud. Each answer gets a score out of 10, what to fix and a model answer, then a report card. Free for 15 minutes every day, no credit card.
Try a free AI mock interviewFAQ
Is it OK to say money motivates me?
It is fine to be honest that pay matters, but don't make it the whole answer. Mention fair pay briefly if you want, then name what keeps you engaged in the work itself, because that is what the interviewer is trying to learn.
How long should my answer to “what motivates you” be?
About 45 to 90 seconds: one sentence naming the motivator, a 30 to 45 second example, and one or two sentences tying it to the role. Let the follow-up questions pull out more detail.
What if I don't know what motivates me?
Look backward. List the moments in the last two years when you were most absorbed in your work, then name what they have in common. A pattern you can point to is more convincing than a word picked from a list.
How is this different from “why do you want to work here?”
“What motivates you” is about you: the kind of work that keeps you engaged anywhere. “Why do you want to work here” is about the company. A strong motivation answer ends by connecting to the role, but its core is your own driver.
Should I change my answer for each company?
Keep the motivator itself the same, since it should be true, and change the example and the last sentence to match each role. A startup and a large platform team reward different drivers, so lead with the true one that fits best.
What should I say if they ask what demotivates me?
Name something real that isn't central to the job, then explain what you do about it. Avoid anything the role is built around, such as code reviews, working with product managers or on-call if the team runs one.