CRO Job Description Template 2026: What to Include and What to Cut

I read CRO job descriptions every week. Hundreds of them. The pattern is unmistakable: most are terrible. They read like they were assembled from three different LinkedIn posts, a Gartner report, and someone's old VP Sales JD with "CRO" pasted over the title.

The result? The best candidates skip the posting entirely. They get recruited through networks, through executive search firms like Spencer Stuart and Heidrick & Struggles. The JD becomes a formality for the board deck, not a tool that actually attracts the right person.

That's a problem worth solving. I've pulled data from 1,500+ executive sales postings tracked by The CRO Report to show what the best CRO job descriptions include, what they skip, and why most companies get this wrong.

Why Most CRO Job Descriptions Fail

Three problems appear in nearly every bad CRO posting I read.

First, the scope is undefined. The posting says "own all revenue" but doesn't specify whether that includes marketing, customer success, partnerships, or just new business sales. A CRO who owns five functions needs a fundamentally different background than one who owns a sales org. When the JD doesn't clarify, strong candidates assume the company hasn't figured it out themselves. They pass.

Second, the comp is hidden. Only 54.8% of executive sales postings in our dataset disclose salary ranges. For CRO roles specifically, the number is lower. Companies justify this by saying "comp is flexible" or "depends on experience." What candidates hear: "We'll lowball you and see what sticks." In states with pay transparency laws, this also creates legal exposure.

Third, the requirements list is a wish list, not a role description. When a CRO posting demands 15+ years of experience, a specific industry background, MEDDPICC certification, experience at three different company stages, P&L ownership, board experience, and fluency in AI/ML, the company isn't describing a person. They're describing a composite of the last four CROs they interviewed. Nobody checks every box. The candidates who know their worth don't bother applying.

The Anatomy of a Strong CRO Job Description

After reviewing the top-performing CRO postings in our dataset, here's the structure that works. I'm defining "top-performing" as postings from companies that successfully hired within 90 days and where the CRO stayed for 12+ months, based on our tracking data and LinkedIn verification.

Section 1: The Opening (50-75 Words)

Start with the company's revenue stage, the size of the team the CRO will inherit, and what success looks like in year one. Skip the corporate mission statement. Skip the "we're disrupting the [industry] space" copy. Candidates want three things immediately: company stage, team size, and what's broken.

Example: "Series C SaaS company at $45M ARR hiring a CRO to own a 60-person revenue org (sales, CS, RevOps). Current challenge: 85% of revenue comes from three enterprise accounts. The CRO will diversify the pipeline and build a repeatable mid-market motion."

That's 42 words. The candidate already knows if this is their kind of problem.

Section 2: Scope of Ownership (100-150 Words)

Be explicit about what the CRO owns. In our dataset, CRO postings fall into three categories:

CRO Type	Functions Owned	Typical Stage
Sales-Focused CRO	Sales, sometimes SDR/BDR	Seed to Series B
Revenue CRO	Sales, CS, RevOps	Series B to D
Full-Stack CRO	Sales, Marketing, CS, Partnerships, RevOps	Series C+, Enterprise

Don't mix these. A Sales-Focused CRO and a Full-Stack CRO are different jobs that attract different candidates. When the JD tries to describe all three, you attract none.

Section 3: Compensation (Be Specific)

Post the range. Include base, variable structure, and equity. The CRO salary data from our tracking shows:

• Seed/Series A: $193K-$257K base, 0.5-1.5% equity
• Series B/C: $220K-$302K base, 0.25-0.75% equity
• Series C/D: $268K-$335K base, RSUs typical
• Late-Stage Private: $263K-$425K base

Posting without comp data is a signal. The candidate interprets it as: the company either doesn't know what the role is worth, or knows and doesn't want to say. Neither builds confidence.

Section 4: Reporting Structure and Decision Authority

State who the CRO reports to and what they control. This matters more than most JDs acknowledge. According to Pavilion's 2025 CRO survey, the number-one predictor of CRO satisfaction is clarity on decision-making authority before accepting the role.

Specify: Does the CRO report to the CEO or the board? Do they have hiring/firing authority for their org? Do they control the budget, or does the CFO approve headcount? Can they restructure comp plans without board approval?

These aren't details to save for the interview process. The best candidates want them in the JD because it signals organizational maturity.

Section 5: Requirements (Keep It Tight)

Maximum five requirements. I mean it. Every requirement beyond five reduces your qualified applicant pool without improving hire quality. Here's what works:

1. Years of experience at the relevant company stage (not total years)
2. Team size managed (a range, not an exact number)
3. Revenue scale they've operated at
4. One specific skill that matters for this role (e.g., "built an outbound motion" or "managed a channel program")
5. One methodology or framework preference (optional, and frame it as preferred, not required)

Drop the rest. "Strong communication skills" is filler. "Strategic thinker" means nothing. "Data-driven" appears in 44% of our postings and differentiates nothing.

Section 6: First-Year Expectations

This is where most JDs fall apart. They either skip it entirely or list vague goals like "accelerate revenue growth." Strong postings break expectations into 30/60/90/365 milestones.

The first 90 days data from our VP Sales research applies here too. Companies that set clear first-year expectations in the JD see lower CRO turnover. The data isn't conclusive on causation, but the correlation is consistent.

The Template

Here's a CRO job description template built from the best postings in our dataset. Modify it for your company. Don't add to it.

That's it. Under 400 words in the template. Your final version should land between 500 and 800 words total. Anything longer and you're writing for the board, not for the candidate.

What to Cut: The Red Flag Phrases

These phrases appear in hundreds of CRO postings in our dataset. Every one of them either means nothing or actively repels qualified candidates.

Red Flag Phrase	Frequency in Data	What Candidates Hear
"Fast-paced environment"	248 postings	Understaffed, chaotic, no process
"Competitive compensation"	198 postings	Below market, won't disclose
"Wear many hats"	87 postings	No support staff, IC work expected
"Rockstar" / "Ninja" / "Guru"	34 postings	Immature leadership team
"Must be comfortable with ambiguity"	112 postings	No strategy, figure it out yourself

The "fast-paced environment" problem is particularly bad at the CRO level. A CRO candidate with 15 years of sales leadership experience has worked in fast-paced environments their entire career. Saying it in the JD adds zero information. What it does communicate is that the company thinks pace is a selling point rather than a baseline expectation.

Methodology and Tool Requirements: What Actually Matters

Our data shows that sales methodology adoption varies significantly by company stage and vertical. Here's what CRO postings mention most frequently:

• Consultative Selling: 172 mentions across all executive postings (13.2%)
• MEDDPICC/MEDDIC: 117 mentions (9.0%)
• Challenger Sale: 42 mentions (3.2%)
• Solution Selling: 38 mentions (2.9%)

For a CRO JD, methodology requirements should be preferences, not gates. A CRO who ran MEDDPICC at their last company can implement it at yours. A CRO who ran Challenger can evaluate whether MEDDPICC is the right fit. The methodology matters less than the ability to choose and execute one.

Tool requirements are even less useful. Yes, Salesforce appears in 180 postings. But requiring "Salesforce expertise" in a CRO JD is like requiring a CEO to know how to use Excel. It's assumed. If you're hiring a CRO to evaluate whether you should migrate from HubSpot to Salesforce, say that. Otherwise, drop the tool list.

The Industry-Specific Angle

Should you require industry experience? It depends on how regulated your vertical is.

In healthcare, government, and financial services, the buying process is so different from standard SaaS that industry experience matters. Procurement cycles, compliance requirements, and buyer relationships in these verticals are not transferable from general B2B experience.

In general SaaS, manufacturing, and e-commerce? Industry experience is a nice-to-have, not a requirement. A CRO who scaled a $20M ARR SaaS company in HR tech can do it in MarTech. The GTM motion is the same. The logos change.

The mistake most JDs make is requiring "5+ years in [specific vertical]" for a role where the sales motion is generic. That single requirement eliminates 80% of your candidate pool for a filter that doesn't predict success.

Posting Strategy: Where and How

CROs don't browse Indeed. The distribution strategy for a CRO posting matters as much as the content.

• Executive search firms: Spencer Stuart, Bain Executive Search, and SaaStr-connected firms handle most C-level sales placements. Budget $80K-$150K for a retained search. Contingency search at this level is rare and signals budget constraints to candidates.
• LinkedIn (paid): The posting itself won't attract passive candidates. But running it as a promoted post through the CEO's or board member's personal profile can. CROs respond to people, not job boards.
• Pavilion community: Pavilion (formerly Revenue Collective) has a strong CRO network. Their job board reaches candidates who are employed but open.
• The CRO Report: Our job board tracks executive sales roles weekly and sends them to a targeted subscriber base of revenue leaders.

Don't post a CRO role on general job boards without a parallel outbound effort. The conversion rate on inbound applications for C-level roles is under 2%. The hire almost always comes from a direct referral or executive search.

Common Mistakes by Company Stage

Seed/Series A

The biggest mistake: using the CRO title when you need a VP Sales. If the company is under $5M ARR with fewer than 20 employees, the "CRO" will spend 70% of their time selling, not leading. Title the role honestly. The candidates who want to build from scratch aren't offended by a VP Sales title. The candidates who want the CRO title at this stage may be the wrong hire.

Series B/C

The mistake here is writing a JD for where the company wants to be, not where it is. "Must have managed 100+ person orgs" for a company with a 15-person sales team means you're hiring for a job that won't exist for two years. The CRO who managed 100 people will be bored and frustrated managing 15. Hire for the next 12-18 months, not the next five years.

Enterprise/Public

Enterprise CRO JDs tend to be the most bloated. They go through legal, HR, the CMO, the CFO, and sometimes the outgoing CRO. By the time it's published, it reads like a compliance document. The fix: one person writes the JD. The CEO. Everyone else gets to comment, not co-author.

The Compensation Disclosure Debate

I'll be direct: disclose the compensation range. Here's why it matters specifically for CRO roles.

CRO candidates are evaluating multiple opportunities simultaneously. They are having conversations with executive search firms who know what every other company is paying. When your posting says "competitive compensation" and the Spencer Stuart recruiter tells them the other company is paying $280K-$350K base, your posting loses before the first conversation.

The equity compensation data is equally important to disclose. At the CRO level, the equity package can double total comp. Candidates won't invest time in your process without knowing the equity structure.

In our data, postings that disclose compensation attract candidates 18 days faster (median time to first qualified applicant) than those that don't. That's not a small difference for a role where every week without a CRO costs the company pipeline.