Home › Blog › Answering the what motivates you question

Answering the what motivates you question

This sounds like small talk and is not. The interviewer is checking one thing: whether the work that energises you is the work this role contains. An answer that is true but irrelevant to the job is still a bad answer.

What is being checked

The test: would your answer be true of a different job? If "solving hard problems" could apply to any engineering role anywhere, tighten it until it points at this one.

Motivations that work, with evidence

Pick one, prove it with a sentence of evidence from something you have actually done, and connect it to what this team works on. Three sentences total is plenty.

The honest handling of money

If compensation genuinely is a motivator, you do not need to pretend otherwise - but it is a poor answer alone, because it says nothing about why this job rather than a better-paying one. Pair it with something about the work, and keep the compensation conversation where it belongs, which is covered in answering the salary expectations question.

The variants

What to avoid

Where CoPilot Interview fits

Disclosure: we build an interview assistant, so treat this as a disclosed pitch. CoPilot Interview is a native Windows and macOS app that puts suggested answers on your own screen in about two seconds, across coding, system design and behavioral rounds, with a permanent free tier that needs no credit card.

Frequently asked questions

How do you answer 'what motivates you'?

Name one motivation, prove it with a sentence of real evidence from something you have done, and connect it to this team's work. The test of a good answer is that it could not be said word for word about any other job.

Is it acceptable to say money motivates you?

It is honest and legitimate, but weak as a sole answer because it says nothing about why this role rather than any better-paying one. Pair it with something about the work itself and keep the compensation discussion to the appropriate conversation.

What are good answers for what motivates a software engineer?

Seeing something you built actually used, hard problems with a real constraint such as latency or scale, making other engineers faster through tooling or mentoring, deep domain learning, and end-to-end ownership. Each is provable with a short example.

How do you answer 'what demotivates you'?

Choose something structural rather than personal - unclear priorities, work that gets shelved before shipping, long gaps without feedback. Avoid naming something that is a known feature of how this company works, unless you are deliberately testing whether the role fits.

Walk into the round with a second pair of eyes

CoPilot Interview is a native Windows and macOS app that puts suggested answers on your own screen in about two seconds, across coding, system design and behavioral rounds. The free tier is permanent: 15 minutes a day, no credit card.

Try it free