A memo claimed an executive was recruited to spy on Nvidia's CEO. The question about disagreeing with leadership.
On November 7, 2026, TechCrunch reported that a memo circulated earlier this year claimed technology executive Alice Huang had been recruited by China's Ministry of State Security to spy on Nvidia chief executive Jensen Huang. TechCrunch attributed the account to multiple media reports. The New York Times was the first to report on the memo, which was reportedly based on U.S. intelligence, and the Financial Times subsequently reported that the memo also claimed a romantic relationship between the two. Alice Huang is an executive at Megaspeed, a Singapore-based company. 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. Everything in the memo remains, in TechCrunch's own word, something it "claimed."
Why they ask it
The question is "Tell me about a time you disagreed with leadership." It gets asked at senior levels because the interviewer has usually been on the other side of it. They have had a staff engineer or a manager come to them with a concern, and they remember which ones were useful. A useful dissenter brought evidence rather than a feeling, chose the moment and the room, was clear about what they wanted changed, and, when the decision went the other way, executed it as if it had been their own. A useless dissenter never spoke up, or spoke up to be on record, or kept relitigating after the decision. So the question is a proxy for judgment about when a disagreement is worth its cost, skill at making a case upward, and the ability to disagree and then commit. That last part is checked far more than candidates expect. The interviewer is about to become your leadership, and they are asking what it will be like to be disagreed with by you.
The trap
The common failure is the vindication story. The candidate disagreed, leadership overrode them, the thing went wrong, and the candidate was proven right. It feels like the strongest story available and it is among the weakest, because it tells the interviewer that the candidate measures disagreements by whether they won and remembers the ones where leadership looked bad. It also tends to skip the only part that matters, which is how the case was made. A second failure is the costless disagreement, about a naming convention or a meeting cadence, where nothing was at stake and so nothing was tested. A third is a story that is really about a peer or a distant skip-level, dressed up as leadership. Choose a disagreement with your own chain, with real money or real risk attached, where you can be specific about what you argued and how the decision landed. If you lost, that is fine. It may be better.
Applying STAR-T
Situation. A sentence or so, and the stakes have to be in it. Our director wanted to ship the new billing pipeline to every tenant on the quarter boundary, and I owned the migration. The data team had just reorganized and the people who understood the legacy schema were gone. The interviewer needs to know why disagreeing cost anything at all.
Task. Name what you believed and what you were accountable for. I thought a full cutover was likely to produce billing errors we could not reverse quickly, and I was the person who would answer for them either way.
Action. This is what the question is really about, so spend most of your time here. Say how you built the case: what data you pulled, who you tested the argument on before taking it up, how you framed it in the director's terms rather than yours. Say where you raised it, privately first and then in the review. Say what you proposed instead, because disagreement without an alternative is a complaint. I brought the error rates from our earlier partial migrations, a staged rollout by tenant tier, and the date it would cost us. I asked for a private conversation before the planning review so she was not hearing it in front of her peers.
Result. State the decision honestly and what you did next. If you won, say what the alternative delivered. If you lost, say how you executed the original plan and what you put in place to catch the risk you had flagged. She held the date. I committed to it, built the reconciliation job we would have wanted anyway, and it caught a rounding bug on a small slice of invoices in the first week, before any customer saw it. Resist editorializing about who was right.
Trade-off. This question rewards naming a cost. Perhaps you spent political capital you would rather have kept for something else. Perhaps raising it privately meant the team never saw you push back, and someone later assumed you had agreed all along. Naming that shows you treated the disagreement as a decision rather than a reflex.
The follow-up that breaks weak answers
"What did you do after the decision went against you?" Or, if the candidate won: "How did your director feel about the way you raised it?" The first exposes the vindication story at once, because a candidate who was proven right usually has nothing to say about execution; their story ended at the moment of being right. The second exposes the candidate who disagreed in public in order to be seen disagreeing. A strong answer has a specific, slightly uncomfortable response to either: the job you built anyway, the apology you owed for the room you chose, the conversation weeks later in which the director said she would rather hear it early next time. The interviewer is listening for whether the relationship survived the disagreement, and whether you noticed.
Score your answer against the director’s bar
Q: Tell me about a time you disagreed with leadership.
Bank one disagreement with your own chain where real money or real risk was on the table, and rehearse it until the decision and what you did afterwards take as long to tell as the argument. Try it free →
