Tell me about a time when you strongly disagreed with your manager or peer on something you considered very important to the business.

In my first year, I disagreed with my manager about releasing a data import feature on the original date. During testing I found that a few malformed files could partially import and leave records in an inconsistent state, and I felt that would create real customer support issues. Instead of just saying we should delay, I asked what was driving the date and learned a customer demo was already scheduled that week. I put together a short investigation with example failures and suggested a compromise: keep the demo date, but limit the import format and add validation before general release. My manager agreed, we shipped the narrower version, and the follow-up release went out a week later without the data issue. What I learned was to ask about the business constraint early so I can frame my pushback around a workable option, not just a concern.

In a previous role at a health‑tech startup I pushed back when my manager suggested turning off authentication in a demo environment so executives could quickly try a new feature. I was uncomfortable exposing any patient data, so I calmly explained the legal and reputational risks and proposed a concrete alternative: add a short-lived feature flag scoped to a few accounts, enable audit logging, and prepare a redacted demo dataset. My manager was initially skeptical about the extra work, so I implemented the flag and scrubbed data overnight and asked legal for a quick check. The demo went ahead on schedule with zero data exposure, and our team adopted the scoped-flag + audit approach for future demos. I learned that standing firm on ethical and privacy concerns works best when you pair it with a practical, low-cost solution.