Tell me about a time when you were unsatisfied with the status quo.

In my first few months on a backend team, I was unsatisfied with how long it took new engineers to get the service running locally. It had taken me almost three days, and I noticed people were asking the same setup questions repeatedly in chat. Instead of assuming the toolchain was the problem, I wrote down where I had gotten stuck and compared notes with another new hire; the bigger issue was that our setup guide was outdated in a few critical places. I updated the guide, added a short troubleshooting section, and asked one of the more experienced engineers to review it before we published it. When the next intern joined, she finished setup the same day, and the number of repeated questions dropped a lot. What I took from that was that small process improvements can save the team real time if you validate the actual pain point first.

I kept seeing support tickets from users who couldn't complete the checkout using only a keyboard, and as someone who cares about accessible products I was unsatisfied that accessibility seemed like an afterthought. I did a short manual audit of the checkout page, created a handful of targeted fixes (missing form labels, focus outlines, and a contrast variable), and submitted small, well-documented PRs so they could be reviewed quickly. I also added a three-item accessibility checklist to our PR template and ran a 20-minute demo showing how to do quick checks before merging. In the following weeks similar support tickets decreased and reviewers began flagging accessibility in code reviews, which felt like a real shift in the team's priorities toward more inclusive design.