.avif)
.avif)
I've watched a lot of sharp operators lose Chief of Staff interviews they should have won. Almost every time, it traced back to how they talked about their own work. They described the role the way the job description reads, and the job description sells it short.
Most Chief of Staff postings reduce the job to a list of tasks. Run the exec meeting. Keep projects on track. Manage the all hands. Every line is true, and every line understates what it takes to do it well. Candidates absorb the list and interview to it, walking in determined to prove they're organized and responsive. The operators who walk out with strong offers spend their time somewhere else.
The work the job description leaves out
The real work of a Chief of Staff, even early in the arc, is running the operating cadence of a team or a company. You own the rhythm of the business: the All Hands, the board prep, the leadership meetings that have to end in decisions. You keep teams aligned when their priorities pull apart. You own the communication that keeps everyone moving in the same direction. You carry the projects that matter most, the ones that would quietly stall without someone holding them accountable. These are the things that matter most to your principal. The job description gives you almost none of the language for that work.
COSN's leveling framework maps the full arc, and it's worth being precise about what separates the levels. A more junior Chief of Staff might not be the person their CEO reaches for on the hardest strategic calls. That comes later, with autonomy and scope. Junior here is a statement about how much direction you take and the scale you operate at. You run the operating machinery of the organization with closer guidance and smaller stakes, and you grow into larger, higher-stakes work over time. What you own is real at every level. The interview is where you show which part of that arc you can credibly hold today.
A hiring principal, a CEO or founder, feels the difference in about ten minutes. They can't always name it. But they know whether they're talking to someone who will take work off their plate or someone who will take problems off their mind. Those are different people, and the interview is built, often unconsciously, to tell them apart.
What they're actually testing
When a principal says "walk me through a hard week," they want to hear how you think when the situation is ambiguous and the stakes are real. They're listening for whether you saw the problem before it reached them, whether you turned a mess into a decision they could actually make, and whether you can be trusted in the room when the conversation gets uncomfortable.
A few things a good hiring manager or principal should be listening for:
- Judgment when the information is incomplete.
- The ability to turn a messy situation into a decision the principal can act on.
- Trust with the parts of the job that are hard and unglamorous.
Job descriptions rarely mention any of this, which is exactly why the interview carries so much weight.
The playbook
Talk about the cadence you owned and what it produced. Every story has a version that sounds like task management and a version that shows judgment. "I ran the offsite" is the first one. "The offsite was drifting toward the wrong three priorities, so I reworked the agenda and the leadership team left with real decisions" is the second. Prepare three stories where your judgment changed the outcome, and tell them at that altitude.
Name the real problem before they do. In the interview you're being auditioned for how you'll operate once you're inside, so start operating. When they describe the role, say back the gap you actually hear. Something like, "It sounds like decisions get made in hallways and don't stick." If you're right, you've shown them the work you'll do. If you're close, you've shown them how you think.
Ask questions that surface the real scope. Who does the principal rely on today for the judgment calls, and where does that break down? What's a decision they keep having to revisit? A year from now, if this is working, what's different about how they spend their time? Questions like these tell you whether the seat is real or decorative, and they signal that you already understand the difference.
Let the tactical work be assumed. You'll run the meeting and keep the follow-ups under control, and everyone knows it. Spend the interview proving it and you define yourself by the mechanics of the cadence rather than its purpose. Give it a sentence and move on to the judgment.
The level you signal is the level you get
The altitude of the role gets set in the interview as much as in the offer. Present yourself as someone who executes defined tasks well, and defined tasks are what you'll be handed. Present yourself as someone who owns the operating cadence and the decisions inside it, and that's the scope you'll be trusted with. The title tends to catch up to the altitude you claim.
The market still uses "Chief of Staff" loosely, and some of these roles are genuinely scoped small. You can't always change that from the outside. What you can do is decide, before you walk in, which part of the arc you're ready to own, and describe your work so the person across the table can see it clearly.
Looking for your next Chief of Staff role?
Join the our Talent Network and don't forget to subscribe to the CoS Network Job Board for a weekly digest of the top Operators roles.
