Who and why
Looking back over four years of hiring, five people changed the shape of the company rather than adding to it. Three we can name here, two we cannot yet.
The pattern is uncomfortable, so it is worth stating up front: all five made us do less, not more.
The staff engineer who blocked the release
In her second month she refused to ship a release with a failing test that everyone else had learned to ignore. The argument lasted a day and a half.
She was right, and more importantly the test was right — it had been failing intermittently for eleven weeks and was pointing at a genuine race in the job scheduler. The norm changed that week and has not changed back.
The designer who booked the calls
He insisted on weekly customer calls when we were "too early" for research. The first four calls killed a feature we had been building for a month.
We now run the calls permanently. The cost is two hours a week of a designer's time; the return, on that first month alone, paid for the role.
The finance lead who said no
She said no eight times in her first month — to a conference, two tools, a hire, and a pricing experiment that would have been very hard to reverse.
Six of the eight were the right call. We ran two of them anyway and she was right about one. A finance function that only reports is an expensive spreadsheet.
And the ones we got wrong
Two hires in the same period did not work, and both failures were ours rather than theirs. One was a role we invented because a candidate was good, without a job to attach it to. The other was a senior hire into a team that had not agreed it wanted one.
The tell in both cases was the same: nobody could say, in one sentence, what would be different in six months. We now refuse to open a role until someone can.
The pattern
Hires that say no shape the company more than hires that say yes. They are also the hardest to hire for, because a good interview rewards agreeableness and a good first month does not.
The practical version: in the final conversation, ask what the candidate refused to do at their last job, and why. The answer sorts people faster than any technical question we have tried.
We hire for what someone will stop. It is the only part of the job description that never appears in the job description.