I've read dozens of Chief of Staff job descriptions while helping founders hire for their Founder's Offices. The pattern is consistent and consistently wrong: either the JD lists tasks an EA should own (manage the calendar, handle travel, coordinate meetings), or it floats into vague MBA-speak ("serve as a thought partner to the CEO on strategic priorities").
Neither is useful for a hiring manager. Neither attracts the right candidate. And neither gives the eventual hire a clear picture of what success looks like.
Here's the version I actually recommend to founders — grounded in what the role needs to do at a 30–200 person startup.
What a CoS Actually Does (At a Growth-Stage Startup)
Forget Fortune 500. At a 30–200 person company, the Chief of Staff operates closest to the founder and covers ground that no other role owns cleanly. In practice, this means:
- Meeting rhythm and follow-through. Running the weekly leadership sync, tracking action items, and ensuring decisions made in meetings actually happen. The CoS is the membrane between conversation and execution.
- Founder communications. Board decks, investor updates, all-hands content, customer escalation responses — anything written in the founder's voice but too important to be written at 1am.
- Cross-functional project ownership. New market entry, repositioning, strategic partnerships, key hiring sprints — initiatives with no natural functional home but with high founder priority.
- Strategic research and decision prep. The CoS produces the 2-page memo, not the 30-page doc. Options, recommendation, trade-offs. Founder reads it, decides faster.
- Board and investor ops. Prep, materials, follow-up, relationship tracking. Not just logistics — the CoS should understand the subtext of every board conversation.
- Internal culture and comms. Town hall agendas, pulse surveys, team rituals, recognition cadences. The CoS often becomes the internal face of the founder's values.
The Chief of Staff converts founder bandwidth from doing into directing. Everything else flows from that.
The JD Template
Copy and adapt this for your actual hire. Remove sections that don't apply and add your company-specific context.
About the Role
We're looking for a Chief of Staff to work directly with our CEO. This is a high-trust, high-scope role for someone who is energised by ambiguity, owns outcomes (not just tasks), and wants to understand every corner of a scaling business. You will be the connective tissue between the CEO's vision and the company's execution.
What You'll Do
- Own the weekly leadership operating rhythm — agenda prep, facilitation, action tracking, close-out
- Write the CEO's most important documents: board decks, investor updates, all-hands narratives, key external communications
- Lead cross-functional projects that have no other home — from market expansion research to key partnership negotiations
- Produce decision memos that give the CEO structured options with a recommended path forward
- Manage board and investor relationships: materials, scheduling, follow-up, relationship tracking
- Represent the CEO in internal and external conversations where context and trust are more valuable than hierarchy
- Identify bottlenecks in the company's operating system and fix them or flag them — whichever is faster
What You Won't Do
- You won't manage the CEO's calendar or travel (that's our EA's job)
- You won't be a generalist coordinator — you'll own specific outcomes, not just coordinate activities
- You won't build a large team — this is an influence role, not a headcount role
What We're Looking For
- 3–6 years in consulting, investment banking, strategy at a venture-backed startup, or prior CoS/FO experience
- Exceptional written communication — you can turn a 90-minute meeting into a clear 1-page memo
- Comfort operating without a playbook — you figure out the right approach and you ship it
- High influence-without-authority instinct — you get things done through people who don't report to you
- Discretion — you will know things other people in the company don't; that's a responsibility, not a status signal
Nice to Have
- Prior experience in your industry vertical
- Familiarity with your primary tools (Notion, Salesforce, Jira, etc.)
- Board-level communication experience
- Series A–C startup experience specifically
KPIs for a Chief of Staff
This is the section most hiring managers skip. It's also the one that will save you from a bad hire at the 90-day mark. CoS KPIs are hard to define — the role is inherently qualitative — but these are the four I've found most useful:
Chief of Staff KPIs
Meeting-to-action close rate
What % of action items from weekly leadership syncs are closed by the next meeting? A healthy CoS should push this above 80% within 60 days.
Time-to-decision on founder decisions
How long does it take from "we need to decide X" to a final decision? Track before and after the CoS starts. Good CoS hires cut this by 30–50%.
Projects stuck >2 weeks
How many strategic projects are stalled with no owner and no progress? The CoS's job is to drive this to zero — either by owning it themselves or escalating clearly.
Founder calendar reclaimed
Hours per week the founder spent on low-leverage work before vs. after. Track this at 30-day intervals. If the CoS is working, the founder's reactive time drops and strategic time rises.
5 Interview Questions (and What to Listen For)
Skip case studies and hypotheticals. These five questions surface real judgment quickly.
-
"Tell me about a project you owned where you had no direct authority over the people you needed."
Listen for: specific influence tactics, relationship-building instincts, and whether they actually got the outcome or just facilitated conversation.
-
"Walk me through the most complex document you've written. Who was the audience and what decision did it drive?"
Listen for: structured thinking, audience awareness, ability to simplify complexity. Ask for a sample.
-
"Give me an example of when you disagreed with a senior decision-maker and how you handled it."
Listen for: courage paired with deference — they pushed back, did it professionally, and ultimately supported the final call.
-
"What does a good week look like for you in this role, and a bad one?"
Listen for: self-awareness about the role's ambiguity, realistic expectations, comfort with context-switching. Red flag: a bad week is "when I don't have clear tasks."
-
"What's something you've observed in a leadership team that was clearly broken, and what did you do about it?"
Listen for: pattern recognition, willingness to name uncomfortable truths, and action vs. avoidance.
Red Flags in the Hiring Process
These aren't disqualifiers on their own, but each one should give you pause:
- Overly focused on title progression. The CoS role is a trust-based operating role, not a stepping stone the candidate is clearly planning to exit in 12 months. If their first question is "what does the path to VP look like," that's worth probing.
- No examples of influencing without authority. If every project story involves direct reports, they may struggle in a role where they have almost none.
- Wants to build a team immediately. The CoS role derives power from proximity and trust, not headcount. Candidates who lead with "what team would I have" misunderstand the role.
- No comfort with ambiguity. If they need a detailed job description before they'll commit, the first week will be rough. The role rewrites itself constantly.
- Needs explicit instructions for everything. The CoS should be filling gaps nobody asked them to fill. If they're waiting for direction, they're in the wrong seat.
If you can't name three outcomes you want this hire to own in week one, you're not ready to hire a CoS yet. The role only works when the founder has clarity about what they want to delegate. Coach yourself first.
Compensation Range
These are US-market benchmarks as of 2026. India/APAC comps run roughly 40–60% lower for equivalent stage:
The CoS almost always reports directly to the CEO. If you're routing this hire through the COO or CPO, reconsider the scope — you may be hiring a Chief of Staff to someone other than the person who needs one.