Recruiting a Chief of Staff is not about filling a role. It is about choosing a thinking partner, a pressure absorber, a trust carrier. Which is why the process feels less like recruitment and more like a marriage.
I am a Chief of Staff, and I can tell you the hiring process is unlike anything I have been through. The moment you know you are doing it right is when it starts to feel uncomfortable in a way most hiring does not. What I remember most, from both sides of the table, is a particular discomfort, different from the ordinary kind about money or qualifications or whether someone will fit. This was the feeling of being assessed while assessing, for something I could not have named if asked. The evaluation runs in both directions, and the right candidate will know they are interviewing you just as hard.
This is what the marriage analogy is reaching for, however much it makes people squirm. It is not about romance, it is about access. A Chief of Staff gets the unedited version of you: the late messages when something has collapsed, the conversations about people that cannot be written down, the gap between the decision you actually made and the one you described to the board. Trust at that level cannot be built retrospectively. You build it during the process, or you spend the first year cobbling it together from nothing, and by then you have taken damage you have not yet located.
Most founders run a Chief of Staff search the way they run any senior hire: job spec, agency brief, competency framework, panel. That is fine if you are hiring a function head with defined outputs. A Chief of Staff works in the gap where the remit is genuinely unclear, where the outputs are partly indistinguishable from yours, where the real question is not “can this person do the job” but “can this person think with me when I do not know what I am doing”. A competency framework cannot answer that. You need real situations on the table, real stakes, real uncertainty, and then you watch how they carry it.
Chemistry matters more than credentials
The questions worth asking are not the well-behaved ones. Not “where do you see yourself in five years”, which deserves the rehearsed answer it gets. Try “tell me about something you held that you could not share with anyone”. Or “how do you disagree with someone who has more power than you”. Or “what do you do when there is no right answer”. You are watching how they sit with the question more than the content of the answer.
One thing the standard advice leaves out: do not hire a Chief of Staff if what you actually want is someone to stand between you and difficulty. The impulse is understandable, someone to absorb the friction, buffer the team, keep the hard things at arm’s length. But that impulse will wreck the relationship before it starts. A Chief of Staff is a thinking partner who is also operationally capable, and the thinking partnership depends entirely on your willingness to be challenged and to be wrong in front of them. If what you want is a buffer, hire an EA with real authority. Do not hire a Chief of Staff and then keep them outside the actual thinking. You will pay the full cost and get none of the value.
A bad hire at most levels can be corrected. A bad Chief of Staff, or a good one placed in the wrong relationship, works differently, because their presence slowly destabilises the whole system. The misalignment goes everywhere, since they are close to everything, and the damage is slow and diffuse, so that by the time you can describe what has gone wrong you have been paying for it for months.
So take your time. Show them how you actually think, not a curated version. Have the conversation about your blind spots before they find them unassisted. And notice, when you are sitting across from the right person, that the discomfort does not resolve. It changes character. That change is what you are looking for.
Hiring a Chief of Staff should feel uncomfortable. If it does not, you are probably doing it wrong.
