A practical guide to writing Chief of Staff job descriptions that attract ex-MBB and startup operators
The Chief of Staff role has exploded in popularity over the past few years, especially at startups. But because the role varies so much from company to company, job descriptions for it tend to be all over the map—and that's costing companies great candidates.
The best Chief of Staff candidates are selective. They're often coming from consulting, banking, or other high-performing environments where they have options. A vague or poorly written job description signals that you haven't thought through the role, which makes top talent hesitant to apply.
Here's how to write a Chief of Staff job description that actually works.
Before we get into what to do, let's look at what goes wrong.
The "everything and nothing" description. These postings list every possible responsibility—strategic planning, board prep, team management, special projects, culture initiatives, exec communication—without any sense of priority. Candidates read it and have no idea what the job actually is.
The glorified EA description. Some postings describe calendar management, travel booking, and meeting logistics as the core of the role. That's an Executive Assistant, not a Chief of Staff. Conflating the two will attract the wrong candidates and turn off the right ones.
The generic consulting-speak description. Phrases like "drive strategic initiatives" and "partner cross-functionally with stakeholders" are so vague they're meaningless. Candidates have seen these phrases hundreds of times. They don't tell anyone what makes your role unique.
The laundry list of requirements. Asking for 10+ years of experience, an MBA, management consulting background, startup experience, and expertise in your specific industry eliminates most of the candidate pool—including many people who would excel in the role.
The best job descriptions start with honesty about why the role exists. What's the actual pain point? What will this person fix?
Maybe it's: "Our CEO is stretched thin across too many priorities and needs someone to take ownership of key initiatives so she can focus on fundraising and product."
Or: "We're at 80 people and growing fast. Cross-functional coordination is breaking down, and we need someone to make sure nothing falls through the cracks during this scaling phase."
Or: "We're preparing for a Series C and need someone to own the operational rigor—board prep, investor materials, company metrics—that we've been doing ad hoc."
When you're clear about the problem, candidates can self-select. The ones who get excited about your specific challenge are more likely to be a fit.
Chief of Staff roles typically fall into a few archetypes. Knowing which one you need helps you write a more focused description.
The CEO multiplier. This person operates as an extension of the CEO - attending meetings on their behalf, preparing them for key decisions, following up on action items, and generally making the CEO more effective. The role is tightly coupled to one executive.
The initiative owner. This person runs strategic projects that don't have a clear home elsewhere. They might lead a pricing overhaul, manage an office move, or build out a new operational function. The role is more autonomous and project-based.
The operating rhythm owner. This person builds and maintains the systems that keep the company running - leadership meetings, planning cycles, goal-setting frameworks, internal communications. The role is more process-oriented and persistent.
Most Chief of Staff roles are a blend, but one archetype usually dominates. Be explicit about which one you're hiring for. It'll save everyone time.
Instead of generic bullet points, describe the actual work. Here's the difference:
Vague: "Support executive team with strategic initiatives"
Specific: "Own the quarterly planning process end-to-end - designing the framework, facilitating sessions with leadership, and ensuring teams leave with clear priorities and owners"
Vague: "Prepare materials for board meetings"
Specific: "Build the board deck each quarter, working directly with the CEO and CFO to shape the narrative, pull together metrics, and anticipate investor questions"
Vague: "Drive cross-functional projects"
Specific: "Lead our expansion into a new market segment, coordinating across sales, marketing, and product to develop the GTM strategy and hit launch milestones"
Specificity does two things: it helps candidates understand what the day-to-day actually looks like, and it signals that you've thought carefully about the role.
Here's a structure that works:
About the company (2-3 sentences). What you do, your stage, and what makes this an exciting moment to join. Keep it brief - candidates can read your website for more.
Why this role exists (1 paragraph). The honest version of why you're hiring. What problem will this person solve? What does success look like in the first year?
What you'll do (5-7 bullets). The core responsibilities, written specifically. Lead with the most important ones. Avoid the temptation to list everything - prioritize.
What we're looking for (4-6 bullets). The skills, experiences, and attributes that matter most. Separate the must-haves from the nice-to-haves. Be realistic.
What we offer (3-5 bullets). Compensation range, equity, benefits, and anything else that makes the role compelling. Including comp ranges attracts more applicants and saves time.
Here's an example of how the key sections might read:
Why this role exists
We're a 60-person Series B company growing quickly, and our CEO needs a strategic partner to help scale the business. You'll work directly with her on the company's most important priorities, owning cross-functional initiatives, building operational systems, and ensuring the leadership team stays aligned as we grow. This is a high-visibility role with significant autonomy and a path to a leadership position.
What you'll do
What we're looking for
Don't conflate Chief of Staff with Business Operations. They're related but different roles. If you need someone to build long-term operational systems, you might want a Biz Ops hire instead. (We wrote about how to decide between the two.)
Don't hide the compensation. Top candidates won't waste time on a role without knowing if it's in their range. Posting comp also signals that you're a transparent, candidate-friendly company.
Don't oversell the "seat at the table." Every Chief of Staff posting promises access to the CEO and exposure to high-level decisions. That's table stakes. Focus on what's distinctive about your company and role.
Don't forget to sell the opportunity. The best candidates have choices. Tell them why this role—at this company, at this moment—is worth their time.
"Chief of Staff" is the most common title, but alternatives include "Head of CEO Office," "Strategic Projects Lead," or "Business Operations Manager." The title matters less than the substance of the role—just make sure it's searchable (candidates are looking for "Chief of Staff" roles) and doesn't over- or under-represent the seniority level.
Writing a strong job description is just the start. The best Chief of Staff candidates are often passive - they're not actively searching job boards. You'll need to source proactively, leverage your network, and consider working with a recruiter who specializes in these roles.
When you do get applicants, move quickly. Top candidates are evaluating you as much as you're evaluating them. A slow, disorganized process will cost you the best people.