Choose a real, low-stakes technical disagreement where you had data to support your view, and narrate how you sought to understand your manager's perspective before advocating for your own. Emphasize the resolution process and the positive outcome, then reflect on what you learned about influencing without authority.
Pro tip: Frame the disagreement as a shared problem-solving exercise, not a personal conflict—show that you prioritized the team's goals and the relationship over being right.
Describe the project, your role, and the decision at stake in 1-2 sentences so the interviewer understands the stakes without getting lost in details.
State your manager's position and yours neutrally, focusing on technical or strategic trade-offs rather than personalities.
Describe how you listened, gathered data, ran experiments, or sought input from others to make the case constructive and evidence-based.
Explain what was decided, how it was implemented, and the measurable or qualitative results for the team or product.
Show self-awareness by identifying one thing you'd change—e.g., involving stakeholders earlier, communicating more clearly, or testing assumptions sooner.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.