### **Behavioral Question:**
**"Tell me about a time when you disagreed with a decision at work. How did you handle it?"**
### **Good Example Answer:**
"During a project, our team decided to prioritize adding new features over fixing a critical performance issue that was impacting a small but important subset of users. I strongly believed we needed to address the performance issue first, as it affected user retention and long-term trust in the product.
Rather than pushing back immediately, I gathered data on the number of affected users, their impact on revenue, and the potential long-term risks if the issue wasn’t resolved. I then scheduled a meeting with the product manager and team lead to present my findings. I explained the risks of continuing without addressing the problem and proposed a compromise where we could allocate part of the sprint to performance fixes while still moving forward with feature development.
After reviewing the data, the team agreed, and we were able to resolve the performance issue in parallel with new features. This approach maintained user trust and led to a smoother feature rollout. I learned that data-driven communication can help resolve disagreements constructively."
### **What You Should Not Say:**
1. **"I disagreed with the decision but didn’t say anything and just followed along."**
2. **"I argued with the team until they changed their minds."**
3. **"I worked on the performance issue on my own without telling the team."**
**"Tell me about a time when you disagreed with a decision at work. How did you handle it?"**
### **Good Example Answer:**
"During a project, our team decided to prioritize adding new features over fixing a critical performance issue that was impacting a small but important subset of users. I strongly believed we needed to address the performance issue first, as it affected user retention and long-term trust in the product.
Rather than pushing back immediately, I gathered data on the number of affected users, their impact on revenue, and the potential long-term risks if the issue wasn’t resolved. I then scheduled a meeting with the product manager and team lead to present my findings. I explained the risks of continuing without addressing the problem and proposed a compromise where we could allocate part of the sprint to performance fixes while still moving forward with feature development.
After reviewing the data, the team agreed, and we were able to resolve the performance issue in parallel with new features. This approach maintained user trust and led to a smoother feature rollout. I learned that data-driven communication can help resolve disagreements constructively."
### **What You Should Not Say:**
1. **"I disagreed with the decision but didn’t say anything and just followed along."**
2. **"I argued with the team until they changed their minds."**
3. **"I worked on the performance issue on my own without telling the team."**