Tell me about a time when a staff engineer strongly disagreed with your approach and their resistance was preventing the project from moving forward, and how you handled it.

On a small internal tool project, I suggested handling retries in the client because it looked faster to build. A staff engineer pushed back pretty hard and said that approach would create failure cases we would struggle to debug later, and the discussion started stalling the work because I did not fully understand the concern. I asked for a short follow-up and had them walk me through a past incident where duplicated requests had caused data issues, which made the risk much more concrete to me. After that, I proposed a smaller server-side change that removed the risky part of my idea, and I put together a quick test to confirm it behaved the way we expected. We ended up shipping that narrower version on time, and the project moved again because we were no longer debating abstractly. The biggest thing I learned was to ask earlier about operational risks instead of only optimizing for implementation speed.

On a customer support project, I was helping build a simple admin page so agents could refund failed orders without using a manual spreadsheet process. I wanted to keep the page very flexible because I thought it would save time for the team, but a staff engineer strongly disagreed and said I was creating something too easy to misuse, which caused the work to slow down. Instead of arguing in the thread, I asked for a 15-minute call and had them show me a few examples of mistakes that had already led to real customer problems in the past. That changed my thinking, because I realized the priority was not just making the tool useful, but making it hard to do the wrong thing. I updated the plan to include clearer defaults, a confirmation step, and a simple log entry for every refund, and I documented the tradeoff so the team could move forward. Once I did that, they were comfortable approving it, and we shipped the smaller version without more back-and-forth. I learned that when someone senior pushes back that hard, it usually helps to focus on the risk they are protecting against, not on proving my first idea was clever.