Tell me about a time where you proactively proposed a change.

On my last team, I noticed that new engineers, including me, kept getting stuck on the same local setup step when trying to run one of our services. It wasn't a huge issue by itself, but it kept costing people time and interrupting whoever happened to know the fix. I suggested adding a short setup checklist to our team documentation, and before writing it I asked two teammates which steps were most commonly missed so I could focus on the real pain points. I wrote the first version, had a teammate review it, and we linked it from the onboarding page. When another engineer joined a few weeks later, I checked in with them and found one missing step, so I updated the checklist. After that, we saw a lot fewer setup questions in chat.

At my last job I worked on a small front-end team and noticed we kept recreating buttons, headers, and spacing rules slightly differently in each feature, which led to dozens of nit-picky PR comments and frustrated designers. I proposed we adopt a tiny shared set of UI components plus a one-page style guide so people wouldn't have to guess which spacing or color to use. To lead by example I implemented a simple button component, wrote clear usage notes, and walked the team through it during our weekly demo so we could iterate quickly. After a couple of quick updates the team started using the shared components from the repo and referencing the guide in PRs. Over the next month we saw far fewer style-related review comments and less back-and-forth with design, which let us deliver features faster and with better consistency.