Give me an example of an initiative you undertook because you saw that it could benefit the whole company or your customers, but wasn't within any group's individual responsibility.

In my first year, I noticed that new engineers kept asking the same setup questions in chat, and the answers were scattered across old documents and message threads. Nobody specifically owned onboarding documentation, but it was clearly slowing people down across multiple teams, so I gathered the most common issues from recent hires and support channels and drafted a single setup guide. I asked a few teammates and one engineer from another team to review it so it reflected the real pain points rather than just my experience. After we published it, my team started linking it in onboarding, and two other teams did the same. A few weeks later, the number of repeated setup questions had dropped enough that my manager asked me to keep maintaining it with another new hire.

At my previous job as a junior front-end developer, I kept noticing the same accessibility problems — unlabeled form fields, poor keyboard navigation, and low color contrast — across features owned by different teams. There wasn't an accessibility owner, so I ran quick checks on our top five user flows, compiled clear, prioritized fixes, and created a one-page accessibility checklist and a short example guide showing how to fix each issue. I reviewed the guide with a designer and a senior engineer, then added the checklist to our pull-request template and ran a short lunchtime demo for two product teams. Over the next quarter, the number of accessibility-related support tickets dropped and several product managers started asking me to review designs before implementation. The company decided to adopt the checklist as part of our release checklist, and I kept updating it as I learned more.