Describe the most innovative thing you've done.
Asked at:
Amazon
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to understand how you define innovation and what role you personally played in creating something meaningfully new or unusually effective. They are usually not looking for novelty alone; they want to see judgment, problem framing, and whether the idea actually mattered in practice. For more senior candidates, this also tests whether your innovation scaled beyond your own work and changed how others operated.
“Tell me about a time you came up with a novel solution to a hard problem.”
“What's the most creative improvement you've driven in your work?”
“Can you walk me through a project where you challenged the usual approach and did something meaningfully different?”
“What's an example of a non-obvious idea you turned into a real result?”
Key Insights
- You do not need a flashy invention story. A strong answer is often a practical change that solved a hard problem in a non-obvious way and produced durable impact.
- You should explain why the problem was genuinely constrained or non-routine; otherwise the story can sound like normal execution being rebranded as innovation.
- If your idea was adopted by others, say how you earned that adoption. Interviewers often care as much about making innovation real as about having the idea in the first place.
What interviewers probe atlevel
Top Priority
Even for a small project, explain how you tested your idea instead of just saying it seemed smart.
Good examples
🟢'I compared the current process with a small prototype and showed that the new approach cut several manual steps before I asked the team to adopt it.'
🟢'I wasn't sure whether the issue was slow code or slow setup, so I measured both and focused on setup after seeing that was where most of the time was going.'
Bad examples
🔴'I had a feeling this would be faster, so I built it that way and it ended up being fine.'
🔴'I wanted to try a different approach because it sounded more elegant, and my mentor let me do it.'
Weak answers center on taste or novelty; strong answers show the candidate reduced uncertainty and used evidence to justify the new approach.
At junior level, innovation usually means finding a thoughtful new approach within a small scope, not inventing a company-wide system.
Good examples
🟢'We kept misclassifying support tickets because the categories were too broad, so I proposed a lightweight tagging helper in the internal tool. It was a small project, but the novelty was noticing the real issue was input quality rather than reporting.'
🟢'During onboarding I saw that new test failures were hard to debug because logs were scattered across systems. I created a local script that grouped the relevant outputs together, which was new for our team because people had assumed the pain was unavoidable.'
Bad examples
🔴'The most innovative thing I did was automate a report my teammate asked for. It was straightforward once I found the right library, and people used it instead of doing it manually.'
🔴'I built a dashboard for our service and that was innovative because no one had done that exact dashboard before on our team.'
Weak answers relabel routine tasks as innovation; strong answers show the candidate identified a real friction point that others had accepted and reframed it in a useful way.
Valuable
Your story does not need huge scale, but the result should be real and clearly better than before.
Good examples
🟢'The script reduced a repetitive setup task from about twenty minutes to five for the three engineers who used it most, and it became part of our onboarding notes.'
🟢'The tagging change cut the number of tickets needing manual recategorization during my internship, which was a small but visible win for the support engineer I worked with.'
Bad examples
🔴'It saved a lot of time for everyone, and people were really happy with it.'
🔴'The project was successful because my manager said it was a great idea.'
Weak answers make inflated or ungrounded claims; strong answers give proportionate, believable impact tied to the candidate's actual scope.
Example answers atlevel
Great answers
One of the most innovative things I did was during an internship when I noticed engineers spent a lot of time gathering logs from different places whenever a test failed. People mostly accepted it as part of the job, but I thought the real problem was that the information was fragmented, not that debugging itself was unusually hard. I built a small internal script that pulled the most relevant logs together into one view and tried it first on the test suite I was working on. I asked two engineers on the team to use it for a week, and based on their feedback I simplified the setup and added clearer error messages. It ended up saving time on repeated failures and got added to the team's onboarding notes for new engineers. I liked that project because it was small in scope but changed an annoying workflow people had stopped questioning.
At the small nonprofit where I work, many of our users in rural areas complained the site was unusable on slow connections, so I proposed a lightweight “low-data” mode. I implemented a toggle that deferred nonessential images, replaced large assets with simple placeholders, and stored key pages for offline reading, then rolled it out to a small pilot group. After a week of user testing and a couple quick iterations based on feedback, engagement from those regions rose by about 25% and support requests about timeouts fell significantly. It felt meaningful to build something small that directly improved access for people who otherwise couldn’t use our service.
Poor answers
The most innovative thing I've done was building a dashboard for our team's service. We didn't have that exact dashboard before, so I designed it myself and put a lot of useful graphs on it. People thought it looked good and it gave us more visibility into the service. I like that example because it shows I can come up with new ideas and build them independently.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late June, 2026
Amazon
Mid-level
Late February, 2026
Amazon
Mid-level
Early June, 2025
Amazon
Senior
Hello Interview Premium
Your account is free and you can post anonymously if you choose.