How to Answer "Tell Me About a Time Your Recommendation Was Ignored"

Why This Question Matters

"Tell me about a time your recommendation was ignored" surfaces frequently at companies like Meta, Uber, and other organizations where data teams advise but do not always control the final decision. Interviewers ask it because being right is easy in hindsight, but handling the moment when leadership overrules sound analysis, and staying professionally engaged afterward, is a genuine test of maturity.

This question exists because data scientists are advisors, not decision-makers, in most organizations. Even excellent, well-supported recommendations get overruled sometimes for reasons involving factors outside the data — timeline pressure, competing priorities, or risk tolerance the analysis did not fully capture. Interviewers want to know whether you understand that dynamic or whether you expect your analysis to be treated as the final word simply because it is correct.

There is also a resilience dimension. A candidate who becomes disengaged, resentful, or passive-aggressive after being overruled is a real risk on a team, regardless of how good their analysis was. Interviewers are listening for whether you can advocate firmly, accept a decision that goes the other way, and remain genuinely useful afterward rather than checking out or quietly saying "I told you so."

The STAR Method for Data Questions

STAR works well here because the story naturally has two phases: the advocacy before the decision, and your behavior after it went against you.

• Situation: What was the recommendation, and what decision did it inform?
• Task: What was your role in making the case, and to whom?
• Action: How did you advocate for your recommendation, and what did you do once it was overruled?
• Result: What ultimately happened, and how did you follow up afterward?

Spend real time on what happened after the decision went against you. That is usually the part interviewers care about most.

What Interviewers Are Really Looking For

1. Quality of the Original Case

Was the recommendation genuinely well-supported, with clear reasoning and evidence, or was it a preference dressed up as analysis? A strong case makes the eventual outcome more meaningful either way.

2. Professional Advocacy

Did you make your case clearly and persistently without becoming combative or disrespectful of the decision-maker's authority?

3. Graceful Acceptance of the Decision

Once the call was made, did you support it professionally, or did you continue relitigating it or quietly undermine the chosen direction?

4. Constructive Follow-Through

Did you set up a way to track the outcome, so that if your concern turned out to be right, the organization would learn from it rather than the information being lost?

Example Answer Structure

Situation: "At a subscription fitness app, I built a price-elasticity model ahead of a planned 15% price increase and found that the increase would likely push churn up enough to reduce net revenue in the near term, even though it would look good on a simple 'revenue per subscriber' metric leadership was focused on."

Task: "I needed to present this to the VP of Growth, who had already committed to the price increase publicly to the board as part of the quarter's revenue plan."

Action: "I presented the elasticity analysis clearly, including my confidence interval and the specific assumptions behind it, and proposed a smaller 8% increase as a lower-risk alternative that the model suggested would avoid most of the churn impact. The VP heard the analysis but decided to proceed with the full 15% increase anyway, citing the board commitment and a belief that the churn estimate was too conservative. Rather than continuing to push after the decision was made, I said clearly that I disagreed but would fully support the rollout, and asked if I could set up a two-week post-launch tracking dashboard specifically to monitor the churn signal my model had flagged, framing it as useful validation regardless of which of us turned out to be right."

Result: "Churn rose in the two weeks after the price increase, tracking closely with what my model had predicted, and net revenue came in below the board's plan for the quarter. Because I had the tracking dashboard already in place, the team was able to see the pattern within two weeks rather than a full quarter later, and the VP walked back the increase to roughly 9% before it compounded further. She specifically credited the early dashboard, not just the original analysis, for letting the team correct course quickly, and she began looping me into pricing decisions earlier in the process afterward."

Common Mistakes to Avoid

Sounding Bitter or Vindicated

Even when the data later proved you right, frame the story around organizational learning, not personal vindication. A tone of "I told you so" undermines an otherwise strong story.

Disengaging After Being Overruled

If your story implies you stopped caring about the outcome once your recommendation was rejected, it signals a risk that you will do the same thing again on this team.

Weak Original Advocacy

If you did not make a clear, well-supported case in the first place, the story does not demonstrate much beyond "I was overruled." Show that your case was genuinely strong.

No Follow-Through Mechanism

A story that ends at the decision, without describing how you tracked or validated the outcome afterward, misses an opportunity to show constructive persistence.

Framing Every Disagreement as the Decision-Maker Being Wrong

Occasionally acknowledge legitimate reasons your recommendation might have been overruled, since a story with zero nuance about the other side's reasoning can come across as one-sided.

Preparing Your Stories

Prepare a story where your recommendation was overruled for a legitimate business reason, not just organizational politics, since that version demonstrates more nuance. Write out the strength of your original case, exactly how you advocated for it, what you did once the decision went the other way, and any follow-up tracking or validation you set up.

If your recommendation turned out to be wrong in the end, that is also a usable story, as long as you can describe accepting the outcome gracefully and learning something real from being wrong.

Tailoring Your Answer to the Company

At a company with a strong data-driven culture, such as a marketplace or ad-tech company, emphasize the rigor of your original analysis, since that audience will expect a technically credible case. At a company where the culture is more instinct-driven or leadership-heavy, emphasize your professionalism in accepting and supporting the final call, since that is likely the dynamic you would face there too.

Consider mentioning how you would set up tracking on a recommendation in this specific company's context, which shows you have thought concretely about how you would operate on this particular team.

Handling Follow-Up Questions

Be ready for questions like:

• "Looking back, could you have made your original case more persuasively?"
• "How did you maintain a good working relationship with the decision-maker afterward?"
• "What would you have done differently if you still believed you were right a year later?"
• "Have you ever been overruled and later realized the other person was right?"

Answer with genuine reflection rather than a one-sided account. Interviewers respect candidates who can acknowledge real ambiguity in these situations.

Key Takeaways

Being overruled is not a failure — it is a normal part of working as a data professional inside an organization with competing priorities. What interviewers are really evaluating is whether you can advocate for your analysis clearly, accept a decision gracefully once it is made, and build in a way to learn from the outcome regardless of who turns out to be right. Handle that well, and this question becomes a strong demonstration of exactly the professional maturity most technical answers cannot show.