The Time You Said 'Yes' to a Bad Idea
Tell me about a time you had to implement a feature or decision that you personally believed was technically or strategically flawed. What was the outcome?
Why Interviewers Ask This
LinkedIn values intellectual honesty and psychological safety. Interviewers ask this to assess your ability to challenge decisions constructively without being obstructive. They want to see if you can balance technical conviction with team alignment, ensuring you advocate for quality while respecting the final strategic authority of leadership.
How to Answer This Question
1. Select a specific scenario where you identified a genuine flaw in a feature or strategy but were overruled by business priorities or stakeholder consensus. 2. Briefly explain the context and clearly articulate your specific technical or strategic objection using precise reasoning. 3. Describe how you voiced your concern professionally, focusing on data and risk rather than personal opinion. 4. Detail the execution phase: how you implemented the flawed decision despite reservations, perhaps adding safeguards to mitigate risks. 5. Conclude with the outcome, emphasizing what the project achieved versus the predicted pitfalls, and highlight the key lesson learned about balancing idealism with pragmatic delivery.
Key Points to Cover
- Demonstrating the ability to voice dissent respectfully and data-drivenly
- Showing commitment to the team's decision once it is made
- Highlighting proactive risk mitigation strategies during implementation
- Providing concrete metrics that validate the outcome analysis
- Reflecting on the balance between technical ideals and business realities
Sample Answer
In my previous role, the product team mandated launching a new recommendation algorithm based on real-time user clicks to boost immediate engagement metrics. As an engineer, I knew this would degrade long-term content quality by amplifying sensationalist posts and increasing server load unpredictably. I presented a simulation showing a potential 15% drop in user retention after two months, but leadership prioritized the short-term engagement spike required for Q3 goals. Instead of blocking the launch, I negotiated a phased rollout with strict monitoring dashboards and a kill-switch if retention dipped below 5%. We launched as planned; engagement spiked 20% initially, but retention did drop 8% within six weeks, validating my concerns. However, because we had the monitoring in place, we pivoted quickly to a hybrid model that balanced both needs. This experience taught me that while technical integrity is vital, delivering value often requires navigating imperfect constraints. It reinforced LinkedIn's culture of 'radical candor'—speaking up early, then supporting the team's decision wholeheartedly even when it isn't your first choice.
Common Mistakes to Avoid
- Claiming you always agreed with every decision, which suggests a lack of critical thinking
- Describing a situation where you refused to implement the idea, appearing uncooperative
- Blaming colleagues or leadership for the failure without acknowledging your own role
- Failing to mention any positive outcomes or lessons learned from the flawed decision
Practice This Question with AI
Answer this question orally or via text and get instant AI-powered feedback on your response quality, structure, and delivery.