The hiring criterion that decided a senior loop, and that isn't on most rubrics.
I had three finalists for a leader role on the team. All three were skilled. All three could have done the work. I hired one of them, and the criterion that decided it isn’t on most hiring rubrics I’ve seen.
The role is one I’d waited a long time to fill. It carries technical depth, but most of the actual job is upward in the organization: working with product and technology executives on cross-team prioritization, defending the team’s roadmap to the broader leadership group, and translating engineering tradeoffs into language a product leader can use. The hardest part of leadership roles in fast-moving, AI-motivated SaaS environments isn’t about having the right answer. It’s the part that happens after a decision goes the way the leader didn’t recommend.
Two of the three finalists I’ll call A and K. The one I hired I’ll call N. All three had defensible answers to the technical screen, the team interview, and the case study. The interview process did not reliably distinguish them on the things the role actually requires.
What distinguished them was a question I asked late in the loop, and the way each of them answered it. The question, more or less verbatim:
Tell me about a time you argued strongly against a direction your manager set, lost the argument, and then had to lead the team in executing the decision you’d recommended against. Walk me through how the next two months went.
A’s answer was thoughtful but defensive. The story was structured around having been right, the project having struggled, and the earlier objections having been validated. The work got delivered but the team knew where A stood. It came through in the telling: the right call at the wrong altitude, framed as something the manager eventually came around to. Useful self-knowledge; risky in a role that requires sustained alignment with leaders he won’t always agree with.
K’s answer was more concerning. K spoke clearly about the disagreement, then described giving the team latitude to find their own path. When pressed, it became clear that the project had been allowed to drift, with the failure expected to vindicate the original position. K couldn’t quite say it, but the shape of the story was a commitment made with words and not with hands. I’ve worked with that pattern before. It’s expensive.
N’s answer was unremarkable in its content and remarkable in its posture. She’d lost an argument about a major architectural call. She thought the chosen direction was wrong. She told the team she thought it was wrong, told them she’d been overruled, and then publicly committed to making the chosen direction succeed. She organized the team around it, removed obstacles, and shipped on time. The bit that landed for me was a sentence near the end, to the effect that she owed it to the team and to her manager to make the decision they’d made the best version of itself, not the worst version of hers.
The criterion has a name in some leadership writing, mostly out of Amazon’s principle of disagree and commit. What’s missing from most discussions of it is the directional asymmetry. Disagreeing and committing with peers is hard but tractable. Disagreeing and committing upward, where the asymmetry of authority makes resentment cheap and execution expensive, is the hard version. Most senior leader rubrics never name it.
I’m going to ask the question I asked N in every senior loop I run from here on. The phrasing isn’t the point. It’s the pattern of the answer that mattered most.
A note for anyone thinking about this from the candidate side. The trap on this question is to use it to demonstrate how often you’ve been right.