Describe experience working on an innovative project you started or became part of

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.