Interviewers who ask “what motivates you” check the answer against your recent work. So the trouble starts when that work is mostly maintenance. The obvious shape is a motivator plus a project. But your best project may be two years old. Answer with one kind of problem you go looking for. Make it specific enough that someone could watch you chase it. Then prove it with something you chose to do while the job didn’t require it. Maintenance helps here. Nobody hands out exciting work in a maintenance phase. So anything you started there shows what drives you. Close with the part of this role that gives you more of that problem. Don’t explain your current job’s slowdown unless asked. Prepare one more answer, because the next question can be what demotivates you. Below, an Android engineer on a banking app in maintenance mode builds both answers.
What motivates you gets checked against what you did last quarter
The question sounds like small talk. The interviewer is matching two things. One is what drives you. The other is what this job will hand you every week. A mismatch means you may coast or leave.
Interviewers have good reason to wonder about coasting. The 2025 Stack Overflow Developer Survey drew over 49,000 responses. About one in four respondents said they were happy at work. Another 47% called themselves complacent. So “I love building things” proves little. The interviewer needs evidence that you still act on it.
The same survey asked what adds to job satisfaction. On its work page, autonomy and trust to manage your own tasks ranked first. Competitive pay came second. Solving real-world problems came third. That ranking suggests what a believable answer sounds like. It describes a problem you pick up on your own, with a real user at the end.
A maintenance phase is where your motivation is easiest to prove
Take Hira, a senior Android engineer. She has spent four years on a retail banking app. The big redesign shipped 18 months ago. Since then, her team mostly fixes bugs, updates libraries and handles compliance changes. She is interviewing for a role on a fast-growing ride-hailing app.
Her first instinct is to talk about the redesign. It was the most exciting work she has done. But it is old. The interviewer will notice. If her motivation only showed up when the work was exciting, it may not show up here either.
The maintenance period is better evidence. Nobody asked Hira to improve anything during it. The roadmap was library bumps and bug tickets. Whatever she started in that time, she started because she wanted to.
Name the motivator as a problem you go after
“I’m passionate about technology” fails because nobody can check it. A motivator becomes useful when it names a type of problem. Then the interviewer can ask where you found one.
Hira’s first draft was “I like making apps better.” Her second was sharper. “I like taking something slow that people use every day and making it measurably faster.” Now the interviewer knows what to ask. Which slow thing? How much faster? Who noticed?
That wording also contains a number that moves. Teresa Amabile and Steven Kramer studied knowledge workers’ diaries. Their May 2011 Harvard Business Review article told managers to “help them see their own progress.” The research is from 2011. It still explains why Hira’s version works. A measurable problem lets her show progress she can point to.
The proof is a choice nobody asked you to make
Hira’s proof comes from the maintenance period. Customers had complained in app reviews that the app was slow to open. Nobody had made that a ticket. She pulled the startup traces from her team’s monitoring tool. Cold start on mid-range phones took about 2.8 seconds.
She found three SDKs that started up before the first screen could draw. She moved two of them to start after the first screen appeared. The third needed the security team’s sign-off, so she wrote up the case and got it. She did this in the slack between tickets over about six weeks. Cold start on those phones dropped to about 1.6 seconds. Her manager then added startup time to the team’s release checklist.
Her manager’s change shows the work counted for the team, beyond her own interest. If your story ends with a habit someone else adopted, keep that sentence.
Tie it to the new role without blaming the old one
Hira’s real reason for leaving is that the app has little left to build. She could say that without blaming anyone. Still, she leaves it out of this answer. The question is about what drives her. The reason for leaving has its own question. Our post on why you’re leaving your job covers that one.
Instead, she ends on the overlap. A ride-hailing app has a slow thing millions of people use daily. Riders wait between opening the app and seeing a nearby car. That wait is the kind of problem she described. She names it. Our post on why you want to work here shows how specific that last line needs to be.
What Hira says when the question comes
We invented Hira for this post. Her bank, her app and every figure in her story are made up too. Use the order and replace the content with your own.
I like taking something slow that people use every day and making it measurably faster.
The clearest recent case came during a quiet stretch on our banking app. Our roadmap was mostly library updates. But users kept saying in reviews that the app was slow to open. I pulled our startup traces. Cold start on mid-range phones was about 2.8 seconds. Three SDKs were starting before the first screen could draw. I moved two of them later and got security’s sign-off on the third. It took about six weeks between tickets. Cold start on those phones dropped to about 1.6 seconds. My manager then added startup time to our release checklist.
That’s part of why this role interests me. Your riders wait between opening the app and seeing a car. That’s the same kind of problem at a much bigger scale.
Each paragraph does one job. The first names a problem type the interviewer can test. The second gives a recent choice, with a before and an after. It also shows a manager acting on her work. The third points at this employer’s version of the problem. She never says she was bored.
“What demotivates you?” needs an answer that fixes something
This follow-up can come right after. The easy dodge is a safe answer like “unclear requirements.” Give a real one. Make it the reverse of your motivator. Then say what you do when it happens.
For Hira, the reverse is work where nobody can tell if anything improved. That was her team’s maintenance backlog before the startup project. Her answer is short. “What drains me is shipping fixes with no way to see if they helped. So on my current team, I added crash-free rate and startup time to our sprint review. Now each fix has a number next to it. If a new team lacks those numbers, I’d set them up early.” The interviewer now has a demotivator they can believe. They also have a fix she has already made once.