Hiring for a role with no fixed job description is harder than it should be, because the usual checklist, years of experience, a clean resume, a confident interview, doesn't tell you whether someone can actually define their own scope and deliver against it. A chief of staff who needs you to tell them exactly what to do every week isn't doing the job. Here's what actually separates a strong candidate from a well-rehearsed one.
Ask for specifics, not a philosophy
Anyone can describe what a chief of staff "should" do in the abstract. What matters is whether they can walk through an actual engagement: what the founder's week looked like before, what they changed in the first thirty days, and what broke when they tried something that didn't work. Vague answers about "driving alignment" are a warning sign. Specific answers about a dashboard they built, a decision log they installed, or a vendor relationship they fixed are what you're listening for.
Check references for what changed, not for a character reference
A reference call that confirms someone is "great to work with" tells you almost nothing. Ask the reference a narrower question: what measurably changed in the three months after this person started, and what would have happened if they'd left after month one. The answers to those two questions separate someone who was genuinely load-bearing from someone who was pleasant to have around.
Test for judgment, not just competence
A chief of staff spends a meaningful share of their time deciding what not to do, which fires to let burn and which to run toward. In the interview, ask about a time they deliberately didn't escalate something, or chose not to fix a problem that looked urgent. The answer tells you whether they can triage independently, which is most of the job once the engagement is underway.
Confirm how confidentiality and access actually work
This role sits close to sensitive information by design: financials, personnel decisions, investor conversations. Before signing anything, confirm the practical details: a mutual NDA before any detail is shared, client-owned systems rather than the chief of staff's own tools, and a clear data-retention plan for when the engagement ends. If a candidate hasn't thought about this already, that's its own answer.
Watch how they scope the first thirty days
A strong candidate will push back on starting without a scoping conversation. Someone who agrees to "just start helping" without a structured discovery period is more likely to spend the first month reacting to whatever's loudest rather than identifying what actually matters. The discovery call itself is a useful test: does it feel like triage, or does it feel like a sales pitch?
A short list before you sign anything
- Specific, verifiable examples from past engagements, not general descriptions of the role
- References who can answer "what changed," not just "were they good to work with"
- A clear answer on confidentiality, access, and data handling before day one
- A structured discovery process, not an offer to "just start"
Seven verified reviews and published case studies are the fastest way to see this in practice rather than take it on faith. If you're ready to run a real discovery conversation, book the free 30-minute call and bring the questions above; every one of them is fair game.