‹ Field Notes
Disagreeing upward

A memo said Nvidia's CEO was a spy target; Nvidia called the contact "not unusual". The question that tests how you disagree upward.

On November 7, 2026, TechCrunch reported on a memo that "circulated earlier this year" and claimed that Alice Huang, an executive at a Singapore-based company called Megaspeed, had been recruited by China's Ministry of State Security to spy on Nvidia CEO Jensen Huang. TechCrunch attributed the account to multiple media reports: The New York Times reported on the memo first, and the Financial Times later reported that the memo also claimed a romantic relationship between the two. The memo was reportedly based on U.S. intelligence. An Nvidia spokesperson told the Times that Jensen Huang's interactions with Alice Huang were "not unusual," and that the company does not share classified information with its customers. In a separate report, the Times examined New Matrix, a Chinese company authorized by the U.S. Commerce Department to buy advanced Nvidia chips. At the office address the company listed, reporters found only "a hollow gray shell," which TechCrunch said raised concerns that New Matrix could be a front for a blacklisted private equity firm.

Nothing in this story is settled. The memo is a claim, every step of the reporting is attributed, and the company has answered. But notice what the two threads share. In each, a piece of paper carried authority: an intelligence memo in one case, a government authorization in the other. And in each, the thing that moved the story was someone comparing the paper to what could actually be observed. The company's answer, as reported, described the interactions rather than arguing with the memo. The New Matrix report did not dispute the authorization; it described an address. That is the behaviour an interviewer is reaching for when they ask you to describe disagreeing with leadership. The question is not whether you held a different opinion from the people above you. It is whether, when the authoritative account and the observable facts came apart, you went and looked, and what you did with what you found.

The interview question
“Tell me about a time you disagreed with leadership.”

Why they ask it

Experienced managers disagree with leadership constantly, so the fact of a disagreement tells an interviewer nothing. They ask because they want to know what your disagreements are made of. Three things are being checked. Whether you can tell the difference between a preference and a finding. Whether you raised it at a point when it could still change the decision, rather than afterward, when it could only assign blame. And whether you could let the decision stand once it was made, without relitigating it in hallways. At senior levels the hiring risk is not the person who never pushes back. It is the person whose pushback is indistinguishable from complaint, or who treats being overruled as an injury that the organization owes them for.

The trap

There are two common failure modes, and they look like opposites. The first is the vindication story. The candidate disagreed, leadership proceeded, the thing failed, and the candidate was right. The interviewer hears someone who keeps score, and learns nothing about how the disagreement was conducted, only that it happened. The second is the capitulation story dressed as alignment: "I raised my concerns and ultimately supported the decision," with no account of what was raised, to whom, or on what evidence. Both omit the same thing, which is the work between noticing the gap and the meeting where you named it. It is the equivalent of declaring the paper wrong without ever visiting the address. A third, smaller trap is casting the leader as the villain. A strong answer has a disagreement in it and no antagonist.

Applying STAR-T

Situation. Establish the authoritative position and the specific thing you saw that did not match it. "Leadership had committed to a public launch date for the new billing platform on the strength of a vendor readiness report. I ran the integration team, and the vendor's staging build had not passed our reconciliation suite." Say what the leadership position rested on. That detail is what makes your disagreement about evidence rather than taste.

Task. Your job was not to be right. It was to get the decision made with the correct information in front of the decision-maker, before the date hardened. Say that in those terms. It tells the interviewer you understood whose decision it was.

Action. This is where the going-and-looking lives, and it should be the longest part of the answer. Describe what you checked, how, and how you brought it. "I reran the reconciliation suite against the vendor's current build myself rather than relying on the earlier run, wrote up the specific failures with the transactions that produced them, and asked for time with the VP before the steering meeting rather than surfacing it in the room." Then describe the ask. A strong disagreement carries a recommended alternative, not just an objection, and it states plainly what you will do if overruled.

Result. Be honest about which way it went, because the decision can legitimately go either way. "The date held, but the launch went out behind a flag with the reconciliation gap documented, and the vendor closed it before general release." Or the date moved. What the interviewer is scoring is that the decision was made with the evidence present and that you executed it afterward as your own.

Trade-off. Name the cost. Going to the VP privately meant the room never saw the data and risked looking like you had gone around your peers. Re-verifying a vendor's attestation consumed a week your team did not have. Saying the cost aloud is the signal that you experienced this as a decision and not as a grievance.

The follow-up that breaks weak answers

"What would you have done if they had said no?" Vindication stories collapse here, because the only plan was to be right. A strong answer describes the line drawn in advance: what you would have escalated over, and what you would have carried out without further argument. A close variant is "Who else knew you disagreed?" If the answer is "my whole team," the interviewer has learned the disagreement travelled outward instead of upward. The strong answer is that the team heard the decision from you, as yours to deliver.

Score your answer against the director’s bar

Q: Tell me about a time you disagreed with leadership.

Ready when you are

Bank the story where the official account and what you saw came apart, and rehearse it until the answer to "what if they had said no" comes out first. Try it free →

Rehearse this in L8 Loop →