Describe experience working on an innovative project you started or became part of
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 behave when the path is unclear and the work is not just routine execution. They want to see whether you can identify opportunity, shape something new, and drive it toward a useful outcome rather than just participate in novelty. For more senior candidates, they are also checking whether the scale and influence in the story match the level you are interviewing for.
“Tell me about a time you helped bring a new idea from concept to reality.”
“What's an example of a project where the problem or solution wasn't well defined at the start?”
“Have you worked on something genuinely new for your team or company? What was your role?”
“Walk me through a project where you had to experiment because there wasn't an obvious playbook.”
“What's the most innovative thing you've built or helped launch, and why was it innovative?”
Key Insights
- You do not need a moonshot story. A strong answer often comes from improving a process, product, or internal tool in a way that required initiative, experimentation, and judgment under uncertainty.
- Do not spend the whole answer proving that the project was technically cool. You need to show why it mattered, what was unclear at the start, and what you specifically did to move it from idea to result.
- If you joined an innovation effort rather than starting it, be crisp about the part you owned. Interviewers are listening closely for whether you shaped direction or mainly executed someone else's plan.
What interviewers probe atlevel
Top Priority
Your story does not need massive scope, but it should solve a real problem and you should explain why that problem was worth working on.
Good examples
🟢It was a small project, but it solved a recurring issue for our support rotation by reducing the manual steps needed to trace failures. That mattered because it saved time for several people every week.
🟢The work was limited in scope, but it addressed a real gap in how our team reviewed incoming requests. I chose it because it was manageable for me and clearly useful to the team.
Bad examples
🔴The project was innovative because I rebuilt my local development setup in a new way and learned a lot from it. It didn't affect much else, but it was interesting.
🔴I made a dashboard for a side need on the team because I wanted to try a new framework. People thought it looked nice, so it felt like a successful innovation project.
Weak answers confuse personal novelty with meaningful impact; strong answers connect the project to a real problem and right-sized scope.
A junior candidate does not need to have invented the whole project, but they should clearly own a piece and show initiative within that scope.
Good examples
🟢I didn't start the project, but I owned the prototype for the reporting flow and took it from rough idea through implementation and feedback from a few internal users. I also documented what we learned so the next iteration was easier.
🟢My manager suggested the overall project, and I volunteered to investigate one especially unclear piece. I proposed a simple first version, built it, and shared the results with the team so we could decide whether to continue.
Bad examples
🔴I was part of the innovation project and helped wherever needed. I mostly took tickets from the board and made sure my tasks were done on time.
🔴My team was building a new internal tool, and I contributed to the front end. The lead made most of the decisions, but I was involved in the work.
Weak answers place the candidate at the edge of the story; strong answers make their specific ownership legible and consequential.
For junior candidates, a strong innovation story includes some form of learning loop instead of treating the first idea as automatically correct.
Good examples
🟢Because we weren't sure the idea would help, I built a small version first and asked a few users to try it. Their feedback showed the main issue was setup time, so I simplified that before expanding the feature.
🟢I assumed automation would save time, but I measured the current manual process first and then checked whether the prototype actually improved it. That helped us see that one part of the idea was useful and another part wasn't worth continuing.
Bad examples
🔴I built the first version based on what seemed reasonable and we shipped it. There wasn't much need to test because it was an internal tool.
🔴I compared a couple of approaches and picked the one I preferred, then moved forward. Since it worked technically, we considered it successful.
Weak answers treat innovation as intuition plus implementation; strong answers show a simple but real evidence-based learning loop.
Valuable
At staff level, a strong story often shows that you left behind mechanisms, patterns, or talent growth that outlasted the project itself.
Good examples
🟢I used the project to establish reusable patterns and shared language so teams could innovate faster in related areas later. The long-term value was larger than the initial project itself.
🟢I was intentional about growing local leaders during the initiative by giving them real decision areas and coaching them through tradeoffs. That meant the organization retained capability after the initial push.
Bad examples
🔴I drove the initiative personally because consistency was important, and most of the key choices came through me. That kept quality high across teams.
🔴The project succeeded largely because I stayed closely involved in all the major decisions. It would have been risky to distribute too much ownership.
Weak answers make the candidate the permanent center of gravity; strong answers create lasting organizational leverage.
Example answers atlevel
Great answers
One innovative project I worked on was a small internal tool to help our support rotation find failed orders faster. The idea came from noticing that engineers were manually checking several places to understand what went wrong, and I offered to build a first version during my internship. Since we weren't sure what information was actually useful, I started by talking to two people on support and mapping the steps they followed, then built a simple page that pulled the most common failure details into one place. After a few teammates tried it, I learned the biggest time saver was not the summary itself but having direct links to the underlying records, so I changed the design before we shared it more broadly. It was a small project, but it cut down investigation time for routine issues and taught me how to turn a vague improvement idea into something practical.
At my junior role at a small ed‑tech startup, I joined a project to simplify how teachers create in-class quizzes after noticing a steady stream of support questions about formatting and scoring. I spent time talking with three teachers and sat in on a demo to understand their pain points, then put together a lightweight quiz-template feature using our existing form components so it fit into the current product quickly. We launched a 20-teacher pilot and saw average quiz-creation time drop by roughly 40%, and teachers reported fewer scoring mistakes. It was a small, focused effort, but it taught me the value of observing real users, keeping scope tight so we can iterate, and using simple metrics to decide what to build next.
Poor answers
An innovative project I was part of was when our team started using a new front-end framework for an internal dashboard. I handled several of the tickets and got the pages working quickly, which helped the project move forward. It was interesting because none of us had used that framework before, so there was a lot to learn. In the end the dashboard looked much more modern, so I think it was a strong innovation project.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid October, 2024
Amazon
Mid-level
Describe experience working on an innovative project you started or became part of
Hello Interview Premium
Your account is free and you can post anonymously if you choose.