Tell me about a time when you had to go against management or your colleagues

In my first year, I was working on a small change to our internal dashboard, and my teammate suggested we skip validation on one input so we could finish before the sprint ended. I was uncomfortable with that because the same field fed into a report used by operations, and bad data would have been hard to unwind later. I asked if we could talk through the risk, and I learned they were under pressure because another task had slipped and they were trying to protect the deadline. I suggested a smaller version of the feature that kept the validation but reduced some nonessential polish, and I put together a quick test to show it would not add much time. We went with that plan, shipped on time, and avoided the riskier shortcut. Afterward, my teammate thanked me for raising it directly, and I learned that when I disagree, it helps to understand what's driving the push before defending my own view.

At a previous startup I was asked to build a small interactive widget for our product landing page and the product manager wanted a full-screen animation that ran on load and prevented interaction until it finished. I knew that would be a poor experience for people using keyboard navigation or screen readers, so I raised my concern with the PM and designer and showed them a quick demo of how the animation broke focus and hidden content. Instead of just saying no, I proposed and implemented a compromise: let the animation play but include a visible "skip" control, preserve logical focus order, and add proper labels for assistive tech. We shipped on time with those changes, and support tickets about accessibility dropped; I learned that bringing a concrete demo and a low-cost fix makes it much easier to go against the plan and get buy-in.