Can you share an instance when you had a disagreement with the Engineering team?

The question "Tell me about a time you disagreed with Engineering" is designed to assess your critical thinking abilities and your approach to handling professional disagreements. The interviewer is interested in understanding whether you value differing opinions, can objectively challenge viewpoints, and manage conflicts in a constructive manner that leads to resolutions without creating friction. It is essential to recall a specific instance in which you disagreed with a decision, method, or process implemented by your Engineering team. Demonstrate how effectively you articulated your viewpoint, the strategies you employed to navigate the situation, your ability to consider other perspectives, and how the disagreement was ultimately resolved. Here are some key points to keep in mind while formulating your response: The situation: Clearly identify the project or decision you took issue with. Your role in the situation: Clarify your responsibilities to illustrate your involvement in the project or decision. The reason for disagreement: Elaborate on the rationale behind your disagreement. Was it related to efficiency, effectiveness, ethics, etc.? How you expressed the disagreement: Describe how you communicated your perspective. This provides insight into your communication and persuasion abilities. The result: Was the disagreement resolved? What was the outcome? This part highlights your conflict resolution skills.

In my last position as a Product Manager, we faced an important project that had strict deadlines. The Engineering team recommended adopting a technology stack that was unfamiliar to our organization. However, I was opposed to this idea because I felt it would extend our completion time due to the considerable learning curve associated with that technology. I expressed my concerns to the team, highlighting that although the new technology could offer long-term advantages, we needed a dependable and established solution for the current project—one that our engineers were already skilled in. I proposed that we utilize our existing in-house technologies, with which we had prior experience and success. This sparked a productive discussion, and we were able to come to a shared understanding. The Engineering team acknowledged that introducing a new technology posed a significant risk of delays for this project. We ultimately decided to use the proven framework. As a result, we not only completed the project on schedule but also maintained high quality. This experience reinforced for me the value of open, respectful dialogue and sound reasoning.

In my previous role as a Software Analyst, I noticed that the Engineering team often started coding without adequately analyzing requirements or creating prototype designs. I was opposed to this practice, as it frequently resulted in inefficiencies, the need for rework, and a final product that did not align with user needs. I raised my concerns with the Project Manager and proposed a more organized approach to software development. This would involve thoroughly gathering and documenting requirements and designing detailed prototypes before starting the coding process. I emphasized that this method would reduce ambiguity and rework while enhancing productivity and the overall quality of the product. Initially, there was some resistance to my suggestion, but the team agreed to implement my approach on a smaller project as a trial. The outcome was a well-functioning product with fewer bugs and less rework, completed within the designated timeline. The team recognized the effectiveness of this methodology, and it subsequently became our standard practice for all upcoming projects. This experience taught me the importance of advocating for my beliefs while maintaining a rational and respectful demeanor.